afranco

kashibabu,you make some very good points. There are so many problems that are introduced with each new update, while many of the old problems are simply passed by. I think before the developers venture forth with new features ALL of the current modules need to be culled and adapted to the suggesst new structure--function in modules; styles in themes; translations in text files or database tables (one or the other NOT both!!!) It is an absolute NIGHTMARE trying to nail down where to find stuff to adapt or fix. AND WITH SO MANY F'ing versions that almost none of the posters write into their posts, I never know if what I am reading applies to my case or not!

En mi caso eran los permisos de directorios e archivos. Los directorios deben de ser 755 y los archivos 644. Con esto puedo llegar hasta la vuelta a mi webshop pero alli hay un fallo de acuerdo de importe--sera un error de redondeo del IVA o algo...

I have been having this problem. I have resolved the inmediate 500 error by changing all the directory permissions to 755 and all the file permisions to 644. Now I get all the way through paypal and then the process blows up because the sales amount and/or pre-tax amounts are not matching. But the first hurdle was the file permissions! Make sure they are correct or you'll never get to the next bug...

All directories must have 755 permissions and files 644. If you are on a shared type server than it is possible you will not get any error pointing to this problem since the local logs don't show it. Before trying anything else change the permissions!!! Good luck to the rest of you all! Prestashop 1.5.3 Paypal 3.4.4

Tengo el mismo problema...mismas versiones... Hay alguien con información???

Also, you'll have to add the field to the product class definition. Overriding the class is the best way, I suppose. But I did it directly in the product.php file in the classes directory. You have to add a property, and later the field in the definition array. Doing this allows all the other units to find your field automatically. Beware that it will be an automatic feature in all "blanket" accesses to the DB, So, you may break things that don't know it is there. Make sure to run through the back end to see where you have to add the field to make things right.

Sorry, latest version 1.5.3

Call objectmodel first! require_once '../classes/ObjectModel.php' require_once '../classes/Order.php'; require_once '../classes/OrderHistory.php';

I added a field to the product table to aid ordering the display of items on the front page. The fornt end worlks fine. But now thew back-end complains about a problem with the eco-tax. I have spent 5 hours scrolling through the virtually uncommented source code and still have no idea in which file the process is blowing up. 1) does anyone have a "blueprint" to the files (something like c's header files)? 2) does anyone know in which file the admin process is trying to verify the field values once the save button is clicked. 3) Does anyone have a feeling for where the addition of a field (the very last column) would cause the back-end to break. I have succeeded in changing the product class with the definitions and as I said the front-end works fine in all respects. Thank you

Has anyone got a different solution that is not written in french? Or that costs so much?

Good job Pit Group Intech B.V.. Very concise and elegant solution.

I know exactly how you feel! Se exactamente como sientes. Se pierde demasiado tiempo en encontrar respuestas y las descripciones son pesimas. El codigophp carrece de comentario util... Far too much time is lost looking for information and the php code is devoid of useful commenting...

Can't find any direct answers to my questions in other posts... What is the Prestashop? What is it used for? What does it accomplish? Thanks in advance.