Friendica/upgrading - Revision history

Woozle: /* upgrade to 2018-09 */

2019-10-13T18:39:32Z

upgrade to 2018-09

← Older revision		Revision as of 18:39, 13 October 2019
Line 42:		Line 42:
	#* <code>bin/console dbstructure update</code>		#* <code>bin/console dbstructure update</code>

	At this point I encountered [[User:Woozle/Friendica/2019 upgrade\|many hairy database errors]].		At this point I encountered [[User:Woozle/Friendica/2019 upgrade\|many hairy database errors]], which I was able to resolve.

			Reloading the current page in the web installer returned a different message:

			[[File:2019-10-13.screenshot.ICMS Friendica maintenance message.png\|400px]]

	==Documentation Whine==		==Documentation Whine==

Woozle: /* upgrade to 2018-09 */

2019-10-13T01:19:20Z

upgrade to 2018-09

← Older revision		Revision as of 01:19, 13 October 2019
Line 42:		Line 42:
	#* <code>bin/console dbstructure update</code>		#* <code>bin/console dbstructure update</code>

	At this point I encountered ~~several large, complicated-looking~~ database errors.		At this point I encountered [[User:Woozle/Friendica/2019 upgrade\|many hairy database errors]].

	==Documentation Whine==		==Documentation Whine==

Woozle at 01:15, 13 October 2019

2019-10-13T01:15:12Z

← Older revision		Revision as of 01:15, 13 October 2019
Line 28:		Line 28:
	</pre>		</pre>
	====upgrade to 2018-09====		====upgrade to 2018-09====
			I've <s>struck out</s> steps which turned out to be dead-ends.
	# Unzip the [https://github.com/friendica/friendica/files/2409065/friendica-full-2018.09.tar.gz v2018-09] Friendica distribution		# Unzip the [https://github.com/friendica/friendica/files/2409065/friendica-full-2018.09.tar.gz v2018-09] Friendica distribution
	# Rename ~~the configuration file (~~.htaccess-dist) to .~~htconfig~~.php ~~(TO BE TESTED)~~		# <s>Make it accessiable to the web</s>
	# ~~Edit the configuration file~~ to have the ~~proper access~~ parameters for your ~~Friendica~~ database.		# <s>Rename <code>.htaccess-dist</code> to <code>.htaccess</code></s>
			# <s>Browse your Friendica domain in order to access the web installer.</s>
			# <s>Fix any errors and enter the database information into the web installer.</s>
			#* <s>You will get a "Database already in use" message if this works.</s> (Nope: this does not write the config file.)
			# Copy <code>config/local-sample.ini.php</code> to <code>config/local.ini.php</code>
			# Modify <code>config/local.ini.php</code> to have the connection parameters for your Friendical database.
			#* If your database's password contains any "$" characters, be sure to prefix them with backslashes: "pa$$word" -> "pa\$\$word"
	# From the {{arg\|fka-root}} folder, run:		# From the {{arg\|fka-root}} folder, run:
	#* <code>chmod +x bin/console</code>		#* <code>chmod +x bin/console</code>
	#* <code>bin/console dbstructure update</code>		#* <code>bin/console dbstructure update</code>

	~~''in progress''~~		At this point I encountered several large, complicated-looking database errors.

	==Documentation Whine==		==Documentation Whine==

Woozle at 23:01, 12 October 2019

2019-10-12T23:01:34Z

← Older revision		Revision as of 23:01, 12 October 2019
Line 28:		Line 28:
	</pre>		</pre>
	====upgrade to 2018-09====		====upgrade to 2018-09====
			# Unzip the [https://github.com/friendica/friendica/files/2409065/friendica-full-2018.09.tar.gz v2018-09] Friendica distribution
			# Rename the configuration file (.htaccess-dist) to .htconfig.php (TO BE TESTED)
			# Edit the configuration file to have the proper access parameters for your Friendica database.
			# From the {{arg\|fka-root}} folder, run:
			#* <code>chmod +x bin/console</code>
			#* <code>bin/console dbstructure update</code>

	''in progress''		''in progress''

Woozle: /* Steps */

2019-10-12T22:52:13Z

Steps

