weaselbringer Posted July 29, 2009 Share Posted July 29, 2009 I just upgraded from beta 1.2.0.(6?) about 2-3 betas back to the latest stable dev, and it broke my theme, so I copied across the new theme included with the stable and it's still showing up as broken (mainly text) I looked in the source for the main page of the store and I noticed the <base href=" shows ashttp://www.mydomain.com/storehttp://www.mydomain.com/storeI'm assuming that might have something to do with it, but in my settings.inc.php file it's just listed as /store/ for the base URL - what went wrong? why is it showing this duplicate URL and why is my template broken even after transitioning everything (but mails/img etc) over to the new stable ver? HELP, my site is all broken and I've replaced every file I can... any ideas? Link to comment Share on other sites More sharing options...
weaselbringer Posted July 29, 2009 Author Share Posted July 29, 2009 I put the "mydomain" as an example it DOES read my actual domain, but it lists it twice with no gap... Link to comment Share on other sites More sharing options...
yoyoman Posted July 30, 2009 Share Posted July 30, 2009 I have the same problem. My global css file won't load be/c it's trying to find ps2http://ps2 ... The files that won't load are not always the same. It depends on what page I'm on. Link to comment Share on other sites More sharing options...
dfunkydog Posted July 30, 2009 Share Posted July 30, 2009 Similar problem here.my base href is localhost/shop, but the global css is /shop/themes/..., so it's trying to find localhost/shop/shop/themes/... which obviously does not exist. Strangely everthing else is linked correctly except for the global css file. Link to comment Share on other sites More sharing options...
yoyoman Posted July 30, 2009 Share Posted July 30, 2009 OK, I think it's v1.1 theme related. If you copied the prestacart theme from 1.1, in "header.tpl" there is this line <base href="{$protocol}{$smarty.server.HTTP_HOST|escape:'htmlall':'UTF-8'}{$base_dir}" />That line isn't in v1.2's "header.tpl". If you delete that line, it fixes the problem. Link to comment Share on other sites More sharing options...
dfunkydog Posted July 31, 2009 Share Posted July 31, 2009 Thanks for that yoyoman. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now