strarsis

The Translation Tools plugin indeed allows downloading the missing JSON files and restoring the translations.

@jamesosborne: Hi James, I followed the steps for forcing Site Kit to regather the site details, but the issue persisted:
I changed the primary site domain, reset Site Kit and started the Site Kit setup process again, but the same error occurs.

One thing comes to mind: Could it be that the particular Google account reached its limit for Google Analytics accounts? But would not this cause a specific error message during the setup?

@jamesosborne: I submitted the form. (Thank you for keeping the site name and domain private.)

• This reply was modified 1 year, 1 month ago by strarsis.

@mguenter: I mean the pre-release which works without issues. When would it become a new, stable release?

@mguenter: When would be the next stable release, that would include this fix?

Hi Matthias,

thanks for the patch! Indeed, after installing the patch, the content blocker can be created/updated without an error.

The service that previously also failed updating (failed with an error) still failed updating – but creating it anew works fine.

Concerning the issue with non-listed “zombie” services and content blockers: I will try to create a reproducible example with steps. It appears that on update/creation errors a part of the service or content blocker was not saved in database, it is still listed in the Dashboard, but not in the edit lists.

• This reply was modified 1 year, 4 months ago by strarsis.

@mguenter: After some further investigation it appears clear that indeed the TcfVendorConfiguration class is simply missing from the plugin files.

I can find class files for the namespace DevOwl\RealCookieBanner\lite\settings, but TcfVendorConfiguration is not among them. I grepped the whole plugin directory, after plugin installation and setup (in case the plugin downloads those files somehow), and nothing came up as a class definition.

In the aforementioned Hooks.php:

$postType = $meta_key === Blocker::META_NAME_SERVICES ? Cookie::CPT_NAME : TcfVendorConfiguration::CPT_NAME;

When $meta_key is something else than the service group, e.g. “Statistics”, the custom post type name is retrieved from the constant CPT_NAME of the TcfVendorConfiguration class. That TcfVendorConfiguration class does not exist in the plugin directory, nor in any files of the whole WordPress site.

What surprises me is that the TCF feature is used at all in the free variant of the plugin, as TCF is only available in the PRO variant and should always be disabled anyway.

This is the (redacted) JavaScript equivalent fetch request the client side does:

fetch("https://example-site.localhost/wp-json/wp/v2/rcb-blocker?_method=POST&_v=3.7.2&_locale=user&_dataLocale=de", {
"headers": {
"accept": "application/json, /;q=0.1",
"accept-language": "de,en;q=0.9,en-US;q=0.8",
"cache-control": "no-cache",
"content-type": "application/json;charset=utf-8",
"pragma": "no-cache",
"sec-ch-ua": "\"Not.A/Brand\";v=\"8\", \"Chromium\";v=\"114\", \"Google Chrome\";v=\"114\"",
"sec-ch-ua-mobile": "?0",
"sec-ch-ua-platform": "\"Windows\"",
"sec-fetch-dest": "empty",
"sec-fetch-mode": "cors",
"sec-fetch-site": "same-origin",
"x-wp-nonce": "cc5b2a2ec1"
},
"referrer": "https://example-site.localhost/wp/wp-admin/admin.php?page=real-cookie-banner-component",
"referrerPolicy": "strict-origin-when-cross-origin",
"body": "{\"title\":\"Test 2\",\"content\":\"Test 2\",\"status\":\"publish\",\"meta\":{\"rules\":\"Test 2\",\"criteria\":\"services\",\"services\":\"5904\",\"isVisual\":false,\"visualMediaThumbnail\":0,\"tcfVendors\":\"\"}}",
"method": "POST",
"mode": "cors",
"credentials": "include"
});

When I strip the tcfVendors field from the JSON payload (body), the request works fine and the content blocker is saved correctly (with a service linked to it). The mere presence of that tcfVendors field, even just holding an empty string, causes this issue.

When those services were saved with an error, they are not listed, but still counted in the Cookie Banner dashboard, they are stored incompletely in the database.

• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.
• This reply was modified 1 year, 4 months ago by strarsis.

@mguenter: So I think I found the reason, accidentally 90 years instead of days was set. However, although this may be very rare, it should not cause the save process to crash. I guess the duration is converted to a number (e.g. seconds) and 90 years would result in a number that is too large for the variable/field to hold.

Edit: I also had to remove and re-add some cookies to make saving the service work again.

• This reply was modified 1 year, 4 months ago by strarsis.

@mguenter: I reset everything, but the error re-occurs when saving a new service.

@mguenter: Is there a way to find out why exactly saving the settings fails?
Are there diagnostics information that I can post here?

Hi Matthias,

This issue occurs in the free version.

Just had the issue again. Can the fonts be reinstalled using the WP CLI?

The fonts are cached in uploads/-directory, correct?
So the plugin does not notice when the font files are missing or corrupted, hence the incorrect text in the generated PDFs? Can a check be added that triggers are re-install of the fonts in case the font files are corrupted?

• This reply was modified 1 year, 5 months ago by strarsis.

The other plugin has styles that cause this issue (selectors not being specific enough), it is a bug in that other plugin and I report it there.

The WooCommerce PDF Vouchers plugin has a style conflict with this plugin, as it sets the position of the input checkbox elements to static.

There ia a button for reinstalling the fonts in the tools section on the plugin status settings page.

• This reply was modified 1 year, 5 months ago by strarsis.