← Older revision		Revision as of 22:52, 12 October 2019
Line 8:		Line 8:
	The configuration file is <code>{{arg\|fka-root}}/.htconfig.php</code>, although it is distributed without the dot prefix (just <code>htconfig.php</code>).		The configuration file is <code>{{arg\|fka-root}}/.htconfig.php</code>, although it is distributed without the dot prefix (just <code>htconfig.php</code>).

	# Unzip ~~or [[git clone]]~~ the ~~version of~~ Friendica ~~to which you are trying to upgrade.~~		====upgrade to 3.5.4====
			# Unzip the Friendica distribution
	# Rename the configuration file to .htconfig.php.		# Rename the configuration file to .htconfig.php.
	# Edit the configuration file to have the proper access parameters for your Friendica database.		# Edit the configuration file to have the proper access parameters for your Friendica database.
	# Open a terminal in {{arg\|fka-root}} and run:		# Open a terminal in {{arg\|fka-root}} and run:
	#* <code>~~bin~~/~~console dbstructure update~~</code> ('''~~NOTE~~'~~'':~~ this ~~folder does not exist~~ in 3.5.4~~; trying~~ to ~~find out what the equivalent is)~~		#* <code>php util/db_update.php</code>
			#* This will probably give warnings, but seems to complete even under PHP 7.2.
			<pre>
			$ php util/db_update.php
			PHP Warning: count(): Parameter must be an array or an object that implements Countable in /home/icms/domains/hey.iseeamess.com/site/git/friendica-3.5.4/include/pgettext.php on line 45
			PHP Warning: Invalid argument supplied for foreach() in /home/icms/domains/hey.iseeamess.com/site/git/friendica-3.5.4/include/pgettext.php on line 111
			Old DB VERSION: 1159
			New DB VERSION: 1234
			Updating database...
			Error 1050 occurred during database update:
			Table 'temp-addon' already exists
			PHP Warning: Use of undefined constant dbesc - assumed 'dbesc' (this will throw an Error in a future version of PHP) in /home/icms/domains/hey.iseeamess.com/site/git/friendica-3.5.4/include/dbstructure.php on line 47
			Done
			</pre>
			====upgrade to 2018-09====

	''in progress''		''in progress''

Woozle: /* Steps */

2019-10-12T22:43:45Z

Steps

← Older revision		Revision as of 22:43, 12 October 2019
Line 7:		Line 7:

	The configuration file is <code>{{arg\|fka-root}}/.htconfig.php</code>, although it is distributed without the dot prefix (just <code>htconfig.php</code>).		The configuration file is <code>{{arg\|fka-root}}/.htconfig.php</code>, although it is distributed without the dot prefix (just <code>htconfig.php</code>).

			# Unzip or [[git clone]] the version of Friendica to which you are trying to upgrade.
			# Rename the configuration file to .htconfig.php.
			# Edit the configuration file to have the proper access parameters for your Friendica database.
			# Open a terminal in {{arg\|fka-root}} and run:
			#* <code>bin/console dbstructure update</code> ('''NOTE''': this folder does not exist in 3.5.4; trying to find out what the equivalent is)

	''in progress''		''in progress''

	==Documentation Whine==		==Documentation Whine==
	Database upgrade instructions are still difficult to find as of v2019-09:		Database upgrade instructions are still difficult to find as of v2019-09:

Woozle at 22:36, 12 October 2019

2019-10-12T22:36:28Z

← Older revision		Revision as of 22:36, 12 October 2019
Line 2:		Line 2:
	This page is about upgrading Friendica instances.		This page is about upgrading Friendica instances.
	===Steps===		===Steps===
	To determine what version you are currently running, look at the <code>VERSION</code> file ~~located~~ in the ~~deployment root~~.		The folder where you put Friendica – which should be the same as your public web folder (typically <code>public_html</code>), will be referred to as {{arg\|fka-root}}.

			To determine what version you are currently running, look at the <code>{{arg\|fka-root}}/VERSION</code> file. Upgrading must be done in stages: 3.54, 2018-09, and finally 2019-09.

			The configuration file is <code>{{arg\|fka-root}}/.htconfig.php</code>, although it is distributed without the dot prefix (just <code>htconfig.php</code>).

	''in progress''		''in progress''

Woozle at 19:25, 12 October 2019

2019-10-12T19:25:02Z

← Older revision		Revision as of 19:25, 12 October 2019
Line 1:		Line 1:
	==About==		==About==
			This page is about upgrading Friendica instances.
			===Steps===
			To determine what version you are currently running, look at the <code>VERSION</code> file located in the deployment root.

			''in progress''
			==Documentation Whine==
	Database upgrade instructions are still difficult to find as of v2019-09:		Database upgrade instructions are still difficult to find as of v2019-09:
	* Update instructions on the [https://friendi.ca/2019/09/29/friendica-2019-09-released/ 2019-09 release page] say "please first update your Friendica instance to [v2018-09]".		* Update instructions on the [https://friendi.ca/2019/09/29/friendica-2019-09-released/ 2019-09 release page] say "please first update your Friendica instance to [v2018-09]".
Line 13:		Line 19:

	This means that the automated upgrade may fail, and the SQL to create or modify tables will have to be tweaked and executed manually. (Details may change from version to version, but my notes are [[User:Woozle/Friendica/2017 upgrade\|here]].)		This means that the automated upgrade may fail, and the SQL to create or modify tables will have to be tweaked and executed manually. (Details may change from version to version, but my notes are [[User:Woozle/Friendica/2017 upgrade\|here]].)
	==Old Notes==		===Old Notes===
	Notes I took during the last upgrade seem to indicate that there was a way to explicitly request a db upgrade in the "admin area", but I haven't been able to find the admin area yet in the current version (which isn't currently working; hopefully when I get it working, it will appear and I can update this section).		Notes I took during the last upgrade seem to indicate that there was a way to explicitly request a db upgrade in the "admin area", but I haven't been able to find the admin area yet in the current version (which isn't currently working; hopefully when I get it working, it will appear and I can update this section).

