?
avatar greenorca
greenorca
29 Mar 2016

Steps to reproduce the issue

Customize Protostar template.css and template.js
Run update.

Expected result

After updating, the website still looks as before. This worked fairly well on previous updates (

Actual result

Default Protostar template css and template.js replaced the customized files

System information (as much as possible)

3.4.8 --> 3.5; other than that I guess it is not a system specific thing...

Additional comments

Overall: great work guys!

avatar greenorca greenorca - open - 29 Mar 2016
avatar infograf768
infograf768 - comment - 29 Mar 2016

Customising protostar and expecting the behavior to be the same after an update where some stuff has been changed (for certainly good reasons)is wrong.

For sure it never happened in the past. You may have had a cache set which gave you the feeling it was the same.

The only way to be sure to keep your custom stuff is to Copy the template through Exensions=>Templates and use that instance of the core template. Evidently, it is strongly suggested to have a look at the changes introduced in core and use them or not in your copy.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9642.

avatar infograf768 infograf768 - change - 29 Mar 2016
Status New Closed
Closed_Date 0000-00-00 00:00:00 2016-03-29 07:30:34
Closed_By infograf768
avatar joomla-cms-bot joomla-cms-bot - close - 29 Mar 2016
avatar infograf768
infograf768 - comment - 29 Mar 2016
avatar joomla-cms-bot joomla-cms-bot - close - 29 Mar 2016
avatar infograf768
infograf768 - comment - 29 Mar 2016

Closing as this is expected behavior.


This comment was created with the J!Tracker Application at issues.joomla.org/joomla-cms/9642.

Add a Comment

Login with GitHub to post a comment