msgid "" msgstr "" "Project-Id-Version: Exec-PHP\n" "POT-Creation-Date: \n" "PO-Revision-Date: 2009-01-07 01:11+0100\n" "Last-Translator: Sören Weber \n" "Language-Team: Sören Weber \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Poedit-Basepath: ..\n" "X-Poedit-KeywordsList: __;_e;__s;_es\n" "X-Poedit-Language: German\n" "X-Poedit-Country: GERMANY\n" "X-Poedit-SearchPath-0: .\n" #: includes/admin.php:70 msgid "No user matching the query." msgstr "" #: includes/admin.php:71 msgid "Exec-PHP Security Alert." msgstr "" #: includes/admin.php:72 msgid "The Exec-PHP plugin found a security hole with the configured user rights of this blog. For further information consult the plugin configuration menu or contact your blog administrator." msgstr "" #: includes/admin.php:74 msgid "Exec-PHP AJAX HTTP error when receiving data: " msgstr "" #: includes/config_ui.php:49 #: includes/user_ui.php:46 #: includes/user_ui.php:48 msgid "Exec-PHP Settings" msgstr "" #: includes/config_ui.php:50 msgid "Exec-PHP" msgstr "" #: includes/config_ui.php:61 #: includes/config_ui.php:164 msgid "Settings" msgstr "" #: includes/config_ui.php:70 #: includes/config_ui.php:79 msgid "Exec-PHP Error." msgstr "" #: includes/config_ui.php:71 #, php-format msgid "No necessary upgrade of the the Exec-PHP plugin could be performed. PHP code in your articles or widgets may be viewable to your blog readers. This is plugin version %1$s, previously there was version %2$s installed. Downgrading from a newer version to an older version of the plugin is not supported." msgstr "" #: includes/config_ui.php:80 #, php-format msgid "An unknown error (%s) occured during execution of the Exec-PHP plugin. PHP code in your articles or widgets may be viewable to your blog readers. This error should never happen if you use the plugin with a compatible WordPress version and installed it as described in the documentation." msgstr "" #: includes/config_ui.php:121 msgid "The list can not be displayed because you may have disabled Javascript or your browser does not support Javascript." msgstr "" #: includes/config_ui.php:127 msgid "An animated icon signaling that this information is still be loaded." msgstr "" #: includes/config_ui.php:127 msgid "Loading user information..." msgstr "" #: includes/config_ui.php:152 msgid "Settings saved." msgstr "" #: includes/config_ui.php:160 msgid "Exec-PHP Plugin" msgstr "" #: includes/config_ui.php:161 #: includes/write_ui.php:46 #: includes/write_ui.php:57 msgid "readme.html" msgstr "" #: includes/config_ui.php:161 #, php-format msgid "Exec-PHP executes <?php ?> code in your posts, pages and text widgets. See the local documentation for further information. The latest version of the plugin, documentation and information can be found on the official plugin homepage." msgstr "" #: includes/config_ui.php:172 msgid "Execute PHP code in text widgets" msgstr "" #: includes/config_ui.php:176 msgid "Executing PHP code in text widgets is not restricted to any user. By default users who can modify text widgets will also be able to execute PHP code in text widgets. Unselect this option to generally turn off execution of PHP code in text widgets." msgstr "" #: includes/config_ui.php:185 msgid "Save Changes" msgstr "" #: includes/config_ui.php:190 msgid "Security Information" msgstr "" #: includes/config_ui.php:191 msgid "The following lists show which users are allowed to write or execute PHP code in different cases. Allowing to write or execute PHP code can be adjusted by assigning the necessary capabilities to individual users or roles by using a role manager plugin." msgstr "" #: includes/config_ui.php:196 msgid "Security Hole" msgstr "" #: includes/config_ui.php:197 #, php-format msgid "The following list shows which users have either or both of the "%1$s" or "%2$s" capability and are allowed to change others PHP code by having the "%3$s" capability but do not have the "%4$s" capability for themself. This is a security hole, because the listed users can write and execute PHP code in articles of other users although they are not supposed to execute PHP code at all." msgstr "" #: includes/config_ui.php:202 msgid "Executing PHP Code in Text Widgets" msgstr "" #: includes/config_ui.php:203 #, php-format msgid "The following list shows which users have the "%s" capability and therefore are allowed to write and execute PHP code in text widgets. In case you have deselected the option "Execute PHP code in text widgets" from above, this list will appear empty." msgstr "" #: includes/config_ui.php:208 msgid "Executing PHP Code in Articles" msgstr "" #: includes/config_ui.php:209 #, php-format msgid "The following list shows which users have the "%s" capability and therefore are allowed to execute PHP code in articles." msgstr "" #: includes/user_ui.php:52 msgid "Disable WYSIWYG Conversion Warning" msgstr "" #: includes/user_ui.php:56 msgid "Select this option to turn off the WYSIWYG Conversion Warning in the Write menu. Nevertheless the recommended way is to switch off the WYSIWYG editor so you can be sure not to break existing PHP code by accident." msgstr "" #: includes/write_ui.php:44 msgid "Exec-PHP WYSIWYG Conversion Warning." msgstr "" #: includes/write_ui.php:45 #, php-format msgid "Saving this article will render all contained PHP code permanently unuseful. Even if you are saving this article through the Code editor. You can turn off this warning in your user profile. Ignore this warning in case this article does not contain PHP code. Read the Exec-PHP documentation if you are unsure what to do next." msgstr "" #: includes/write_ui.php:55 msgid "Exec-PHP Widget Conversion Warning." msgstr "" #: includes/write_ui.php:56 #, php-format msgid "Saving the widgets will render all contained PHP code permanently unuseful. Ignore this warning in case the text widgets do not contain PHP code. Read the Exec-PHP documentation if you are unsure what to do next." msgstr ""