Joomla! Issue Tracker | Joomla! CMS #25467 - [4.0] Test upgrade path from Joomla 3 to Joomla 4 on Postgres

J4 Issue ?

Closed
9 Jul 2019
Medium
Build: staging
# 25467

wilsonge
7 Jul 2019

@alikon @richard67 (or anyone else running postgres) can you please test the following:

Install a copy of Joomla 3.x (I was using 3.9.9 RC) on postgres
Use the upload file functionality with the latest nightly (https://developer.joomla.org/nightly-builds.html)
Check if Joomla upgrades successfully

Caveats:

On the intermediate authentication pages you'll get template not found warnings (and the styling is not optimal)
But once you get the Update finished page then you need to navigate to any other page and then proceed without any issues.

However I expect the upgrade to actually work in functionality

wilsonge - open - 7 Jul 2019

joomla-cms-bot - change - 7 Jul 2019

Labels

Added: ?

joomla-cms-bot - labeled - 7 Jul 2019

richard67 - comment - 7 Jul 2019

Ok, will do that tomorrow evening after work, German time.

franz-wohlkoenig - change - 8 Jul 2019

Labels

Added: J4 Issue

franz-wohlkoenig - labeled - 8 Jul 2019

franz-wohlkoenig - change - 8 Jul 2019

Status

New

⇒

Discussion

alikon - comment - 8 Jul 2019

let me invite @twister65 to this postgresql party

twister65 - comment - 8 Jul 2019

I have this error during the upgrade:

It means that the timestamp of "checked_out_time" in

joomla-cms/administrator/components/com_admin/sql/updates/postgresql/4.0.0-2016-10-02.sql

Lines 7 to 8 in 0f83986

    
           ('atum', 'template', 'atum', '', 1, 1, 1, 0, '{}', '{}', '', '', 0, '0000-00-00 00:00:00', 0, 0), 
        
           ('cassiopeia', 'template', 'cassiopeia', '', 0, 1, 1, 0, '{}', '{}', '', '', 0, '0000-00-00 00:00:00', 0, 0);

is not correct, it should be:
'1970-01-01 00:00:00' instead of '0000-00-00 00:00:00'

twister65 - comment - 8 Jul 2019

Error
The template for this display is not available.

I've got the same error with MySQL.

twister65 - comment - 8 Jul 2019

After building a new update package, I have this error:

It means that the home expression should be smallint and not text.

joomla-cms/administrator/components/com_admin/sql/updates/postgresql/4.0.0-2016-10-02.sql

Lines 11 to 12 in 0f83986

    
           ('atum', 1, (CASE WHEN (SELECT count FROM (SELECT count("id") AS count FROM "#__template_styles" WHERE home = '1' AND client_id = 1 AND "template" IN ('isis', 'hathor')) as c) = 0 THEN '0' ELSE '1' END), 'atum - Default', '{}'), 
        
           ('cassiopeia', 0, (CASE WHEN (SELECT count FROM (SELECT count("id") AS count FROM "#__template_styles" WHERE home = '1' AND client_id = 0 AND "template" IN ('protostar', 'beez3')) as c) = 0 THEN '0' ELSE '1' END), 'cassiopeia - Default', '{}');

alikon - comment - 8 Jul 2019

@twister65 can you add your findings to #25461 if you want
https://github.com/joomla/joomla-cms/pull/25461/files#diff-18dfb1b9c26a65fe27454cb3d7081eb0
branch is open even if is most related to mysql

twister65 - comment - 8 Jul 2019

@alikon , I can't push in your branch:

Unable to push
remote: Permission to alikon/joomla-cms.git denied to twister65.
fatal: unable to access 'https://github.com/alikon/joomla-cms.git/': The requested URL returned error: 403

Should I make a PR ?

richard67 - comment - 8 Jul 2019

@twister65 Would be good if you could make a PR. I don't think it was a good idea by @alikon to add that to his PR, because his PR is focused on mysql and we should not mix things.

alikon - comment - 8 Jul 2019

not a problem do as it is best for you

richard67 - comment - 8 Jul 2019

@wilsonge With twister's PR #25477 applied to the update package from last nightly build, the SQL errors disappear, and the behavior becomes like you described above, i.e. there are "template not found" warnings, but they disappear when update is finished and you are navigating through backend. So that PR makes the update finish without crash.

But there remain other issues to be handled. The first thing I saw is that com_search has been removed, but the menu entry in the left side admin menu in backend is still there. I don't dare to think about what will happen when updating a site with a search module in frontend. Do you have any plan for that already?

franz-wohlkoenig - comment - 9 Jul 2019

Closed as having Pull Request #25477

franz-wohlkoenig - change - 9 Jul 2019

Status	Discussion	⇒	Closed
Closed_Date	0000-00-00 00:00:00	⇒	2019-07-09 04:04:56
Closed_By		⇒	franz-wohlkoenig

franz-wohlkoenig - close - 9 Jul 2019

Add a Comment

Older
Newer

Joomla! Issue Tracker - CMS

[#25467] - [4.0] Test upgrade path from Joomla 3 to Joomla 4 on Postgres

Add a Comment

	('atum', 'template', 'atum', '', 1, 1, 1, 0, '{}', '{}', '', '', 0, '0000-00-00 00:00:00', 0, 0),
	('cassiopeia', 'template', 'cassiopeia', '', 0, 1, 1, 0, '{}', '{}', '', '', 0, '0000-00-00 00:00:00', 0, 0);

	('atum', 1, (CASE WHEN (SELECT count FROM (SELECT count("id") AS count FROM "#__template_styles" WHERE home = '1' AND client_id = 1 AND "template" IN ('isis', 'hathor')) as c) = 0 THEN '0' ELSE '1' END), 'atum - Default', '{}'),
	('cassiopeia', 0, (CASE WHEN (SELECT count FROM (SELECT count("id") AS count FROM "#__template_styles" WHERE home = '1' AND client_id = 0 AND "template" IN ('protostar', 'beez3')) as c) = 0 THEN '0' ELSE '1' END), 'cassiopeia - Default', '{}');