15,534
edits
Changes
→Regenerate Version-Specific Content
== Rolling over the Gramps user manual ==On this page, <code>5.x</code> refers to the 'old' (current) version of the manual - <code>5.z</code> refers to the new, to be created, version...#Use phpmyadmin to backup all of the wiki tables (if phpmyadmin times out use the commandline )!** [NOTEhttps://au.godaddy.com/help/exporting-mysql-database-in-ssh-26367 Command line: Updating through multiple xml ] <code>mysqldump -p -h hostname -u username database > dbname.sql</code>#Locate all pages on the wiki that have <code>5.x</code> in the title - from the {{man label|wiki menu: [[Special:AllPages|Tools > Special pages > All pages]]}}, page by page copy the text 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 not necessary nowon the wiki, as we have command one title per line access to our hosting account.] There are serious restrictions Save it as a text file (I'll call it <code>myfile.txt</code> for both this example).#Use grep to find only the pages with <code>5.x</code> in the title: ''<code>grep "5\.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 size , and processing time delete any pages that you don't want to roll over (That is, some pages may refer to <code>5.x</code> in the title, but are not pages that we want duplicated into <code>5.z</code>...)#Go to the {{man label|wiki menu: [[Special:Export|Tools > Special pages > Export pages]]}} and Copy/paste the new list of page titles into the {{man label|Add pages manually:}} section then {{man menu|Be sure the checkbox is ticked for {{man label|Include only the scripts - I had current revision, not the full history}}}} and then to create the xml to split screen press the {{man label|Export}} button.#Copy/paste the xml file into 8 pieces a text processor and use search/replace to get replace <code>5.x</code> with <code>5.z</code> #Save the file (I'll call it all uploaded.<code>export.xml</code> for this example).
=== Import xml from the command line===For the change to 3<code>5.4 </code> and then from 3<code>5.4 </code> to 4<code>6.0</code>, I used a the mediwiki script in the maintenance directory to import xml from the command line. The GoDaddy hosting service uses I was successful with (but I got an old version of error in <code>importDump.php from </code> and had to edit the command line, but I file to ensure that <code>Maintenance.php</code> was successful withincluded properly!):
'''-bash-3.2prompt$ /usr/local/php5/bin/<code>php importDump.php 34export.xml</code>'''
followed by:
'''-bash-3.2prompt$ /usr/local/php5/bin/<code>php rebuildrecentchanges.php</code>'''
That should now have created all of the new pages.
That updates a blob field to force protection without having to do the pages individually. You need to do the above sql statement for each page that you want to protect...
*Copy the resulting SQL statement to a text file <code>protectoldpages.txt</code>* check the SQL statements syntax [https://www.piliapp.com/mysql-syntax-check/ here]* Then run the SQL statement by either using phpmyadmin("SQL" tab to run the query) or the commandline. Backup the database. ===Screenshots===As there is no [[Available_screenshotsScreenshots|naming scheme]] we are trying to follow a rule for manual updgrade upgrade : * <code>filename-{number of version}-{lang}.extension</code>
ex:
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...) ?
===Regenerate Version-Specific Content===
Update files dependency list :
''The documentation assumes the default (English-US) language on Linux''
Edit the manual section :
<code> https://gramps-project.org/wiki/index.php?title=Gramps_{{Version manual}}_Wiki_Manual_-_Command_Line&action=edit§ion=8</code>
Copy (or pipe) the updated Gramps installation output from the command line Version option :
<code> gramps -v</code>
Replace any user-specific directory information with '''<~username>'''
If appropriate, please reference the Gramps [[Gramps_5.1_Wiki_Manual_-_User_Directory|User Directory]] page instead of redundantly explaining the directory paths under any of the multiuser OSes.
<code>[[Gramps_5.1_Wiki_Manual_-_User_Directory|User Directory]]</code>
Gramps user directory available on various operating systems.
==Version manual template==
Update the current ( {{Version manual}} ) version number using on [[:Template:Version_manual]] for pages outside of the user manual.
Manually update any REDIRECT pages also eg: "Third-party Addons" link redirects to 5.1 Addons etc..
==Email announcement==
Send the following email announcement (see embedded email) to the mailing list.
<!--
Hello,
Due to scheduled maintenance the Gramps Wiki services will be unavailable for most of the day on Sunday, 23rd of June 2019.
Please Note: during this offline period you may still be able to view the wiki.
The wiki software Mediawiki is being upgraded.
Then Gramps User Manual is being rolled over for the upcoming release of Gramps 5.1.x.
Apologies for any inconvenience that this may cause and thank you for patience and understanding.
Regards,
Sam
Volunteer Website Administrator
The Gramps Project
-->
<!--
Hello,
The rollover of the wiki user manual pages in preparation for the 5.1 version has been completed.
Please let me know if you see any obvious problems with the rollover.
Over the next few days, I'll be making all of the 5.0 manual pages non-editable, so please only edit the new 5.1 manual.
Sam
Volunteer Website Administrator
The Gramps Project
-->
==See also==
* [[User manual]]
* [[Manual Generation 3.0]]
* [[What to do for a release]]
[[Category:Developers/General]]