Admin interface corrupted after incorrect upgrade

[katon]

I ran an upgrade from a pretty old version. I wasn't careful to read documentation, which said that the upgrade needs to be done in several steps. Now when I click the page I want to edit, the admin interface totally disappears, and I see the frontend template with broken images and styles. Any ideas where to look to fix this?

[Jo Morg]

I believe it has to do with the use of {stylesheet} tag on your templates...

a) Open the template;
b) Search for {stylesheet};
c) Replace {stylesheet} with {cms_stylesheet};
d) Save template;
e) Open style sheets and change image calls:
old url(uploads/folder/image.jpg)
new url([[root_url]]/uploads/folder/image.jpg);
HTH

[katon]

No, not really. I have already gotten past this point. I have updated the frontend template, and frontend pages now display fine. What appears to be broken is the backend page edit functionality. Possibly, it is a bad link from the content list to the edit content page. Or the link is correct, but the edit content page just fails to load properly.

The edit content link looks like this:
http://frisbee.lviv.ua/admin/editconten ... d=48&page=
(nothing appears afer the "=" sign).

[Jo Morg]

Ok, so the next thing I would do is search for errors in Smarty tags syntax and/or GCB's names.
Smarty 3 is way less forgiving regarding syntax, so there may be one or more lines that would work before the upgrade and not after.
As to GCB naming, there were a few changes made to the core (IIRC), so that only alphanumeric characters and underscore can be used when naming GCB's.
HTH.

[velden]

The link seems correct. There is no need to be something after the page=

Could be that you're using a UDT (User Defined Tag) in your template(s) that fails when called from backend (admin).

If php error reporting is off you won't notice when a script dies and admin page will be blank.

Seen things like this (other users) that had UDT's that included other files with relative path. As admin is in it's own directory those relative paths pointed to non-existent files, which made the script fail.

I believe that in earlier versions of cmsms UDT's were not called from admin and they now do. So that COULD be a reason.

[Rolf]

What admin theme do you use? The old "default" template doesn't work anymore in 1.11+.
NCleanGrey and OneEleven themes are tested and work.

[katon]

velden, you are the man! I have found the UDT that is breaking the page! Thanks a million!

Jo Morg and Rolf, thanks for your input, too!

[Jo Morg]

Cool! Please add [Solved] to the topic.