Marcus

Hello, i will wait release new update a now i use own fix to next update

Have a great day)

Yeah) I install update dayago) thanks

Temporary workaround for Interactivity API Router crash

If you are using the WordPress Interactivity API Router (data-wp-router-region="content"), the share buttons may break the router due to inline onclick="xs_social_sharer(this);".

A simple workaround is to wrap the share buttons (or shortcode output) in a container with:

<div data-wp-ignore data-wp-router-region="static"> <!-- share buttons --> </div>

This prevents the router from hydrating and parsing the inline onclick handler, avoiding the crash.

As a possible plugin-side fix, you could also add these attributes directly to the <ul> element that outputs the share buttons:

<ul data-wp-ignore data-wp-router-region="static">

This avoids changing global logic and ensures compatibility with the Interactivity API Router.

Alternatively, updating the buttons to use modern event handling instead of inline onclick would fully resolve the compatibility issue.

Hi today is resovled issues with

chunk-vendors.min.js?ver=3.4.16:81 Error: Type mismatch. Value 0 does not match type number in column index 1 at gvjs_yk (jsapi_compiled_default_module.js:277:264) at gvjs_M.<anonymous> (jsapi_compiled_default_module.js:294:194) at gvjs_M.<anonymous> (jsapi_compiled_default_module.js:295:73) at o.setupList (chunk-common.min.js?ver=3.4.16:1:43105) at o.onChartReady (chunk-common.min.js?ver=3.4.16:1:43611) at zn (chunk-vendors.min.js?ver=3.4.16:81:24932) at o.n (chunk-vendors.min.js?ver=3.4.16:81:14729) at zn (chunk-vendors.min.js?ver=3.4.16:81:24932) at o.$emit (chunk-vendors.min.js?ver=3.4.16:81:30959) at chunk-vendors.min.js?ver=3.4.16:191:5754

is resolved

But i see in console this issues

js?key=:164 Geocoding Service: You must use an API key to authenticate each request to Google Maps Platform APIs. For additional information, please refer to http://g.co/dev/maps-no-account
.ml @ js?key=:164 js?key=:164 Geocoding Service: You must use an API key to authenticate each request to Google Maps Platform APIs. For additional information, please refer to http://g.co/dev/maps-no-account .ml @ js?key=:164
f @ geocoder.js:4
c @ common.js:103
(anonymous) @ GeocodeService.Search?4sT%C3%BCrkiye&9sen-US&r_url=https%3A%2F%2Fsite.com%2Fwp-admin%2Fadmin.php&callback=xdc.x6u1uj&token=84669:1 js?key=:164 Geocoding Service: You must use an API key to authenticate each request to Google Maps Platform APIs. For additional information, please refer to http://g.co/dev/maps-no-account .ml @ js?key=:164
f @ geocoder.js:4
c @ common.js:103
(anonymous) @ GeocodeService.Search?4sCzechia&9sen-US&r_url=https%3A%2F%2Fsite.com%2Fwp-admin%2Fadmin.php&callback=xdc.gbqnf2&token=80877:1 js?key=:164 Geocoding Service: You must use an API key to authenticate each request to Google Maps Platform APIs. For additional information, please refer to http://g.co/dev/maps-no-account .ml @ js?key=:164
f @ geocoder.js:4
c @ common.js:103
(anonymous) @ GeocodeService.Search?4s(not%20set)&9sen-US&r_url=https%3A%2F%2Fsite.com%2Fwp-admin%2Fadmin.php&callback=xdc._je55co&token=88069:1
js?key=:164 Geocoding Service: You must use an API key to authenticate each request to Google Maps Platform APIs. For additional information, please refer to http://g.co/dev/maps-no-account

Ok great will wait)) thanks

Stack Trace Summary:

The issue stems from yobm-wc-blacklist-manager-verifications.php:17 during the WC_Blacklist_Manager_Verifications->__construct() call, initiated in wp-settings.php. –

Issue: The plugin is loading translations too early, before the init hook, which triggers this notice in WordPress 6.8 Beta. This may indicate a need for adjustment to align with WordPress 6.7.0+ standards. Can you confirm if this is a known issue or suggest a fix to delay translation loading until the appropriate hook? I’d appreciate any assistance.

Best regards,