Desk9 Notice Planner – Announcement Bar & Scheduler

A notice is displayed only when all of these are true: it is published, “Enable this notice” is checked, its schedule is currently active, its display rules match the current page, and (on multilingual sites) it matches the visitor’s language. The computed status is shown in the notice list and in the Schedule box.

The end is exclusive: a notice with end “January 2, 23:59” disappears at exactly 23:59. All times use the timezone configured under Settings → General.

Yes. Every notice starts from a style set and a tone, which together define all fourteen colour slots. In the Design tab you can switch on “Override individual colours” and set any of them with the WordPress colour picker; fields you leave empty keep the colour of the set. Spacing, radius and typography can be fine-tuned the same way. There is no free-text CSS field – all values are validated and rendered as CSS custom properties.

Almost always a page cache: a caching plugin, your host’s built-in cache or a CDN stored a copy of the page before the notice was created, changed or ended, and keeps delivering that copy. Desk9 Notice Planner handles this in two ways. It asks known cache plugins to clear their cache whenever a notice changes, and – with cache-safe delivery (on by default, Settings > Advanced) – it checks for the current notices with a small request on every page view and corrects the page in the visitor’s browser. If a cached page was stored while the plugin was inactive, it does not contain the loader yet; clear the cache once (in your caching plugin or hosting panel) and every page stored from then on corrects itself.

Two ways, depending on what you want:

• Only for you, to check something: append ?d9notice_show=1 to any URL of your site. While you are logged in and allowed to edit notices, dismissals are ignored for that single page view. Nobody else is affected.
• For everyone who closed it: use the “Show again” row action in the notice list, or the “Show again for everyone” button in the notice editor under Dismissal. This raises the notice’s content version, which is part of the browser storage key, so every stored dismissal stops matching and the notice reappears.

Nothing is read from or written to a visitor’s device in either case – their old entry simply becomes irrelevant and expires on its own terms.

No. The optional dismiss feature stores a small entry in the visitor’s browser storage ( sessionStorage or localStorage ) under keys like d9notice:notice:123:v4 . Nothing is transmitted anywhere, and the entry expires with the notice or the chosen duration. If browser storage is blocked, the notice simply stays visible.

Yes. On activation the plugin creates a dedicated Notice Manager role. Assign it to a user and their admin area contains nothing but Dashboard, Media, Profile and Notices – they can write, schedule and publish notices and reach the plugin settings, but they cannot touch posts, pages, plugins, themes or other users.

The role holds every plugin capability plus read (needed to enter wp-admin at all) and upload_files (needed for the image field). If the role already exists, the plugin leaves it alone, so any adjustments you make with a role editor survive a reactivation.

You can also grant the capabilities to an existing role instead: edit_d9notices , edit_others_d9notices , publish_d9notices , delete_d9notices and manage_d9notice_settings for the settings screen.

The role is only deleted again if you enable “Remove the plugin capabilities …” under Notices → Settings → Advanced before uninstalling. Users keep their accounts either way.

Yes. The notice post type is registered as translatable, a wpml-config.xml defines which fields are translated and which are copied, and a setting controls whether untranslated notices are hidden or fall back to the default language. The plugin also works without any multilingual plugin.

Yes, classic and block themes are supported. For themes that do not call wp_body_open , a fallback output path is used.

Nothing is deleted unless you enabled “Delete all plugin data on uninstall” (and optionally “Remove plugin capabilities on uninstall”) under Notices → Settings → Advanced.