Not logged in. · Lost password · Register
Forum: General Help and Support Plugins Plugin Wishlist RSS
Some news about the pagemove plugin?
We all miss it...
Page:  1  2  next 
Avatar
pletiplot #1
Member since Jan 2011 · 5 posts
Group memberships: Members
Show profile · Link to this post
Subject: Some news about the pagemove plugin?
Hi,
the pagemove plugin is incompatible since 2010.  But we all need it much. Do somebody have some news about it? New volunteer programer? Or even paid :-)
This post was edited on 2012-01-26, 18:13 by pletiplot.
Avatar
andi (Administrator) #2
Member since May 2006 · 2446 posts · Location: Berlin Germany
Group memberships: Administrators, Members
Show profile · Link to this post
Quote by pletiplot on 2012-01-26, 18:03:
Or even paid :-)

I'm sure you'll find someone here: http://www.wikimatrix.org/consultants/dokuwiki/-/-
Read this if you don't get any useful answers.
Lies dies wenn du keine hilfreichen Antworten bekommst.
Avatar
HansBKK #3
Member since Nov 2011 · 104 posts · Location: Bangkok
Group memberships: Members
Show profile · Link to this post
In reply to post #1
Also note, depending on your needs, you can just go ahead and modify the wiki's content in the filesystem and reset the index/cache/history etc; DW will just rebuild its meta-data as needed, so far without any problems that I've come across, other than pageload times the first time - which I overcome by batch-spidering the site.

http://forum.dokuwiki.org/post/28191
http://forum.dokuwiki.org/post/29467

Of course, I'm not saying an integrated batch rename/move tool shouldn't be considered an essential feature, but in the meantime. . .
Avatar
turnermm (Moderator) #4
Member since Oct 2009 · 2322 posts
Group memberships: Global Moderators, Members
Show profile · Link to this post
You might find the openas plugin useful:

http://www.dokuwiki.org/plugin:openas

It can both move and save to another name, as well as opening a page using the newpagetemplate plugin.
Myron Turner
fckgLite (&ckgedit): http://www.mturner.org/fckgLite/
github: https://github.com/turnermm
plugins, templates: http://www.mturner.org/devel
Avatar
epicycles #5
Member since Feb 2012 · 12 posts
Group memberships: Members
Show profile · Link to this post
It is very important especially for a hierarchical wiki to implement movement within the hierarchy, and renaming of entire namespaces.     I am a new Dokuwiki user and was very excited about the simplicity and ease of use of DW, along with its very nice latex and dokutexit pdf generation, and handy security model.  After reading about how the basic move/rename development has stalled over the past few years, I am sadly looking for another wiki that at least does better in this regard.   Unfortunately this issue appears to be the achilles heel of Dokuwiki, at least for some of us.  Please, please, try to make this core functionality.
Avatar
HansBKK #6
Member since Nov 2011 · 104 posts · Location: Bangkok
Group memberships: Members
Show profile · Link to this post
Of course, you are free to use whatever you like.

If this is an important feature for you and being used in a commercial context, perhaps consider contributing toward a bounty to get it done?

The key feature I like about DW - I believe unique among the other mainstream wiki platforms - is the fact that the content-data is 100% transparent plaintext documents and the name-spaces are a bog-standard filesystem hierarchy of folders.

As I pointed out above, this should allow you to use whatever tools you like to re-factor you're content's organisation from within the filesystem, reset the meta-data kruft (assuming there isn't anything there valuable for your use case) and your DokuWiki instance will now work with the new content-data without any problem.

This may not be as user-friendly as the built-in tools in other wiki platforms, but to me offers a lot more power and flexibility, particularly when you desire integration with other programs and tools delivering data from the back end.

This is how I use DokuWiki - as a "target output format" for upstream data generation, collecting edits and feedback to be incorporated into the upstream "master source" data.
Avatar
epicycles #7
Member since Feb 2012 · 12 posts
Group memberships: Members
Show profile · Link to this post
Thanks HansBKK,
Is my understanding correct, that this would destroy the revision history of the moved parts?
I think this would be better than nothing for my use case.   Would you consider making your scripts part of a server-side toolbox?

Of course this puts the burden of organizing things upon the wiki admin, whereas it should rightly reside with the users that disorganized it in the first place :).   So ultimately a mature wiki move feature from the user side is needed.
This post was edited on 2012-02-05, 15:37 by epicycles.
Avatar
turnermm (Moderator) #8
Member since Oct 2009 · 2322 posts
Group memberships: Global Moderators, Members
Show profile · Link to this post
When it comes to moving pages, unfortunately the MoveTo function of my openas plugin doesn't do much more than move the page to another namespace:page_name.   It is rather 'quick and dirty'.  But I am thinking of adding some more functionality to it.  For me, at the moment, the most important thing is that all links are brought up-to-date.
Myron Turner
fckgLite (&ckgedit): http://www.mturner.org/fckgLite/
github: https://github.com/turnermm
plugins, templates: http://www.mturner.org/devel
Avatar
HansBKK #9
Member since Nov 2011 · 104 posts · Location: Bangkok
Group memberships: Members
Show profile · Link to this post
In reply to post #7
> Is my understanding correct, that this would destroy the revision history of the moved parts?

