I'm having a problem with categories that are template-updated. The templates are set to add a category at a certain number of days after the template on the page is updated, which should then be picked up by DPL to keep a "to-do list" up to date (it's supposed to track farm chores), but the category isn't "visible" to the DPL unless the page the template is used on recieves a null edit. Is there some way to force the categories to update as soon as the template kicks in? Having to null-edit sort of defeats the purpose (it's supposed to remind you to check for weeds/germination/diseases or do any number of other jobs, sometimes months after the reminder was set).
We ran into the same problem on en.wikiversity a few months ago when trying to do a category update for the "Bloom Clock", which also uses a type of DPL.
Any ideas would be greatly appreciated!
-Johnny.
Hello everybody,
I added a mediawiki installation to my debian machine on the following
page: http://www.dejongehondenvanheemskerk.nl/mediawiki/
The wikipage is part of basic website for a new dutch thinktank that
helps our government to use open standards and open source technologies:
http://www.dejongehondenvanheemskerk.nl/
I would like to have a nice CSS file that "tweaks" the mediawiki looks to
make it fit better with the main website.
Would somebody be willing to spent a little time on this and receive some
money or some other satisfying resolution? The result of the CSS does not
have to be perfect, it just have to look more integrated with the main site.
There are several suggestions how we could do this.
1) Just change the current CSS and leave the mediawiki on the same place,
change colors, images, backgrounds etcetera, This is the easies way I can
think of.
2) Or something that I would find really great, is to integrate the wiki
with the main site so the large top navigation links stay intact, and
inside the wiki page make the special wiki navigation, view and other
navigators appears.
It is not the allowed to change the php, because the wiki is on an good
maintained server that fully uses the Debian update systems. The new CSS
must also be an cascaded CSS of the standard current used one. The new
CSS must be CC-by-sa licensed or fully given to me so I may choice the
copyleft.
If you want, you can get a subversion account to get access to the html
and CSS of the main websites and all our other files, else use the public
part of the svn to work on the new CSS file.
Would somebody be willing to help out, I got no time doing the work
myself but I can coach and review when you want to do the task.
Would something like 50 euro for a nice 1) basic CSS and 100 euro for the
2) integrated CSS motivate somebody the make the CSS?
The payment can be done with PayPal or with an IBAN: or BIC: number.
Contact me in any way you prefer,
Thanks in advance,
Best regards,
Jelle de Jong
De Jonge Honden van Heemskerk (JHvH)
http://www.dejongehondenvanheemskerk.nl/
Welcome to mediawiki-l. This mailing list exists for discussion and questions
about the MediaWiki software[0]. Important MediaWiki-related announcements
(such as new versions) are also posted to this list.
Other resources.
If you only wish to receive announcements, you should subscribe to
mediawiki-announce[1] instead.
MediaWiki development discussion, and all Wikimedia technical questions, should
be directed to the wikitech-l[2] mailing list.
Several other MediaWiki-related lists exist:
- mediawiki-api[5] for API discussions,
- mediawiki-enterprise[6] for discussion of MediaWiki in the enterprise,
- mediawiki-cvs[7] for notification of commits to the Subversion repository,
- mediawiki-i18n[8] for discussion of MediaWiki internationalisation support,
- wikibugs-l[9] for notification of changes to the bug tracker.
List administrivia (unsubscribing, list archives).
To unsubscribe from this mailing list, visit [12]. Archives of previous postings
can be found at [3].
This list is also gatewayed to the Gmane NNTP server[4], which you can use to
read and post to the list.
Posting to the list.
Before posting to this list, please read the MediaWiki FAQ[10]. Many common
questions are answered here. You may also search the list archives to see if
your question has been asked before.
Please try to ask your question in a way that enables people to answer you.
Provide all relevant details, explain your problem clearly, etc. You may
wish to read [13], which explains how to ask questions well.
To post to the list, send mail to <mediawiki-l(a)lists.wikimedia.org>. This is a
public list, so you should not include confidential information in mails you
send.
When replying to an existing thread, use the "Reply" or "Followup" feature of
your mail client, so that clients that understand threading can sort your
message properly. When quoting other messages, please use the "inline" quoting
style[11], for clarity.
When creating a new thread, do not reply to an existing message and change the
subject. This will confuse peoples' mail readers, and will result in fewer
people reading your mail. Instead, compose a new message for your post.
Messages posted to the list have the "Reply-To" header set to the mailing list,
which means that by default, replies will go to the entire list. If you are
posting a reply which is only interesting to the original poster, and not the
list in general, you should change the reply to only go to that person. This
avoids cluttering the list with irrelevant traffic.
About this message.
This message is posted to the list once per week by <river(a)wikimedia.org>.
Please contact me if you have any questions or concerns about this mailing.
References.
[0] http://www.mediawiki.org/
[1] http://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
[2] http://lists.wikimedia.org/mailman/listinfo/wikitech-l
[3] http://lists.wikimedia.org/pipermail/mediawiki-l/
[4] http://dir.gmane.org/gmane.org.wikimedia.mediawiki
[5] http://lists.wikimedia.org/mailman/listinfo/mediawiki-api
[6] http://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise
[7] http://lists.wikimedia.org/mailman/listinfo/mediawiki-cvs
[8] http://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[9] http://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[10] http://www.mediawiki.org/wiki/FAQ
[11] http://en.wikipedia.org/wiki/Posting_style#Inline_replying
[12] http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
[13] http://www.catb.org/~esr/faqs/smart-questions.html
I had a local Mediawiki 1.7.1 installation on my client Debian 4.0
Etch computer. I bought a new computer and run Mediawiki 1.12.0 and
Debian 5.0 Lenny on it. I've mounted the old harddrive on the new
computer. What would be the easiest way to import all the old articles
into my new installation, with preserved history? It's about 50
articles.
--
Regards,
Thomas Anderson
"Quidquid latine dictum sit, altum sonatur"
The Wikipedia Usability Initiative has extended the application deadline
for the Software Developer position till May 30th. We are recruiting
two candidates for this position. Both local applicants to the San
Francisco Bay Area and remote applicants are encouraged to apply.
Please help spread the word.
http://wikimediafoundation.org/wiki/Job_openings/Software_Developer_(projec…
Naoko Komura
Program Manager
Wikipedia Usability Initiative
Wikimedia Foundation
-----
Job Title
Software Developer
Employment Duration
June 1, 2009 to April 16, 2010
About the Wikipedia Usability Initiative
The Wikipedia Usability Initiative was realized by a grant from the
U.S.-based Stanton Foundation. The goal of this initiative is to
measurably increase the usability of Wikipedia for new contributors by
improving the underlying software on the basis of user behavioral
studies, thereby reducing barriers to public participation. This
position is part of the program team for the initiative.
For more information, please see the press release.
http://wikimediafoundation.org/wiki/Press_releases/Wikipedia_to_become_more…
Job Purpose
The core responsibility of this position is to design, develop, test and
deploy new features and improvements of the MediaWiki software for the
the Wikipedia usability initiative by working closely with the
interaction designer and peer developers of MediaWiki.
Reports to
Program Manager
Job Summary
*Propose software design solutions and obtain consensus from senior and
peer tech teams
*Create implementation prototypes based on design concepts
*Develop, test, and deploy new features and improvements to the
MediaWiki core and to MediaWiki extensions
*Collaborate in designing and implementing QA processes including
multi-lingual and performance tests
*Work closely with operations staff to ensure proper integration with
testing and production systems
Required Qualifications
*Computer Science degree or equivalent work experience
*5+ years experience as a software developer is required
*Experience with PHP development is required
*Extensive experience with AJAX/HTML/CSS is required
*Experience with cross-browser compatibility testing is required
*Experience with security implications of JavaScript/PHP software is
required
*Experience with LAMP is a major plus
*Experience with testing and analyzing usability and accessibility is a
major plus
*Experience with MediaWiki is a major plus
*An understanding of internationalizing and localizing software products
a major plus
*Any other free/open software development experience highly welcome
*Comfortable in a highly collaborative, consensus-oriented environment
*Experience with wikis and participatory production environments is a plus
*Understanding of the free culture movement is a plus
*The ideal candidate will be creative, highly motivated, and able to
operate effectively in multiple cultural and language contexts
Salary
The salary is in the range of $75,000 to $85,000 plus benefits,
commensurate with experience.
This position will be filled in June 2009. Due to the volume of
responses that we anticipate we will not reply to all applications, so
please do not interpret our silence as a lack of interest.
Based in San Francisco, CA., but remote candidates will be considered.
--
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
What is it about <code style='white-space:pre'><nowiki> that looks fine
with stylesheets, but melts into a puddle of text without them?: Can't
there be anything done with http://lyricwiki.org/LyricWiki:SOAP/client
so it still looks good in w3m or lynx, or Firefox's View>Page Style>No
style, without the author having to recode the embedded <pre>'s?
Hi Folks,
After many many months of stable operation, on going to some of the image
pages on my site, I am getting the following error thrown under 1.10.1:
[11-May-2009 04:06:34] PHP Fatal error: Allowed memory size of 50331648
bytes exhausted (tried to allocate 4416 bytes) in [snip]
/wiki/includes/media/Bitmap.php on line 168
I have done some searching on the web and a couple of other folks have
encountered this and have raised the amount of memory PHP is allowed. This
doesn't solve the issue for me however. I have looked at the images in
question and they are not overly large (one is 700KB another 500KB) and in
.jpg format.
Has anyone run into this and found a solution?
Thanks,
Tim
I'd like to announce the first release of EzMwLucene. This project
provides a simplified Lucene search to Mediawiki. It is designed to be
easy to install, configure, and run. It provides real-time, multiple
field indexing and searching as well as text indexing of standard
attachment types (pdf, xls, doc, ppt, vsd). The server is a self
contained Java application (no application server needed), and the
client portion is a standard Mediawiki extension. It is currently in
production on an internal site with over 1000 users running on Mediawiki
1.13.
https://sourceforge.net/projects/ezmwlucene/
I welcome all feedback: questions, suggestions and offers to help
improve it!
