One of the main complaints we get from our MW users is about file handling.
The comparison to Sharepoint often comes up, where Sharepoint has a feature
to "check out" a file before editing it. This locks the file so no one else
can edit it until the user who checked the file out has checked it back in.
Is there such an extension for MW?
I'd love to get rid of Sharepoint altogether and I think file handling
might be the biggest hurdle since it has a couple features that "beat" MW:
- File checkout (preventing upload conflicts)
- In-browser editing
I realize the concept of files for MW is intended for images, but we have
been using file revision history through MW with success. It's way better
than where our group started, with things spread out in a huge folder
system on a shared drive with no version control. I don't think we can
address in-browser editing, but file checkout seems like something pretty
simple to implement. So I'm wondering if someone has already worked on it.
I did a quick search and didn't see anything.
=== Permissions ===
A line is needed in the "Unpack the new files" section specifying the
permissions. CPanel doesnot allow me to upload a file without first
specifying the permissions.
=== To Overwrite or Not To Overwrite, That is the Question ===
The instructions say, "You should put the decompressed tarball in a new
and empty folder on your server," but this is not consistent with the
Upgrade[.txt] file, which says, "Replace the existing MediaWiki files
with the new." Which is correct? How do we get the incorrect instruction
=== Where to unpack them ===
Assuming I'm not to overwrite, then I also assume that I can dispense
with a separate backup since the current files are not being touched. My
current installation is in /home/myname/public_html/w so I **think**
what I'm supposed or can do is rename w to w-old then create a new
directory w then put the downloaded mediawiki-1.24.2.tar.gz file in the
new directory w and proceed from there. Is this correct?
I have a local Wiki that I have been trying to install the Math
extension on. In LocalSettings.php I have the following lines for the
> $wgUseTeX = true;
> $wgTexvc = "/extensions/Math/math/texvc.exe";
texvc was installed via following instructions here [1
<https://www.mediawiki.org/wiki/Texvc#Windows>]. I have a texvc.exe file
in the directory extensions/Math/math/ created via following these
instructions. I also have LaTeX installed on my PC via MiKTeX, currently
my path variable points to C:\Program Files\MiKTeX\miktex\bin\x64 (where
latex.exe and dvipng.exe files exist). Despite this inserting an
equation via <math></math> into a Wiki page gives the error:
> *Failed to parse (Missing <code>texvc</code> executable. Please see
> math/README to configure.):*
Thanks for your time,
I'm using Mediawiki as a Quality Management System
<https://en.wikipedia.org/wiki/Quality_management_system> (QMS). I'm using
the ApprovedRevs <https://www.mediawiki.org/wiki/Extension:Approved_Revs>
extension to enable a lightweight approval workflow. This enables me to
show users only the approved version of a given policy, process or
I'd like to add a button at the bottom of each page that an employee would
click to acknowledge they read and understood the approved version of the
document. If a new version of the document is approved, the user would need
to return to the page and repeat the acknowledgement. The acknowledgements
would likely be stored in new tables in the database.
Ideally, I'd use the "This is a minor edit" flag to indicate when a page
might need an employee to re-read it. If all changes between approved
versions were minor, rereading (retraining) would not be needed. But if
there were a non-minor change and the page was approved, then individuals
would need to return and indicate they re-read and understood the page.
I'd like to only show the "I read and understood this" button when the user
belongs to a specific group for whom the policy, procedure or process
applies. We use Semantic Mediawiki, and I imagine I'd make use of template
properties to create an "Applies to groups" property, and wire things up to
Active Directory to determine group membership.
I have other ideas for rounding out this feature. Adjunct user pages might
be created so users can track which pages they need to review and which
they're "trained" on already. Will likely need reports so managers can keep
tabs on employee training.
I'm wondering if anyone's done anything like this previously and could
steer me to existing extensions that might help. I've searched through the
existing extensions but nothing jumped out at me as an obvious fit.
I'm guessing I'll need to write a custom extension to accomplish most of
=SMWCon Spring 2015 Final Call for Contributions=
This is a reminder that the deadline for contributions to SMWCon is Wednesday, April 22nd.
We are inviting you to submit your contributions to help collect and put together the conference program. We’ve started to rough in our schedule and would love to have a diverse group of speakers. Submit your proposed talk today!
==Call for Contributions==
Talks could be about anything related to semantics, wikis, or yes semantic wikis! We welcome new contributions on the use of semantic wikis in different industries and the development and proposal of new tools in and around the semantic wiki community.
You can propose your contributions on the conference website (http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015) in form of regular talks or short lightning talks. All submitted proposals will be reviewed and we will do our best to consider your proposal in the conference program. If you've already announced your talk it's now time to expand its description.
We are also looking for folks to help us with our tutorial day. We’re looking for presentations on the basics of Semantic MediaWiki and related extensions. The deadline is April 22nd, but we encourage submissions, even in a draft form, as soon as possible to help with planning.
Please note that all tutorials and presentations will be video and audio recorded and made available for others after the conference.
Please add yourself to the informal list of attendees if you’d like to attend.
*Submission Deadline is April 22nd (please contact the organizers if you need more time)
*SMWCon is from Wednesday, May 6th to Friday, May 8th 2015
*T-Rex (http://downtowntrex.com), 911 Washington Ave., St. Louis, MO, USA
*Conference site: http://semantic-mediawiki.org/wiki/SMWCon_Spring_2015
*Participants: Everybody interested in semantic wikis, especially in Semantic MediaWiki, e.g. administrators, developers, wiki users, consultants, business representatives and researchers.
==List of Topics==
Here are some suggestions. All submissions are welcome.
Use of wikis in
Use of wikis for
Extending Semantic MediaWiki
*Integration with other services (databases, external APIs, etc)
*Visualization and reporting tools
Developments around Semantic MediaWiki
*Feature wish lists
*SMW and related extensions roadmaps
*Improving the experience using semantic wikis
*How to contribute to SMW and related projects
Tickets can be purchased at http://smwcons2015.eventbrite.com
Your registration fee includes:
*3-day Conference Pass (including the tutorial day)
*Breakfast for all three days
*Lunch on the first and 3rd day
*Evening social event with hors d'oeuvres and drinks
Please note that the registration fee does not cover accommodation or travel expenses.
Attendees from education organizations can purchase a discounted ticket. Proof of affiliation may be requested.
*Chris Koerner [Local Chair]
*Paul Boal [Program Chair]
This electronic mail and any attached documents are intended solely for the named addressee(s) and contain confidential information. If you are not an addressee, or responsible for delivering this email to an addressee, you have received this email in error and are notified that reading, copying, or disclosing this email is prohibited. If you received this email in error, immediately reply to the sender and delete the message completely from your computer system.
On Monday April 20th, Houston-based MediaWiki users and developers will
meet to share lessons-learned, open-source extensions, and collaborate on
developing new extensions beneficial to any organization using MediaWiki.
This event is being hosted by NASA’s Johnson Space Center and the
Technology Collaboration Center of Houston.
The preliminary agenda includes:
Overview of key MediaWiki extensions used at NASA
Watch Analytics extension
What features and qualities make for the "perfect" knowledge
Comparison: A single wiki vs. a wiki farm. Which works better for a
What is the best way to share data between wikis?
Wiki Conversations: Turning e-mail conversations into useful
Idea for development: Citations of references
How to complete the culture change to using a wiki (i.e., getting the
last 10% to use it)?
Please visit the event information page to register for attendance and
presentations. We are looking for people volunteering to present topics at
this meetup. Email us with any questions at enterprisemediawiki(a)gmail.com
On 24 October 2014 08:41, Chad <innocentkiller(a)gmail.com> wrote:
> On Fri, Oct 24, 2014 at 8:12 AM, James Forrester <jforrester(a)wikimedia.org
> > On 23 October 2014 18:39, Legoktm <legoktm.wikipedia(a)gmail.com> wrote:
> > > Hi,
> > >
> > > As part of the librarization project, we are planning on taking the
> > > CSSJanus library that is currently in includes/lib/ and bringing it in
> > > with composer. However, it requires PHP >=5.3.3 in its
> > > Krinkle has stated that is due to the fact that it has only been
> > > tested on 5.3.3 and higher, and it's also what travis-ci provides.
> > >
> > > After doing some research, it appears that we would be dropping
> > > support for Ubuntu 10.04LTS, which has security support until April
> > > 2015. MediaWiki 1.25.0 is expected to be released in May 2015.
> > >
> > > Does anyone have any objections to dropping 5.3.2 support? I've
> > >  that actually increments the required version number.
> > >
> > I understood that the vague plan was to switch over to 5.4.x
> > and that we'd only waited because Wikimedia wasn't ready yet. Has this
> > changed? I know a number of people have talked about wanting to use PHP
> > traits.
> Yes, but that's longer term.
How much longer? 1.25 is May 2015; Wikimedia's ZAP -> HAT migration is
nominally to be finished within a month…
> This minor bump still in the 5.3.x branch I think we can do immediately.
Sure, if announcing a 1.25 dependency change and then changing the change
later won't disrupt people too much.
(Copying the main MediaWiki-l list for those who don't follow wikitech-l)
James D. Forrester
Product Manager, Editing
Wikimedia Foundation, Inc.
jforrester(a)wikimedia.org | @jdforrester