datakick

The code goes through following process: if the post request contains gift field with value 1, then gift_message must be set and valid -- non-empty string. So either make sure that gift input field is not present or is set to 0 or that post contains dummy gift message - for example <input type="hidden" name="gift_message" value="dummy"> or override ParentOrderController::_processCarrier and remove this condition

Let me start by saying that this is, most likely, caused by some module. But it is also possible that this is a side effect of hack attempt, especially since this is related to smarty cache. If attacker discovers an SQL injection vulnerability in your store, they can use it to read and write arbitrary data to your database - they can construct custom PHP script and save it inside tb_smarty_cache table. Old versions of thirty bees (<1.4.0) would then execute this custom script when the page is displayed. That's extremely dangerous, because it elevates SQL injection vulnerability to absolute PHP code execution. Because you are on 1.4, you can at least be sure that this attempt was blocked. However, the sql injection vulnerability might be there, so it's essential that you investigate further and find the root cause of this.

You can simply log in to your paypal account and check if the payment was indeed processed. If so, there was some problem during cart to order conversion. If there is no payment, then it can be scam (or simply confused customer)

Carts are converted to orders only after successful payment validation, and that depends on payment module used. And yes, sometimes validation process can fail, and there is dangling cart that has been paid but not converted.

I've fixed the bug and released new version of this module. You should be able to download see it in your back office

There's a bug in this module on line 217. It should read $this->_clearCache('blockadvertising.tpl'); Obviously, nobody is using that module, or at least never bothered to report this error on github.

APCu is most likely the most performant option, because it caches data directly inside php server shared in-memory object cache. There is no overhead to connect to cache server like in the case of memcache or redis. However, there are some things to consider: storing data directly inside php server can be somewhat risky. PHP server process can get pretty big over time. And when your server is low on memory, operation system may choose and kill your php server because it hogs all the memory. This is just hypothetical cache is not distributed. If you need multiple store fronts (== multiple php servers behind nginx proxy for load balancing) than this cache will actually cause a lot of headaches. For multiple php servers, use redis or memcache

Yes, this library introduced backwards incompatible changes. Version 2.8 used Mobile_Detect in global namespace. Since version 3.x, the classname was moved to \Detection\MobileDetect Old version 2.8 do not work on php7.1 and newer, so we had to update it You have to fix the module code that depends on old version of library. In fact, you should rewrite the module to use Context::getDevice / Context::isMobile / Context::isTablet

I've attached new version of module to the first post of this thread. Couple of small issues were fixed. I've also implemented two new payment methods - WeChat Pay and Sepa Direct Debit to test how flexible the new system is. I'm happy to note that it's quite easy to implement the methods now - it looks something like this: https://github.com/thirtybees/stripe/commit/a184785c0475310d7f72d2736d43b0c7e13fb219

Apple pay is displayed on embedded Stripe credit card form payment method. It is displayed only on devices that supports it. On Stripe Checkout, it should be displayed as well, if device supports it.

Yes, I believe it is. I also deployed it to my store already

Please see

Stripe is deprecating old source api soon, so we had to rewrite the module, and migrate all payment methods to use new PaymentIntents api. The rewrite is quite significant change, so I'd like to ask everyone to help with testing before we officially release it. This new version also fixes couple of old bugs (related to webhooks, refunds, etc) stripe-v1.8.2.zip

You have to use correct name for your override, otherwise system will not use it: class Module extends ModuleCore { ... }

Thanks for letting us know. I use stripe, but I don't use these payment options, so I wasn't aware about the api deprecation. We will investigate the effort needed to fix the module. If possible, we will fix it.

simple, update your thirty bees version

Module blockshopreviews is not compatible, it depends on old version of mobiledetect library. Disable this module, uninstall it, or fix it.

these are fields from core, not module. Please file enhancement request issue in github.

It's not commented out. If you beautify the result content, you will get this /* <![CDATA[ */ ;window.addEventListener('load', function () { if (typeof window.cookieconsent !== 'undefined') { window.cookieconsent.initialise({ "position": "bottom-right", "static": false, "theme": "edgeless", "palette": { "popup": {"background": "#004c99", "text": "#ffffff"}, "button": {"background": "#f1d600", "text": "#000000"} }, "geoip": false, "content": {"message": SOME MESSAGE FROM THE COOKIE MODULE} }); } }); ;window.dataLayer = window.dataLayer || []; function gtag() { dataLayer.push(arguments); } gtag('js', new Date()); gtag('config', 'G-R6CE3JK4G6'); ;(function () { function s() { var e = document.createElement('script'); e.type = 'text/javascript'; e.async = true; e.src = ('https:' === document.location.protocol ? 'https://' : 'http://') + 'cdn.fraudlabspro.com/s.js'; var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(e, s); } (window.attachEvent) ? window.attachEvent('onload', s) : window.addEventListener('load', s, false); })(); /* ]]> */ The all comments are closed. There is, however, syntax error in this javascript snippet, related to text SOME MESSAGE FROM THE COOKIE MODULE

Note: if you don't see core updater in the list of modules, you probably don't have tbupdater module installed. This module used to be used to download other thirty bees modules. Since 1.5, it is no longer needed. But on older tb version you still need it. You can easily install core updater from github repository - https://github.com/thirtybees/coreupdater/releases , and then update to 1.5.

I've already replied in the other thread you have created for this very same problem.

Unfortunately it's quite common that CSS or JS from one module impacts other modules. If you are using CCC, try to disable it -- sometimes that helps. If it won't help, then you look into your browser console, look for any errors or warnings.

This indeed looks like your hosting provided changed PHP version of your store. You are running on older version of thirty bees (error lines suggests version 1.1.0, or maybe older) that is not compatible with PHP 8, or even PHP7.4 You should either downgrade your PHP version back to what you were using before (my guess would be php7.2, but who knows), or update your store to newer version of thirty bees and take advantages of new PHP version.

What payment method did you try to set up?

Hello, could you please retry again? There was old inactive paypal subscription associated with your account that blocked the process.