2021-11-08, 02:23 PM
Upgraded on test server from 1.8.26 to 1.8.29.
Changing themes in footer or UserCP results in complete theme1 css being called. One exception is a theme migrated from 1.6 which calls the css3 appropriately. Global.css is called incorrectly.
Screenshots show file loads between 1.8.26 on production server vs. 1.8.29 on test server. Page is index page.
I have gone through Find Updated Templates and copy/pasted minor changes after reverting template to default.
I observe there's new code that adds a timestamp reference for calling a css file.
Production:
[attachment=44674]
Upgrade test:
[attachment=44675]
Obviously I'm missing something.
Help is appreciated.
Global.php does the initializing for theme and stylesheet, and I notice there are fallback positions to load defaults if problems are found.
Is there a relatively easy way to check on the progress of php execution in a live environment, or is a vardump statement edited into the code the simplest way to monitor status at a given point?
What debugging tool do you use?
Changing themes in footer or UserCP results in complete theme1 css being called. One exception is a theme migrated from 1.6 which calls the css3 appropriately. Global.css is called incorrectly.
Screenshots show file loads between 1.8.26 on production server vs. 1.8.29 on test server. Page is index page.
I have gone through Find Updated Templates and copy/pasted minor changes after reverting template to default.
I observe there's new code that adds a timestamp reference for calling a css file.
Production:
[attachment=44674]
Upgrade test:
[attachment=44675]
Obviously I'm missing something.
Help is appreciated.
Global.php does the initializing for theme and stylesheet, and I notice there are fallback positions to load defaults if problems are found.
Is there a relatively easy way to check on the progress of php execution in a live environment, or is a vardump statement edited into the code the simplest way to monitor status at a given point?
What debugging tool do you use?