?
avatar astridx
astridx
18 Jun 2021

Steps to reproduce the issue

  1. Install Joomla 3.9.27
  2. Switch the Update Channel to “Custom URL” and and the Minimum Stability option to “Alpha” set the Custom URL to “https://update.joomla.org/core/nightlies/next_minor_list.xml”
    Now you get, update to the 3.10.0 Alpha Version.
  3. Switch the Update Channel to “Custom URL” and and the Minimum Stability option to “Release Candidate” set the Custom URL to “https://update.joomla.org/core/nightlies/next_major_list.xml”
    Now you get, update to the latest 4.0 Development Version.

Expected result

Update works

Actual result

After the update to 3.10
1

I see this message:
0

After the update to 4.0.0
8

I see this message:
7

The Pre Update Checker has no entry, because it was a fresh installation
00

System information (as much as possible)

php: Linux php80_mysql 5.8.0-53-generic #60~20.04.1-Ubuntu SMP Thu May 6 09:52:46 UTC 2021 x86_64
dbserver: mysql
dbversion: 5.7.34
dbcollation: latin1_swedish_ci
dbconnectioncollation: utf8mb4_general_ci
phpversion: 8.0.7
server: Apache/2.4.41 (Ubuntu)
sapi_name: apache2handler
version: Joomla! 3.9.27 Stable [ Amani ] 25-May-2021 15:00 GMT
platform: Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
useragent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:89.0) Gecko/20100101 Firefox/89.0

safe_mode: false
display_errors: true
short_open_tag: false
file_uploads: true
magic_quotes_gpc: false
register_globals: false
output_buffering: true
open_basedir:
session.save_path: xxxxxx
session.auto_start: 0
disable_functions: pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare,
xml: true

Additional comments

I tryed the update like explained here: https://www.joomla.org/announcements/release-news/5838

"Go to the Joomla Update Component Options and switch the Update Channel to “Testing” and the Minimum Stability option to “Alpha”." did not offer me an update.

Also "Switch the Update Channel to “Custom URL” and the Minimum Stability option to “Development” and set the Custom URL to “https://update.joomla.org/core/test/310to4_list.xml”" did not offer me an update.

What is my mistake?

avatar astridx astridx - open - 18 Jun 2021
avatar joomla-cms-bot joomla-cms-bot - change - 18 Jun 2021
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 18 Jun 2021
avatar zero-24
zero-24 - comment - 18 Jun 2021

Hmm is the database up-to-date when you start updating? The SQL error does not make sense on a quick look as the plugins are part of the package for a long time now.

Will check the update server xmls whethere there are issues and why it does not work for you.

avatar astridx
astridx - comment - 18 Jun 2021

I have freshly installed this for this issue to rule out other things. Could it be because of PHP 8?

avatar richard67
richard67 - comment - 18 Jun 2021

@astridx Have you done all that in an empty folder? Or have you used a git clone and only checked out branch and pulled? In this case or if the folder was not empty at the beginning there might be old SQL files which have been removed later. E.g. between 4.0 Beta 7 and RC 1 files have been removed.

avatar richard67
richard67 - comment - 18 Jun 2021

It cannot have anything to do with PHP 8.

avatar richard67
richard67 - comment - 18 Jun 2021

I think the folder in which the 3.9.27 was installed was not empty and contained some remainders from experiments with J4 Beta 7 or earlier, and so there were some of the files present which have been removed with PR #34139 in J4.

avatar astridx astridx - change - 19 Jun 2021
Status New Closed
Closed_Date 0000-00-00 00:00:00 2021-06-19 08:45:52
Closed_By astridx
avatar astridx astridx - close - 19 Jun 2021
avatar astridx
astridx - comment - 19 Jun 2021

Thanks for your answers. No. It can't be the files. I installed it fresh in real. If no one else is having the problem, it's probably my environment.

Add a Comment

Login with GitHub to post a comment