Discuss Joomla! 3.8.8

[pe7er]

Here you can discuss about the release of Joomla 3.8.8

See Announcement: viewtopic.php?f=8&t=962389

[sozzled]

Thanks, @pe7er, for creating this topic. I've been able to update my J! 3.8.7 websites without any problems and I haven't noticed any issues that should trouble anyone. Good work on the part of the release team.

[JAVesey]

Thanks, @pe7er, for creating this topic. I've been able to update my J! 3.8.7 websites without any problems and I haven't noticed any issues that should trouble anyone. Good work on the part of the release team.

Ditto

[toivo]

No issues whatsoever.

[TaylorCTU]

Ever since I've updated I can't open modules with the type set as custom.

[ribo]

The update proccess went fine without any issues. Thank you again joomla team for the good work

[ribo]

Ever since I've updated I can't open modules with the type set as custom.

Did you clear browser cache?

[TaylorCTU]

Ever since I've updated I can't open modules with the type set as custom.

Did you clear browser cache?

Yes. Cleared cache, tried to access on a different device, and I've tried on chrome, ie, and firefox.

[ribo]

Do you have anything in global check in?

[TaylorCTU]

Do you have anything in global check in?

I did but updated. It's articles too. Created a thread.

[ribo]

Lets try this. Back up your joomla first. After download full package of joomla 3.8.8 . Then go to Components-Joomla Update-Upload & Update and upload and install full package with write files directly. It will need to login there before you will update(you will see). When the update will finish check again.

[ribo]

Before do that please check my answer in here viewtopic.php?f=708&t=962472

[Jaydot]

I did have an issue, actually, on a site that uses the random image module.
Discussion here: viewtopic.php?f=710&t=962221
Other sites updated without problems.

[sozzled]

Ever since I've updated I can't open modules with the type set as custom.

The issue referred to here (viewtopic.php?f=706&p=3526809) involves a third-party extension—an extension that I have not used, myself. There may be a compatibility issue with this third-party extension and J! 3.8.8 (or PHP), I don't know. I don't have any of the problems mentioned by @TaylorCTU when editing articles or custom modules with TinyMCE, CodeMirror, JCE Editor or "No editor".

[TaylorCTU]

Ever since I've updated I can't open modules with the type set as custom.

The issue referred to here (viewtopic.php?f=706&p=3526809) involves a third-party extension—an extension that I have not used, myself. There may be a compatibility issue with this third-party extension and J! 3.8.8 (or PHP), I don't know. I don't have any of the problems mentioned by @TaylorCTU when editing articles or custom modules with TinyMCE, CodeMirror, JCE Editor or "No editor".

Yeah I did try different editors, not an editor issue for me either. Must be an issue with articles anywhere from Regular labs.

[leolam]

Must be an issue with articles anywhere from Regular labs.

Based on what makes you post such conclusion? We use Regularlabs extensions on all our sites and on all our client sites without any issues

Leo

[TaylorCTU]

Must be an issue with articles anywhere from Regular labs.

Based on what makes you post such conclusion? We use Regularlabs extensions on all our sites and on all our client sites without any issues

Leo

It was an issue with Regularlabs being compatible with an older PHP version. I have reported the issue and Regularlabs put an update out very quickly. A+ developer.

[leolam]

Glad to hear you got it resolved!

Leo

[sozzled]

It seems that J! 3.8.8 has been well behaved except for the defective Random Image module that has caught out a few people. I don't use the Random Image module—I don't have any particular use for it—and I suspect the problem may have been dormant for a while: https://docs.joomla.org/J3.x:Module_ran ... fter_3.8.8

Cheers

[mbabker]

Your suspicions are wrong. It was an issue introduced into 3.8.8. Statements like "may have been dormant for a while" spreads misinformation about QA processes or even accepting shipping a fatally broken element in the core package "for a while".

[sozzled]

Thanks for pulling me back into line. I perused the list of issues addressed by J! 3.8.8 (https://github.com/joomla/joomla-cms/mi ... 3?closed=1) but I couldn't seen anything on that list that suggested that mod_random_image had been changed. I mean, if mod_random_image had not been changed before J! 3.8.8 then what was it, specifically, about J! 3.8.8 that changed that impacted on mod_random_image. And, if mod_random_image wasn't changed as part of the release J! 3.8.8 then, in fact, there was a nascent problem with it. It's not worth splitting hairs over the matter; I'm simply saying that I looked to see how this problem came into being and I can't, for the life of me, figure out how J! 3.8.8 created the problem.

[mbabker]

Not every commit is in the list of issues, i.e. security related changes or the version number updates.

[sozzled]

Nice deflection

The point I wanted to make is that, when there are new releases of software (and that includes most software that I use), I generally skim over the issues that these new releases were intended to address; that's all I was trying to say. The fact that a problem was introduced in the mod_random_image module (as the result of an unannounced change made to that module) is unfortunate; it appears that this module isn't one of those things that most people often use judging on the number of questions that have been asked about it.

It was never my intention to cast aspersions on the QA process.

[mbabker]

The GitHub issue list that is linked in the release notes does not and will not ever contain a list of security issues. If you look, none of the security related fixes in 3.8.8, or any security issues at least since I started running releases the first time in July 2013 have corresponding issues. So no, not a deflection, statement of fact.