New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | A plugin that lets you quickly and easily create new plugins. | A plugin that lets you quickly and easily create new plugins. | Details |
Original current
A plugin that lets you quickly and easily create new plugins.
You have to log in to edit this translation. |
|||
| ↑ | Pluginception | Pluginception | Details |
Original current |
|||
| Then modify the plugin however you like to do whatever you want. Don't bother me with it. This plugin does what I want it to do. | Then modify the plugin however you like to do whatever you want. Don't bother me with it. This plugin does what I want it to do. | Details | |
Original current
Then modify the plugin however you like to do whatever you want. Don't bother me with it. This plugin does what I want it to do.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If you paste in non-working code, or decide to use the plugin editor to experiment, then you'll likely break your site. So don't do this if you don't know what you're doing. This is a power user's tool. | If you paste in non-working code, or decide to use the plugin editor to experiment, then you'll likely break your site. So don't do this if you don't know what you're doing. This is a power user's tool. | Details | |
Original current
If you paste in non-working code, or decide to use the plugin editor to experiment, then you'll likely break your site. So don't do this if you don't know what you're doing. This is a power user's tool.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Because I frequently spin off new plugins in order to paste simple code snippets into handy places. I know the code works, I've already tested it. Having to then encapsulate it into a plugin, fire up Filezilla, navigate, upload the plugin... It's a pain. This gives me an easy way to create a new blank plugin and go to the editor to paste in the known working code. | Because I frequently spin off new plugins in order to paste simple code snippets into handy places. I know the code works, I've already tested it. Having to then encapsulate it into a plugin, fire up Filezilla, navigate, upload the plugin... It's a pain. This gives me an easy way to create a new blank plugin and go to the editor to paste in the known working code. | Details | |
Original current
Because I frequently spin off new plugins in order to paste simple code snippets into handy places. I know the code works, I've already tested it. Having to then encapsulate it into a plugin, fire up Filezilla, navigate, upload the plugin... It's a pain. This gives me an easy way to create a new blank plugin and go to the editor to paste in the known working code.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| All this plugin really does is make it quick and easy to create a new one-off plugin and take you directly to editing it. Cowboy-coding at its finest. | All this plugin really does is make it quick and easy to create a new one-off plugin and take you directly to editing it. Cowboy-coding at its finest. | Details | |
Original current
All this plugin really does is make it quick and easy to create a new one-off plugin and take you directly to editing it. Cowboy-coding at its finest.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| That said, it's perfectly "safe", given a certain defintion of the word "safe". The "create a new plugin" screen itself is secure, and inaccessible to anybody who lacks the capability to "edit_plugins" to begin with. Pluginception also uses the proper WP_Filesystem methods to create the plugin, so there's no worries about incorrect file ownership on shared hosting. You may have to give it FTP credentials on some hosts for it to be able to create the plugin, that's the WP_Filesystem at work, making sure the files are correctly "owned". | That said, it's perfectly "safe", given a certain defintion of the word "safe". The "create a new plugin" screen itself is secure, and inaccessible to anybody who lacks the capability to "edit_plugins" to begin with. Pluginception also uses the proper WP_Filesystem methods to create the plugin, so there's no worries about incorrect file ownership on shared hosting. You may have to give it FTP credentials on some hosts for it to be able to create the plugin, that's the WP_Filesystem at work, making sure the files are correctly "owned". | Details | |
Original current
That said, it's perfectly "safe", given a certain defintion of the word "safe". The "create a new plugin" screen itself is secure, and inaccessible to anybody who lacks the capability to "edit_plugins" to begin with. Pluginception also uses the proper WP_Filesystem methods to create the plugin, so there's no worries about incorrect file ownership on shared hosting. You may have to give it FTP credentials on some hosts for it to be able to create the plugin, that's the WP_Filesystem at work, making sure the files are correctly "owned".
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Nope, not in the slightest. You have been warned. | Nope, not in the slightest. You have been warned. | Details | |
Original current
Nope, not in the slightest. You have been warned.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| Any of those cases will prevent the menu item from appearing, because you lack the edit_plugins permission. | Any of those cases will prevent the menu item from appearing, because you lack the edit_plugins permission. | Details | |
Original current
Any of those cases will prevent the menu item from appearing, because you lack the edit_plugins permission.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| There are 4 cases where you will not see the new menu: | There are 4 cases where you will not see the new menu: | Details | |
Original current
There are 4 cases where you will not see the new menu:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If the DISALLOW_FILE_MODS define is enabled, then you cannot edit plugin files. | If the DISALLOW_FILE_MODS define is enabled, then you cannot edit plugin files. | Details | |
Original current
If the DISALLOW_FILE_MODS define is enabled, then you cannot edit plugin files.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| If the DISALLOW_FILE_EDIT define is enabled, then you cannot edit plugin files. | If the DISALLOW_FILE_EDIT define is enabled, then you cannot edit plugin files. | Details | |
Original current
If the DISALLOW_FILE_EDIT define is enabled, then you cannot edit plugin files.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Your site is on a multisite configuration and you are not logged in as a super-admin user. | Your site is on a multisite configuration and you are not logged in as a super-admin user. | Details | |
Original current
Your site is on a multisite configuration and you are not logged in as a super-admin user.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| You are not logged in as an admin user. | You are not logged in as an admin user. | Details | |
Original current
You are not logged in as an admin user.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| I want this plugin to do something other than what it does. | I want this plugin to do something other than what it does. | Details | |
Original current
I want this plugin to do something other than what it does.
CommentFound in faq header. You have to log in to edit this translation. |
|||
Export as
Comment
Found in description paragraph.