You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since version 1.3.4 the plugin always includes the block assets for tabs and tab items. This causes a chain reaction, because of dependencies, that leads to an GET-request for every visitor on the site.
The tabs and tab item blocks both have wp-block-editor as dependency, which on it's place again has dependencies on wp-preferences and wp-preferences-persistence.
wp-preference has an after script that looks like this:
<script type="text/javascript" id="wp-preferences-js-after">
/* <![CDATA[ */
( function() {
var serverData = false;
var userId = "0";
var persistenceLayer = wp.preferencesPersistence.__unstableCreatePersistenceLayer( serverData, userId );
var preferencesStore = wp.preferences.store;
wp.data.dispatch( preferencesStore ).setPersistenceLayer( persistenceLayer );
} ) ();
/* ]]> */
</script>
which triggers the GET-request. When not logged in, the request fails.
FYI: Since we're not using the plugin anymore, we'll be disabling it soon. But we'll leave it there for another week or so, so you can check the site if you need any data.
Describe the bug
Since version 1.3.4 the plugin always includes the block assets for tabs and tab items. This causes a chain reaction, because of dependencies, that leads to an GET-request for every visitor on the site.
The tabs and tab item blocks both have
wp-block-editor
as dependency, which on it's place again has dependencies onwp-preferences
andwp-preferences-persistence
.wp-preference
has an after script that looks like this:which triggers the GET-request. When not logged in, the request fails.
Steps to Reproduce
preference-js-after
script, which is included af terpreferences-js
.Screenshots, screen recording, code snippet
No response
Environment information
No response
WordPress information
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: