Discuss Joomla! 4.3.0

[ch2856]

New tags router
So pagination works fine now, but for general tags, that are not linked to a menu, it adds to the URL ?Itemid=104 so - xxx.com/component/tags/tag/tag-alias?Itemid=104

[PhilTaylor-Prazgod]

New tags router

Maybe related to this bug in Joomla 4.3.0

https://github.com/joomla/joomla-cms/issues/40423

[mikepritchard]

THE WORKAROUND for this issue at the moment is to MANUALLY upload the WHOLE Joomla 4.3.0 files using FTP and then MANUALLY DELETE administrator/cache/autoload_psr4.php and then you should be able to login again - Then go to System -> Database and ensure all database tables are up to date (this also runs script.php if needed). This restores the missing files and is enough for you to get back into your site.

Thanks Phil, solved my problem on a few sites.
You are my hero for the day!

[JasnaSontag]

For those having the error:

Code: Select all

setcookie(): Expects exactly 3 arguments when argument #3 ($expires_or_options) is an array

For a temporary workaround:
Go to the 'language filter' system plugin and change the cookie lifetime parameter from 'Year' to 'Session'.

Thank you!

[obuisard]

To improve on our messaging, we wanted to let you know what are our upcoming plans:

Next Release: 4.3.1 (Off-cycle)
Release Date: Tuesday, 2-May-2023 (pending successful testing of fixes)
New Features: No
Bug Fixes: Yes
Security Fixes: No

Summary: The 4.3.1 release specifically addresses post release issues. After evaluating these issues with representatives from the major teams, it was determined to do an off-cycle release.

Additional information:
FAQ https://docs.joomla.org/Category:Version_4.3.0_FAQ
PRs included in the release https://github.com/joomla/joomla-cms/pu ... s%3Aclosed

The 4.3.1 release is meant to specifically address the post release issues. Other bug fixes are in progress and scheduled for release 4.3.2.

Looking Ahead: 4.3.2 scheduled for Tuesday, 30-May-2023

Olivier & SD

[PhilTaylor-Prazgod]

Well I guess thats better than nothing - although you could have said this hours ago when people were sat waiting for the release that never happened that had been announced in multiple places would take place at 1600UTC

[sozzled]

+1 @Phil

[obuisard]

The roadmap was modified April, 24 in that regard.
4.3.1 RC1 had to be pushed back due to a release blocker preventing the release.

[PhilTaylor-Prazgod]

Even though that page https://developer.joomla.org/roadmap.html states “ Last Updated: 18 April 2023”- and that pages clearly state the current release is “4.3.1” LMAO!

[obuisard]

Yes, very funny indeed.
The date at the bottom of the file was a mistake, the dates you should be looking at are at https://developer.joomla.org/roadmap.html#R43.

[tansely]

This issues happens even if you are at Joomla 4.2.9. I have rolled back to 4.2.9 by using akaabe backup and also by using zip downgrade version. Everything was fine till today. And tody all of sudden I have same cookie, login issues.

Solution is very simple. Delete additional directories created on all the class error subdirectories.

Code: Select all

rm -Rf plugins/authentication/joomla/services
rm -Rf plugins/authentication/joomla/src

You dont need to disable or re install any plugins as explained above. Just delete 'services' and 'src' subdirectories.

In my case I have deleted below subdirectories

Code: Select all

rm -Rf plugins/content/emailcloak/services
rm -Rf plugins/content/emailcloak/src
rm -Rf plugins/content/fields/services
rm -Rf plugins/content/fıelds/src
rm -Rf plugins/authentication/joomla/services
rm -Rf plugins/authentication/joomla/src
rm -Rf plugins/content/contact/services
rm -Rf plugins/content/contact/src

[PhilTaylor-Prazgod]

I have rolled back to 4.2.9

There is no need to roll back - all the bugs in Joomla 4.3.0 now have solutions that are documented in this thread and copied to the official documentation here: https://docs.joomla.org/Category:Version_4.3.0_FAQ

I have rolled back to 4.2.9 by using akaabe backup

But did you clear your webspace of files first - no you did not, so you just overwrote what was there, and you left the additional files in place. Thats why it will not work.

by using zip downgrade version

There is no such thing as a Zip downgrade version. Joomla only supports upgrades, not downgrades. You are on your own when it comes to downgrades.

In my case I have deleted below subdirectories

There are also database changes that would need to be manually reverted, unless you also restored your database from backup

[darb]

Today there are 284 open Pull Requests, 125 of those are targeted at Joomla 4.3 but were not merged before 4.3.0 was released, The oldest PR goes back to 2019 which has now been pushed to Joomla 5!!! There are still 96 PR's targeted at the Joomla 4.2 branch, which is now end of life and superseded by Joomla 4.3 series.

There are 54 Pull Requests flagged as RTC (Ready to commit) that have not yet been merged into the codebase. The oldest of those goes back to Aug 19th 2022...

These are just facts, Im not making these up.

So whats the facts today? Is Joomla progressing to catch up with all these pull requests and merging? hmm

[PhilTaylor-Prazgod]

Look for yourself at https://github.com/joomla/joomla-cms/pulls

[darb]

Look for yourself at https://github.com/joomla/joomla-cms/pulls

Yes seems to be a small progress though -25 less now only 259.

284 - 259 = 25

Dont know how good or bad this is in many ways.

[edthenet]

Everyone,

I did have this same issue on one of my websites. I could not login to the administration anymore with a name and password. Luckily i also added web authentication so i could still login, because that did work. I did all kinds of investigation based on whatever i could find. Thanks Phil Taylor and al others.

Because the fact that i could still login was there. I just re-installed the core Joomla! files and the problem was fixed.

That doesn't mean that we don't need to find the source of this issue. So i can be of assistance to anyone just let me know.

[PhilTaylor-Prazgod]

That doesn't mean that we don't need to find the source of this issue. So i can be of assistance to anyone just let me know.

The root source of the issue has been completely ignored by the core Joomla contributors. I fully expect the next version to have the same issue for some reason.

There seems to be some extraction issue when extracting and writing the files, which leaves sites broken as some files are not there after upgrade, and then the upgrade finalisation scripts clean up old files, leaving the site in a broken state.

Ive seen no pull requests to resolve this issue, or to add more logging to the process, or to identify and fix the actual issue. At the moment all we have are many people all reporting the same symptoms - regardless of the process used to upgrade (using a 3rd party service, or using Joomla's own com_joomlaupdate plugin)