When I try to add CSS in the text box designed for that purpose, then click save, nothing saves . . .
]]>Has this plugin been abandoned?
]]>On the primary site it works as advertised. On new sites changes get over-ridden with the stock comments and nothing is changed.
]]>Seems the plugin hasn’t been updated in awhile.. maybe the supported version needs to be adjusted in the plugin. Thought I’d check in to see how we’re doing here with this plugin. Thanks!
]]>A minor change is needed to make safecss work properly when a site is being viewed under HTTPS context – otherwise it’ll use “siteurl” directly from wp_options which, in all likelihood, is using the https:// protocol. This will cause mixed content errors and browsers will throw up scary looking “site not secure! omgwtfbbq” errors.
On line 433 of safecss/safecss.php, replace:
$href = get_option( 'siteurl' );
to:
$href = site_url();
would be super helpful to have page numbers in this CSS editor…
i was using liveCSS which did but I understand this editor is safer to
use. would love to turn on page numbers !!
thanks
Te
In the admin panel in a RTL case it could be a good practice toforce the css text box to be directed LTR.
adding the direction property in safecss.php:595
solves the problem.
.wrap textarea#safecss {
width: 100%;
height: 100%;
direction: ltr;
}Could this be integrated?
]]>The Custom CSS plugin has proven to add quite a bit of flexibility in our multisite network, especially combined with the Twenty Eleven theme.
Twenty Eleven features some advanced CSS that cannot be overridden via this plugin because CSSTidy strips out the code. Namely, the background gradients in the #access div and the @media queries.
Does anyone have experience with editing the CSSTidy files that come with the “WordPress.com Custom CSS” plugin to allow CSS3 gradient backgrounds and/or @media queries?
]]>running this on a multisite installation. I have network activated this plugin.
as I said in the title: only saves every 2nd time I click on save stylesheet. the first time you try and save a piece of CSS it reverts to the default one it ships with. the second time you save it works. from then on it seems to save every time !?
Howdy,
It seems that the SafeCSS plugin is stripping the single quotes from fonts that are used from the Google font directory. I understand this is something kses does, but am curious if there is a way to have exceptions for certain elements.
A Google font can be called like so from a standard stylesheet:
@import url('https://fonts.googleapis.com/css?family=Candal:regular');
And used like so within the stylesheet:
#h1 {
font: normal normal bold 55px/85px 'Candal', serif; }Unfortunately, neither scenario works because the plugin is stripping elements it thinks shouldn’t be in the css. I can get around importing the font with a hook and using theme settings for individual sites to manipulate that, but is there a way to allow the use of single quotes in calling the Google fonts when styling an element?
Otherwise, I may have to abandon these pretty fonts for users in a custom stylesheet : )
Thanks for any help.
]]>Hi!
I’d be interested in localizing this plugin – now it’s supposed to get its translations from wp.com, right? I have validator access for the norwegian at both wp.com and wp.org – but it doesn’t do anything when I translate strings at https://translate.wordpress.com/projects/wpcom/no/default
So it would maybe be an idea to add a local textdomain??
Also, When a user activates the plugin, before saving their own stylesheet, and while using php 5.3 – there is an error. It can be fixed by applying this patch (printout from svn diff):
--- wp-content/plugins/safecss/safecss.php (revision 21)
+++ wp-content/plugins/safecss/safecss.php (working copy)
@@ -103,8 +103,9 @@
*
* @return array
*/
-function get_safecss_post() {
- $safecss_post = get_object_vars( array_shift( get_posts( array( 'numberposts' => 1, 'post_type' => 'safecss', 'post_status' => 'publish' ) ) ) );
+function get_safecss_post() {
+ $a = array_shift( get_posts( array( 'numberposts' => 1, 'post_type' => 'safecss', 'post_status' => 'publish' ) ) );
+ if ($a) $safecss_post = get_object_vars( $a ); // needed for php 5.3
return $safecss_post;
}With the W3 Validator, I’m getting 9 errors related to ampersands in the CSS generated by SAFE-CSS
Warning Line 126, Column 76: cannot generate system identifier for general entity “csblog”
An entity reference was found in the document, but there is no reference by that name defined. Often this is caused by misspelling the reference name, unencoded ampersands, or by leaving off the trailing semicolon (;). The most common cause of this error is unencoded ampersands in URLs as described by the WDG in “Ampersands in URLs”.
Is that to be expected? Is there anything I can do to change the encoding to resolve this problem?
]]>