This guide covers installing GateForge, adding your first visibility rule, and importing rules from Widget Logic if you used it. It is for site owners who want to decide where a widget or block appears — on the front page, in 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.
What you need
- WordPress 6.5 or later.
- PHP 7.4 or later.
Install and activate
- Install and activate GateForge from the Plugins screen.
- If Widget Logic is active, deactivate it first. The GateForge importer stays disabled while Widget Logic is active.
- Add rules to blocks from the Visibility rule panel, or to classic widgets from the Edit rule button.
GateForge adds no scripts to your front end: visitors get no extra CSS or JavaScript. The builder only loads in the editors and on GateForge’s own screens, and the free plugin makes no outbound requests and collects no data.
Add a rule to a block
- Select the block in the post editor, the Site Editor, or the block widgets editor.
- Open the Visibility rule panel.
- Choose Show or Hide, then build your conditions. Conditions can be combined in any-of and all-of groups.
- Read the plain-English summary GateForge shows for the rule, and check it says what you meant.
- Save the post, page or widget area as usual.
Add a rule to a classic widget
- Open the widget in the widgets editor.
- Use the Edit rule button on the widget.
- Build the rule the same way as for a block, and save.
One limit to know: widgets displayed with the_widget() or by widget shortcodes do not go through the sidebar filters, so widget rules are not applied to them.
Example: hide a block from logged-out visitors
Add a rule with the “Visitor is logged in” condition and switch it to Hide. Logged-in visitors see the block; everyone else does not. Remember that hidden is not the same as protected — see “Visibility is not security” below.
Scheduling
The free version includes date scheduling: a rule can show something between a start date and an end date. Dates are wall-clock times in your site time zone, and a date-only end date includes the whole day. If you change the site time zone later, stored dates are read as wall-clock times in the new zone.
Reusable condition groups
A group is a set of conditions you save once and reference from many rules. A rule refers to a group by id, and the group resolves when the rule is checked — so editing the group changes every rule that uses it at once, with no need to re-save each rule. A rule that refers to a missing or deleted group fails closed (the item is hidden), and a group that refers to itself, directly or through other groups, also fails closed.
Import from Widget Logic
- Make sure Widget Logic is deactivated (the importer stays disabled while it is active).
- Go to Tools > GateForge Import and run the scan.
- Read the report before you apply anything. It lists every rule with its original text, what was translated, and what could not be translated. Nothing is dropped silently.
- Apply the import. The importer offers a dry run first, and Undo and Retry afterwards if you need them.
- Separately, when you are ready, use the “Remove Widget Logic data” step to delete the old data. It never runs on its own — Widget Logic itself never shipped an uninstall routine that deletes its data, so your old rules stay in place until you use it.
GateForge never runs your old Widget Logic code. Old rules are read as text and translated into GateForge rules. Anything that cannot be translated is listed in the report, and the item stays hidden until you decide what to do with it.
How unsure rules are handled
If GateForge cannot decide a rule, the item is hidden — it fails closed. 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.
Check your rules with Explain mode and Diagnostics
Explain mode is for administrators: it puts a card on each widget or block saying why it is shown or hidden, with a “View as logged-out visitor” switch so you can check what visitors see. The Diagnostics screen under Tools lists rules that could not be checked, block rules across all content, and the limits GateForge works within.
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.
Two things to know
- 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.