workingwiki-users Mailing List for WorkingWiki
Status: Beta
Brought to you by:
worden
Menu
▾
▴
workingwiki-users — Email list for WorkingWiki users (including WW admin and ProjectEngine topics)
You can subscribe to this list here.
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
(11) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2011 |
Jan
|
Feb
(3) |
Mar
(5) |
Apr
(10) |
May
(2) |
Jun
(6) |
Jul
|
Aug
(10) |
Sep
(1) |
Oct
(4) |
Nov
|
Dec
|
| 2012 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
(3) |
| 2013 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(5) |
Nov
|
Dec
|
| 2014 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
|
From: Lee W. <wor...@gm...> - 2014-10-07 21:00:58
|
Dear WorkingWiki community, Just writing to let you know that I'm soon going to be shifting WorkingWiki's requirements, so that new revisions of WW will require MediaWiki 1.23 or later. It currently supports MW 1.19 or later, so installations running 1.19 or any other pre-1.23 version will need to upgrade. Please let me know if you have any concerns or other thoughts. As always, thanks for your support and for all the valuable feedback! LW |
|
From: Lee W. <wor...@gm...> - 2014-04-16 20:05:21
|
[Summary: as of revision 1124 of WorkingWiki, you have to install the MultiUpload extension on your wiki in order for WorkingWiki to run.] Dear WorkingWiki community, A while back I completely rewrote WorkingWiki's file-upload interface, to make it work in recent releases of MediaWiki. In my opinion, the new interface works much better, and has various convenient features that work immediately without requiring clicks that reload the whole page. I developed it in two parts: first a modification of the standard Special:Upload page, allowing it to handle multiple files on a single upload page; and second a modification of that, supporting WorkingWiki's import-into-a-project operation rather than the standard upload-to-a-File-page operation. The first half of that is generally useful independent of WorkingWiki, so I've pulled it out into a separate MediaWiki extension so that people can use that who don't care to install WorkingWiki. This is now the MultiUpload extension, available at http://www.mediawiki.org/wiki/Extension:MultiUpload. Now that I've pulled those features out of WorkingWiki, MultiUpload is now a prerequisite for WorkingWiki. Once you upgrade beyond WorkingWiki's revision 1124, you must also have the MultiUpload extension installed on your wiki. Installation instructions are at the above-linked page. If there's anything I can do to help, please don't hesitate to let me know. My apologies if you receive this message more than once. Thanks! Lee Worden |
|
From: Lee W. <wor...@gm...> - 2013-10-25 08:48:11
|
Here's a video showing how we can pull a project's files from a wiki directly into RStudio, where we can run the R code... http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki-RStudio_video LW |
|
From: Lee W. <wor...@gm...> - 2013-10-25 01:35:27
|
Hello - I've created a page documenting how to work with Make and makefiles in WorkingWiki. This has been a long-standing need, and I appreciate that it's been frustrating trying to guess what's going on without useful documentation about this. I hope this page is helpful. I would very much appreciate suggestions about what's missing or could be different on this page. Here's the direct link: http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki/Writing_Makefiles_in_WorkingWiki Thanks! Lee |
|
From: Lee W. <wor...@gm...> - 2013-10-23 00:17:26
|
I just learned of this project: https://github.com/arfon/fidgit Seems like it could possibly be used with what we have today, to get Figshare.org to assign a DOI (a permanent "Digital Object Identifier") to a particular version of a WorkingWiki project. i.e. * Use http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki/Git_interface to pull the project from the wiki to a local directory, and push it onto github.com * Use this fidgit thing to put the github version into a Figshare project, and have figshare give it a permanent DOI. Or it might be able to do it without the intermediate github step. Possibly I should stop making idle comments about DOIs and figure out whether I myself have any use for one, and if so, what it would take to make it happen... But I think it would be great to be able to consider a WW wiki a publishing platform, in a potential non-journal-dominated world, and this would be an important part of it... |
|
From: Lee W. <wor...@gm...> - 2013-10-04 07:57:01
|
OK, I wrote some stuff at <http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki/Using_LaTeX_in_WorkingWiki>. That includes some detail (on a separate page) about how the makefiles work. Do please let me know if it's helpful or missing something, or unclear, etc. Thanks, Lee On 10/03/2013 01:11 PM, Lee Worden wrote: > Hi all, > > As I mentioned in the Dushoff lab meeting just now, I'm planning a push > to improve the documentation for our WorkingWiki software. (The > documentation we have is collected in the list of links at the bottom of > <http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki>.) > > My impression is that the biggest lacks right now are documentation on > how to use WorkingWiki to manage LaTeX documents (especially how to work > with the automatic building features that WW provides), and > documentation on how to work with makefiles. Ideally, these things will > be inter-linked with the existing page on how to do stuff with R. > > I'm writing to ask what other needs you are having. Are there > particular things that you find impenetrable, or just haven't been able > to find information about? > > Thanks, > Lee |
|
From: Lee W. <wor...@gm...> - 2013-10-03 20:12:06
|
Hi all, As I mentioned in the Dushoff lab meeting just now, I'm planning a push to improve the documentation for our WorkingWiki software. (The documentation we have is collected in the list of links at the bottom of <http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki>.) My impression is that the biggest lacks right now are documentation on how to use WorkingWiki to manage LaTeX documents (especially how to work with the automatic building features that WW provides), and documentation on how to work with makefiles. Ideally, these things will be inter-linked with the existing page on how to do stuff with R. I'm writing to ask what other needs you are having. Are there particular things that you find impenetrable, or just haven't been able to find information about? Thanks, Lee |
|
From: Lee W. <wor...@gm...> - 2013-08-24 03:46:27
|
This post on Scientific American's blog is interesting to me: http://blogs.scientificamerican.com/information-culture/2013/08/23/citing-data-without-tearing-your-hair-out/ Do any of you use our wikis to make data sets public? If so, is it a problem that we don't assign DOIs to them? Do you publish them in particular ways? Are there other ways we could support people who use our wikis for data sets? Lee |
|
From: Lee W. <wor...@gm...> - 2013-02-08 00:04:28
|
Dear WorkingWiki users, I want to let you know of some planned changes. We're working toward upgrading all our McMaster wikis to a current release of MediaWiki. After that's done, I'm going to gradually adopt some changes in the WorkingWiki software that will take advantage of recent features in MediaWiki to improve the interface. At some point we'll have to stop supporting old releases of MediaWiki, and you'll have to be on MediaWiki 1.20 or maybe 1.19 to use WorkingWiki. Later releases of WorkingWiki will continue to abandon outdated MediaWiki platforms. This is to give you ample notice, so that you can plan. Thanks! Lee Worden |
|
From: Lee W. <wor...@gm...> - 2013-01-28 20:02:14
|
Forwarding from the Dushoff lab list. These features are in r967 of the WW code repository, also available as a .tar.gz at https://sourceforge.net/projects/workingwiki/files/. LW -------- Original Message -------- Subject: A small step for Lee Date: Mon, 28 Jan 2013 14:08:51 -0500 From: Jonathan Dushoff <du...@mc...> To: lab But a giant step for WW users. Our working wikis now have: * buttons to add tags and tabs (look to the right of the button bar that appears above the edit window) * upload file buttons in context. These appear in the source file list on the MP page, and also on the View Project File page for source files. In my opinion, this makes it much easier to introduce people to doing small projects on the wiki. In particular, it makes it very easy to set up a project for somebody and tell them to manually upload new versions of files when they want to. Yay! -- McMaster University Department of Biology http://lalashan.mcmaster.ca/theobio/DushoffLab/index.php/Main_Page https://twitter.com/jd_mathbio |
|
From: Quim G. <qg...@wi...> - 2012-12-01 20:50:49
|
Hi there, On 11/30/2012 05:49 PM, Lee Worden wrote: > To the math-wikis and workingwiki-users lists - > > See below, from the Wikimedia Foundation. They are creating > institutional support for MediaWiki user groups. Anyone interested in > joining to create a MediaWiki math user group? Or another one? I'm happy to see you find the idea good. I'm looking forward to your feedback so we can approve MediaWiki reps and groups sooner than later. If you like alphatesting :) you could start drafting a proposal for a MediaWiki Math Group at http://www.mediawiki.org/wiki/User:Qgil/MediaWiki_groups/Groups/Proposals/Math - and I will help you with the progress. This would be very useful to polish the process and see what are the real needs. http://www.mediawiki.org/wiki/User:Qgil/MediaWiki_groups#Creating_a_group Looking forward to hearing more from you! -- Quim Gil Technical Contributor Coordinator Wikimedia Foundation |
|
From: Joe C. <hol...@gm...> - 2012-12-01 01:44:50
|
That seems like a step forward in the world (one that I can support even though I'm not a major MediaWiki user). I'd be happy to join as a regular "user", and to stay informed. |
|
From: Lee W. <wor...@gm...> - 2012-12-01 01:38:38
|
To the math-wikis and workingwiki-users lists - See below, from the Wikimedia Foundation. They are creating institutional support for MediaWiki user groups. Anyone interested in joining to create a MediaWiki math user group? Or another one? Lee Worden ----- http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064732.html From: Quim Gil qgil at wikimedia.org Date: Fri Nov 30 00:50:21 UTC 2012 Hi, here you have a first draft about MediaWiki Groups, and implicitly MediaWiki reps: http://www.mediawiki.org/wiki/User:Qgil/MediaWiki_groups MediaWiki groups organize open source community activities within the scope of specific topics and geographical areas. They extend the capacity of the Wikimedia Foundation in events, training, promotion and other technical activities benefiting Wikipedia, the Wikimedia movement and the MediaWiki software. Imagine MediaWiki Germany Group, MediaWiki Lua Group... These groups may become a significant source of growth and wider diversity of our community. Please bring your ideas to the discussion page - or here. Thank you! -- Quim Gil Technical Contributor Coordinator Wikimedia Foundation |
|
From: Lee W. <wor...@gm...> - 2012-09-07 23:37:00
|
Summary: some bookkeeping that only affects wiki administrators, not wiki users. I'm sorry to say that due to some kind of corrupted write operation to the workingwiki repository, which seemed to require rebuilding the thing, there's a slight interruption in service. (If you had a problem connecting to it in the last couple hours, that'd be why.) Subversion won't recognize it as the same repository, and you'll have to check it out fresh. For me that looked like this: $ cd /usr/local/workingwiki $ svn checkout svn+ssh://wo...@sv.../p/workingwiki/code/trunk/ WorkingWiki-new $ cp WorkingWiki/ProjectEngine/resources/site WorkingWiki-new/ProjectEngine/resources $ (cd WorkingWiki-new/ProjectEngine && make) $ (mv WorkingWiki WorkingWiki-old && mv WorkingWiki-new WorkingWiki) In English: 1. checkout from the rebuilt repository into a separate working copy 2. if you have installed site-specific makefiles and other resources in the "site" directory, copy them over to the new working copy 3. compile the pe-make executable 4. replace the live copy of WorkingWiki with the new working copy Once you're satisfied, you can delete the old stuff, carefully of course. Sorry for the inconvenience! Lee |
|
From: Lee W. <wor...@gm...> - 2012-08-18 09:31:53
|
Friends: I've committed several changes to the WorkingWiki code. One of them is important for site administrators to know about before you upgrade your wikis, and some of the others are important for wiki users as well. 1. For site administrators: from revision 873 on, the directory structure where the project files are stored is changed. It will take care of moving the directories from the old locations on its own, but there is one exception: all your background jobs will be abandoned. So you'll need to make sure everyone's background jobs are finished and merged or destroyed before you upgrade. 2. There are no more "implicit project descriptions". What this means to you is mainly that certain pages that used to just work will now have warnings saying "Source file X does not belong to project Y. Click here to add it to the project." Since you may not want these messages to show on pages you show to the public, you'll want to look over those pages and fix these complaints. 3. Instead of ".latexml.xhtml" files we now use ".latexml.html5" files to display LaTeX documents in the wiki pages. In most cases this is taken care of for you, but if you're explicitly asking for .latexml.xhtml files on certain pages (some people are), you'll need to switch to asking for .latexml.html5 instead. 4. When you save after editing and previewing, we used to do a slow process of comparing all the project files and copying the ones that were changed into the permanent project directory. Now we just replace the permanent directory by the complete preview copy of the directory. This is massively faster. But you should know about it, because if you remove files in the preview directory, they'll end up being removed in the permanent one. I mention it because you might have gotten used to removing things during a preview without consequences. There are details, and other changes, on http://lalashan.mcmaster.ca/theobio/projects/index.php/WorkingWiki/ChangeLog. The new version of WorkingWiki is committed to the Subversion repository, and also uploaded to https://sourceforge.net/projects/workingwiki/files/ for admins who install from tarfiles. As always, let me know if anything is puzzling or wrong. LW On 03/02/2012 05:16 PM, Lee Worden wrote: > And secondly, a change in the internals of the system that I want to > write about before it happens, to allow you to raise objections. > > We've been working out the bugs on out McMaster wikis on a change that > reorganizes the cache directory where the project files are stored. This > makes it easier for humans to navigate the cache files if needed, and > removes some redundancy in the filenames. > > For the most part, changing to the new system will make no difference, > as WW will silently move your files to their new locations as it comes > across them. The one exception is that existing background jobs will > not be compatible with the new system, meaning that it won't recognize > that they exist, and it won't be able to tell you their status or merge > their files into the persistent project directories. > > In case you're wondering: background jobs are listed in a special box at > the top of your wiki pages, and they have to be explicitly created by a > user: unless you have a user who's making background jobs on purpose, > you don't have any background jobs. You can find out for sure by > looking in your cache directory (the one that has a subdirectory called > "persistent/") and seeing if it has any subdirectories whose names start > with "background_". > > So you'll need to make sure all background jobs are merged or destroyed > before updating your WW installation to the new source code. I'm > writing to find out whether that'll be a problem, and whether I should > roll out the new code at a particular time. Also, you should be warned, > because there might be bugs in the code, and you should upgrade at a > time when there's breathing room to discover and fix them, not like the > day before a major deadline. > > Please let me know if you have any thoughts about that. Otherwise I'll > go ahead and make a decision. Thanks! > Lee |
|
From: Lee W. <wor...@gm...> - 2012-08-15 20:48:19
|
To all(*) WorkingWiki svn users: there's been an upgrade at SourceForge. It looks like the issue trackers have some new features, including letting you vote on unresolved bugs. Feel free to use that. It also looks like it changed the SVN repository and we need to switch to using the new repository address. I didn't know that was going to happen, and I apologize for any inconvenience. I'm guessing we could probably use "svn switch" rather than just checking out into a whole new directory. Here is the message from SourceForge. Lee (*) Or is it "both"... -------- Original Message -------- Subject: SourceForge Repo Clone Complete Date: Wed, 15 Aug 2012 20:41:50 +0000 From: SourceForge.net <nor...@in...> Reply-To: no...@in... To: no...@in... Your cloned repository code in project workingwiki is now ready for use. Old repository url: http://workingwiki.svn.sourceforge.net/svnroot/workingwiki New repository checkout command: svn checkout --username=worden svn+ssh://wo...@sv.../p/workingwiki/code/trunk workingwiki-code You and any other developers should do a fresh checkout using the new repository location. |
|
From: Lee W. <wor...@gm...> - 2012-03-03 01:38:11
|
On 03/02/2012 05:04 PM, Lee Worden wrote: > We've been using MathJax [www.mathjax.org] to display the math on our > wikis at McMaster for a while, and it seems to be working well enough > that I want to go ahead and make it the default behavior. > . . . > This change takes effect in revision 837 of WorkingWiki. Sorry, that should say revision 839. -LW |
|
From: Lee W. <wor...@gm...> - 2012-03-03 01:16:53
|
And secondly, a change in the internals of the system that I want to write about before it happens, to allow you to raise objections. We've been working out the bugs on out McMaster wikis on a change that reorganizes the cache directory where the project files are stored. This makes it easier for humans to navigate the cache files if needed, and removes some redundancy in the filenames. For the most part, changing to the new system will make no difference, as WW will silently move your files to their new locations as it comes across them. The one exception is that existing background jobs will not be compatible with the new system, meaning that it won't recognize that they exist, and it won't be able to tell you their status or merge their files into the persistent project directories. In case you're wondering: background jobs are listed in a special box at the top of your wiki pages, and they have to be explicitly created by a user: unless you have a user who's making background jobs on purpose, you don't have any background jobs. You can find out for sure by looking in your cache directory (the one that has a subdirectory called "persistent/") and seeing if it has any subdirectories whose names start with "background_". So you'll need to make sure all background jobs are merged or destroyed before updating your WW installation to the new source code. I'm writing to find out whether that'll be a problem, and whether I should roll out the new code at a particular time. Also, you should be warned, because there might be bugs in the code, and you should upgrade at a time when there's breathing room to discover and fix them, not like the day before a major deadline. Please let me know if you have any thoughts about that. Otherwise I'll go ahead and make a decision. Thanks! Lee |
|
From: Lee W. <wor...@gm...> - 2012-03-03 01:04:40
|
Dear watchful WorkingWiki warriors, I want to warn you of a change in the software. We've been using MathJax [www.mathjax.org] to display the math on our wikis at McMaster for a while, and it seems to be working well enough that I want to go ahead and make it the default behavior. This will give us good-looking scaleable math on a wide variety of browsers, as opposed to the current setup, which basically gives you nice scalable math on Firefox if you download the right math fonts and ask for it in the wiki preferences, and gives you bitmap images of the math otherwise. If you do happen to use Firefox and have the math fonts, because using that is faster than MathJax, you'll still get that behavior instead of MathJax if you select the "use MathML" preference item on the wiki. This change takes effect in revision 837 of WorkingWiki. If you're already using the WW MathJax feature (by explicitly enabling it on your wikis) you're fine already and you can ignore this, unless you want the part where the preferences item turns off MathJax. If you're using WW tarfiles instead of subversion and you want the new code, let me know. Any concerns or questions, please let me know. Lee P.S. Note that this whole business is completely independent of any other MW extensions including the Math extension and the MathJax extension, which can be confusing. P.S.2. There is one exception to that, which is that if you use the Math extension's preference item to request MathML, WorkingWiki respects your choice, so that we can avoid having redundant questions on the preferences page. In MediaWiki 1.18 or later, there's a WW-specific preferences item, because you don't necessarily have the Math extension. If you are opting to use the Math extension anyway, WW's preference item is redundant and you can make it go away by setting $wwProvideMathmlPreference = false. |
|
From: Lee W. <wor...@gm...> - 2011-10-11 20:38:39
|
Just want to mention to list users that the 741 package does not in fact fix the problem that Josep discovered. It's an issue with MediaWiki 1.17.0, which is the latest version that's available in a downloadable package. The issue does not show up in later versions of MediaWiki 1.17 and 1.18. The newer WorkingWiki package, WorkingWiki-748.tar.gz, fixes the problem and is now available on sourceforge. The fix can also be had from the WW subversion repository by updating to revision 743 or later. LW On 10/06/2011 11:52 AM, Lee Worden wrote: > OK, WorkingWiki-741.tar.gz is now uploaded to > https://sourceforge.net/projects/workingwiki/files/. It includes the > changes that made the ManageProject page stop crashing on our 1.17 > installation, so I'm hopeful it will work for yours too. > > If you reinstall from this package, you'll need to compile pe-make again. > > The newer version also includes an option to use MathJax, which is not > enabled by default because we're still testing it. See this email list's > archive for details: > > https://sourceforge.net/mailarchive/forum.php?thread_name=4E823144.6030500%40gmail.com&forum_name=workingwiki-users > > > Lee > > On 10/06/2011 11:35 AM, Lee Worden wrote: >> Hi Josep, welcome and thank you for your kind words! >> >> I've made some fixes since r696 to make WW work in MW 1.17, so you'll >> need a newer version. I think this will probably fix your problem. I'll >> make an updated package and let you know when it's ready. Alternatively, >> if you prefer not to wait, you can install WW from the svn repository >> and get the newest version right away. >> >> Out of curiosity, do you mind if I ask how you came across the WW >> project? >> >> Lee >> >> On 10/06/2011 08:09 AM, josep plans wrote: >>> Hi, >>> >>> I've just discovered WorkingWiki and I've started using it immediately. >>> >>> I'm new to MediaWiki too. So long, everything is working as described in >>> the documentation except one thing. >>> >>> The scenario: I have a project called "myproject" and the corresponding >>> "ProjectDescription:myproject" page. I can add source files to that >>> project by editing its ProjectDescription page or by doing as described >>> in the tutorial: "... when you add this source file to a page and save >>> it, you will be given a "Click here" link to add the file to the >>> project." I can also import project data from a tar or zip file. >>> >>> The problem is: If I try to go to >>> "Special:ManageProject?project=myproject" by following the link in the >>> menu on the left, I just get a blank page. And when I add a source file >>> to a page and save it, and I follow the link to add the file to the >>> project, I also get a blank page (although the file is properly added to >>> the project). >>> >>> I'm using MediaWiki 1.17.0 and WorkingWiki 696. >>> >>> Does anybody know why that happens? >>> >>> Thank you so much for giving us WorkingWiki! >>> >>> Josep >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> >>> >>> All the data continuously generated in your IT infrastructure contains a >>> definitive record of customers, application performance, security >>> threats, fraudulent activity and more. Splunk takes this data and makes >>> sense of it. Business sense. IT sense. Common sense. >>> http://p.sf.net/sfu/splunk-d2dcopy1 >>> >>> >>> >>> _______________________________________________ >>> workingwiki-users mailing list >>> wor...@li... >>> https://lists.sourceforge.net/lists/listinfo/workingwiki-users |
|
From: Lee W. <wor...@gm...> - 2011-10-06 18:52:50
|
OK, WorkingWiki-741.tar.gz is now uploaded to https://sourceforge.net/projects/workingwiki/files/. It includes the changes that made the ManageProject page stop crashing on our 1.17 installation, so I'm hopeful it will work for yours too. If you reinstall from this package, you'll need to compile pe-make again. The newer version also includes an option to use MathJax, which is not enabled by default because we're still testing it. See this email list's archive for details: https://sourceforge.net/mailarchive/forum.php?thread_name=4E823144.6030500%40gmail.com&forum_name=workingwiki-users Lee On 10/06/2011 11:35 AM, Lee Worden wrote: > Hi Josep, welcome and thank you for your kind words! > > I've made some fixes since r696 to make WW work in MW 1.17, so you'll > need a newer version. I think this will probably fix your problem. I'll > make an updated package and let you know when it's ready. Alternatively, > if you prefer not to wait, you can install WW from the svn repository > and get the newest version right away. > > Out of curiosity, do you mind if I ask how you came across the WW project? > > Lee > > On 10/06/2011 08:09 AM, josep plans wrote: >> Hi, >> >> I've just discovered WorkingWiki and I've started using it immediately. >> >> I'm new to MediaWiki too. So long, everything is working as described in >> the documentation except one thing. >> >> The scenario: I have a project called "myproject" and the corresponding >> "ProjectDescription:myproject" page. I can add source files to that >> project by editing its ProjectDescription page or by doing as described >> in the tutorial: "... when you add this source file to a page and save >> it, you will be given a "Click here" link to add the file to the >> project." I can also import project data from a tar or zip file. >> >> The problem is: If I try to go to >> "Special:ManageProject?project=myproject" by following the link in the >> menu on the left, I just get a blank page. And when I add a source file >> to a page and save it, and I follow the link to add the file to the >> project, I also get a blank page (although the file is properly added to >> the project). >> >> I'm using MediaWiki 1.17.0 and WorkingWiki 696. >> >> Does anybody know why that happens? >> >> Thank you so much for giving us WorkingWiki! >> >> Josep >> >> >> >> ------------------------------------------------------------------------------ >> >> All the data continuously generated in your IT infrastructure contains a >> definitive record of customers, application performance, security >> threats, fraudulent activity and more. Splunk takes this data and makes >> sense of it. Business sense. IT sense. Common sense. >> http://p.sf.net/sfu/splunk-d2dcopy1 >> >> >> >> _______________________________________________ >> workingwiki-users mailing list >> wor...@li... >> https://lists.sourceforge.net/lists/listinfo/workingwiki-users |
|
From: Lee W. <wor...@gm...> - 2011-10-06 18:35:39
|
Hi Josep, welcome and thank you for your kind words! I've made some fixes since r696 to make WW work in MW 1.17, so you'll need a newer version. I think this will probably fix your problem. I'll make an updated package and let you know when it's ready. Alternatively, if you prefer not to wait, you can install WW from the svn repository and get the newest version right away. Out of curiosity, do you mind if I ask how you came across the WW project? Lee On 10/06/2011 08:09 AM, josep plans wrote: > Hi, > > I've just discovered WorkingWiki and I've started using it immediately. > > I'm new to MediaWiki too. So long, everything is working as described in > the documentation except one thing. > > The scenario: I have a project called "myproject" and the corresponding > "ProjectDescription:myproject" page. I can add source files to that > project by editing its ProjectDescription page or by doing as described > in the tutorial: "... when you add this source file to a page and save > it, you will be given a "Click here" link to add the file to the > project." I can also import project data from a tar or zip file. > > The problem is: If I try to go to > "Special:ManageProject?project=myproject" by following the link in the > menu on the left, I just get a blank page. And when I add a source file > to a page and save it, and I follow the link to add the file to the > project, I also get a blank page (although the file is properly added to > the project). > > I'm using MediaWiki 1.17.0 and WorkingWiki 696. > > Does anybody know why that happens? > > Thank you so much for giving us WorkingWiki! > > Josep > > > > ------------------------------------------------------------------------------ > All the data continuously generated in your IT infrastructure contains a > definitive record of customers, application performance, security > threats, fraudulent activity and more. Splunk takes this data and makes > sense of it. Business sense. IT sense. Common sense. > http://p.sf.net/sfu/splunk-d2dcopy1 > > > > _______________________________________________ > workingwiki-users mailing list > wor...@li... > https://lists.sourceforge.net/lists/listinfo/workingwiki-users |
|
From: josep p. <chi...@go...> - 2011-10-06 15:09:26
|
Hi, I've just discovered WorkingWiki and I've started using it immediately. I'm new to MediaWiki too. So long, everything is working as described in the documentation except one thing. The scenario: I have a project called "myproject" and the corresponding "ProjectDescription:myproject" page. I can add source files to that project by editing its ProjectDescription page or by doing as described in the tutorial: "... when you add this source file to a page and save it, you will be given a "Click here" link to add the file to the project." I can also import project data from a tar or zip file. The problem is: If I try to go to "Special:ManageProject?project=myproject" by following the link in the menu on the left, I just get a blank page. And when I add a source file to a page and save it, and I follow the link to add the file to the project, I also get a blank page (although the file is properly added to the project). I'm using MediaWiki 1.17.0 and WorkingWiki 696. Does anybody know why that happens? Thank you so much for giving us WorkingWiki! Josep |
|
From: Lee W. <wor...@gm...> - 2011-09-27 20:25:49
|
We're testing out a change to WorkingWiki on the lalashan wikis today: it's using MathJax (www.mathjax.org) to display math content instead of using the brittle and unfriendly XHTML webpage format. If all goes well, this will mean no more orange parse-error pages when there's a software problem; and also, high-quality math that scales when you make the font bigger and smaller, on all modern browsers, not only on Firefox. If you're on a lalashan wiki, hopefully you'll just notice that the math is a little nicer. If anything seems wrong please let me know. If you want to test the mathjax output on a non-lalashan wiki, just update to r738 or later from the svn repository and add $wwUseMathJax = true; to your LocalSettings.php somewhere before it invokes WorkingWiki.php. lw |
|
From: Peter L. R. <pl...@st...> - 2011-08-26 20:02:22
|
Ooops, I see this page already exists. =) It just wasn't linked to from
the WorkingWiki page (just from the Main_Page). I've edited the "How do
I upload a file" section a bit.
-p
On Fri, Aug 26, 2011 at 12:39:35PM -0700, Peter L. Ralph wrote:
> Hi, all -- I've added an FAQ page for WW to the documentation. This is
> because I wanted to write up the answer to "How do I upload a
> {spreadsheet, image, binary file} to my project?" and this didn't seem
> to go exactly into the other categories of documentation existing. The
> information is certainly there otherwise, but harder for people to
> access. If you disagree, move it? We could also collect ideas of FAQs
> here to serve as a useful reference to folks trying to remember what the
> right way to do certain things is.
>
> -p
>
> ------------------------------------------------------------------------------
> EMC VNX: the world's simplest storage, starting under $10K
> The only unified storage solution that offers unified management
> Up to 160% more powerful than alternatives and 25% more efficient.
> Guaranteed. http://p.sf.net/sfu/emc-vnx-dev2dev
> _______________________________________________
> workingwiki-users mailing list
> wor...@li...
> https://lists.sourceforge.net/lists/listinfo/workingwiki-users
|
