Changes

Jump to: navigation, search

Rollover for the manual

72 bytes added, 00:09, 29 May 2018
Rolling over the Gramps user manual
== Rolling over the Gramps user manual ==
On this page, <code>35.x</code> refers to the 'old' (current) version of the manual - <code>35.z</code> refers to the new, to be created, version...#Use phpmyadmin to backup all of the wiki tables(or the commandline if phpmyadmin times out!)! #Locate all pages on the wiki that have 3<code>5.x </code> in the title - from the {{man label|wiki: toolbox, Special pages}}, All pages to get a full list of wiki pages.
#Copy/paste it into text processor - it may be in three columns separated by tabs. If so, use regular expression search/replace to replace tabs with carriage returns. Using GEDIT, best to replace <code>\t</code> with <code>\n</code> rather than <code>\r</code>. You now have a list of all files on the wiki, one title per line. Save it as a text file (I'll call it <code>myfile.txt</code> for this example).
#Use grep to find only the pages with <code>35.x</code> in the title: ''<code>grep "35\.x" myfile.txt > mynewfile.txt</code>'' The backslash will make the full stop a literal rather than trying to be part of a regular expression.#Use a text editor to view the new file, and delete any pages that you don't want to roll over (That is, some pages may refer to <code>35.x</code> in the title, but are not pages that we want duplicated into <code>35.z</code>...)
#Copy/paste the new list of page titles into the wiki export using toolbox, Special pages, Export pages and create the xml to screen. {{man menu|Be sure box for Include only the current revision, not the full history is ticked.}}
#Copy/paste the xml into a text processor and use search/replace to replace <code>35.x</code> with <code>35.z</code>
#Save the file (I'll call it <code>export.xml</code> for this example).
For the change to <code>35.4</code> and then from <code>35.4</code> to <code>46.0</code>, I used a script in the maintenance directory to import xml from the command line. I was successful with (but I got an error in <code>importDump.php</code> and had to edit the file to ensure that <code>Maintenance.php</code> was included properly!):
'''-bash-3.2$<code>php importDump.php 3454.xml</code>'''
followed by:
* <code>filename-{number of version}-{lang}.extension</code>
ex:
* <code>Edit-person-4050-en.png</code>
We need to know if we keep the {number of version} or if we use the new one on migration (3.1->3.2->4.0->15.0...) ?

Navigation menu