We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It's really easy to set custom visibility for some blocks and to forget about it.
If you do so, you may deactivate the plugin and make public some content without noticing.
If at least one block has a visibility option set, warn user before plugin deactivation. The message could be like :
You have at least one block with a visibility option set. Deactivating this plugin will make this content public.
It doesn't have to specify which blocks or where to find the blocks (even if this would be nice).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What problem does this address?
It's really easy to set custom visibility for some blocks and to forget about it.
If you do so, you may deactivate the plugin and make public some content without noticing.
What is your proposed solution?
If at least one block has a visibility option set, warn user before plugin deactivation. The message could be like :
It doesn't have to specify which blocks or where to find the blocks (even if this would be nice).
The text was updated successfully, but these errors were encountered: