the.rampage.rado

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.

Great work! Looking forward to the custom 'stars' feature! :)

I was referring to the 1.0.x version as minor, not your automated system. Can't those items be automated as well?

OMGOMGOMG!!! I'm blind... Thank you very much! I was searching for it in the code and db...

I would recommend to update your sitemap with the new adresses (using the gsitemap module). You will have few lost clicks but otherwise manually redirecting all product and categories via .htaccess file will take you ages depending on the number of products. Right after the migration with the new URL scheme you will see lots of errors in your Google search console account that their bot was unable to find the products. Those will last for few weeks up to few months and after you mark them as old/fixed the bot will stop going there and Google search will display only the new addresses.

I think I asked this couple of months ago but I can't find the thread. I'm making new site and I want to change the mobile chrome tab colors from tb yellow to my green but I downloaded the whole site and I can't find this meta tag. Am I stupid or what?! :D

Thank you! How much time does it takes with the new automated system to push minor releases let's say every two weeks?

I tried both TB and PS versions of the module and I'm using one of the left header versions of Warehouse. I need this block to show under the cart but it does not allow to show in the sellected hook. I have to manually add link in top bar and then there's no exit option easily visible. Of course the hook does not show in the list with choices when I want to transplant it. Do some of you use Warehouse with the same configuration?

I'm eager to test the new cache fixes... :)

This is the same behevour as in PS - you always have to firstly click save on the first tab - name and desc. Afterwards you can add all items except Combinations generator with just one save.

Yes of course. If it was most of the time I would have posted a thread here.

I got this on the homepage couple of times yesterday. Clean 1.0.6 w/o full cache.

I understand that. Can you tell me how I can troubleshoot this one on my own? There's no error. Do the possition in advanced settings play any role? I don't have any extravagant modules that could mess the work of this one and it's only strange that it's only failing on contact page.