Widget Logic

This plugin gives every widget an extra control field called "Widget logic" that lets you control the pages that the widget will appear on. The text field lets you use WP's Conditional Tags, or any general PHP code. PLEASE NOTE The widget logic you introduce is EVAL'd directly. Anyone who has access to edit widget appearance will have the right to add any code, including malicious and possibly destructive functions. There is an optional filter 'widget_logic_eval_override' which you can use to bypass the EVAL with your own code if needed. (See Other Notes). The configuring and options are in the usual widget admin interface. BIG UPDATE:

• Now you can control widget in Gutenberg Widgets editor as well as in Classic Editor. It is just as easy as before but also in gutenberg view.
• Pre-installed widgets let you add special widget with one click of the mouse. First pre-installed widget is Live Match that let you add widget of one random live football game with real time score updates (teams logos, livescore, minute of the match, tournament name). And more interesting widgets to come!

Configuration Aside from logic against your widgets, there are three options added to the foot of the widget admin page (see screenshots).

• Use 'wp_reset_query' fix -- Many features of WP, as well as the many themes and plugins out there, can mess with the conditional tags, such that is_home is NOT true on the home page. This can often be fixed with a quick wp_reset_query() statement just before the widgets are called, and this option puts that in for you rather than having to resort to code editing
• Load logic -- This option allows you to set the point in the page load at which your widget logic if first checked. Pre v.50 it was when the 'wp_head' trigger happened, ie during the creation of the HTML's HEAD block. Many themes didn't call wp_head, which was a problem. From v.50 it happens, by default, as early as possible, which is as soon as the plugin loads. You can now specify these 'late load' points (in chronological order):
• after the theme loads (after_setup_theme trigger)
• when all PHP loaded (wp_loaded trigger)
• after query variables set (parse_query) – this is the default
• during page header (wp_head trigger)

You may need to delay the load if your logic depends on functions defined, eg in the theme functions.php file. Conversely you may want the load early so that the widget count is calculated correctly, eg to show an alternative layour or content when a sidebar has no widgets. * Don't cache widget logic results -- From v .58 the widget logic code should only execute once, but that might cause unexpected results with some themes, so this option is here to turn that behaviour off. (The truth/false of the code will be evaluated every time the sidebars_widgets filter is called. Interaction with External Services Widget Logic uses the external service to obtain up-to-date information about the results of football matches. widgetlogic.org is a source of sports information, that provides a wide range of information about football, including various leagues, tournaments, and championships from around the world. The functioning of the widgetlogic.org service is based on delivering real-time data about selected matches without the need to refresh the page. This means that data is automatically updated without requiring page reload. This approach ensures users quick and uninterrupted access to the latest sports data without the effort of manually updating information, allowing them to stay informed about ongoing events in real-time.

6.02

• fixed bug for php7.2

6.0.1

• Bug fixes

6.0.0

• Gutenberg widgets editor added
• Pre-installed widgets added (Live Match)
• Bug fixes
• Code cleanup

5.10.4

• Security update. The export feature has been protected with nonce.

5.10.3

• Security update. Huge thanks to the Plugin Vulnerabilities Team!

5.10.2

• The plugin's security has been improved, big thanks to Paul Dannewitz for his excellent security audit!
• The widget_content filter option has been removed from the settings block, but kept in the code for backward compatibility. The plan is to remove it completely and make the plugin simpler (let us know what you think).
• Code cleanup.

5.9.0 wp_reset_query works better under certain conditions. 5.8.2 The code has been adapted to work on the servers with restricted <?= Fixed support for the wp_register_sidebar_widget widgets. Some content was prepared for translation. 5.8.1 Fixed the issue of displaying errors under certain conditions. 5.8.0 Added full support for WP customizer. In case of a fatal error in logic, the widget will not be displayed. 5.7.4 Fixed the "Warning: Attempt to assign property of non-object" bug. https://wordpress.org/support/topic/latest-update-seems-break-my-installation/ 5.7.3 Fixed the issue when in some cases the plugin displayed user logic errors in the Widgets section and this didn't allow to save the widgets. https://wordpress.org/support/topic/an-error-has-occurred-please-reload-the-page-and-try-again-3/ Fixed ini_set() related warnings for some rare hosting configurations. https://wordpress.org/support/topic/ini_set-diabled-warning/ 5.7.2 Removed conflicts with outdated WP versions. 5.7.1 Fixed the settings form not being saved settings under some circumstances. Added a setting to show logic code errors for admins (turned off by default). Fixed the issue with quotes in error messages on some WP installations. 5.7.0 Fixed PHP 7 compatibility issue. Fixed a conflict with the latest WPML plugin. A new default load logic point attached to the action 'parse_query'. By default the widget logic is only evaluated once. Translation added: Ukrainian by Roman Sulym 0.57 Small fixes to satisfy some define('WP_DEBUG', true) errors 0.56 Small fix to the original WP3.5 fix in 0.54 that had the side effect of failing to save logic text on newly added widgets. 0.55 Restored a striplashes that vanished in 0.54 causing much grief. Translation: Spanish by Eduardo Larequi http://wordpress.org/support/profile/elarequi 0.54 Removed a WP 3.1+ function call, hopefully making it 2.8 compatible again. A little 'trim' of WL code to stop "syntax error, unexpected ')'" errors, which could occur if your WL was just a single space. Thanks to https://twitter.com/chrisjean for pointing this out. Translation support! Thanks to Foe Services Labs http://wordpress.org/support/profile/cfoellmann for the work on this and the German Social Translation Added a 'widget_logic_eval_override' filter. This allows advanced users to bypass EVAL with a function of their own. 0.53 Accidentally released code with a terrible bug in it :-( 0.52 Two new features: optional delayed loading of logic (see Configuration under Installation), and the ability to save out and reload all your site's widget logic into a config file 0.51 One important bug fix (fairly major and fairly stupid of me too) 0.50 For the first time since this started on WP 2.3, I've rewritten how the core widget logic function works, so there may be 'bumps ahead'. It now uses the 'sidebars_widgets' filter (as it should have done when that was introduced in WP2.8 by the look of it). The upshot is that is_active_sidebar should behave properly. Widget callbacks only get intercepted if the 'widget_content' filter is activated, and much more briefly. (A widget's 'callback' is rewired within the 'dynamic_sidebar' function just before the widget is called, by the 'dynamic_sidebar_param' filter, and is restored when the callback function is invoked.) 0.48 Kill some poor coding practices that throws debug notices - thanks to John James Jacoby. 0.47 FINALLY tracked down the elusive 'wp_reset_query' option resetting bug. 0.46 Fix to work with new WP2.8 admin ajax. With bonus fixes. 0.44 Officially works with 2.7 now. Documentation changes and minor bug fixes. 0.43 simple bug fix (form data was being lost when 'Cancel'ing widgets) 0.42 WP 2.5+ only now. WP's widget admin has changed so much and I was getting tied up in knots trying to make it work with them both. 0.4 Brings WP 2.5 compatibility. I am trying to make it back compatible. If you have trouble using WL with WP 2.1--2.3 let me know the issue. Thanks to Kjetil Flekkoy for reporting and helping to diagnose errors in this version 0.31 Last WP 2.3 only version