Date   
DokuWiki User Forum #wikispaces #export #dokuwiki

Tom H
 

Found the beginnings of a discussion here.

CiviHosting offers migration to DokuWiki #wikispaces #export #dokuwiki #civihosting

Tom H
 

CiviHosting now offers a Wikispaces wiki migration to DokuWiki in conjunction with its DokuWiki hosting service. There's a one-time and a recurring fee. See https://civihosting.com/wikispaces-migration/ for details.

If you use their service, please share your experience here. 

Re: CiviHosting offers migration to DokuWiki #wikispaces #export #dokuwiki #civihosting

@willm
 

I used their service and it went very smoothly. They set me up a custom domain and moved our whole Wiki over within hours. The new DokuWiki looks like it will work really well, but many of the pages will require significant clean up. The table of contents was duplicated on many pages and most internal links were broken (both to media and wiki pages). Spacing in bulleted lists ended up weird and was flattened to one level of indentation. And the headers on pages were all flattened to Level 1 Headers.

While it will require a fair amount of clean-up, I think our organization will be very happy with the results in the end. DokuWiki seems very full featured and easy to manage.

Re: CiviHosting offers migration to DokuWiki #wikispaces #export #dokuwiki #civihosting

CiviHosting
 

I used their service and it went very smoothly.
Glad to hear you're happy with our services.

While it will require a fair amount of clean-up,
We will contact you privately offline, as internal links both to media and wiki pages should all be preserved with our importer. We will check on your site and see what may have gone wrong.

Thank you,
CiviHosting

Re: CiviHosting offers migration to DokuWiki #wikispaces #export #dokuwiki #civihosting

Tom H
 

On Tue, Mar 20, 2018 at 05:21 am, @willm wrote:
The new DokuWiki looks like it will work really well, but many of the pages will require significant clean up.
Thanks for the report, @willm. If your sites are public, would you kindly add them to the Examples database at https://wikispaces-refugees.groups.io/g/main/table?id=4607 so others can get a sense of how theirs might come out.

Glad to see CiviHosting being proactive with support. They are certainly marketing their migration and hosting services wherever they find a lead. 

Re: CiviHosting offers migration to DokuWiki #wikispaces #export #dokuwiki #civihosting

@willm
 

Update: 

CiviHosting was extremely responsive and helped me fix all the links in my wiki within a few hours. Our organization is very happy with the resulting DokuWiki.

Sorry, @Tom_H, our Wiki is private because it's internal to our organization. The results look quite similar to the main DokuWiki site, however, as it uses that template.

Re: CiviHosting offers migration to DokuWiki #wikispaces #export #dokuwiki #civihosting

CiviHosting
 

CiviHosting was extremely responsive and helped me fix all the links in
my wiki within a few hours. Our organization is very happy with the
resulting DokuWiki.
For the record, there was a glitch in our migrator tool which we found and fixed.

Glad to see CiviHosting being proactive with support. They are
certainly marketing their migration and hosting services wherever they find a lead.

We are and this is truly a win/win situation. We have several clients who are actually grateful to have found a resource who can migrate their wikis for them. Whereas Marc's directions for migrating to WordPress are fantastic and quite detailed, it is not possible for most non-technical users to do this migration alone.

Many users need someone who can migrate their wiki for them, and then support it as well and that's what we are offering.

Two more notes for completeness and transparency:

We are also offering migration to WordPress now as well. We had begun to unravel the process before Marc's post and we are now automating and generalizing his procedures to work for most any Wikispaces wiki.

Prices at editme.com begin at $19/month on https://www.editme.com/Pricing although once logged in, they do offer a $9/month plan as well, but it's a bit limited. These plans also are branded by "Powered by EditMe" and we haven't yet found how to add a Contact Us form on a wiki with them, but it may exist and we just can't find it.

CiviHosting's prices begin at $15 a month and that includes unlimited users, has no branding, and comes with other features like a contact us form and more.

