[#19372] - JS Issue in admin, cannot save
- Closed
- 16 Jan 2018
- Medium
- Build: staging
- # 19372
Steps to reproduce the issue
PHP 5.6
Updated to 3.8.3
Expected result
Actual result
Administrator in menu item, cannot save, save & close, close, toolbar is gone
System information (as much as possible)
Database Version | 5.5.58-cll
PHP Version | 5.6.32
Web Server | Apache
WebServer to PHP Interface | cgi-fcgi
Joomla! Version | Joomla! 3.8.3 Stable [ Amani ] 12-December-2017 15:00 GMT
Joomla! Platform Version | Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36
Error in console (After button click):
Uncaught TypeError: Cannot read property 'task' of null
at Object.e.submitform (core.js?3ceec799b7da3f08b7a33b49820bea4d:1)
at Object.e.submitbutton (core.js?3ceec799b7da3f08b7a33b49820bea4d:1)
at HTMLButtonElement.onclick (index.php?option=com_menus&view=item&client_id=0&layout=edit&id=235:1693)
Additional comments
Browser cache wiped
Tried Chrome, Chrome incognito, Firefox, IE Edge, same result.
| Labels |
Added:
?
|
||
From which Version you Updated first to 3.8.3?
| Status | New | ⇒ | Information Required |
| Category | ⇒ | com_joomlaupdate |
3.8.2~3.8.3... i always upgrade as they come.
Note, issue may have existed since 3.8 in general as i haven't added anything since.
| Status | Information Required | ⇒ | Discussion |
| Category | com_joomlaupdate | ⇒ | com_joomlaupdate JavaScript |
Thanks for Info from which Version you updated first.
Have you asked at the forums - Migrating and Upgrading to Joomla! 3.x? If i understand your Info correct you have updated a earlier Version to 3.8, later to 3.8.3.
I am having the same issue. I can login to Admin but it is blank after that with now way to edit, no save, save closed, no toolbar, nothing but you can change the edit account or logout. Cache is cleared and tried in all browsers. I didn't change or update anything since the last login. Anyone have any ideas.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/19372.
@ocutshaw Have you asked at the forums - Migrating and Upgrading to Joomla! 3.x?
I am there now and it seems to be a number of people with the same issue, so I am not the only person having this problem. Looks like something happened on Joomla's end with something they did over the past few days.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/19372.
joomla can not change anything - only you can change something.
where you able to log in since you upgraded to 3.8.3
| Status | Discussion | ⇒ | Information Required |
@angelexevior Is this happening to all menu items? If not, please advise the offending menu item type.
Hope this helps someone figure it out.
My best guess was caching either serverside or clientside. I made 2 moves which solved my issue (Don't know which one worked as i checked after both were done).
1.) Cleared and restarted memcached on server. (Running centos 6.9).
2.) Reinstalled Gantry framework (Rockettheme template).
Everything back to normality after these.
Can someone confirm if they face same issue with a rockettheme template (Gantry uses it's internal caching in both frontend and backend for rockettheme modules ~might affect rest of admin interface). If so, then this is not a joomla core issue.
Memcached? Anyone?
@angelexevior I installed Fluent 1.0.3 and had no issues.
Per your error at HTMLButtonElement.onclick (index.php?option=com_menus&view=item&client_id=0&layout=edit&id=235:1693), HTMLButtonElement is found in this file \plugins\editors\rokpad\ace\worker-javascript.js which is from RocketTheme.
I would say it is not a Joomla core issue.
| Status | Information Required | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-01-16 16:50:01 |
| Closed_By | ⇒ | Quy |
| Closed_By | Quy | ⇒ | joomla-cms-bot |
Set to "closed" on behalf of @Quy by The JTracker Application at issues.joomla.org/joomla-cms/19372
Closed as stated.
@ocutshaw Please open a new ticket because your issue is different.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/19372.
Tried re-applying the 3.8.x~3.8.3 manually. No result