Jump to content

Carriers Page All Messed Up in 1.5.5.0


Recommended Posts

A day ago, I was able to add carriers normally. Then I cleared cache and deleted cookies and now the page where I add carriers is messed up. Even the PREVIOUS, NEXT and FINISH buttons have disappeared.

 

I've tried this on Chrome, Firefox and Internet Explorer, all with cache, cookies, forms, fields and histories completely cleared. All show the same messed up interface. I also tried it on a friend's computer and his browsers experienced the same issue.

 

The picture attached shows more about how bizarre it looks now.

 

How do I solve this?

 

Thank you.

post-657795-0-31963000-1380386957_thumb.png

Edited by nate (see edit history)
Link to comment
Share on other sites

can you please turn on browser console (ctrl+shift+J in chrome) 

have you got there some 404 errors? (in console log)

 

No 404 errors. But I see a lot of "Uncaught ReferenceError: $ is not defined". Check out the pic for details.

 

What does this mean?

post-657795-0-04159900-1380388879_thumb.jpg

Edited by nate (see edit history)
Link to comment
Share on other sites

Wow, that is awful.

 

I've never seen that before.  Did you change template styles between the good and bad view?

 

Maybe try change templates and see if it makes any difference. 

 

Ok, we figured part of it out.

 

We didn't change templates. What happened was, one of our coders put the Prestashop into a folder in our hosting service. So instead of shopname.com, it became shopname.com/foldername.

 

He then rewrote the URL so that it became shopname.com again. However, while front end users could access the shop with no problems, back end users would see some messed up pages. I found out after first posting about this that the product pages in the back office were completely blank and the Paypal module configuration page was also affected.

 

I don't know the full details at the moment but this was apparently caused by "foldername" remaining in the htaccess after URL rewriting.

 

We currently partially solve the problem by deleting "foldername" manually from the URL every time we log into the back office. We're still figuring it out. Hopefully we'll have a fuller understanding of what happened soon.

 

:)

Edited by nate (see edit history)
Link to comment
Share on other sites

×
×
  • Create New...