Discussion Forum
You are not logged in.
- Topics: Active | Unanswered
Pages: 1
#1 September 1, 2020 10:54am
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Outdated CMS & having trouble upgrading
We are behind several versions of the CMS due to having issues getting our PHP upgraded. We are on 4.2.18 of BigTree. I just tried to update to 4.3.4 and was successful on the front end. On the backend, all looks fine until you go into page editing. The editing pages seem broken with missing CSS and missing information. Am I missing something or should I have done something prior to that update?
Offline
#2 September 1, 2020 10:56am
- timbuckingham
- Administrator
- From: Baltimore, MD
- Registered: April 2, 2012
- Posts: 978
Re: Outdated CMS & having trouble upgrading
Two things might be causing this:
- You may need to clear your cache to get the latest Javascript and CSS for the admin.
- You may need to do a composer update (BigTree 4.3+ use composer packages)
That said, you may want to upgrade directly to 4.4.10 as the 4.3 branch is no longer maintained.
Offline
#3 September 1, 2020 11:26am
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Re: Outdated CMS & having trouble upgrading
Tried to clear cache and no luck. Composer update? I am not sure what that means.
Offline
#4 September 1, 2020 11:28am
- timbuckingham
- Administrator
- From: Baltimore, MD
- Registered: April 2, 2012
- Posts: 978
Re: Outdated CMS & having trouble upgrading
Composer is a dependency manager for PHP:
https://getcomposer.org/
BigTree SHOULD include the correct /vendor/ folder at the root by default, but if for some reason it is not, you can run "composer update" from the root of your site after installing composer and it will update the dependencies for you.
Offline
#5 September 2, 2020 10:29am
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Re: Outdated CMS & having trouble upgrading
I have installed composer and run the update. I am still seing a broken page editor within the CMS. All else looks good. Any other ideas why this might be? Do I need to install a specific package of Composer? I just installed the package from the getting started pages on their website.
Offline
#6 September 2, 2020 10:30am
- timbuckingham
- Administrator
- From: Baltimore, MD
- Registered: April 2, 2012
- Posts: 978
Re: Outdated CMS & having trouble upgrading
BigTree 4.3+ should have a "composer.json" file at the root that contains the packages to install. If the only thing you're seeing broken is the WYSIWYG editor in the back-end then it's likely that your TinyMCE javascript cache is stale.
Offline
#7 September 2, 2020 12:00pm
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Re: Outdated CMS & having trouble upgrading
I think I finally figured out the issue. The CSS isn't getting picked up on the editing pages. The list of pages is fine but once you click to edit one that is where I lose the CSS and the entire page appears broken. The CSS is compiled so not sure what else the problem could be.
Offline
#8 September 2, 2020 12:02pm
- timbuckingham
- Administrator
- From: Baltimore, MD
- Registered: April 2, 2012
- Posts: 978
Re: Outdated CMS & having trouble upgrading
If the CSS is only failing to load when editing a page it sounds more likely that one of your fields is throwing an error and stopping the page from rendering. When you view the source does it get all the way to the closing </html> tag on that page?
Offline
#9 September 2, 2020 1:38pm
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Re: Outdated CMS & having trouble upgrading
Yes, the closing <html> tag is there. The header tag is completely empty though, I think that's my problem.
Offline
#10 September 2, 2020 1:41pm
- timbuckingham
- Administrator
- From: Baltimore, MD
- Registered: April 2, 2012
- Posts: 978
Re: Outdated CMS & having trouble upgrading
If <head> is empty it sounds like you may have some kind of custom override inside your /custom/ folder that is causing issues.
Offline
#11 September 3, 2020 9:59am
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Re: Outdated CMS & having trouble upgrading
I think I've narrowed it down to the _open-graph.php file. For whatever reason if that is in the automodules > forms folder everything breaks. When it's out the page editing is almost fine again. The entire core folder was updated to the new version so I am unsure what could be causing that.
Offline
#12 September 3, 2020 10:01am
- timbuckingham
- Administrator
- From: Baltimore, MD
- Registered: April 2, 2012
- Posts: 978
Re: Outdated CMS & having trouble upgrading
Does the bigtree_open_graph table exist in your database? If not, you may need to run the database updates. The latest 4.4.10 release should run them all for you if you hit the Developer tab as a developer level user.
Offline
#13 September 3, 2020 10:31am
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Re: Outdated CMS & having trouble upgrading
Yes, it does exist. Will version 4.3.4 of the CMS run with PHP 5.5?
Offline
#14 September 3, 2020 10:33am
- timbuckingham
- Administrator
- From: Baltimore, MD
- Registered: April 2, 2012
- Posts: 978
Re: Outdated CMS & having trouble upgrading
I believe 4.4 requires PHP 5.6 or higher.
Offline
#15 September 9, 2020 10:33am
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Re: Outdated CMS & having trouble upgrading
Still experiencing problems, unfortunately. I am getting this error in the CMS when trying to switch templates.
Fatal error: Call to undefined method BigTreeAdmin::rectifyResourceTypeChange() in \core\admin\ajax\pages\get-template-form.php on line 21
Any clues as to why that might be?
Offline
#16 September 9, 2020 10:34am
- timbuckingham
- Administrator
- From: Baltimore, MD
- Registered: April 2, 2012
- Posts: 978
Re: Outdated CMS & having trouble upgrading
Do you have a custom admin class override?
Offline
#17 September 9, 2020 11:26am
- mckenzieriley
- Member
- Registered: October 17, 2017
- Posts: 25
Re: Outdated CMS & having trouble upgrading
We have a custom base class and base class path. When I set those to false the error goes away but the CMS is still broken with no resources being pulled in and missing CSS.
Offline
Pages: 1