gretzteam

Hi, Nothing here? I can't believe nobody is using the 'message' feature of the back office with a language different than english! I'm using 1.4.3 Thanks

Hi, I created a few custom 'order messages' in the BO/Orders/Order Messages tab. Then, I can send this template email to the customer using the 'New Message' option from the bottom left corner of the order page. I also edited the translation file for my language so that the /email translation/order_merchant_comment.txt looks like this: ------- Olá, {firstname} {lastname}, Você recebeu um nova mensagem em relação a compra #{id_order}: {message} {shop_name} ------- Now, the customer receives an email that is exactly as predicted, except that any special character that were in the {message} part created in the BO/Orders/Order Messages tab appear all wrong. For example, the email could look like: -------------- Olá, John Doe, Você recebeu um nova mensagem em relação a compra #27: Você optou pelo pagamento com depósito bancário, ------------- That last line should have been: Você optou pelo pagamento com depósito bancário Any idea how to fix this? Thanks, Dave

I think I figured this out. First, like DsToys pointed out, setting the status of the order to 'cancelled' will not affect the stock. You need to cancel the actual product in that particular order page. However, for this to automatically increase the stock, you need to have 'merchandise return' turned on. Anyway for me that did the trick. Dave

Hi Potentam, I'm having the same problem here. Did you ever figure out how to put the product automatically back in stock if I cancel the order? Thanks! Dave

Hi, I'm trying to figure out what the preferred flow is for product import with .csv (Prestashop v1.4). Should I create one file for categories, one for products and one for attributes? I can see this becoming a little hard to track - but looks like the only supported way. Is it possible to manage everything with csv import, or there are stuff that can only be done manually in the BO? Thanks, Dave

Yeah now that I've gotten my head around the problem better, I see what you mean. You do the grunt work offline once, then upload to server. If you need to make new mods later, you simply try offline, and replicate the procedure online when you've debugged it. This leads me to this question: Isn't it a huge flaw that we cannot create a blank database, if only given a working version of some prestashop store - that might contain custom modules etc..? It seems like the ONLY way we have to create a database with all the required field is to redo the whole thing manually. Dave

Hi, I understand the need for a local development setup. Say we start everything from scratch. 1) install prestashop locally. 2) install languages, currency install a bunch of modules, edit some files, debug stuff...basically transform a raw install into my shop. 3) when mostly ready and happy with the shop, follow the instructions to upload everything to the server. This seems quite easy, put everything there and modify a few config files. 4) Export the local database and import it online. Is this really going to update the online 'raw' database with all the fields required. I mean all the fields that prestashop needs, AND also everything that might have been added by the various modules install? Thanks a lot, Dave