the URL for the wiki is http://datafedwiki.wustl.edu and the pages that
have the problems are Consoles, 2006-09-22:Wiki Use Discussion,
2007-02-24: Atmospheric Aerosols - Tools, Methods, and 2006-03-07: netCDF,
CF, ncML, GML, WCS.
The error is not in rss_fetch, it is actually in rss_parse still on line 404.
Thanks,
Mark
> Arthur wrote: ... So you have Apache,
> PHP, MySQL and MediaWiki working;
> what are you having problems with?
Peter Blaise responds: I'm having problems finding any leads on a basic
wiki setup-and-configure instruction manual.
Okay, the word "basic" may be is presumptive and ambiguous.
So, make that "Any leads on a basic wiki setup-and-configure instruction
manual that is accurate (complete, contemporaneous), and has
installation checks and troubleshooting."
Yes, I'm familiar with
http://www.mediawiki.org/wiki/Manual:Installation
which is Linux only, and I'm familiar with
http://www.mediawiki.org/wiki/Manual:Installing_MediaWiki_on_Windows_XP_
-_MediaWiki_1.9.2
which is Windows and IIS not Windows and Apache, and
http://www.mediawiki.org/wiki/Manual:Simple_Windows_Apache_Installation
for Windows and Apache, but seems not up to date and overly brief.
None of our shared MediaWiki resources have installation checks and
troubleshooting.
We seem to be handling troubleshooting on a case by case bases as
presented.
So that's why I asked:
"Any leads on a basic wiki setup-and-configure instruction manual?"
So far, the answer is "no", but if I have specific questions and
problems to overcome trying to install MediaWiki, there seem to be many
willing to chat.
Thanks.
- Peter Blaise
I'm writing a ArticleAfterFetchContent hook:
$wgHooks['ArticleAfterFetchContent'][] = 'myArticleAfterFetchContent';
function myArticleAfterFetchContent (&$article) { ... }
Inside myArticleAfterFetchContent, how do I tell if the user is
in edit/view source mode?
A hacky way that almost works: if (isset($article->mMinorEdit)) {...}
This works fine if the user has permission to edit, but not when I'm
using the "view source" hack (user who can't edit can still view the
source):
$wgHooks['userCan'][] = 'fnMyUserCan';
function fnMyUserCan ($title, $user, $action, $result) {
if (($action == 'edit') && $user->isAnon()) {$result = false;}
}
What's the correct way of telling if a user is edit mode, even if he's
viewing the source? I don't want my hook to run in this case, because
I want people to see/edit what's stored in the MySQL backend *before*
my hook processes it.
--
We're just a Bunch Of Regular Guys, a collective group that's trying
to understand and assimilate technology. We feel that resistance to
new ideas and technology is unwise and ultimately futile.
Hi guys
I am wondering if it is possible to pass PHP variables into the
mediawiki extension Parser.
i.e. instead of having a static template, I would like to somehow use
a couple variables from a MySQL table.
The extension is availabe from here
Thanks
> Platonides wrote: I'm sure this list is full
> of people willing to install MediaWiki on a
> foreign machine, and document every
> screenshot... for the right price ;)
Prove it - just like your open source compatriots, document your success
in public view, and for MediaWiki, that's MediaWiki.org, and then also
offer to sell your proven-valuable support to anyone who'd prefer to
have you do it for them.
Otherwise, what are you doing on an open source support forum?
- Peter Blaise
To follow up on my own post of a month ago: I just build Mediawiki in a
Solaris 11 zone, with no real problems. I built the SAMP server using this
page from Neal Pollack of Sun:
http://www.sun.com/bigadmin/features/articles/samp_setup.html
This used Solaris Apache, mysql5 from blastwave.org, and php5 from php.net.
Once PHP and mysql were talking, MediaWiki worked without any
modifications.
I started with a "small" zone with a local loopback-mounted /usr/local and
shared /usr, /var, and /opt. I built SAMP in the global zone, but had to
rebuild libxml2 and reinstall PHP on the client zone to get all the right
libraries in the right places. Reinstalled PHP the quick-n-dirty way with
gmake -i install, to get the right things written to /usr/local . Of course
PHP was otherwise identical in the global and client zones. I would not be
comfortable doing this on a customer-facing production server so I am going
to rethink this.
Next up: security tightening, and probably php cacheing.
Hello,
I'd like to extend MediaWiki to work with the Markdown Extra syntax (
http://www.michelf.com/projects/php-markdown/ ).
Two questions:
1. Does anyone know of anyone else who has already started work on something
like this? (I did some searching, but didn't find anything.)
2. Any ideas on how to implement this?
Because Markdown Extra is written in PHP, you'd think it would be pretty
easy to bolt this in. The tricky part is that I'd like be able to just
write pages in Markdown Extra syntax but still have double brackets create
new pages. One idea is to write an extension and put the Markdown Extra
stuff between XML-style tags: <markdown> .... </markdown>. But I think that
wouldn't allow the creation of new wikipage links inside those tags. So
maybe it would make sense to write something that would convert the
mediawiki text into markdown at the time of editing?
Thanks,
Simon
> Daniel wrote: ... I did this [install
> MediaWiki on Windows]with the
> EXISTING notes on MediaWiki.org.
> I didn't do anything out of the
> ordinary. If you are finding this
> hard, you should hire an expert
> to help you ... I have done 5
> MediaWiki installations, on the
> same PC and on different PCs,
> using nothing but the instructions.
> If you are finding this too hard,
> I recommend you hire an expert.
Peter Blaise responds:
Daniel,
Please try LESS work and instead of arguing and telling me to hire "an
expert" (as if I've had much luck finding any who are wiling to prove
their value here! And, without a reference to a specific expert with
which you've had success, well then, what's a referral good for
anyway?!?), why not just respond with a LINK as was missing from your
original posts, and was asked for?
A link, man, a LINK?!? That is all I ask for!
And when you Googled to resolve a conflict, since that was a departure
from the "official instructions" can you help out with a link there,
too?
A link, man, a LINK - that is all I ask for!
Please, Daniel. Way less work has been asked of you than you proffered
here! No explanations or retributions needed. Save your energies, man!
Instead, how about simply sharing the 2 links YOU used to accomplish
your success?
Thanks.
-- Peter Blaise
------------------------------
> Kasimir wrote: ... do not ask people for
> their success stories. They take a *very*
> long time to write up ... If something is
> going to take a long time ... I just don't
> feel like doing it ... There is no way that
> I am going to spend a day writing up
> everything that I did ... you do not
> understand the fundamental workings
> of the code ... Play around with simple
> projects until you understand how code
> and sysadmining works ... you should
> first become very comfortable with the
> basics, and with the ideas behind how
> code functions, before jumping into a
> project ... any amount of documentation
> about MediaWiki would not help you at
> this point ... step back a bit and just
> understand the basics ...
Peter Blaise responds:
Thanks ... I think.
I am playing with the basics.
I am playing around.
I am exploring what happens when I install and try different choices for
each component. Over and over.
I thought maybe someone in or using MediaWiki might have already
confirmed a decision tree that best supports MediaWiki so that MediaWiki
has the best chance for success in the end user's hands - with official
guidance: "these specific decision trees work for us". I was wrong -
oh, so wrong! And even asking for such - wrong again! Shame on me!
:-(
While I understand why some people do not want to share their success
stories, that is still all I ask for, and all I can offer (failure
stories, too)!
I'll revisit http://www.wikipedia.org/ and http://www.mediawiki.org/ and
see what they're made of ... OH, they're made of people contributing
contents that makes sense to them, and some of it appears to have taken
a long, long, *very* long time to master and share! Oh, my! Why on
earth would they do that?!? =8^o
Kasimir, I think you are insincere. You say it would take a long time,
but you are only speculating, not speaking from experience. If you were
speaking from experience, you'd have already done the documentation and
known exactly how long it took, and then you'd be able to quickly share
your documentation regardless. You say it would be useless to you or
anyone else but again you are speculating. I value it. I imagine you
and others would too, especially if you shared it on MediaWIki.org.
My experience? I see automotive web pages and high-fidelity sound web
pages and even PC-building web pages (and sewing and boating and health
and home building and so on) that document to the minutest detail how to
accomplish success in creating something beloved by their creators.
What I ask for is nothing new or unprecedented. MediaWiki apparently
has yet to garner such reverence and joy, at least on this list,
apparently. MediaWiki is supposedly open source ... well?
-- Peter Blaise
------------------------------
> Ian wrote: ... I followed the instructions.
... [link?!?]
> It worked. If you want a keystroke-by-
> keystroke log of what I did, well, I didn't
> create one. If you want me to go through
> the whole process again and record
> everything, I can do that, but it would
> take solid days of work to cover the stuff
> you want, and that is *way* more effort
> than I am going to donate to the USPTO
> for free. So, do you have a budget to pay
> for this kind of support?
Peter Blaise responds:
... oh, and you've proven yourself soooo willing to earn it! ;-)
I KNOW how long it takes. In the earlier example I quoted of my own
experience, it took approximately 100 times longer to accurately
document any task than it took to perform the task itself in the first
place. This is no news. I know that, though what I am asking for is
simple to ask for, it is also very difficult and time consuming to
execute authoritatively.
However, I am not asking you or anybody to support the USPTO, I'm asking
you to support MediaWiki. You don't have to. Nobody does.
-- Peter Blaise
PS - The US Trademark Office, by the way is paying-customer-driven,
law-driven, and public (no tax-payer revenues here!). You're welcome to
anything we create - none of our contractors own anything they design
for us or for our customers! The US Patent Office (unrelated to the US
Trademark Office, really) may be secret to protect patent applicants, I
dunno nor care. Trademark applications and processes are public record
from day one. Private individuals and companies may own the rights to
their programming, and be as secretive as they wanna be. I do not
control any moneys (or even admin rights) around here, that's why I
built our first MediaWiki prototype on my own USB drive! But, as I see
it, the only ones spending inordinate time and effort to avoid spending
inordinate time and effort are ...
Thanks, i will look in to setting up postfix.> Date: Sun, 27 May 2007 12:57:46 -0700> From: rex(a)nosyntax.com> To: mediawiki-l(a)lists.wikimedia.org> Subject: Re: [Mediawiki-l] Email and MediaWiki> > Robert Leverington <lcarsdata(a)googlemail.com> [2007-05-27 11:03]:> > If your server has sendmail installed (most do) there should not be a problem.> > The default MTA for Ubuntu server is Postfix, which should be fine for> Mike's situation.> > -rex> -- > Common sense is the collection of prejudices acquired by age eighteen.> -- Albert Einstein> > > _______________________________________________> MediaWiki-l mailing list> MediaWiki-l(a)lists.wikimedia.org> http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
_________________________________________________________________
Try Live.com: where your online world comes together - with news, sports, weather, and much more.
http://www.live.com/getstarted
I would just like to clarify that i need an external email server to be able to use the email functionality of MediaWiki. The reason that I ask is that I am sure that I have read somewhere that MediaWiki (once up a time) had email functionality built in?
Anyway I am in the process of transferring my Wiki from WAMP on Windows to Ubuntu Server. On Ubuntu I am up to the point where I can open up a browser and point it to my "server" and get to the setup page of the Wiki.
Assuming that I need to install some kind of SMTP server on Ubuntu I would like to know what you guys recommend? I do not need anything that fancy, just something that will send out emails to Wiki users - when a new page is created / updated, account created / password changed, for example.
If anyone has any recommendations in terms of overhead / performance / security etc I would be most grateful. My Wiki is used at work for 10 - 15 users.
Many thanks
Mike
_________________________________________________________________
Try Live.com: where your online world comes together - with news, sports, weather, and much more.
http://www.live.com/getstarted