Pedalman

old www.shop.de/category/product.html new www.shop.de/category/product

/sending you a coffee

OLD: articles {categories:/}{rewrite}.html categories {categories:/}{rewrite}/ (! notice the final / )

I migrated, too :) with a live shop less than 12 hours later I notice that product pages are rewritten to a scheme without .html. I like that but all old seo juice and links is now gone to error 404 :( I read your comments carefully and wonder if I still want to have ThirtyBees rewrite of (e.g.) product pages: Is there no way to rewrite via regex in the htaccess?

No no, but any way thanks for showing me the patch. I applied it. The issue is with Warehouse and Shoply theme only as far as I am aware of. As I read in the link given above by me, “products ratings on product page v1.0” - by IQIT-COMMERCE.COM is of course dependent on productcomments. Problem is that if both are installed and activated, the product page is no more correctly rendered.

Uhh, another isse: This is to be seen with 3rd party theme: Warehouse / Shoply: https://themeforest.net/item/warehouse-responsive-prestashop-16-theme-blog/3178575/faqs/20892 TB's productcomments module does not work with "products ratings on product page v1.0" - by IQIT-COMMERCE.COM. Or, vice versa... If both are activated and that is I want at the moment than the product.tpl is rendered flawly. It looks as without CSS etc.

Hello I want to report an issue with TB productcomments module. I hope it is ok to do it here instead of the bug forum. Can be moved anyway :) The issue is: I wanted to try out the module myself and commented on a product. But the module reads out the wrong product title. The image is correct in my case. May be more is convoluted?

Mh, I wanted to migrate since I am more than disacouraged by bizarre issues by Prestashop ;) Ok, I will see. I actuall ran the migrater now three times in a row. Does this raise issues or is it safe to go? I would like to know before I procede. Moreover, after migration I will then use the TB Updater module ( tbupdater-v1.2.4.zip ) to update to the latest 1.0.3, right?

Hello I just copied online shop to a subdomain and all was fine. Than I went to migrating to TB. The updater file tells me it migrates only to TB 1.0.0 That is fine with me since I thought I can then in an eye blink update to the latest TB 1.0.3 I went to https://thirtybees.com/migrate-from-prestashop/ and then to https://github.com/thirtybees/psonesixmigrator/releases/tag/1.0.0 and downloaded, installed and run the module. Anyhow after to the migration it tells me this: Your current PrestaShop version: 1.6.1.999 ?!?! I assume there were issues. It looks to me as TB was only partially installed. Shal I run the migration module a 2nd time or the TB updater or do I have to make a reroll of all?

I understand your arguments well. I already cloned the live shop locally and mirgrated to do tests and set up a new template. I thought that I could set up a server to the state my live shop was when I migrate to TB (In order to make this happen I would as always backup the DB and all files from the live shop before I migrate) so literally speaking I would return from TB x.x to PS 1.6.14. But this was wish thinking. So I migrate to TB in a few days fully. And may be TB will offer some day in the future a 'perfect' export feature that makes migration to a freshly set up PS or even other ecommerce system possible.

Hello I am really eager to migrate our live shop from 1.6.1.14 to ThirtyBees. My gut feelings are more than fine also due to the really fast and perfect response of coders and developers here in the forum. But you never know what happens in the future. Dekker might win an old Alpha Romeo and could decide to become an automobile enthusiast .) Anyhow, I just want to know if the way back to Prestashop is possible if needed. In my case we would leave PS 1.6.1.14 and migrate to TB. TB will develop. So will Prestashop in its own way. I assume the way back would be to the PS version that was left if possible at all? Thanks alot

You are right I mixed up the terms. I meant translations packs and then the files in it. Can you me explain please that the function to export a language is for? How can it help me to be up to date with my language/translations.

At the moment we run Prestashop 1.6.1.14 with slighty modified translation fields. What I never understood in 4 to 5 years Prestashop is how to mirgrate language packs updates best . Locally I migrated 1.6.1.14 to TB 1.0.1 and I downloaded via backoffice the actual language pack for our language (German) for TB. I also downloaded it from the given TB language download website and compared the files in the gzipped language pack. So far so good. It looks for me as files downloaded via backoffice or the from the website are identical (even V1.0.0 up to 1.0.2?). Anyhow, is there a handy way to merge an actual language pack with an existing one. Mostly shop users may modify some fields in their template or add some fields to it. I tried to do a file comparission but that seems not to work. Is it best to download each time a new language (pack) if one exists und to copy it to the working template while overwriting at the same time any given 'own' translation and we have to manually correct fields where we need our own translation? PS: The ID's of the fields. Are they unique or alter they from version to version?

