stender89

@dbisupport i did indeed include both posts and post meta tables. A lot of changes were made ind the db, and some words did change. So it might have something to do with ?,?,? and /, lige A/S did not change. Neither did A\/S if you’re wondering.

For me, it doesn’t even seem to be able to switch simple sentences.

We have an active discount plugin, but no rules are active on the products in question – The pricing and discount is just set in the normal WooCommerce “sales price” method on the product.

It seems to only happen when the sum of regular price exceeds the weight based rules subtotal price limit. But that limit should listen to the subtotal of the cart, and not the regular price.

Might actually be something with the list settings in klaviyo..

That is really good, and it works by updating the profile with the new fields – but it doesn’t seem to allow me to subscribe to two different lists in klaviyo still?

If I set the ListID to another list, and subscribe again, then the profile will be updated – But the user is not added to the new list.

Kind regards – And thank you for the quick support

The cookies should be blocked until consent, since they are now necessary for any functionality other than statistics. Which is why they should default to the statistics category of cookies. I would think that if users are saying “no” to statistics data and cookies, then they don’t want to be a statistic on the website either. Sourcebuster/order attribution should be an optin feature, and not auto enabled.

To comply with the regulations governing cookies under the GDPR and the ePrivacy Directive you must receive users’ consent before you use any cookies except strictly necessary cookies.

@luciamarinescu so basically – since it is now becoming default on new installs, new stores won’t be able to use PPOM fields – I would see that as high priority – but that’s just me I guess.

*EDIT – Here is the image, that says you are not compatible btw.

Nothing is corrupt, you just have duplicated functions if you have the newest ocean Extra, and the second-newest theme version.
You could have made checks in your plugin functions to see if the typography functions were already declared, but you didn’t.
That is what caused this error.

@leecollings I fixed it, by going in through FTP and removing the typography functions in the theme file /themes/oceanwp/inc/customizer/controls/typography/webfonts.php
(basically, anything from line 127 and down)

after that you can access the site again, and update the theme, which will fix what you just removed.

NOTE:
Just saw, that you said you updated the theme – but this error should be about updating the plugin first.
Because those lines does not exist in the new theme version.

I also notified their support about this error.

• This reply was modified 2 years, 7 months ago by stender89.
• This reply was modified 2 years, 7 months ago by stender89.
• This reply was modified 2 years, 7 months ago by stender89.