Thread

After updating to 2.1.3 from 2.1.0 I am seeing a weird CP with no styles.
After looking at the code I noticed weird url’s:
http://mydomain.com/themescp_themes/default/css/global.css?v=1303482754
http://mydomain.com/themesjavascript/compressed/jquery/jquery.js?v=1303482761

as you can see a slash is missing, but in the middle of the url.

what can I do to fix this?

Cheers

Ngezi,

Did you also replace your /themes/cp_themes folder with the newer files when upgrading?

Hi Brandon,

yes I even tried putting the old ones back.
but since the url is so misformed i figured it wasn’t the themes folder, because this way it can not even find the folder?

I’ve also re-uploaded the themes folder, and it didn’t help.
Any suggestions?

Make sure your themes folder settings have a trailing / in it.

Hi Sue,

I’ve also tried that, but somehow the system doesn’t store that slash. Upon saving it just shows the ‘old’ URL without slash again.

Now I replaced the URL for the themes in the config.php, but i noticed that non of the other url’s have a / at the end.
It seems to work now, but i’m still wondering what causes this behaviour? And are the other URL’s correct now, or should I also fix these with a trailing slash? (captchas, photo’s, avatars)

Hi Ngezi,

I’m not sure what could have caused it but I’m glad that it seems to be resolved. With regards to the other links are you experiencing other problems with them?

Cheers

Greg

Hi Greg,

not sure yet,

but if you look at your config.php do your url’s have a / at the end?
like I said, mine don’t, and it seemed to work fine in the ‘old’ 2.1.0 setup…

Ngezi, I can’t quite seem to nail down a direct link for your case, but if you look at the User Guide change logs, you’ll see Ellis has been moving away from using trailing slashes for some time.

This may have to do with clarifying information that there’s no reason to have them for SEO purposes.

Regards,
Clive

Hi Ngezi,

Have you modified your default config.php file to add in some config overrides (apart from the themes path) and those are the things that you are worried about? Please give me some examples of things that you suspect may not be correct?

Cheers

Greg

Yes, to make my updated site work I fixed the config.php and added the slash at the end of both the url and the path for the themes folder.
Before the update the CMS was 2.1.0 and before that it was an update from 1.6. The config file has never been changed by me before. I did try to add the slash in the CP, but that would not stay, so I fixed it in the config file directly. Like I said it works now, but I;m sure this should not be the way 😊

BTW, I replaced the CMS with the old backup several times and redid the upgrade, but what ever I did, I got the same error.

Ngezi,

I did try to add the slash in the CP, but that would not stay, so I fixed it in the config file directly.

The config.php is always going to override what you add in the CP

Are you happy for us to close this thread out for you now or do you have any more questions regarding it?

Hi John,

I fixed it for now, but the upgrade is still not functioning properly and the main problem is not solved. So maybe other people might experience the same problem when upgrading. It took me a couple of hours, so maybe you want to figure out what happened so other people don’t have to?

Niels

Niels,

I fixed it for now, but the upgrade is still not functioning properly and the main problem is not solved.

What else is not functioning?Can you list all your current issues please
Make sure you have permissions of 666 on your config.php
Comment out the theme urls in the config.php and make sure they are correct in your General Configuration
We will then tackle each issue as you list one by one

Hi John,

the problem is as described in my first post: the upgrade process didn’t work properly for me.
only after editing the config.php manually did I see a CP with styles.

my problem is solved for now, but I can imagine more people run into the same problem at some stage.

Niels

Hi Niels,

Typically the theme paths don’t need to be specified in config.php at all, so what you encountered may have been caused by an old setting that did not really need to be there. Since everything’s working I’ll close this thread, but we will be aware of this if it crops up again. And please don’t hesitate to start a new thread with any other questions.