Acer

Does anyone know if this TB Bleeding Edge + Panda caching issue has been resolved? @rubben1985

MyPresta HTML Box link if anyone is interested (though with TB's built-in HTML block this one is actually not needed): https://mypresta.eu/modules/front-office-features/html-box.html Some great Free Modules from MyPresta: https://mypresta.eu/prestashop/tag/for-free/ And yes, most of these modules are Thirtybees compatible. Bytw: MyPresta is the company of great Prestashop legend Vekia - used to be very active on the PS forums for years and supplied excellent help and modules...

@Traumflug @datakick @Jonny Please may we ask you to shed some light on this?

Hi I'm curious, did you get an answer or solution to this issue? A lot of us are running Panda, so if there's a problem with Panda + 1.1.x bleeding edge...

So I encountered the same problem now with TB 1.1.0 and latest "nocaptcharecaptcha" module... I can confirm that Datakick's fix above works. For those of us with an existing override, this post will help. Module Update Request please: Can Datakick's fix please be incorporated into the module and pushed as update? https://github.com/thirtybees/nocaptcharecaptcha/issues/5 New users / developers will continue to experience this problem until it's been patched. Also, I'm sure (from what I've seen in this thread) that there are merchants that think this is working when it's actually not.

For those of us with an existing ContactController override: Ok confirmed, the reason why it wasn't working on my side is because I already had an override for ContactController as stated above. Used the new ContactController file as created by the "nocaptcharecaptcha module" as main. Identified Nemo's code from previous override and pasted into new main override (the entire "if (Tools::isSubmit('submitMessage')) {}" code block) Commented out "return parent::postProcess();" from the "nocaptcharecaptcha" module. Now everything works as expected. For those with no previous ContactController override: The following works: Go to "override\controllers\front\ContactController.php" and replace all occurrences of Module::isEnabled('NoCaptchaRecaptcha') with Module::isEnabled('nocaptcharecaptcha') As per DataKick's post here Hopefully this gets patched and rolled out as update to "nocaptcahrecaptcha" module.

I still think the module should be patched and pushed as update, as people have been downloading 1.1.0 with this bug, activating Captcha and just assuming that it was working correctly... However, I think that the reason why the "fix" is not working for me at the moment is because I already have an override for ContactController. My override is a result of implementing Nemo's "add additional field to Contact form" post. (http://nemops.com/adding-new-fields-to-prestashop-contact-form/#.XjkioCOxWUl) Will see what I can do to merge the two and will give update.

Hi Nope, this doesn't work :( @datakick mentions here to do the following: "you edit override file (\override\controllers\front\ContactController.php) and replace all occurrence of Module::isEnabled('NoCaptchaRecaptcha') with Module::isEnabled('nocaptcharecaptcha') " For me, there's only one instance of the title case "NoCaptchaRecaptcha" in this file and replacing it with lowercase does not work. Contact form still bypasses Captcha. Can this module not be patched with the fix and pushed as an update? Like the other TB modules (Beez Blog etc)?

Hi Tried implementing NoCaptcha Re-Captcha on the Contact form (using TB 1.1.0 with Panda with latest Captcha module) But the Captcha validation is being skipped, so the form allows you to post without Captcha validation. Login attempts is set to 0. I see this has been reported as a bug a while back, but not seeing any updates? Also, it appears to be mentioned in the thread below, but no apparent solution? https://github.com/thirtybees/nocaptcharecaptcha/issues/5 https://forum.thirtybees.com/topic/2400-2400/no-captcha-recaptcha-installed-but-start-receiving-spam-mails-again/#comment-23808 Is there perhaps a temporary fix that I can implement in the code until a bug fix becomes available? There is a javascript error that occurs after the form has been submitted (in case this is relevant): recaptcha__en.js:515 Uncaught Error: reCAPTCHA placeholder element must be an element or id at Object.lS [as render] (recaptcha__en.js:515) at onloadCallback (contact-us:299) at WY (recaptcha__en.js:518) at recaptcha__en.js:511 at Qo (recaptcha__en.js:504) at Cc (recaptcha__en.js:511) at recaptcha__en.js:519 at recaptcha__en.js:539

He himself mentioned this in a thread. Community all wished him well here. So... Is it wrong asking how the guy is doing? Not asking for private info bytw.

The reason is that he as come out and mentioned this himself (in the thread included below). This comes from a genuine sense of caring and well-wishes from myself and it seems from others. Unfortunately, it's now become awkward... All we wanted to know is how he is doing (not private specifics of course). He happens to be a big part of TB... It's great that you guys are missing the point here...

Hehehe. Look, I asked 18+ hours ago. I think it's reasonable to do a follow up, to keep this post / thread alive. If you want to make a comment, you can ask the team guys why they haven't bothered to reply?

Can the team give us an update please? @datakick @Traumflug @wakabayashi @lesley

Hi I'm sure many of us are wondering how Lesley is doing? Can we have an update please?

Yeah, any news on @lesley? I'm sure we're all curious how he's doing? Best wishes to Lesley and for a speedy recovery.

Thanks @lesley and @Traumflug for the feedback here And for the original DH42 email (Lesley) 😉

As @Traumflug mentioned, search for a folder with the name phpunit if you find it, you can delete the phpunit folder and all its content. Also, I think it's safe to assume that "upgraded PS 1.6 to TB sites" could be at risk here also.

Right, obviously. Lol... I think when something like this comes up, it's easy to panic automatically and risk not seeing things 100%. To quote myself: 😊

If there are no folders, but the phpunit.xml file comes up? vendor\greenlion\phpunit.xml vendor\swiftmailer\phpunit.xml

Ummm. I think the TB admin guys need to reply here pls... Just doing a quick search on my local TB 1.1.0 install and I'm getting phpunit.xml in multiple locations. @GotaborTry doing a search just for the file "phpunit.xml" and see if something comes up? TB admins, some feedback pls?

Hi I've received a mail for DH42 about a new PrestaShop Security Vulnerability that affects all versions of PS. Can you guys please inform us if this applies to TB? This is the "more info" doc from PS https://docs.google.com/document/d/1D76Lj93gw-XZ8GgV8UzK6Oi6u5qLxLDEsC2298Go-as/edit#heading=h.tjhj04l5p8kk

Hi @rubben1985 Nope, as mentioned in this post, Panda+TB+LiteSpeed cache does not work together at the moment. I've reached out to both developers (Panda+LiteSpeed) and they've mentioned that they would like to fix this eventually. However, as they are both pretty busy I'm not sure when this will be. Will update this thread when I hear more.

Just an update on this: Awesomely, both @Jonny and Lauren from LiteSpeed have shown willingness to make TB Panda compatible with the LiteSpeed plugin! 😁 Big thanks in advance to both of them. It now all depends on workload on their sides, as they are both currently focused on other projects. Will update this post when I've heard of any progress.

It's worth experimenting. But I'm not sure if it will work. One thing that I did notice is that it caches the user name that is logged in (in the top bar, front-end, shop side). So I'm not sure if telling LSCache to not cache the 'Login' module will stop this from happening. Either way, I'm waiting to hear back from @Jonny and the plugin developer.

Alas... 🤨 It appears we celebrated a bit too early on this one... So my initial testing was done on a quick test site - and at first everything appeared to be working... Unfortunately when I did testing with an actual production / Live site, I discovered it's actually not compatible. LiteSpeed plugin caches the crap out of Panda. Stuff like user logged in, cart etc. are all cached. Yes it's blazing fast - but it's not working. Apparently Panda needs to be modified to handle LiteSpeed. I've reached out to the LiteSpeed plugin author and she appears to be willing - but has other priorities to wrap up first. At the same time, I've reached out to @Jonny to check his willingness & availability. Will update this thread when I know more. Perhaps someone here has been able to make Panda compatible with LiteSpeed? Bytw: A side benefit of being on a LiteSpeed server (even without the plugin), is that the server is natively faster than Apache/Nix. Also, when you're on a LiteSpeed server, it comes with a modified and optimised LiteSpeed version of Memcached. When this is enabled (both in PHP options and TB caching settings) you get a speed boost anyway. No, not 'light speed', but it certainly is close.