Changeset 791941 for php-code-widget
- Timestamp:
- 10/22/2013 06:28:10 PM (12 years ago)
- Location:
- php-code-widget
- Files:
-
- 2 edited
-
tags/2.2/readme.txt (modified) (1 diff)
-
trunk/readme.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
php-code-widget/tags/2.2/readme.txt
r791939 r791941 17 17 This can make it easier to migrate to a widget-based theme. However, this plugin should not be used long term, as anybody with access to edit the widgets on your site will be able to execute arbitrary PHP code. 18 18 19 All PHP code must be enclosed in the standard php opening and closing tags ( <?php and ?>) for it to be recognized and executed.19 All PHP code must be enclosed in the standard php opening and closing tags ( `<?php` and `?>` ) for it to be recognized and executed. 20 20 21 21 Only users with the unfiltered_html role will be allowed to insert unfiltered HTML. This includes PHP code, so users without admin or editor permissions will not be able to use this to execute code, even if they have widget editing permissions. -
php-code-widget/trunk/readme.txt
r791939 r791941 17 17 This can make it easier to migrate to a widget-based theme. However, this plugin should not be used long term, as anybody with access to edit the widgets on your site will be able to execute arbitrary PHP code. 18 18 19 All PHP code must be enclosed in the standard php opening and closing tags ( <?php and ?>) for it to be recognized and executed.19 All PHP code must be enclosed in the standard php opening and closing tags ( `<?php` and `?>` ) for it to be recognized and executed. 20 20 21 21 Only users with the unfiltered_html role will be allowed to insert unfiltered HTML. This includes PHP code, so users without admin or editor permissions will not be able to use this to execute code, even if they have widget editing permissions.
Note: See TracChangeset
for help on using the changeset viewer.