Description
GateForge lets you decide where a widget or a block appears: on the front page, on one category, for logged-in visitors only, between two dates, and so on. Rules are built with a point-and-click builder and stored as data. GateForge never runs code taken from the database.
If you used Widget Logic, GateForge reads your old rules, translates what it can into GateForge rules, and shows you a report that lists every rule with its original text. Nothing is dropped silently.
What it does
- A Visibility rule panel on every block in the post editor, the Site Editor and the block widgets editor, plus a rule field on classic widgets.
- A builder with Show and Hide, any-of and all-of groups, and a plain-English summary of every rule.
- An importer for Widget Logic rules with a dry run, a report, Undo, Retry and a separate “Remove Widget Logic data” step that never runs on its own.
- Explain mode for administrators: a card on each widget or block that says why it is shown or hidden, with a “View as logged-out visitor” switch.
- A Diagnostics screen under Tools that lists rules that could not be checked, block rules across all content, and the limits below.
- A snippet generator for site-specific conditions: it gives you text to copy into your own code. GateForge never writes code files.
- Free scheduling: show something between a start and an end date.
- Reusable condition groups: save a set of conditions once, then reference it from many rules, and edit it in one place.
An optional paid add-on adds a nested editor, a group library editor and recurring schedules. See the GateForge product page for the full details.
How unsure rules are handled
If GateForge cannot decide a rule, the item is hidden. Imported rules that depend on who the visitor is (logins, users, roles, memberships) stay hidden until you rebuild them. Rules that only depend on the page can be switched to “show” one widget at a time in the import report.
Reusable condition groups
A group is a set of conditions stored by GateForge and reused by many rules. A rule refers to a group by id; the group resolves at evaluation time, so editing the group changes every rule that uses it at once, with no rule re-save. A rule that refers to a missing or deleted group fails closed (hidden). A group that refers to itself, directly or through other groups, also fails closed. Groups are counted against the same size and depth limits as inline rules, once expanded.
Visibility is not security
Hiding a widget or block only stops it from being displayed. The content is not protected: it may still be reachable through feeds, the REST API, search, caches, other plugins or the page source. Do not use GateForge to protect private information.
If GateForge is turned off
If you deactivate or delete GateForge, every rule stops working and every widget and block it was hiding is shown again. This is the one case where GateForge fails open. The rules stay stored and work again when you reactivate it.
Page caches
A page cache stores one copy of a page for everyone. Rules that depend on the visitor or the device (logged in, capability, mobile, cart cookies) and date schedules can show a cached copy to the wrong visitor. Exclude such pages from the cache or skip those rules. GateForge asks common cache plugins to purge when a schedule boundary passes.
Known limits
- Widgets displayed with
the_widget()or by widget shortcodes do not go through the sidebar filters, so widget rules are not applied to them. - Navigation links and, on WordPress 7.0 and later, synced pattern blocks are rendered a second time by WordPress without the usual early check. GateForge removes hidden ones at a later point, but their inner blocks may already have loaded their styles or scripts.
- Blocks inside a pattern that the editor opens in content-only mode do not show the Visibility rule panel. Select the pattern or a block outside it.
- Deleting a block removes its rule with it. The block-rule capability setting controls who can add or change rules, not who can delete blocks.
- For users without the unfiltered_html capability (for example site admins on a multisite network), WordPress filters rule text that contains angle brackets in block widgets saved through raw REST requests. The block panel says when this happened.
- Dates in schedules are wall-clock times in the site time zone. If you change the site time zone later, stored dates are read as wall-clock times in the new zone. A date-only end date includes the whole day.
- Rules stored in theme files, registered PHP patterns, unsaved Customizer changes and page-builder data cannot be scanned. The Diagnostics screen lists these blind spots.
- Widget Logic itself never shipped an uninstall routine that deletes its data, so your old rules stay in place until you use “Remove Widget Logic data”.
Installation
- Install and activate GateForge from the Plugins screen.
- If Widget Logic is active, deactivate it first. The importer stays disabled while it is active.
- Go to Tools, GateForge Import, run the scan and read the report before you apply it.
- Add rules to blocks from the Visibility rule panel, or to classic widgets from the Edit rule button.
FAQ
-
Does GateForge run my old Widget Logic code?
-
No. Old rules are read as text and translated. Anything GateForge cannot translate is listed in the report and the item is hidden until you decide.
-
Can I hide a block only for logged-out visitors?
-
Yes. Add a rule with the “Visitor is logged in” condition and switch it to Hide. Remember that hidden is not protected.
-
Does GateForge add scripts to my front end?
-
No. Visitors get no extra CSS or JavaScript. The builder only loads in the editors and on GateForge screens.
-
Does GateForge contact any server?
-
No. The free plugin makes no outbound requests and collects no data.
Reviews
There are no reviews for this plugin.
Contributors & Developers
“GateForge” is open source software. The following people have contributed to this plugin.
ContributorsTranslate “GateForge” into your language.
Interested in development?
Browse the code, check out the SVN repository, or subscribe to the development log by RSS.
Changelog
1.1.2
- Review fixes: the Customizer preview and explain-mode styles are now enqueued the WordPress way instead of printed inline; the explain-mode output buffer is closed explicitly on shutdown; explain mode caps how deep it walks a stored rule tree.
- The admin notices GateForge shows on its own screens and the widgets screen are now dismissible.
- Plugin header now carries the Locker Forge plugin and author links, with the plugin link pointing at the GateForge product page.
1.1.0
- Reusable condition groups: save a set of conditions once and reference it from many rules. Editing the group updates every rule that uses it, with no rule re-save.
- Rules can now reference a group; a reference resolves at evaluation time. Missing groups and groups that refer to themselves fail closed (hidden).
- Group saves are validated and risk-stamped the same way rule saves are.
1.0.0
- First release: widget and block visibility rules, the Widget Logic importer, explain mode, diagnostics and the snippet generator.