datakick

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.

This error message is a stop-gag measure to prevent leaking information between accounts. Information can leak when you have some sort of cache (can be anything - caching module, build in thirty bees FPC, litespeed server cache,... ) that is incorrectly configured. When customer B request the same page, the cache can return html content originally rendered for customer A -- this html can contain personal information about customer A, including his address. There are other possible reasons for this message to appear. For example, if you have some shipping module that is using the same addresses to calculate shipping costs.

Do you have any full page cache enabled? Looks to me like your server is displaying HTML content that was generated for different user.

Yes, that will be most likely the problem. Most payment modules implement both approaches -- displayPayment and displayPaymentEU. The first one is the older approach, and simply emits HTML code with all payment functionality into a page. And the expectation is that the page to be standard checkout page. This is very easy and convenient for developers, but it's very "hardcoded". It works on standard (or slightly modified) checkout page only. The displayPaymentEU approach is a declarative approach. Instead of emitting HTML, the module describe what is needed to do in order to process payment. And it's responsibility of checkout page to display the HTML and call the payment functions when needed. This makes it very easy to switch between checkout pages. Seems like your modules implemented the old approach only

you look not only for errors, but also for serious warnings. These warnings can raise errors on higher versions of PHP. Look at the fix for this issue in niara theme, and adapt it to your theme: https://github.com/thirtybees/niara/commit/1f9629157606620748b3b5e769d621d9ccdfc751

Your theme is not php8 compatible. You should downgrade to php7.4, install collectlogs module, and fix all (serious) warnings it detects. Only then it is safe to update your store to php8

The migration was probably not complete, some files were not updated to thirty bees version. This could happen, for example, because of invalid file permissions (not writable). Or the migration failed prematurely? The AdminController file should look like this in thirty bees 1.0.8: https://github.com/thirtybees/thirtybees/blob/3880cede3367177640e1ffbe0e7a7f8ffd8d5396/classes/controller/AdminController.php There is no mention of CACHE_FILE_DEFAULT_COUNTRY_MODULES_LIST at all. I suggest you download zip file of thirty bees 1.0.8 and use it to overwrite your installation (ignore install directory, and make sure you upload admin directory to proper location)

I currently run my store on mariadb 11.1.3. It runs smoothly. I updated recently from mariadb 10.6. I haven't seen any performance or other benefits after update to 11, though.

The revws module does not care about how the order was created. It just looks into database to check if the consent was given or not. Note that consent is not per order, but per customer. In this case, your customer probably gave consent when they registered, or during one of their purchase. The only thing that comes to mind is to use dedicated order status for back office orders

Do you mean like infinite scroll ? I'm sure there are couple of modules for ps16 that implements this functionality.

check table tb_shop_url

@Rhapsody please file this enhancement requests on module github: https://github.com/thirtybees/tbphpmailer/issues