Any specific questions about our services probably would best be directed to us privately offline, unless there is group interest. The link again to our Wikispaces Migration service is:

https://civihosting.com/wikispaces-migration/

Thank you,
CiviHosting

Batch Editing in Dokuwiki #edit #regexp

Tom H
 

Civihosting responded privately to my post in the main group about issues with some punctuation or other characters in page names and media filenames and that stimulated some interaction with my Dokuwiki trial out of which I've learned some useful things. I must give Civihosting credit for going through multiple re-migrations over the weekend as they tackled one problem after another. Are we there yet? Too soon for me to say as my time to inspect is limited and I want to record these other lessons I've learned on the user side that I have been exploring in parallel with their revisions to their migration tools.

Dokuwiki has optional plugins

Batch Editing with BatchEdit

I wanted to fix the broken links to images stored on postimages.org servers as reported. Can't do it in bulk on Wikispaces, can be done with Notepad++ on the exported files but they had already been imported into Civihosting's Dokuwiki. The default configuration has no global search & replace tool but Support suggested I look at BatchEdit. Alternatively, I could FTP download the pages (they are .txt files) and batch edit locally with Notepad++ and upload the revised files; however, that method would not record the changes in page histories.  

So I plunged ahead on the Admin page and learned how to search for and install an extension (or plugin). BatchEdit is a regular expression pattern matching tool, much more powerful than a simple string matcher, and more difficult to use. All I wanted to do was replace all instances of "postimg.org" with "postimg.cc". With BatchEdit, the search term has to be expressed "/postimg\.org/", sans quotes. The forward slashes demark the pattern to be matched while the backslash escapes the period to be taken literally, not as a wild card for any character. The replacement term, in this case, is simply "postimg.cc" but could have variables representing sub-pattern matches from the search.

But then I was confronted with the odd result that BatchEdit only found 9 matches in 2 files while Notepad++ found 32 in 15 of the original export and the same number in the migrated pages which I downloaded for comparison. I learned the following from the plugin developer who responded within an hour:

The plugin does not scan file system for pages like grep or Notepad++ do. Instead it uses DW page index, so it can find only those pages that DW search can find. It also takes into account DW ACL to ensure that users can modify only the pages they allowed to edit.

With a little more research, I learned that Dokuwiki builds its full text search index incrementally as users access pages, not all at once. As Civihosting had just done a fresh migration, only 2 of the 15 pages had been touched by anyone.

So how could I build a complete index short of browsing every page?

Batch Indexing with SearchIndex Manager

To the rescue, I found the SearchIndex Manager plugin. Launching it, you see a progress report of what page number it is working on out of the total to be indexed. It's not blazingly fast which makes me wonder if it is basically browsing each page in turn to trigger the indexer, not actually controlling the indexer directly. Perhaps there is a more direct way for those knowledgeable in the workings of Dokuwiki and PHP.

After SearchIndex completed, voila! BatchEdit found the 32 instances. A downside of BatchEdit is that you then have to select each instance you want replaced by checking a box, one at a time. Perhaps it is understandable that the developer wants the users to be very deliberate in their actions by inspecting the now and after states for every match but it seems a nuisance when accustomed to all or nothing decisions with Notepad++.

Re: Batch Editing in Dokuwiki #edit #regexp

Tom H
 

Buoyed by my success, I then went on to see if I could delete all the "Table of Content" sections that came from the Wikispaces ToC widget. They are badly rendered in Dokuwiki, are static and aren't needed because the Dokuwiki template includes a dynamic ToC on every page. Fortunately, I had used the widget on only some 30 of the 265 pages so, if I could come up with a reliable search expression, BatchEdit could take care of it for me without too much clicking of checkboxes and a darned sight faster than editing each page.

The magical search term is "/====== Table of Contents ======\n(\[\[#[^\]]+\]\]){0,}/" sans quotes.
The replace term is just the empty field.

The same expression without the quotes and forward slashes also works in Notepad++ on the Dokuwiki export; this may be the better place to strip out the static ToC in case your migration has to be repeated.

