Alex Nitu Posted February 26, 2015 Share Posted February 26, 2015 (edited) Warning on line 1585 in file /www/ftp.conexelectronic.ro/truse-scule.ro/classes/controller/AdminController.php[2] Cannot modify header information - headers already sent by (output started at /www/ftp.conexelectronic.ro/truse-scule.ro/classes/cache/CacheFs.php:40) So this is what I get when I enter inside carriers->desired carrier. I'm not sure what it means or if it pops up in more places, but I will check. In the meantime, does anyone know what this is? I know it's related to header name, but in my case, I wasn't trying to change any headers. EDIT: I've found a problem inside the carrier options. I've set the ranges of pricing for different values of final order price, so if the final order has a total price of X currency, the shipping costs would be different than if the total order would have a price of Y currency. The problem is that it doesn't do anything inside my front office. It just give me the same price, no matter the order total price. Could it have something to do with that error? Edited February 26, 2015 by Alex Nitu (see edit history) 1 Link to comment Share on other sites More sharing options...
Alex Nitu Posted February 26, 2015 Author Share Posted February 26, 2015 Ok, so it's official, I can't edit the pricings for any of my carriers anymore. This, with the CMS issues, and who knows what else, I think goes deeper than expected. 1 Link to comment Share on other sites More sharing options...
shri Posted May 21, 2015 Share Posted May 21, 2015 hi did you get any help in error. I am getting same error and other issues too. Nobody seems to reply here. I tried searching google with Prestashop + ErrorMessage but it does not give me anything useful at all.. Link to comment Share on other sites More sharing options...
Alex Nitu Posted May 21, 2015 Author Share Posted May 21, 2015 Seems that the only way to fix this is to turn off every piece of cache that you are using: general, smarty, cache for CSS and cache for Java. I don't know exactly about the last two, but I turned them off anyway so I can be sure. Unfortunately, some people still had some of these issues, once cache was turned off, so it could be related to another glitch, but try that and see what happens. 1 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