Since upgrading to PageLines 2.3, custom styles have been ruined

[cloudindigo 0]

I upgraded a site from Pagelines Framework 2.2.5 to 2.3 and custom styles applied to the iBlogPro5 child theme have been ruined. I had modified the theme to have a dark background and light text. Since the upgrade, the text has reverted to black making it unreadable. Also, content boxes have lost padding.

The site is www.cloudindigo.com but you can't see the problem because it renders the site unusable and I have had to temporarily revert back to the base theme as I do not have time to fix the problems at the moment.

What are the best steps to take to revert back to 2.2.5?

For future upgrade stability, what customisations should be avoided when using this framework? Whilst the concept is excellent, implementation is becoming very frustrating. This is the third time in two months an upgrade or activation of an add-on has negatively impacted a site. Upgrading to 2.2.3 lost all dashboard settings/reset them to defaults. Installing the Response Gallery section currently impacts the style of the Carousel (fix due to be released). And now this. Whilst updating WordPress itself has always been straightforward, it seems testing is going to have to be standard before applying PageLines updates to any live sites.

[Danny+ 1,327]

Hi Cloud,

Can you add your custom CSS to our paste service http://paste.pagelines.com/

Also can you provide an image as to how your site looked before the 2.3 update please.

[cloudindigo 0]

Here's the URL http://paste.pagelin...a5��There's 3 lines missing as I lost the formatting to the content boxes but they were only adjusting down slightly. There's some other modifications elsewhere in the style.css too but it's just changing colour values to reverse from dark to light. All style adjustments were made within the child theme.

And no I can't provide an image of the site before the update - if I could do that, I'd have figured out how to revert it back. The theme is on at the moment. All text that is now black was previously pale grey. Blog post titles were not flush with the content box borders, padding had them spaced out. And the background on the post forwarding/backwarding section was a dark grey and has reset to lighter.

p.s. the blockquote formatting for text is unaffected - you can see still displaying as pale grey within the first post.

[Danny+ 1,327]

Hi,

The link you have provided is incorrect and also I have just this moment visited your website again, it appears iBlogPro 5 is the active theme at the moment not the dark theme you're referring to.

Can you provide a link to your paste please

[cloudindigo 0]

update - I've reverted the site to the standard WordPress theme for now. Please please could you share the files for the previous 2.2.5 release of PageLines so that I can roll back to it. An update shouldn't mess with something so basic as the paragraph font color in the child theme. I do not have time to keep messing around with settings after each update.

I have the downloaded files for the 2.2.2 version but 2.2.5 was the last stable release and I'd like to keep on that if possible.

[Danny+ 1,327]

Hi,

Unfortunately, I do not have access to version 2.2.5. I will enquire for you but I can't promise anything.

Also, I updated 9 sites to 2.3 and had no such issue, one of these sites was customised like mad and used a child theme.

The issue you experience with 2.3, can be resolved but if you have reverted back to 2.2.2, we will be unable to diagnose your issue until you're back on 2.3.

[cloudindigo 0]

Please see if it's possible to get a copy of the binaries for 2.2.5 first. There are a number of threads that have been started this week by people experiencing formatting problems after upgrading to 2.3. The site is unusable on 2.3 and I can't leave it in that state over a number of days. It would help if somebody could explain why the upgrade has caused such an impact on styles applied to child themes. I see from one of Bearded Avenger's plug-in's changelog that he has moved all CSS to LESS - is that what's required?

If the worst comes to the worst, I'll have to leave it on 2.2.2. It would be a shame to give up on the framework as I do think it's an excellent idea but the support and upgrade issues are a problem.

[Danny+ 1,327]

Basically, to improve performance and ease of use for both developers and users. All the CSS has been moved LESS.

Would it be at all possible for you to paste all your child themes custom CSS please the link above didn't work and I will try to diagnose the issue.

http://paste.pagelines.com/

[cloudindigo 0]

Have pasted again - it gives this URL back http://paste.pagelin...s.com/6m6 Most of the CSS is iBlogPro5 defaults, with some customisations at the start (commented) and some colour adjustments within (usually to flip from dark to light and vice versa)

[Danny+ 1,327]

Did you add your custom CSS to the iBlogPro 5 style.css file and also make the changes there to?

[cloudindigo 0]

Yes, that's the only place the changes were made.

[Danny+ 1,327]

OK, so you added custom CSS to the top of iBlogPro 5 style.css and then proceeded to make alterations of style.css. If this is correct, then that is the reason as to why your site no longer looked the way it did before the update.

If you wish to make changes to a child theme such as iBlogPro 5, please do not edit the child themes style.css file like you did, as when there is an update the style.css file gets updated also and removes any changes made to it. Instead add your custom CSS to either the CSS/LESS code area in PageLines > Site Options > Custom Code or use the PageLines Customisation plugin which contains both style.css and functions.php files like a child theme.

[cloudindigo 0]

OK, I'll try updating and moving the changes. I stopped using the Custom Code area because it got wiped twice and lost the settings.

[Danny+ 1,327]

Hmm the custom code area shouldn't get wiped. When this happend what version was you on and update to?