Changeset 642034
- Timestamp:
- 12/20/2012 01:03:47 AM (13 years ago)
- Location:
- widget-logic
- Files:
-
- 2 edited
-
tags/0.54/readme.txt (modified) (3 diffs)
-
trunk/readme.txt (modified) (3 diffs)
Legend:
- Unmodified
- Added
- Removed
-
widget-logic/tags/0.54/readme.txt
r642032 r642034 13 13 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](http://codex.wordpress.org/Conditional_Tags), or any general PHP code. 14 14 15 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. If you are worried about the security implications, please let me know how you think I could guard against this without compromising the general power and flexibility of Widget Logic too much.15 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](../other_notes/)). 16 16 17 17 There is also an option to add a wordpress 'widget_content' filter -- this lets you tweak any widget's HTML to suit your theme without editing plugins and core code. … … 136 136 Note the extra ';' on the end where there is an explicit 'return'. 137 137 138 == The 'widget_logic_eval_override' filter == 139 Before the Widget Logic code is evaluated for each widget, the text of the Widget Logic code is passed through this filter. If the filter returns a BOOLEAN result, this is used instead to determine if the widget is visible. Return TRUE for visible. 140 138 141 == The 'widget_content' filter == 139 142 … … 181 184 182 185 = 0.54 = 183 I removed a WP 3.1+ function call, hopefully making it 2.8 compatible again. Also added in a little bit of 'trim' 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. 184 185 Thanks to Foe Services Labs http://wordpress.org/support/profile/cfoellmann for the work on translation support and the German translation files. 186 Removed a WP 3.1+ function call, hopefully making it 2.8 compatible again. 187 188 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. 189 190 Translation support! Thanks to Foe Services Labs http://wordpress.org/support/profile/cfoellmann for the work on this and the German translation files. 191 192 Added a 'widget_logic_eval_override' filter. This allows advanced users to bypass EVAL with a function of their own. 186 193 187 194 = 0.53 = -
widget-logic/trunk/readme.txt
r642032 r642034 13 13 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](http://codex.wordpress.org/Conditional_Tags), or any general PHP code. 14 14 15 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. If you are worried about the security implications, please let me know how you think I could guard against this without compromising the general power and flexibility of Widget Logic too much.15 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](../other_notes/)). 16 16 17 17 There is also an option to add a wordpress 'widget_content' filter -- this lets you tweak any widget's HTML to suit your theme without editing plugins and core code. … … 136 136 Note the extra ';' on the end where there is an explicit 'return'. 137 137 138 == The 'widget_logic_eval_override' filter == 139 Before the Widget Logic code is evaluated for each widget, the text of the Widget Logic code is passed through this filter. If the filter returns a BOOLEAN result, this is used instead to determine if the widget is visible. Return TRUE for visible. 140 138 141 == The 'widget_content' filter == 139 142 … … 181 184 182 185 = 0.54 = 183 I removed a WP 3.1+ function call, hopefully making it 2.8 compatible again. Also added in a little bit of 'trim' 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. 184 185 Thanks to Foe Services Labs http://wordpress.org/support/profile/cfoellmann for the work on translation support and the German translation files. 186 Removed a WP 3.1+ function call, hopefully making it 2.8 compatible again. 187 188 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. 189 190 Translation support! Thanks to Foe Services Labs http://wordpress.org/support/profile/cfoellmann for the work on this and the German translation files. 191 192 Added a 'widget_logic_eval_override' filter. This allows advanced users to bypass EVAL with a function of their own. 186 193 187 194 = 0.53 =
Note: See TracChangeset
for help on using the changeset viewer.