New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Like the Text widget, but also allows working PHP code to be inserted. | You have to log in to add a translation. | Details |
Original untranslated
Like the Text widget, but also allows working PHP code to be inserted.
You have to log in to edit this translation. |
|||
| ↑ | PHP Code Widget | You have to log in to add a translation. | Details |
Original untranslated |
|||
| Code in a template runs in the global context. Code in the widget will run in a function context. Make sure that you declare any global variables as global before attempting to use them. | You have to log in to add a translation. | Details | |
Original untranslated
Code in a template runs in the global context. Code in the widget will run in a function context. Make sure that you declare any global variables as global before attempting to use them.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| So, if it says that you have an error on line 27, I assure you, the problem is yours. Please don't email me about that error. | You have to log in to add a translation. | Details | |
Original untranslated
So, if it says that you have an error on line 27, I assure you, the problem is yours. Please don't email me about that error.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| This widget has no real errors in it, it's about the simplest widget one can possibly make. Any errors coming out of the "execphp.php" file are errors in code you put into one of the widgets. The reason that it shows the error being in the execphp.php file is because that is where your widget's code is actually being run. | You have to log in to add a translation. | Details | |
Original untranslated
This widget has no real errors in it, it's about the simplest widget one can possibly make. Any errors coming out of the "execphp.php" file are errors in code you put into one of the widgets. The reason that it shows the error being in the execphp.php file is because that is where your widget's code is actually being run.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| No, it's not. Really. | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| That error means that your PHP code is incorrect or otherwise broken. | You have to log in to add a translation. | Details | |
Original untranslated
That error means that your PHP code is incorrect or otherwise broken.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| I have code that works normally in a template but doesn't work when in the widget? | You have to log in to add a translation. | Details | |
Original untranslated
I have code that works normally in a template but doesn't work when in the widget?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| But my code is fine! | You have to log in to add a translation. | Details | |
Original untranslated |
|||
| There's some kind of error on line 27! | You have to log in to add a translation. | Details | |
Original untranslated
There's some kind of error on line 27!
CommentFound in faq header. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| All PHP code must be enclosed in the standard php opening and closing tags ( <code><?php</code> and <code>?></code> ) for it to be recognized and executed. | You have to log in to add a translation. | Details | |
Original untranslated
All PHP code must be enclosed in the standard php opening and closing tags ( <code><?php</code> and <code>?></code> ) for it to be recognized and executed.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| 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. | You have to log in to add a translation. | Details | |
Original untranslated
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.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The normal Text widget allows you to insert arbitrary Text and/or HTML code. This allows that too, but also parses any PHP code in the text widget and executes it. | You have to log in to add a translation. | Details | |
Original untranslated
The normal Text widget allows you to insert arbitrary Text and/or HTML code. This allows that too, but also parses any PHP code in the text widget and executes it.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
| The output of the widget on the site. | You have to log in to add a translation. | Details | |
Original untranslated
The output of the widget on the site.
CommentScreenshot description. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.