custom css not holding

[alisamski+ 9]

Today, my custom CSS is not holding upon refresh. Flushed Cache. Checked topics here on forum...and found no answers.

 

Here is the css that I need to apply: Shows upon save.. and disappears.

_____________________________

.pl-content {
background: rgba(250, 250, 250, 0.8);
}
#header .pl-content {
background: rgba(0, 0, 0, 0);
}
#navbar .pl-content {
background: rgba(0, 0, 0, 0);
}
#footer .pl-content {
background: rgba(250, 250, 250, 0.8);
}

 

____________

Suggestions welcomed.

 

 

Thanks.

 

http://bit.ly/1cejKbz

[greenfly 230]

HI alisamski

 

If you could create an admin level account for your site and send the credentials to hello @ pagelines dot com - along with a link to this forum topic in the email i will jump on and take a look for you. 

[alisamski+ 9]

sent :-)

[greenfly 230]

Hi there 

The CSS you entered is still there on your site in the Custom CSS area http://d.pr/i/L6FG - however - it doesn't look as though you have pressed save. Are you making sure the light is green on the DMS visual editor before you refresh . 

 

You may have to click out of the CSS area and then click back into this area again to make sure the entries you made take effect. This is a known bug for the moment that will hopefully be resolved in the next iteration of DMS.

 

i made sure the light was green and changes to Custom CSS stuck this time 

[alisamski+ 9]

I've saved in every configuration possible... and the custom css is still not working... or at least I'm not seeing it..

 

if you go to the inside pages.. not the fron tpage... each area has a transparent white behind the content..

[greenfly 230]

do you mean (for example) this transparent white behind the 'Our Specialities' area: http://d.pr/i/75zW

[alisamski+ 9]

Yes... and the below areas...

 

it is not showing

 

pl-content {
background: rgba(250, 250, 250, 0.8);
}
#header .pl-content {
background: rgba(0, 0, 0, 0);
}
#navbar .pl-content {
background: rgba(0, 0, 0, 0);
}
#footer .pl-content {
background: rgba(250, 250, 250, 0.8);
}

[greenfly 230]

this only shows when your are logged in and accessing the visual editor. it is not present otherwise - i.e. not present to non-admin visitors

 

does this make sense? 

[alisamski+ 9]

No I do not mean  activating the area...

so the css does not work

 

http://bit.ly/1bfqr71

 

the css saves and then it does not hold. So the content area has a transparent white background around it.

[James B 436]

Hi there,

 

Ok something is definitely off there. Logged into your site to test, no css seemed to be sticking at all, so in testing removed all your css and tried a basic change, didn't take affect still showed all the stuff I'd just removed. Kept on going, a little while later, change took affect. Set back with original css and again nothing took. This leads me to think that the host could be caching? I'd check with them to see if they cache any files their end.

 

For the time being, as the original css wouldn't go back in (leaving your site unstyled) I have added the code in to the base themes style.css which override whats in the css editor. So now it's showing.

 

I will speak to our developer to see what could be causing this, but I'd def say check with the host as well in the interim.

[alisamski+ 9]

thanks will do... its a client site... so will find out (GoDaddy) what is going on.

[James B 436]

Just to update we've had another case where something similar is happening and they are also on godaddy, so be interesting to see what they say. If we hear back on the other case I'll post the comments in this thread too. Core team are aware.

[alisamski+ 9]

Waiting to hear what type of servers they have this on... if we have to go to GoDaddy for a client, we usually get at least a Deluxe Host Acct. Linux  with CPanel..

This client has a very old website on these servers... so we'll see and will post..

 

Thanks

[paul_t 21]

To confirm, I've had this problem to. Using the LESS Save Button on the front end of the Pagelines Interface made it stick, but that sort of negates the point of having the custom box in the DMS editor. 

[James B 436]

The Css/Less fallback in the Pagelines tab in the wp admin area is a fix for if the dms editor isn't working correctly. When saving your code in the css/less panel in the editor, make sure you click elsewhere in the panel to see the saving icon spin in the top right hand corner of the editor, once it's finished saving, publish and check if the css has saved. If it hasn't and the panel is clear but saving in the fall back area, it could be a plugin conflict (the dms editor is jquery based so some plugins can break it) try disabling the plugins on your site and reattempting the css changes to see if this is the cause.

[alisamski+ 9]

Client is on hold until he finishes checking the site... so I will go thru again and see if I can apply the above tips... until then..

thank you .. and will like to keep this open until I finish up..

[Danny+ 1,327]

OK, as James mentioned above, there is currently an issue in 1.4 where some users encounter an error in saving there changes, this related to custom CSS/LESS, settings and section setting changes.

 

The issue has been fixed in an upcoming patch, in the meantime, what you can do is this:

 

1. When you add custom CSS/LESS or make a change to a setting.

2. Before clicking the publish button, do the following:

A ) For CSS/LESS, move your mouse cursor to outside of the DMS editor and then click.

B ) For Settings and Section Settings, move your mouse cursor to a different option field and click inside of it.

3. This should now trigger the Saving Progression, which you can confirm by looking next to the Publish button.

4. *Once this Saving has completed, click publish and your settings and custom CSS/LESS should now take effect.

 

* If your custom CSS/LESS doesn't take effect after this, then you either have one of the following issues.

 

1. Your custom CSS isn't correct i.e. is either invalid or isn't targeting the element correctly.

2. You have a cache or other plugin causing a conflict.

3. Your host is using a cache system which is preventing your CSS/LESS to take effect.