Upgraded to Jooma 3.5.1 Now Endless Problems

[mark47855]

I upgraded to Joomla 3.5.1 from version 3.4.8 and now the 'save', 'save as new' and 'cancel' buttons that appear above an article on the Admin Panel, as well as the 'save' and 'cancel' buttons on the frontend that are used for either publishing or cancelling an article do not work when clicked.

Why is this?

[mark47855]

I've had to role back to 3.4.8 as 3.5.1 is buggy it would seem.

[brian]

You just needed to completely clear your site and browser cache

[Webdongle]

Also set your front end Template to Protostar. Custom front end Templates can cause problems in admin

[brian]

If that was true it must be a horrendously bad template to effect the admin

[stawebnice]

how do you suggest to fix the issue that no mails are being sent after update do 4.5.1 and it messed up virtuemart orders too...?

[deleted user]

Update your extensions as they release updates. If you see any suggestions about core hacking the libraries/joomla/mail/mail.php file do NOT follow them.

Long and short, PHPMailer in Joomla 3.5.1 is less error tolerant than before and exposes a lot of incorrect uses of the mail API (including one core bug that had been present for roughly 4 years that was only patched after the error handling change). It's definitely annoying to deal with, but honestly it's a change that has to happen and folks have to make the required updates to their code. I don't know why things gave the impression they worked on 3.5.0 and earlier but some of the use cases I've seen clearly should not have meaning there was bad error handling set up somewhere.

[Webdongle]

If that was true it must be a horrendously bad template to effect the admin

If ? ... but it is true !!!

I upgraded my Joomla from 3.2.7 to 3.5.0. I had no error messages after the upgrade. Now when I go into my admin panel I can go to each menu item (i.e. System, Users, Content, etc) and it will let me into the article, module etc but after I make the changes it will not let me save.
....
changing the default template to Protostar did the trick. Thank you so much. Can you explain to me why that made a difference.

From thread http://forum.joomla.org/viewtopic.php?f=708&t=916312

It's not common (I can only remember a few instances in several years) but it does happen.

[mark47855]

You just needed to completely clear your site and browser cache

I cleared my browser cache and the sites browser cache and the issue is still persisting.

[Webdongle]

...
I cleared my browser cache and the sites browser cache and the issue is still persisting.

Have you set Protostar as default Template ?

[mark47855]

...
I cleared my browser cache and the sites browser cache and the issue is still persisting.

Have you set Protostar as default Template ?

No as Protostar is not the template we use.

Am I stuck with version 3.4.8 if I want to continue using my own template?

[Webdongle]

...
No as Protostar is not the template we use.
...

If you test with Protostar as default Template and the error ceases then you know it is something to do with your Template. Then you can start to do something about it. If the problem persists then you can look elsewhere.

...
Am I stuck with version 3.4.8 if I want to continue using my own template?

You don't even know if it is the Template because you wont test to find out. It probably isn't the Template but you won't know unless you swap Templates. Even if it is the problem you have options.

[mark47855]

...
No as Protostar is not the template we use.
...

If you test with Protostar as default Template and the error ceases then you know it is something to do with your Template. Then you can start to do something about it. If the problem persists then you can look elsewhere.

...
Am I stuck with version 3.4.8 if I want to continue using my own template?

You don't even know if it is the Template because you wont test to find out. It probably isn't the Template but you won't know unless you swap Templates. Even if it is the problem you have options.

Well the problem occurred on the admin panel as well as the frontend. The admin panel has the default (unchanged) template active. Shouldn't this be enough to prove that it isn't related to a custom template?

[Webdongle]

...
Well the problem occurred on the admin panel as well as the frontend. The admin panel has the default (unchanged) template active. Shouldn't this be enough to prove that it isn't related to a custom template?

Does it happen when the default frontend Template is Protostar ? Yes or No ?

[mark47855]

...
Well the problem occurred on the admin panel as well as the frontend. The admin panel has the default (unchanged) template active. Shouldn't this be enough to prove that it isn't related to a custom template?

Does it happen when the default frontend Template is Protostar ? Yes or No ?

I will get back to you with an answer. This is a site with 3000 visitors per month so I'm not one for putting up random templates nor did I think a set of TPL / CSS files would bring a site to a halt both on the backend and frontend.

[Webdongle]

