New to Translating WordPress? Read through our Translator Handbook to get started. Hide
| Prio | Original string | Translation | — |
|---|---|---|---|
| ↑ | Easily define additional CSS (inline and/or by URL) to be added to all administration pages. | You have to log in to add a translation. | Details |
Original untranslated
Easily define additional CSS (inline and/or by URL) to be added to all administration pages.
You have to log in to edit this translation. |
|||
| ↑ | Add Admin CSS | You have to log in to add a translation. | Details |
Original untranslated |
|||
| The initial reaction by some might be to remove the plugin from the server's filesystem. This will certainly disable the plugin and prevent the CSS you configured through it from taking effect, restoring the access and functionality to the backend. However, reinstalling the plugin will put you back into the original predicament because the plugin will use the previously-configured settings, which wouldn't have changed. | You have to log in to add a translation. | Details | |
Original untranslated
The initial reaction by some might be to remove the plugin from the server's filesystem. This will certainly disable the plugin and prevent the CSS you configured through it from taking effect, restoring the access and functionality to the backend. However, reinstalling the plugin will put you back into the original predicament because the plugin will use the previously-configured settings, which wouldn't have changed.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| There are other approaches you can use, though they require direct database or server filesystem access: | You have to log in to add a translation. | Details | |
Original untranslated
There are other approaches you can use, though they require direct database or server filesystem access:
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| The recommended approach is to visit the URL for the plugin's settings page, but appended with a special query parameter to disable the output of its CSS. The plugin's settings page would typically be at a URL like <code>https://example.com/wp-admin/themes.php?page=add-admin-css%2Fadd-admin-css.php</code>. Append <code>&c2c-no-css=1</code> to that, so that the URL is <code>https://example.com/wp-admin/themes.php?page=add-admin-css%2Fadd-admin-css.php&c2c-no-css=1</code> (obviously change example.com with the domain name for your site). | You have to log in to add a translation. | Details | |
Original untranslated
The recommended approach is to visit the URL for the plugin's settings page, but appended with a special query parameter to disable the output of its CSS. The plugin's settings page would typically be at a URL like <code>https://example.com/wp-admin/themes.php?page=add-admin-css%2Fadd-admin-css.php</code>. Append <code>&c2c-no-css=1</code> to that, so that the URL is <code>https://example.com/wp-admin/themes.php?page=add-admin-css%2Fadd-admin-css.php&c2c-no-css=1</code> (obviously change example.com with the domain name for your site).
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| It is certainly possible that you can put yourself in an unfortunate position by supplying CSS that could hide critical parts of admin pages, making it seeminly impossible to fix or revert your changes. Fortunately, there are a number of approaches you can take to correct the problem. | You have to log in to add a translation. | Details | |
Original untranslated
It is certainly possible that you can put yourself in an unfortunate position by supplying CSS that could hide critical parts of admin pages, making it seeminly impossible to fix or revert your changes. Fortunately, there are a number of approaches you can take to correct the problem.
CommentFound in faq paragraph. You have to log in to edit this translation. |
|||
| If your server has WP-CLI installed, you can delete the plugin's setting from the commandline: <code>wp option delete c2c_add_admin_css</code> | You have to log in to add a translation. | Details | |
Original untranslated
If your server has WP-CLI installed, you can delete the plugin's setting from the commandline: <code>wp option delete c2c_add_admin_css</code>
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Presuming you know how to directly access the database: within the site's database, find the row with the option_name field value of <code>c2c_add_admin_css</code> and delete that row. The settings you saved for the plugin will be deleted and it will be like you've installed the plugin for the first time. | You have to log in to add a translation. | Details | |
Original untranslated
Presuming you know how to directly access the database: within the site's database, find the row with the option_name field value of <code>c2c_add_admin_css</code> and delete that row. The settings you saved for the plugin will be deleted and it will be like you've installed the plugin for the first time.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| In the site's <code>wp-config.php</code> file, define a constant to disable output of the plugin-defined CSS: <code>define( 'C2C_ADD_ADMIN_CSS_DISABLED', true );</code>. You can then visit the site's admin. Just remember to remove that line after you've fixed the CSS (or at least change "true" to "false"). This is an alternative to the query parameter approach described above, though it persists while the constant remains defined. There will be an admin notice on the plugin's setting page to alert you to the fact that the constant is defined and effectively disabling the plugin from adding any CSS. | You have to log in to add a translation. | Details | |
Original untranslated
In the site's <code>wp-config.php</code> file, define a constant to disable output of the plugin-defined CSS: <code>define( 'C2C_ADD_ADMIN_CSS_DISABLED', true );</code>. You can then visit the site's admin. Just remember to remove that line after you've fixed the CSS (or at least change "true" to "false"). This is an alternative to the query parameter approach described above, though it persists while the constant remains defined. There will be an admin notice on the plugin's setting page to alert you to the fact that the constant is defined and effectively disabling the plugin from adding any CSS.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| If you're familiar with doing so and have an idea of what CSS style you added that is causing problems, you can use your browser's developer tools to inspect the page, find the element in question, and disable the offending style. | You have to log in to add a translation. | Details | |
Original untranslated
If you're familiar with doing so and have an idea of what CSS style you added that is causing problems, you can use your browser's developer tools to inspect the page, find the element in question, and disable the offending style.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| Some browsers (such as Firefox, via View -> Page Style -> No Style) allow you to disable styles for sites loaded in that tab. Other browsers may also support such functionality natively or through an extension. Chrome has an extension called <a href="https://chrome.google.com/webstore/detail/web-developer/bfbameneiokkgbdmiekhjnmfkcnldhhm?hl=en-US">Web Developer</a> that adds the functionality. | You have to log in to add a translation. | Details | |
Original untranslated
Some browsers (such as Firefox, via View -> Page Style -> No Style) allow you to disable styles for sites loaded in that tab. Other browsers may also support such functionality natively or through an extension. Chrome has an extension called <a href="https://chrome.google.com/webstore/detail/web-developer/bfbameneiokkgbdmiekhjnmfkcnldhhm?hl=en-US">Web Developer</a> that adds the functionality.
CommentFound in faq list item. You have to log in to edit this translation. |
|||
| How can I edit the plugin's settings in the event I supplied CSS that prevents the admin pages from properly functioning or being seen? | You have to log in to add a translation. | Details | |
Original untranslated
How can I edit the plugin's settings in the event I supplied CSS that prevents the admin pages from properly functioning or being seen?
CommentFound in faq header. You have to log in to edit this translation. |
|||
| Go to "Appearance" -> "Admin CSS" and specify some CSS to be added into all admin pages. (You can also use the "Settings" link in the plugin's entry on the admin "Plugins" page). | You have to log in to add a translation. | Details | |
Original untranslated
Go to "Appearance" -> "Admin CSS" and specify some CSS to be added into all admin pages. (You can also use the "Settings" link in the plugin's entry on the admin "Plugins" page).
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| Install via the built-in WordPress plugin installer. Or download and unzip <code>add-admin-css.zip</code> inside the plugins directory for your site (typically <code>wp-content/plugins/</code>) | You have to log in to add a translation. | Details | |
Original untranslated
Install via the built-in WordPress plugin installer. Or download and unzip <code>add-admin-css.zip</code> inside the plugins directory for your site (typically <code>wp-content/plugins/</code>)
CommentFound in installation list item. You have to log in to edit this translation. |
|||
| The 'c2c_add_admin_css_files' filter allows programmatic modification of the list of CSS files to enqueue in the admin. | You have to log in to add a translation. | Details | |
Original untranslated
The 'c2c_add_admin_css_files' filter allows programmatic modification of the list of CSS files to enqueue in the admin.
CommentFound in description paragraph. You have to log in to edit this translation. |
|||
Export as
Comment
Short description.