Before:

After:

Importing the sidebar menu #sidebar

Tom H
 

Wikispaces has a powerful sidebar menu that does not import well into DokuWiki. The examples below are from my Wikispaces site to my Civihosting trial site.

The original has headings as hyperlinks, the tag cloud widget and the Navigation page list widget showing 20 page names at a time. None of these are supported by DokuWiki. Wikispaces violates DokuWiki syntax by exporting the header links as headers; I had to remove the header format and the best I could do to highlight them was bolding. The widgets outputs are static links. Those from the tag cloud point to non-existent pages, named after each Wikispaces tag; the tags themselves are not exported so you have to start all over with tags in the way they are supported in DokuWiki. So I deleted the widgets outputs, leaving a comparatively short sidebar.

The link Go to Complete Page List links to an imported page that contains the static export from a widget that generated the list. Unfortunately this is now static. The closest thing to it is the Sitemap link on the top bar of the page template. Unfortunately, the original page name is lost in the migration process:

Exported filename: Source Templates - Convert Builtins to Editable, Split, Import (the name on the imported page list)

Converted filename: source_templates_-_convert_builtins_to_editable_split_import (the name on the DokuWiki Sitemap)


Wikispaces sidebar:


As imported:


Cleaned up:

Self-hosted DokuWiki Software Import

Marc M
 

I have made a lot of progress in setting up a system to import pages directly into the Dokuwiki software installed on a test server.  Outside of the obvious formatting search and replaces it actually is fairly easy, though the search and replaces can be complex.  The sidebar even begins to work with a little formatting tweaking.

I'm very much in the infancy of this so I don't have a good demo right now, and I am very pressed for time but after a half hour of work I have the beginning of a migration that is workable.  I still like my Wordpress migration the best but this may be a good alternative and less server-hungry for very large Wikis.

Re: Batch Editing in Dokuwiki #edit #regexp

Creuset
 

https://www.patreon.com/posts/find-and-replace-8484591

There is a "find and replace" function in this plugin by the main dokuwiki developer. Haven't tried it yet but thought you, or others, might find it helpful.

Re: CiviHosting offers migration to DokuWiki #wikispaces #export #dokuwiki #civihosting

Creuset
 

After exploring a lot of different options, we've taken the plunge and are going with CiviHosting. Will let you all know how it goes... :)

Re: Self-hosted DokuWiki Software Import

Marc M
 
Edited

Over the last few weeks I have learned a lot about Dokuwiki. 
Previously (as some of your know) I set up a migration to a Wordpress installation - which I was quite proud of.  The process wasn't too bad and the result looked and worked great. 

Unfortunately the editing process seemed complicated to people, even though it's pretty basic WYSIWYG editing.  Plus with nearly 900 pages it put a bit of a load on the shared and leased server.  

So I once again went through the various pieces of Open Source and free wiki software and kept coming back to Dokuwiki.  
The formatting is a bit simple but straightforward for other's to use, and since it doesn't use a MYSQL database or any database for that matter, it runs pretty smoothly on anything, even with lots of pages.  Unfortunately it was a bit more work to migrate into it and I had to use more search and replace en masse in a multi-file text editor and lots of complicated search expressions.  Finding ones that worked took the most time, once they did the editor replaced everyone in all 800+ files in less time than it took to take a sip of coffee.  I had to do some of the same replacements as for migration to Wordpress and then lots more.

The nice thing about Dokuwiki is that the wiki pages are stored in .txt files that you can easily FTP in and out of it.  Find that you need a tweak on a couple hundred pages?  No problem, make the changes to the local copies with the search and replace on an editor across all of the files that need editing, and then re-upload.

I tried to keep some notes on the process but unfortunately I didn't keep very good ones this time around.  If others are interested I can post my notes here and some other observations on conversion. 

I have much more to fix, like formatting and such but got the basics done.  I am running it on a few different servers for testing - my own, a friend's, and a couple free hosting sites even.  Here's one on a free site as a test - https://jeffcowiki.thats.im/doku.php/jefferson_county

