Discuss Joomla! 3.9.26

[AlexVega]

I do backups, I don't use extensions.

[chrisbath2]

I've lost a day to this so far.

I know it is probably my fault for having an ancient template (and for being non-technical) , but 3.9.26 broke our charity's site.

Error messages across the site.

Joomla\CMS\Filesystem\Folder::create: Could not create folder.Path: /homepages/18/d744239237/htdocs//cache/template

Inexplicably didn't back up as discussed here. But I can't even restore an earlier backup because the extraction fails because it cannot open /homepages/18/d744239237/htdocs/***URL removed***/installation/README.html

I cannot actually backup the site as it is:

Cannot save factory state in storage, storage filename /homepages/18/d744239237/htdocs/***URLremoved***//administrator/components/com_akeeba/backup/akstorage_backend.172.dat

I cannot upload an earlier version of Joomla core because it says my Super User login is invalid.

Notably, our test site, which uses an up to date template worked fine.

Also notably, I started having issues under 3.9.25 when some important extensions would no longer update. Something seems to have got corrupted.

[Webdongle]

...

Also notably, I started having issues under 3.9.25 when some important extensions would no longer update. Something seems to have got corrupted.

And you never thought to fix the errors before updating?
No backup? Ask your Host to roll back.

[sozzled]

Automatic backup on update is now working as a result of updating to Akeeba Backup v8.0.4. All good.

Make sure that you update to the v8.0.4 of Akeeba Backup before you run the Joomla! Update process (for those people who want to use J! to make their backups).

Thank you to everyone who helped with the automatic backup problem. I have no other comment about J! 3.9.26 apart from my long-standing criticism of the developers who do not visit this forum or that the developers have never thanked the community for what we do here.

Y'know, I think a lot of goodwill could be rebuilt between the developers and the community if Harald popped in here and wrote two words ...

[Webdongle]

Automatic backup on update is now working as a result of updating to Akeeba Backup v8.0.4. ...

Yep, took me a while to spot Akeeba v.8.0.4 wasn't showing in Extensions >>> Manage update.

N.B.
Anyone using Akeeba and not changing the save folder for jpa files ... the jpa back up files get wiped.

[Fan33GR]

3 sites updated, all OK. Thanks to the team!

(I don't use Akeeba backup, I have automatically daily backup from the host company and I create manually a backup just before every update to new Joomla version to be sure)

How easy is it to backup/reinstall manually compared to Akeeba/Kickstart?
How easy is it to avoid human error backup/reinstall manually compared to Akeeba/Kickstart?

Hi Webdongle,
It just happens to not have Akeeba Backup, I have see excellent reviews for it (and I use admin tools from the same company which I'm very satisfied), but I have used to this way because the host takes daily backup of websites / databases and I can restore anytime from there and also for extra safety I download a backup from host before update (with 1 click and I have in a zip file all sites / databases) so I have just used to it and not installed Akeeba Backup. If in the future I have any problems with my host with the backups, then for sure I'll use Akeeba Backup.

[chrisbath2]

...

Also notably, I started having issues under 3.9.25 when some important extensions would no longer update. Something seems to have got corrupted.

And you never thought to fix the errors before updating?
No backup? Ask your Host to roll back.

I thought updating to the 3.9.26 would solve the issues, as they arrived with 3.9.25. As I mentioned, I am not an IT expert. We are a tiny charity and I wear many hats!

Yes, we have a recent backup from a week ago. But the update to 3.9.26 seems to have resulted in restores from Akeeba backups not working, giving an error message about by login.

Apparently the host does not do backups.

[Nidzo2203]

Manual backup, hosting backup.
Who says that Akeeba is mandatory?
It's the third party extension.
With full respect to all but this is Joomla update 3.9.26 thread, not Akeeba problem thread.

Updated 10 sites without any problem.

[Webdongle]

.
With full respect to all but this is Joomla update 3.9.26 thread, not Akeeba problem thread.
...

Joomla backup is (essentially) Akeeba code. The backup on update plugin was initially designed as part of logic. If Akeeba backup is installed then the backup on update should run. If it does not then then the update is (to some extent) not fully successful.

Therefore (with respect to your opinion al be it totally incorrect) The failure for the plugin to trigger is totally relevant to the Joomla update.

[Maradona]

Hi,

Once again, Joomla Updates - Additional Information goes to a wrong link

[sozzled]

Once again, Joomla Updates - Additional Information goes to a wrong link

From the discussion about J! 3.9.25:

The broken link 'Additional Information' in the Joomla! Update page on an actual website ... will now be raised as a new item in Joomla! Issue Tracker.

Unfortunately, the Joomla! Issue Tracker is broken (meaning that people cannot search the Issue Tracker to find things) but the matter was fixed for J! 3.9.25. The problem with J! 3.9.25 was different: the link resulted in a 404 error. The Additional Information link for J! 3.9.26 points to the release information about J! 3.9.25 (see screenshot below):

j3926_AdditionalInformation-wrong.png

Of course there's no point in discussing these things here. The developers do not visit this forum.

[gilplane]

Several websites updated from 3.9.25 to 3.9.26 without any problems (main components Templates Warp 7 Yootheme, JCE, Widgetkit etc ...).
Many thanks to the whole Joomla team for this volunteer work.
I haven't used Akkeba for several years following this kind of update conflict and I avoid using too many components on my Joomla sites as much as possible ...

[hehemrin]

Update went fine for me from 3.9.25 to 3.9.26, including automatic backup kicked in with the latest Akeeba backup extension 8.0.4.

[Webdongle]

Updating to J3.9.26 RC is not working and non of the dev's have commented about it https://issues.joomla.org/tracker/joomla-cms/34039

[sozzled]

@Webdongle: do you mean J! 3.9.26 RC or J! 3.9.27 RC? And, more importantly, why are "announcements" about RC versions appearing on the J! forum without the opportunity to discuss them? But, to get back to your question, I don't quite follow the reasoning (i.e. going from J! 3.9.26 back to J! 3.9.26 RC, if that's what you mean).

A little off-topic, but J! 3.9.27 is not a "straightforward" update (there are database changes involved as well as file replacements). Those facts should be included in any forthcoming announcement.

I read your request on GitHub and commented. It probably won't make a difference because J! 3.9.27 will go ahead regardless.

[Webdongle]

@Webdongle: do you mean J! 3.9.26 RC or J! 3.9.27 RC? ...

/no. I mean 3.9.26 to 3.9.27 RC with the update component channel set 'Testing' https://docs.joomla.org/Pre-Release_Testing

[sozzled]

I saw there's been a sympathetic response from @PhilTaylor-Prazgod on GitHub. Nonetheless, these "announcements" about RC versions without the means to discuss them on this forum are a complete waste of everyone's time. Either allow discussions about RC release announcements or don't announce those things on the forum. There are other ways to announce those things.

Thanks for clarifying the confusion. Yeah, there's no automated way of going from J! 3.9.26 to J! 3.9.27 RC at the moment. Until that's fixed then the RC release should be postponed another week. But what does it matter anyway? No-one—no-one who can make a difference, that is—pays attention to anything we write on this forum, do they? Waste of time, sorry. Nothing to see here.

[darb]

Well seems to be a fix soon that work this out isnt it?