As Occam said it for PS V1.7 the cuplrit file for PS1.6 is also : hookDisplayProductPriceBlock.tpl For me it worked the 1.5 years to set the whole content of this tpl into the no cache brackets: {nocache}… {/nocache} We could then still run PS smarty caching and a full page cache module (offered by BELVG). cheers

@ssimard said in Retina images! Please help!: Oh and I should also mention that importing through the csv DOES NOT create the 2x retina images, it only works when adding a product via the backend. So I had to hack the copyImg() function in AdminImportController too... That interested me for ages! Great to read about somebody who is interested in best possible image quality in his shop (I know, there is still pagespeed and Google). I always wondered how to get this done and which is the right workflow to adapt! Most of the time I am lacking time so I follow the lazy path. I am a Windows user and shoot product images myself. I have them in high res and tried many workflow and still do not know which is best. Prestashop as TB have their own way of shrinking images. For a year or so I also installed M. Dekkers :) ImageMagick module that trims also white space. But I thought that programs that are specialized on shrinking images, even lossless, that exists for years now can do the job better. Moreover, they are easier to use on a bunch of images via batch that the backoffice uploading of images or CSV import way of Prestashop. To name are PNGout, PngOptimizer (Freeware) and the Riot plugin. These offer a nice user experience since they work well with XNview, IrfanView, standalone and others lXN forum . So, I shrinked all my digital product images and even those images of my template in batch via those tools. Nowadays, eventually, there is a very cool tool for windows users that runs images in batch against dozens of those optimizuers for free by Javier Gutiérrez Chamorro (Guti): FileOptimizer In a nutshellm, I wonder if that was not contra productive or in contrast to the main aim ti improve image quality in the shop while at the same time reducing loading time since Prestashop applies its own shrinking magic?! PS: I set Prestashops's image option in BO to 100% or 90% in order to minimize the shrinking, so called optimizing, of already shrinked images. What do you think about this worklow? Makes it sense to compress images before we load/import them into TB/Presta? As you know there are some modules/services on the market that state the same but take money and bandwith for this purpose.

Hello I am another user from Germany. I run my shop via Prestashop for 5 years now. I am happy that TB supports the Advanced EU Compliance module now and may be Dekker finds a way to integrate it into TB's core. If complicated at all ;) than it will be the tax calculations. Anyway, you find these in the module. Incompatibilities were seen between this modul and Prestashop V1.6.x concerning smarty cache. Sometimes information about delivery time was shown twice on product information. Often in our shop after a complete checkout. Anyway, all information if found on the Prestashop Forum and there has also been ticket opened. But this was never really solved :( All you could do was do exclude certain parts from smarty caching in this module via editing the module. This was done very easily via {nocache}... {/nocache}

Thank you for the tipps. I will procede as suggested. Cheers/Grüße

Hello since two years or so we use the Advanced URL module on Prestashop. It is meant to 'clear' url. addon page I heard about TB half a year ago and spend today some hours reading about it here in the forum. I am really willing to migrate to TB now since I read that the Envato Warehouse template (we bought its kindle Shoply that is based on Warehouse) is compatible to TB and vice versa. Since I run our shop for years now I use and bought a handful 3rd party modules. However, we are luckily still on the V1.6 branch and I hope there are no issues to be expected. With one or two excetions: we bought from BELVG a full page caching module. This I am happily willing to disable since TB seems not to this. I run since 2 years or so this VIP Advanced URL module and Google noticed that :) So, I wonder how to migrate best to ThirtyBees and using its own URL rewrite mechanism without convoluting these due to the named module. I am no SEO expert and am not able to do any rewritings in httacess. I could imagine a nice worklflow for any migration would be to have a tool that stores the actual URLs of the shop in a DB or CSV and compares these to the TB ones after migration? thanks alot for helping me here