So as not scare away some of our contributors I have made it look as close to Wikispaces as possible.

Re: Self-hosted DokuWiki Software Import

Tom H
 

Looking good. 

Two things bother me about migrating to DokuWiki:
  1. Wikispaces does not export a Page Name as a Heading, only as a file name. DokuWiki lower cases and substitutes underscores for the space character and other non-alphanumeric characters in the file name. The end result is that the DW Page Table of Contents tab contains the less readable, lowercase, underscore filled filename in fine print with no page heading (unless the original WS page had one added manually). And the sitemap lists these less readable filenames.
  2. WS Page Discussions cannot migrate well to DW because DW has to flatten a multitopic WS Discussion into one headingless series, assuming you can find a way to import them in the first place.
However, DW is not alone in presenting these problems. The first is partly the fault of the WS Export. I've asked that it include a top level heading of the Page Name. The second is also pretty common but I think MediaWiki supports multi-topic threaded discussions but with the expense of added complexity due to the need for a MySQL database.

Re: CiviHosting offers migration to DokuWiki #wikispaces #export #dokuwiki #civihosting

Tom H
 

If yours is a public wiki, I hope you will share your URL in the Database Table on the main forum with an announcement of when you have posted it. And please do not exercise the Domain Forwarding feature immediately so that we have time to review the before and after sites!

Help

Lynnea Roon
 

I have a wikispaces called RoonScience
All my video links I show as a teacher on it.
Is there a way to just copy and paste it all at once to a new website.... keeping all the titles that connect to each link..
Can it be that simple?

Lynnea Roon

On Fri, May 4, 2018, 5:09 PM Tom H <ve3meo@...> wrote:
If yours is a public wiki, I hope you will share your URL in the Database Table on the main forum with an announcement of when you have posted it. And please do not exercise the Domain Forwarding feature immediately so that we have time to review the before and after sites!

Re: Self-hosted DokuWiki Software Import

Marc M
 

Hey Tom, this got me thinking about a few things.

I found the Admin option called "Use first heading for pagenames", which seems to totally solve this. 

In the pages where I had an actual heading tag all of the display of those page titles were nice names with capitals and punctuation.  Problem solved - except it only worked for a few minutes and now I am getting an error called "Security Token did not match. Possible CSRF attack." and it reset this option back to default (off), so I have to sit down and figure out what's going on with that.  It worked great when it was working though :(

I don't think we're going to find a lot that is going to be perfect for transferring the discussions.  But there is a nice discussion plugin that I set up and tried on one of my other installations that can be automatically added to the end of each page - I was figuring that I would copy and paste any relevant discussions to a box above this discussion area and then people could continue on with whatever they needed to talk about.  Not the best solution but, well...

Re: Self-hosted DokuWiki Software Import

Marc M
 

Ah, okay, weird coincidence - tis free hosting company (GoogieHost) gave me a free SSL certificate and that's why the error came up. 

So anyway, Tom and all - if you take a look at some of the main pages you can see that the page titles look nic and are taken from the headings in each page.  Of course, now I have 800+ pages to fix, and I'm not sure that I can build a search and replace that will do it for me.  Possibly.


So I changed the link above and here it is again - https://jeffcowiki.thats.im/doku.php/jefferson_county


Re: Help

Tom H
 

Not so simple... But, fortunately, your Wikispaces Classroom site comprises only two pages with no use of WS exclusive features. You can readily create a basic HTML website and copy each page from your browser into the website's page editor. All your links are to external URLs and do not need revision. However, the on-page images are from files stored on WS. You will need to download them from WS and upload them to the new site and then change the image links on your new site from the old to the new.

Wikispaces streamlines the process with its Export utility in Settings. Use the HTML option. It will make available to you a zip file containg your HTML pages and the media files, linked. You can upload these to a blank website and be pretty much finished apart from building a home page and maybe a navigation menu.