the.rampage.rado

Encryption by itself is not a bad thing but the problem is the compatibility with the loader.

After I have installed the fixed captcha version only couple of emails got through and I don't believe they were automated. What version do you use and could you share your configuration?

This is what's hardcoded in both modules. Now I notice a strange behaviour - sometimes the modules load webp and sometimes they load jpg. What could be causing this? I mean same image, same place in the module when called from different categories/products displays different format.

What about modules that look for jpg? I have some part of Warehouse (mega menu and content creator) that call for jpg despite webp is enabled. What about them? Up until now TB keeps the original source file and use it for future use? What about your idea? I personally don't upload gifs but I imagine some product schemes may come in it so I believe they all should be enabled for upload in BO.

Are there such shops, still running on PS1.3? You would probably first update to PS1.6 and them migrate using the module above. (using php 7.4) Then remove migrator and update to edge with core updater. Don't forget that TB has core updater and updater module (responsible for the modules updates).

This is exactly my motivation to rise this thread. Warehouse's cookie module depends on external call and this call is slowing our shops. If we can host the .js locally it would be perfect.

Totally agree for every other part of the website except those pesky GDPR popups. I believe they should be standardized across platforms and sites as they aim to comply with single law and the user daily have to open and accept few such popups. If they are similar in appearance the user is more familiar with it and quickly can deal with them. If every site uses their brand colors, different modules, even different 'comply' methods it's a mess for the customer.

Not but the said plugin is. As for the design - yes, you're totally right. In general all my posts here (or in any other forum) express my opinion. Yes, for me the visuals are not that appealing. Regarding the functionality - is the module depending on their service? Because my suggestion is self-dependent can could be called from localhost, not even call to CDN is needed.

@e-com, thanks for your reply. I have few concerns about your suggestion: 1. Project is dead 2. Interface is not appealing 3. Lack of polished features

Hi there! Yesterday I found this nice cookie consent framework: https://github.com/orestbida/cookieconsent/ The static integration will be simple imho but would it be possible to use it and make TBs native cookie module from it? We could have: cookie setup part where the admin can put different types of cookies in different categories. appearance and functionality set up styling links to ToS and Privacy pages, etc. The framework is active since 2020 and I believe the author is very passionate about it. The appearance and functionality is cutting edge, nothing to add there I believe.

Totally agree with you. What I believe will be perfect is just make the current 'Change' (and then Save) button always visible. This will clear the customer expectations when they scan this step with their eyes. Currently if they touch/hover outside the 'cart' portion of the module this hides the Change/Save button. No further changes are needed here I believe.

Quick question - do you sell to individuals and are you registered in with the One Stop Shop?

As continuation to this today I noticed that if customer clicks on Change and then clicks on the second part (Shipping details) but does not click on 'Complete' this text is hidden and also the next part of the checkout is shadowed out. So the customer is stuck there and if they don't click (hover on desktop) back on tl the cart part they are unable to continue. I can see this being an issue on mobile.

He means it's not necessary to delete it.

Any reason why you are running this old version instead of the latest most stable, bug-free and not to mention secure version as of now known as 'edge'?

He means 'edge'. Everything after 1.4...

@Mark I believe it's time for you to rapidly change your tone here. Nobody on this world owns you anything. If you don't like this project there are plenty of paid or premium options that you can migrate to. If you like to help - do it with ideas not with negative criticism that helps nobody. If there is more business there will be more developers. The community is small but healthy thanks to couple of members, @datakick included. If I was you I would not cut the branch I'm sitting on. @datakick and @Smile, guys keeps the great work! The project had never been so vibrant and alive. Plenty of GREAT additions in 2022 and this year is starting excellent. We're waiting for those new modules!

From the lack of answers I'm concluding it's only me that's experiencing this issue and everybody else sees the captcha in the module (if enabled)?

Yes, exactly. APCu is plenty sufficiant for me. I have no need currently to split the servers.

Just installed on 2 of my shops - it's crazy fast with APCu.... No errors so far. I think it's time for the FPC to go forever!

I can not recommend @Daresh's module and support enough. He's pumping versions left, right and center! He also have other usefull modules in CodeCanyon. Definetly a developer that will be of help for the TB project!

Just found a problem (I'm not calling it a bug because the module can't work with all modules on the Earth). When checking out if a customer want to login from within the module and TB's native captcha module is installed the customer sees 'wrong password' notification even if they enter the correct password. The module does not show the captcha. Workaround is to disable the captcha for logins but a strange behavour is that the module creates a profile when customer inputs a password even if the 'account creation' captcha is active. So I believe there's an inconsistency somewhere - either the captcha should be shown or it should be somehow omitted both for account creation and login purposes when in the module.

The module does not work for me and I had to uninstall it. It was working tremendous time savings but after the migration to TB it stopped working.

In the end we're left alone as the developer of Warehouse is not willing to make paid work in the 1.6 of the theme in order to make it compatible with newer php version. I'm starting this thread in order to organize it as self-help guid for the users. Block Cart: themes/modules/blockcart/blockcart-json.tpl (partial merge from community theme - uses different small image and fixes php 7.4 issues) Block Layered Navigation Mod: modules/blocklayered_mod/blocklayered_mod.php (one more warning and one notice but most issues fixed) 18.02.2023 based on the most recent official module

Added ctry in the bypass section as per the advise in github and now it appears to work as expected. Will monitor it further. Do we have this issue in TB: https://github.com/PrestaShop/PrestaShop/pull/23269/files as it's described in the issue thread above?