Yes, I throw away all meta data each revision cycle - but the "master source" content files are kept in a real version control system anyway, so the DW history's redundant once the "canonical" changes have been merged and committed to the VCS.

I've asked for ways to just turn off DW's history feature, but no reply.


> Would you consider making your scripts part of a server-side toolbox?

I don't have a defined package of scripts, just various tools used to output/edit/transform plain text files, depending on where they're coming from and what needs doing to them.

My point is just that you can work with the DW's wiki data as you would any dirtree of plaintext files.


> organizing things upon the wiki admin, whereas it should rightly reside with the users that disorganized it in the first place

In my case the users are just proposing edits to existing docs or adding new ones, a central group of content "editors" are responsible for the organizational aspects, but things are getting pretty constantly re-factored.
Avatar
HansBKK #10
Member since Nov 2011 · 104 posts · Location: Bangkok
Group memberships: Members
Show profile · Link to this post
In reply to post #8
Quote by turnermm:
the most important thing is that all links are brought up-to-date.

The openas doc page states that backlinks aren't updated - is that currently the case?
Avatar
turnermm (Moderator) #11
Member since Oct 2009 · 2322 posts
Group memberships: Global Moderators, Members
Show profile · Link to this post
Correct.  As I said earlier, it is in its present form just "quick and dirty".  But if you don't care about meta data, then it works just fine.
Myron Turner
fckgLite (&ckgedit): http://www.mturner.org/fckgLite/
github: https://github.com/turnermm
plugins, templates: http://www.mturner.org/devel
Avatar
epicycles #12
Member since Feb 2012 · 12 posts
Group memberships: Members
Show profile · Link to this post
In reply to post #9
Subject: version control
HansBKK,
Thanks for your perspective.
This is straying from the subject, but I was wondering about how you handle the version control. 
(Actually it relates to the pagemove issue because maybe if the wiki version control was handled by SVN or Git or whatever, then maybe it would be easier to implement things like page moves, at least when it comes to versioning and rolling back.)
Anyway, do you have a mechanism to check in each page edit to the repository as the user does them, or do you just periodically check things in?   If the goal of versioning is to be able to roll back spam, then the former would be nice.  If it's just to keep backups, then only the latter would be needed.
Avatar
HansBKK #13
Member since Nov 2011 · 104 posts · Location: Bangkok
Group memberships: Members
Show profile · Link to this post
We're mostly using SVN, in some cases starting to transition to Mercurial (Hg).

Only "canonical" changes by the editors are checked in, nothing to do with DW at that point.

It would theoretically be possible to review DW history, but in practice this hasn't been necessary, also no DW/VCS integration.  If spam or other random damage was done to the DW data, we'd just revert using the VCS.

There are wikis that actually use DVCS as their data store - usually Git, but none are as well-supported or actively developed, also harder to implement.
Avatar
turnermm (Moderator) #14
Member since Oct 2009 · 2322 posts
Group memberships: Global Moderators, Members
Show profile · Link to this post
In reply to post #8
I've finally worked up a version of the openas plugin which has a pagemove facility that updates backlinks:

http://www.dokuwiki.org/plugin:openas?&#pagemove
Myron Turner
fckgLite (&ckgedit): http://www.mturner.org/fckgLite/
github: https://github.com/turnermm
plugins, templates: http://www.mturner.org/devel
Avatar
epicycles #15
Member since Feb 2012 · 12 posts
Group memberships: Members
Show profile · Link to this post
Nice!  kudos for your efforts!
I will try it out.
Close Smaller – Larger + Reply to this post:
Verification code: VeriCode Please enter the word from the image into the text field below. (Type the letters only, lower case is okay.)
Smileys: :-) ;-) :-D :-p :blush: :cool: :rolleyes: :huh: :-/ <_< :-( :'( :#: :scared: 8-( :nuts: :-O
Special characters:
Page:  1  2  next 
Go to forum
Imprint
This board is powered by the Unclassified NewsBoard software, 20120620-dev, © 2003-2011 by Yves Goergen
Current time: 2014-04-19, 11:42:35 (UTC +02:00)