Woozle at 18:29, 12 October 2019

2019-10-12T18:29:37Z

← Older revision		Revision as of 18:29, 12 October 2019
Line 1:		Line 1:
	==About==		==About==
	Documentation for upgrading Friendica's code and database schema is minimal or at least difficult to find~~. As~~ of 3.5.2-dev~~, the~~ following ~~was~~ applicable<ref name=woozle1 />:		Database upgrade instructions are still difficult to find as of v2019-09:
			* Update instructions on the [https://friendi.ca/2019/09/29/friendica-2019-09-released/ 2019-09 release page] say "please first update your Friendica instance to [v2018-09]".
			* Update instructions on the [https://friendi.ca/2018/09/23/friendica-2018-09-released/ 2018-09 release page] say "First update to the 3.5.4 release", but do not link to instructions.
			* The [https://friendi.ca/2017/10/16/friendica-3-5-4-release/ 3.5.4 release page] does not seem to have any update instructions.

			Documentation for upgrading Friendica's code and database schema was minimal or at least difficult to find as of 3.5.2-dev. The following were applicable<ref name=woozle1 />:
	# Friendica automatically detects database issues and, when they are encountered, attempts to run a database upgrade.		# Friendica automatically detects database issues and, when they are encountered, attempts to run a database upgrade.
	# Before starting, it automatically puts the site into maintenance mode.		# Before starting, it automatically puts the site into maintenance mode.

Woozle: things I figured out during the 2017 upgrade, link to more extensive but highly specific SQL, and moved old update notes from main page

2017-04-08T13:25:32Z

things I figured out during the 2017 upgrade, link to more extensive but highly specific SQL, and moved old update notes from main page

New page

==About==
Documentation for upgrading Friendica's code and database schema is minimal or at least difficult to find. As of 3.5.2-dev, the following was applicable<ref name=woozle1 />:
# Friendica automatically detects database issues and, when they are encountered, attempts to run a database upgrade.
# Before starting, it automatically puts the site into maintenance mode.
# If the upgrade completes successfully, it presumably takes the site back out of maintenance mode.
# If the upgrade does not complete successfully, there are no notifications to this effect; you have to check the logfile for errors.
# The current schema – much like [[Hubzilla]]'s – has many table rows which try to set a default value for a DATETIME column, which (as of [[MySQL]] v5.7.17) may be disallowed by the server configuration.<ref name=woozle2 />

This means that the automated upgrade may fail, and the SQL to create or modify tables will have to be tweaked and executed manually. (Details may change from version to version, but my notes are [[User:Woozle/Friendica/2017 upgrade|here]].)
==Old Notes==
Notes I took during the last upgrade seem to indicate that there was a way to explicitly request a db upgrade in the "admin area", but I haven't been able to find the admin area yet in the current version (which isn't currently working; hopefully when I get it working, it will appear and I can update this section).

Previous notes said:

The update process does not always go smoothly. If you see a message like this in the admin db_updates area:
Executing update_1141 failed. Check system logs.
...then what you need to do is view the update.php file, manually execute the given SQL (adjusting permissions or whatever is necessary until it has executed), and then click the "DB updates" link again to get the list of failed updates (in this case, it should show 1141) and then click on the link which says "Mark success (if update was manually applied)".

==Footnotes==
<references>
<ref name=woozle1>'''2017-04-08''' [https://plus.google.com/+WoozleHypertwin/posts/6sdxEx1vEcz Friendica migration follow-up post]</ref>
<ref name=woozle2>''ibid.'' If the MySQL server is in strict mode and [http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_no_zero_date NO_ZERO_DATE] is enabled, default values for DATETIME columns must be between '1970-01-01 00:00:01' and '2038-01-19 03:14:07' inclusive. "DEFAULT '0001-01-01 00:00:00'" is therefore disallowed, as are the many '0000-00-00 00:00:00' column values. (Found via [http://stackoverflow.com/questions/9192027/invalid-default-value-for-create-date-timestamp-field Stack Overflow].)</ref>
</references>