Changeset 3432860
- Timestamp:
- 01/05/2026 03:50:06 PM (6 weeks ago)
- Location:
- block-logic
- Files:
-
- 2 edited
-
tags/2.1.3/README.txt (modified) (5 diffs)
-
trunk/README.txt (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
block-logic/tags/2.1.3/README.txt
r3432857 r3432860 36 36 37 37 ### Upgrade Notice 38 When upgrading to version 2.x you will need to update your logic. No `return` is allowed anymore and no semicolons in code as only expressions are evaluated. See Writing Logic Code.38 When upgrading to version 2.x you will need to update your logic. No `return` is allowed anymore and no semicolons in code as only expressions are evaluated. See FAQ Section **Writing Logic Code**. 39 39 40 40 == Frequently Asked Questions == … … 204 204 }); 205 205 ` 206 207 206 * Usage in a block logic field: 208 207 `!empty($_SESSION['special_offer'])` … … 210 209 3. **Add extra WordPress globals** 211 210 * Use the `block_logic_allowed_globals` filter to allow extra global variables. 212 213 211 * Example: 214 212 ` … … 221 219 $GLOBALS['my_global_data'] = ['foo' => 'bar']; 222 220 ` 223 224 221 * Usage in a block logic field: 225 222 `$post->ID == my_global_data['foo']` … … 236 233 $GLOBALS['my_custom_flag'] = true; 237 234 ` 238 239 235 * Usage in a block logic field: 240 236 `$my_custom_flag && is_user_logged_in()` -
block-logic/trunk/README.txt
r3432857 r3432860 36 36 37 37 ### Upgrade Notice 38 When upgrading to version 2.x you will need to update your logic. No `return` is allowed anymore and no semicolons in code as only expressions are evaluated. See Writing Logic Code.38 When upgrading to version 2.x you will need to update your logic. No `return` is allowed anymore and no semicolons in code as only expressions are evaluated. See FAQ Section **Writing Logic Code**. 39 39 40 40 == Frequently Asked Questions == … … 204 204 }); 205 205 ` 206 207 206 * Usage in a block logic field: 208 207 `!empty($_SESSION['special_offer'])` … … 210 209 3. **Add extra WordPress globals** 211 210 * Use the `block_logic_allowed_globals` filter to allow extra global variables. 212 213 211 * Example: 214 212 ` … … 221 219 $GLOBALS['my_global_data'] = ['foo' => 'bar']; 222 220 ` 223 224 221 * Usage in a block logic field: 225 222 `$post->ID == my_global_data['foo']` … … 236 233 $GLOBALS['my_custom_flag'] = true; 237 234 ` 238 239 235 * Usage in a block logic field: 240 236 `$my_custom_flag && is_user_logged_in()`
Note: See TracChangeset
for help on using the changeset viewer.