...
I will get back to you with an answer. This is a site with 3000 visitors per month so I'm not one for putting up random templates nor did I think a set of TPL / CSS files would bring a site to a halt both on the backend and frontend.

It will take two minutes to change default Template, test the save in admin then set the default Template back. Besides which you have copied the site to localhost to test ... yes ?

.. nor did I think a set of TPL / CSS files would bring a site to a halt both on the backend and frontend.

[/quote][/quote]Like I said it is unlikely but it does happen.

The problem you describe is indicative of a javascript conflict caused by a 3rd party extension or Template. Good luck in finding the cause. Goodbye

[mark47855]

The problem you describe is indicative of a javascript conflict caused by a 3rd party extension or Template. Good luck in finding the cause. Goodbye

Goodbye indeed.

[wim72]

Here to for the first time in years some issues with update from 3.4.8 to 3.5.0 and 3.5.1
After first updating all the extensions that noticed me, i updated Joomla from 3.4.8 to 3.5.0.
I did global check on the front end all looks fine, spoiled after some years, after all its just klik the button.
Then couple day's after the update i get noticed that 3.5.1 needs to be installed.
Hmm thats fast there must be some problem and installed the latest version.
From now on i have this problem;

Cant create/edit: global configuration, articles, modules, categories, etc.
No save buttons (trows error 500).

Cleared cache browser/site.... no result
Fixed database ... no result

For now rolled backup out again from 3.4.8 and checked if i had this problem with the 3.5.0 also.
Indeed same problem.
Live site on 3.4.8 again for now

For safety i also updated my MAMP with latest relaese.
Localhost runs on php 5.6.10 now

Now time to disable all extension and hope to find some fix.

If anyone have same kind of issues please share what to do next
Thanks for reading

[Webdongle]

http://forum.joomla.org/viewtopic.php?f ... 1#p3388087

[hypnoyanova]

Now time to disable all extension and hope to find some fix.

worked for me! just one plugin (POWr Icon in my case) was responsible, disabled it and now everything is back to normal!

[Cedbr_Wsu]

Thank you!!! you made my day hypnoyanova

[hypnoyanova]

Thank you!!! you made my day hypnoyanova

Absolutely happy to help! ^u^

[Ocampas]

Now time to disable all extension and hope to find some fix.

worked for me! just one plugin (POWr Icon in my case) was responsible, disabled it and now everything is back to normal!

This also worked for me. It was driving me crazy. Thank you.

[hypnoyanova]

This also worked for me. It was driving me crazy. Thank you.

Know the feeling! You're welcome

[TomTopper]

Now time to disable all extension and hope to find some fix.

worked for me! just one plugin (POWr Icon in my case) was responsible, disabled it and now everything is back to normal!

Great!!! Works for me!!!!

[mark47855]

Is there a fix for Joomla 3.5.1 currently? I am still using version 3.4.8 due to the fact that the save and publish buttons for my WYSIWYG editor do not work in version 3.5.1. I am not clear what needs to be done to rectify this.

[Webdongle]

The problem is not with J3.5.1 .... it will be a 3rd party extension. Most likely a custom Template.

[sovainfo]

What is not clear about keeping current? It is your responsibility to keep all extensions current. That means you need to find out for each extension whether there are updates. And how to implement them when there are updates. Note that not all extensions are using an update server. Even when they are, suggest to verify their site for updates. Specially when you are planning to update Joomla as well.

Normally a minor update doesn't give you these issues, provided the extensions you use play according to the rules. Seems like you are using an extension that needs fixing!

[mark47855]

The problem is not with J3.5.1 .... it will be a 3rd party extension. Most likely a custom Template.

The issue I have resides on the Joomla Administrator Panel and the frontend; If I update to version 3.5.1 I cannot save or publish content. As I use a WYSIWYG editor called 'TINY MCE' that appears to show on both the backend and frontend could it be this that is causing the problem?

The custom template I use is only for the frontend, it doesn't transverse over into the Administration area. No part of the Administration area has been modified in terms of its javascript or CSS template files.

[NickC4555]

Many of the frustrations expressed here are because upgrades are being attempted on live sites. Create a subdomain, put a duplicate of the site in it, keep it offline when you aren't working on it so it doesn't get indexed and use it to test all upgrades. When everything is working, copy it back to the live domain. If it is a complex transactional site, write a regression test plan that has to be followed and signed off against whenever there is a change.