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
{{ message }}
This repository has been archived by the owner on Jun 19, 2024. It is now read-only.
Tested on several multisite networks and if, and only if, network activated it does not load any blocks on admin Cloud Blocks page.
If activated per site it works, so it's not multisite related, but the type of activation. If per site activated first, then network activated later, it stops working, even if site activated on all the sites.
A script is not loaded on the admin page, it seems, but no console errors.
Only difference between network activation and site activation is the order of including the main plugin file, but haven't been able to find the actual reason for this strange behaviour by studying the code.
The text was updated successfully, but these errors were encountered:
The issue was global variable $pagenow which was used to only load plugin assets if we are in the plugin settings page. This variable seems not to work with multisite setup, at least in our case. So replaced it with is_admin() function and changed plugin init function just a bit in version 1.1.2. This fixed the issue for me.
Can you please check and if it solved, close this issue?
Tested on several multisite networks and if, and only if, network activated it does not load any blocks on admin Cloud Blocks page.
If activated per site it works, so it's not multisite related, but the type of activation. If per site activated first, then network activated later, it stops working, even if site activated on all the sites.
A script is not loaded on the admin page, it seems, but no console errors.
Only difference between network activation and site activation is the order of including the main plugin file, but haven't been able to find the actual reason for this strange behaviour by studying the code.
The text was updated successfully, but these errors were encountered: