Discuss Joomla! 3.8.4

[pe7er]

Here you can discuss about the release of Joomla 3.8.4

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

[JAVesey]

Faultless 3.8.3 --> 3.8.4 update on live site and local (MAMP) sites.

Many thanks to all who contributed

[sozzled]

Thanks, John. It's always reassuring to see fast feedback about the latest release of J! and the fact that there's no issue we should [generally] be concerned about.

[JAVesey]

Spoke too soon. I have an issue on live site and MAMP/local installation. Please can someone confirm (or not as the case may be) before I report as bug:

Joomla 3.8.4, PHP7.1.13, Protostar template, TinyMCE Editor:

1. Login to frontend on homepage as Admin
2. Select Edit article
3. Editing window displays but no text, word-count = 0
4. Click Cancel to return to homepage
5. Logout.
6. Go to Admin and Content > Featured Articles
7. Article attempted to edit on frontend is locked

Other notes:
Haven't tried with non-Featured Articles
Have tried with Codemirror editor; same result
Same issue on MAMP/local installation
Repeatable
No issue editing in Admin
Frontend editing worked fine on 3.8.3
Nothing else changed, just 3.8.3 ---> 3.8.4 update applied
ReCaptcha v2 on frontend editing
Made post to Kunena Forum since updating without issue (no Captcha on submission page)

Just me?

[sozzled]

Hmm ... I don't normally perform front-end article editing and I don't usually use TinyMCE editor but there's something rather suspicious going on.

@JAVesey: I logged into the frontend of one of my test sites (updated to J! 3.8.4); my default editor is set to JCE. I attempted to edit a fairly typical article and I faced the same situation. Empty WYSIWYG frame! I didn't attempt to save the article but, on cancel, the article was locked.

Puzzling.

[brian]

I have tested front editing on a few sites with no issues

[sozzled]

Thanks, Brian. Just to double-check (as I wrote earlier, I rarely use front-end editing and, even less, do I use TinyMCE). I tested the scenario on another recently-updated J! 3.8.4 website with Protostar and I had no editing problems with JCE or TinyMCE.

I was able to save changes to an article.
Pressing Cancel abandons any changes and does not leave the article locked.

So, I don't know what happened the first time around. Probably nothing to worry about (although the issue could be template-related). So far so good (4 sites updated). Cheers.

[JAVesey]

I have narrowed it down:
1. I can frontend-edit some featured articles and all other articles not on homepage.
2. The homepage articles that I can't edit on the frontend are in the category "uncategorised"
3. There is no menu item for the "uncategorised" category
4. There is a menu item for all the articles that I can edit
5. Moving an "uncategorised" frontpage article article into a category for which there is a menu item makes it editable
6. Switching it back to "uncategorised" makes it uneditable again

Does this clarify things?

[sozzled]

I tried to reproduce the problem. J! 3.8.4, Protostar, logged-in frontend, default/home menu item (single article), Uncategorised category, featured, TInyMCE editor ... sorry, I couldn't fault it.

Did I overlook something?

[titchagcreation]

Hello,

Since I updated Joomla 3.8.3 to 3.8.4 it is not possible to login to our Kunena forum anymore. We have a 404 error page.
Something changed in URL rewriting or any redirection process ?

[JAVesey]

Did I overlook something?

Did you try it with an uncategorised article with no menu item?

Edit:
You also overlooked the fact that you experienced the issue the first time you tried it

I've done some more checking:
1. for those articles which I can't edit, the "versions" button doesn't show in the editing window (it does show for the articles that I can edit); and
2. the problem is reproducible every time for all articles (not just those on the homepage) where the article is in a category with no menu item for that category or where the article doesn't have a "single article" menu item

To test it yourself:
1. create a new test article in a category with no menu item
2. set that article to featured
3. set your "home" menu item to "featured articles"
4. login to frontend (user with editing permissions) and go to homepage
5. try to edit

[jgress-]

Joomla 3.8.4, PHP7.1.13, Protostar template, TinyMCE Editor:

1. Login to frontend on homepage as Admin
2. Select Edit article
3. Editing window displays but no text, word-count = 0
4. Click Cancel to return to homepage
5. Logout.
6. Go to Admin and Content > Featured Articles
7. Article attempted to edit on frontend is locked

Other notes:
Haven't tried with non-Featured Articles
Have tried with Codemirror editor; same result
Same issue on MAMP/local installation
Repeatable
No issue editing in Admin
Frontend editing worked fine on 3.8.3
Nothing else changed, just 3.8.3 ---> 3.8.4 update applied
ReCaptcha v2 on frontend editing
Made post to Kunena Forum since updating without issue (no Captcha on submission page)

I've been trying to see if I could duplicate this on my own site. I updated to 3.8.4 and have an uncategorised article on my home page.

I created a login module in my RocketTheme template and tried to edit things. I didn't even get an edit icon on any article except my contact page. But I couldn't edit the page. It wouldn't ever go anywhere.

I then got an error message on the home page:

Error
Edit not permitted.

My user is in the Super User User Group.

I tried in Protostar but couldn't even get the edit button on the contact page at this point. So I gave up, put my template back, unpublished the login module, refreshed and got this warning.

Warning
The security token did not match. The request was aborted to prevent any security breach. Please try again.

Interestingly I'm getting that same error on the frontend of CJO. I'm going to have some lunch but then I'll come back to this and see if I can figure out how to duplicate whatever I did.

I didn't do frontend editing on this site ever before, so I don't actually know for sure if these issues might have existed before the update to 3.8.4.

More in a bit.
jenn

[jgress-]

Ok, here's my update...

1. I had some caching issues. Resolved them and retested.
2. I was not able to duplicate the issue you're having JAVesey. I was able to edit fine with TinyMCE/protostar/3.8.4 on an article in Uncategorised without a menu item associated with it.
3. Login modules are throwing that warning message I posted above. When I login with a Menu Item type of Login Form, all works fine. Rowan says this has been reported. I couldn't find it on the issue tracker though.

[GillianBPP]

(I initially posted this in Sites & Infrastructure - Feedback/Information - topic 958820 - but realise it should be here. Sorry)

In Joomla 3.8.3 the code in the index.php template file editor is multi-coloured (see attachment) but in 3.8.4 the colour has disappeared. It doesn't make any difference to the actual code, but the colour is actually rather useful, particularly as it used to come up red if you put something in incorrectly.

I'm not sure what editor is used in the template files editor but I'm using the latest JCE Editor for editing articles and modules.

CSS files are unaffected and are in full colour.

[mikerotec]

We recently upgraded our site to https:// Everything working fine the last few weeks.

But since 3.8.4 update, some users are getting "too many redirects" when they access the site from older http:// links.

I'm not able to reproduce the issue on any Mac, but some PCs with Chrome, I can. (And then have to delete site cookies to clear it) It's not "reliable" though, only once in a blue moon...

[Trakker]

I've not seen any issues while using Joomla 3.8.4 yet but I do want to see if anyone else has been getting update emails with the following. (Remembering that I've already upgraded to 3.8.4)

================================================================================
UPDATE INFORMATION
================================================================================

Your site has discovered that there is an updated version of Joomla! available for download.

Joomla! version currently installed: 3.8.2
Joomla! version available for installation: 3.8.3

This email is sent to you by your site to remind you of this fact.
The Joomla! project will never contact you directly about available updates of Joomla! on your site.

etc etc.....

[Trakker]

Please disregard my previous post. I'd forgotten I had a duplicate site with the same Name for testing purposes.

Non-Issue resolved

[JAVesey]

Update on my issue (not being able to edit some articles on the frontend):

Reading this thread made me think:
viewtopic.php?f=706&t=958789

I reset Articles "Integration" to the "Legacy" SEF URL routing and I was able to edit the articles as before. Since I was able to frontend edit the articles with "Modern" SEF URL routing and removing id-numbers in J3.8.3 I am assuming that J3.8.4 has introduced an issue.

I understand that the routing issues have been bug-reported so happy to leave for now pending J3.8.5

Thanks all.

[sozzled]

In Joomla 3.8.3 the code in the index.php template file editor is [hilighted in colour]... but in 3.8.4 the colour has disappeared. It doesn't make any difference to the actual code, but the colour is actually rather useful, particularly as it used to come up red if you put something in incorrectly.

CSS files are unaffected and are in full colour.

I can confirm this. The GeShi highlighting has disappeared in J! 3.8.4 when editing .PHP files but is present in .CSS files. I compared the situation between one site updated to J! 3.8.3 and a copy of the site updated to J! 3.8.4 (both sites the same webserver). I could not find the cause, looking at GitHub, for the change.

If someone else can also confirm this then we can report it on GitHub.

[sozzled]

Update on my issue (not being able to edit some articles on the frontend):
I reset Articles "Integration" to the "Legacy" SEF URL routing and I was able to edit the articles as before.

Thanks for that info, John. This may explain why, on one website where I had set the SEF routing to the new "experimental" version, the frontend editing didn't work and, on another site (where I hadn't changed the routing setting) the frontend editing did work.

You're right, of course, that the new router is still "experimental" and may have teething problems (not the least of which are that it causes a few problems with existing SERPs that have been indexed on the search engines, the consequences of using those links will result in 404s unless you make other arrangements as I wrote here: viewtopic.php?f=9&t=954795#p3492928).

[jgress-]

If someone else can also confirm this then we can report it on GitHub.

Confirmed. I see the same no colour in 3.8.4 and colour in 3.8.3.

Update on my issue (not being able to edit some articles on the frontend):
Reading this thread made me think:
viewtopic.php?f=706&t=958789

I reset Articles "Integration" to the "Legacy" SEF URL routing and I was able to edit the articles as before. Since I was able to frontend edit the articles with "Modern" SEF URL routing and removing id-numbers in J3.8.3 I am assuming that J3.8.4 has introduced an issue.

Sigh. Good to hear back from you though. I was curious.

[JAVesey]

Thanks for that info, John. This may explain why, on one website where I had set the SEF routing to the new "experimental" version, the frontend editing didn't work and, on another site (where I hadn't changed the routing setting) the frontend editing did work.

You're right, of course, that the new router is still "experimental" and may have teething problems (not the least of which are that it causes a few problems with existing SERPs that have been indexed on the search engines, the consequences of using those links will result in 404s unless you make other arrangements as I wrote here: viewtopic.php?f=9&t=954795#p3492928).

It stopped being called "Experimental" a release or two ago; it's now "Legacy" and "Modern"...

Some interesting discussion on the Issue Tracker about routing; seems that a change in 3.8.4 has caused several problems and the change will be reverted in 3.8.5 and probably sooner rather than later.

[jgress-]

Some interesting discussion on the Issue Tracker about routing; seems that a change in 3.8.4 has caused several problems and the change will be reverted in 3.8.5 and probably sooner rather than later.

I was reading the same. Looking forward to 3.8.5.

[sozzled]

Jenn and @Scrabble: I reported the colour hilighting issue on GitHub.

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

[jgress-]

Jenn and @Scrabble: I reported the colour hilighting issue on GitHub.

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

Thanks, Michael.

[rjo]

...default editor is set to JCE. I attempted to edit a fairly typical article and I faced the same situation. Empty WYSIWYG frame! I didn't attempt to save the article but, on cancel, the article was locked.

I can confirm. Update of JCE to the latest .26 build. The editor area was empty.
Going into the backend and saving the editor profile (no changes) resolved that issue. Now the editor area is visible and the toolbar is back.
Saving, however, does still not work: article changes are not saved, checkout status is not reset.

[rjo]

Another issue seems related to com_users. The release notes only mention code cleanup.
In this case an overrride of the login form stopped working. Frontend login returns the message JINVALID_TOKEN_NOTICE ("The security token did not match. The request was aborted to prevent any security breach. Please try again.").
Removing the override makes the login form work again but profile editing in the frontend is still broken, even without overrides.
Any ideas what might have changed?

[VasyaV001]

Strange problem after update from 3.8.3 to 3.8.4 with guest and users stay login forever, plus can't force logout user from Administrator Control panel.
Session Settings - I try switch from Data base to PHP , same problem.

[sozzled]

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

This problem has been marked as resolved; there was a minor mistake made with the Codemirror editor. I would say the fix will be included in the next release (J! 3.8.5, I guess).

[jgress-]

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

This problem has been marked as resolved; there was a minor mistake made with the Codemirror editor. I would say the fix will be included in the next release (J! 3.8.5, I guess).

Thanks!!