the.rampage.rado

I have not seen any module for this in PS or TB.... It will require a lot of custom code for sure...

I had the same problem after the patch. It simply did not install to the end - the native modules were all turned on and I had to manually fix all of them (uninstall not needed, install needed) in order to get it to work. Latest Warehouse for 1.6 and I think 1.0.6 at the time of install...

As I said - use one of the recaptcha modules - the one of TB also has recaptch on all forms, including BO so this can be one more level of protection for your BO. There's also one free PS module which is compatible but it only covers the contact form. You will exerience a rapid decline of your spam... :) (to be read as zero spam)... nobody will manually spam with your site be sure in that...

Install the recaptcha module. I personally won't buy anything from shop without contact us page and company info...

Can we modify the code of the module so when some color is selected in it the module to switch all cover images of the products with this selected color (of course if the combination has image associated with it)?

I have the same issue - google search console is looking for home... :) @lesley can you merge this fix and make new version of the module?

Hmm.. I missed this new feature. Sorry guys it's the right decision. :)

I'm using the default scheme w/o id_product... Yes, if we keep PS'es way everything is working as expected but this system was introduced to get rid of exactly the ID in urls... so I consider this a bug...

At the moment we can create 2 products with the same URL structure (same name, same category, etc). Both are visible in BO, the category but when we click and open the second it's not opened but we get redirected to the first. It would be nice if the system checks if there's another product with the same URL and assigne number in the end. That way such duplicates will be imposible and the numbers will play little penalty because they will appear only occasionally.

Here we have agency which is responsible to protect customer rights and a private person can't sue the merchant for such idiotic things like missing info on their site, etc. They can summon this agency and their people file a case against the merchant and investigate. If they find the merchant guilty then the fine is paid to the budget not to the customer. Their product/money should be fixed but with no profit if the merchant is guilty... We're very far away from EU compiance in Bulgaria so it's very curious why only Deutch merchants are so afriad of their law (in contrast to UK, France, Spaint, etc...).

It's not visible in BO :)

So... just wait a second... A lawyer or a person can sue some company for money for not displaying the shipping time of some product on 1000 places in their shop?!?! This is crazy. If such requirement is set by law the responsibe side for bringing companies to court should only be the government through some of it's agencies...

This is very strange because such requirements are in force to protect the customers. If I get it right the competitors are trying to soak the non-complient rivals against the goverment. This happens here in Bulgaria too but not at all at that level.

I'm just curious if you as German merchants had direct contact with the agency that's responsible for controlling the online shops and if they manage to apply those strict requirements effectevly? If I have to show all that info on each and every page of my shop it's better to close it off...

I'm having the following issue (it's present both in PS and TB). When I want to use accented symbols in my URLs the link I have with layered navigation applied gets trunkated to # sign every time. I found a solution when using features - you must reindex your URL index but it does not work for URL containing manufacturers in it. Like the following: https://www.izleznavun.com/%D0%BF%D0%B0%D0%BB%D0%B0%D1%82%D0%BA%D0%B8#/%D0%BF%D1%80%D0%BE%D0%B8%D0%B7%D0%B2%D0%BE%D0%B4%D0%B8%D1%82%D0%B5%D0%BB-zajo - I have it in my homepage slider (2nd slide) and when you click on it the layered navigation filter is removed and all products before the # are displayed. It's working perfectly for URLs containing only English letters. More info here: https://www.prestashop.com/forums/topic/325818-block-layered-pagination-problem/

For me right now tb is fast enough with just the working caching mechanisms. If you add php7.2 with some fixes for the current themes w/o need to fix themes it will be enough. Full page caching is a good thing but if I have to check daily if 10 things are broken or not it's not going to be turned on. Great work guys!

The Full caching is still broken as of 1.0.7 so disable it and continue with your site.

Very strange... I don't have it in Possitions at all. Have to check with google... :(

I tried twice (today and when I created this thred). Both times with zero success. And today I noticed that the hook is not visible in Possitions menu at all. Which is very strange. When I open FrontController it's there. Can you check if you see DisplayHeader in your possitions with 1.0.6 or any other version? I tried ps and tb version of My account block which must add the "Login" tab and profile items there. The footer one is working perfect.

@datakick said in Release 1.0.7 is there!: @the-rampage-rado It should. The error on frontend was still there even after cache cleanup? Nope. @wakabayashi - I will do so tonight when I dive into the shop.... :)

I have not deleted it manually but deleted the cache in BO when I gained access. I think it deletes this cache also?! Am I right?

The hook displayHeader is not visible in positions at all. So I can't use it to add My Account block there. But Cart and search are visible but I think they are hooked elsewhere. I only have hook Header which is as we know not what we need to show items in the header...

Anybody to jump up with me on this one? I'm really stuck. The tb module have all hooks as ps one but obviously the issue is somewhere else. displayHeader hook simply does not show when I want to transplant it there. public function hookDisplayHeader($params) { $this->context->controller->addCSS(($this->_path).'blockmyaccount.css', 'all'); }

Just few impressions about 1.0.7 caching stuff: When I just click enable and all hooks are red the front end gives me 500 and few parts of the page (very strange error, I've never seen it like that). The following days I will check what could cause this. I also had problems logging in in BO but this I imagine was caused by not deleting the cache prior to uploading the files.

Great work @datakick ! Looking forward to 1.0.7 when hopefully it will be included. I don't use it at all, too bugy and I literally don't have time to tweak and find what's causing my issues.