roband7

Social media stuff like: facebook pixel tracking google adwords tracking instagram feed facebook like box addthis image sharing short codes I'm also hoping that we can begin thinking about a better way than the current module/hook system. Something more widget-like, where the individual widget has no knowledge at all about where it's used. Coupled with some sort of grid-based layout-system where instances of the widgets are combined. Coupled with some sort of system where these grids are connected to specific pages.

@rubben1985 said in Decent redirect in Multi store: Hi guys, Thanks for answers. @Traumflug I am not developer so I do not really know how to do it. @roband7 I will try to learn what you propose in first link. About those addons, they are not thought to redirect to the correct country store but to" redirect to the correct language version of one each one of "each store" Yes, the webserver GEOIP redirect needs to be in front of these addons. I just wanted to mention them as I know prestaheroes.com have done a lot of addons in this area.

It would be a pain to maintain two full translations. An interesting approach would be to allow a translation to extend another one. That way you could have one base german translation using the "Du" form, and an extension translation using the "Sie" form just overriding the little subset in need of change. I don´t know how technically difficult this is for Crowdin and thirty bees, I´m just throwing it out here as an idea...

@Traumflug said in Retina images! Please help!: Makes it sense to compress images before we load/import them into TB/Presta? Not really. Currently even the "original" image gets rewritten on import[1], so such optimization doesn't survive the minute you add the image. If you want well optimized images, add all of them, then run this optimizer on all the images in img/p/. Like downloading this folder via FTP, then optimizing, then re-uploading the result via FTP. Thirty bees won't touch these images and serve them happily as long as they exist and as long as nobody starts a "thumbnail regeneration". Adding images later requires repeating this procedure for just the new images, of course. [1] This is known and considered to be a mis-feature, but as always, somebody has to rewrite this code section, which didn't happen, yet. If you add the imagemagick addon this misfeature is fixed there. This of course needs to be ported to the core, but this is a nice interim fix.

I would do the initial geoip redirect in the webserver, nginx for instance has this feature builtin. Here's an overview: https://blog.murwell.com/2016/12/03/tutorial-to-redirect-web-traffic-based-on-location/ Some addons worth checking out that might be useful in addition to the above: https://www.prestaheroes.com/en-us/modules/geo-localization/geo-targeting-pro-price-by-country https://www.prestaheroes.com/en-us/prestashop-geo-localization-solutions/prestashop-multistore-multishop-pro

@Havouza Absolutely, see the reply from @DavidP above

@mdekker I noticed in another reply that you´re using the Warehouse theme in your own shop, at least that´s how I understood it. Was anything special needed in thirty bees full page cache config for Warehouse?

One possibility is that the addon uses a hook to add something to the header that in turn tries to contact something slow over the net. Try using the Inspect function in the browser, then select Network, then reload the page and look for slow responses in the Inspect window.

Interesting, looks like we might be hitting two bugs that have been discussed in the forum here: Windows installations Subfolder installations Perhaps we can kill both bugs with these fixes? I agree on @yaniv14 approach for a short term 1.0.2 type fix, things mostly work, just attack the few problems left one by one. @Traumflug approach would be the way to go for a release 1.1 type bigger cleanup fix. That one will not be easy.

@Havouza I'm not sure I understand why you want to create a new category featured and change the category ID in the featured product module. Just put the product in the Home category and it will display as a featured product. No need to add new a new category or change the module.

I'm not sure I understand. Your page now shows both new products and featured products. What you describe above sounds exactly like featured products. If what you want to do is just remove the "new"-attribute on all the products, you could update the database like: update psproduct set dateadd="2017-01-01 00:00:00"; update psproductshop set date_add="2017-01-01 00:00:00";

Happy to hear it got sorted. The migration tool should have detected and reported this earlier in the process though.

Almost all of us run thirty bees on Linux. I agree some time should be spent so it also runs fine on Windows.

@luksl I'm afraid I'm out of suggestions. We really need the logs for the 500 errors to figure this out.

@luksl MySQL 5.7.4 and greater by default disallows 0000-00-00 as dummy date. There's more info about this and some suggested alternatives and workarounds here: https://stackoverflow.com/questions/36374335/error-in-mysql-when-setting-default-value-for-date-or-datetime

@luksl errorlog D:\Dev\xampp7013\php\logs\phperror_log If you're running this in Linux you cannot use Windows style files names. Replace that with a Linux style file name and you'll get your logfile.

Why not just make the automatic logic the one and only way this is done? I'm trying to understand the use case for not doing this automatic, does one exist?

@luksl What we need in order to help you is the server-side PHP error log. This will typically contain a PHP stacktrace for each of the 500 errors.

So you did both of these and didn´t find any errors? Check the serverside log for PHP errors. Check the browser console log for Javascript errors. And what about the serverside HTTP access log, do you see any unexpected requests there returning 500 or 404 errors?

You probably made some error in the override you created. Check the serverside log for PHP errors. Check the browser console log for Javascript errors.

Yeah, the file should end up starting like this: <?php class CategoryController extends CategoryControllerCore { /* * module: jscomposer * date: 2016-02-09 03:58:59 * version: 4.3.13 */ /* * module: jscomposer * date: 2016-02-09 03:58:59 * version: 4.3.13 */ /* * module: jscomposer * date: 2017-06-03 21:52:34 * version: 4.3.20 */

Thanks, that's the right file. Are you really sure that this the file as it was received from the theme author? Because there's no way in hell that file can work. Sure you haven't edited it? Anyway, the fix is easy. Notice there are three lines there at the top like this: * module: jscomposer Notice that the first and third of these lines has a line before it containing: /* So you need to add this /* line also before the second!

I believe the problem with phsimpleblog was covered and fixed here: https://forum.thirtybees.com/topic/332/phsimpleblog See the post from @braffas at the end of that thread

If you just migrate a shop, keeping the database from prestashop unchanged, then all the IDs will be kept. Then thirty bees should do automatic 301 redirects. If it doesn't I would classify it as a bug. In our case we plan to start fresh with thirty bees, so all the IDs will be different. The plan is then indeed to add a crapload of 301 redirects.

Fair enough, I didn't mean to be rude, I just wanted to establish what was most important to you. What exactly is missing in blog system that comes with Warehouse? There's some ideas to improve the thirty bees blog addon here: https://forum.thirtybees.com/topic/312/some-ideas-for-improvement If you really want wordpress you have this addon: https://www.prestashop.com/forums/topic/432988-module-wordpress-blog-integration-to-prestashop-1314151617 https://www.inveostore.com/wordpress-integration-to-prestashop-35 I have no idea how good that addon is or if if works fine with thirty bees, just wanted to mention it as an option