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
We need to find a way to run the plugin code on Dotcom behind something that would simulate a feature flag and enable it only on some sites for initial testing.
Previous efforts to do this ran into some issues because of the loading order and blog_sticker checks (see D28074-code for more info).
The text was updated successfully, but these errors were encountered:
I'm wondering if a Calypsoify approach would work for us: adding a query param that saves the option into a cookie until explicitly removed.
E.g. opening the dashboard via proxied-sandbox.wordpress.com/wp-admin/?full_site_editing=1 (or 0 to disable it).
Folks would need to clearly opt-in, so that they wouldn't be confused of what they see.
At the same time, they wouldn't need the hassle of adding their site ID into a whitelist.
(And last but not least, we already have a working example to copy.)
We need to find a way to run the plugin code on Dotcom behind something that would simulate a feature flag and enable it only on some sites for initial testing.
Previous efforts to do this ran into some issues because of the loading order and
blog_sticker
checks (see D28074-code for more info).The text was updated successfully, but these errors were encountered: