2.2 Known Issues/fixes
Posted 20 June 2012 - 01:22 PM
They affect the way the LESS CSS is minified before being sent to the browser. It seems to remove the letter 'r' from the CSS, we have added an option in 2.2.1 to enable minification and made it disabled by default.
The CSS rewrite was broken on some Windows based ISS hosts. Fixed in 2.2.1
If rewrites are still broken ie the CSS is a 404 and works the add the following to wp-config.php:
Now robs widget post : Friends,
A solution to this issue is likely to be released very soon, but I've noticed that some of you have clients asking for immediate resolution. I can understand your plight. Here's a temporary solution that should take under 10 minutes, even on the most complex sidebars.
Simply go to Dashboard > Appearance > Widgets. You'll notice that the sidebar order has changed and is now set up in descending priority... Primary, Secondary, Tertiary on top.
You'll need to carefully review each of them and slide the widgets from their new, incorrect location, back to the old, correct location.
Please, don't slide the widgets back to the main area of the page. Only slide them up or down. This preserves any settings within the widget. If you move them back to the widget holding area, the settings will be lost.
Once moved back, they will stay where they belong. You do not have to save the widgets to preserve their location. Moving them in place is sufficient. I had to do this myself last night when I upgraded to 2.2 and initially screamed a bit. After getting past the shock, it became clear to slide them and with a large number of complex sidebar combinations took me about 4 minutes to fix.
We apologize for any inconvenience. I can assure you we're working on a solution quickly.
Posted 20 June 2012 - 07:09 PM
Posted 20 June 2012 - 11:41 PM
Posted 21 June 2012 - 12:31 AM
Posted 21 June 2012 - 05:53 AM
Posted 21 June 2012 - 08:37 AM
Posted 21 June 2012 - 08:58 AM
Posted 21 June 2012 - 09:08 AM
Posted 21 June 2012 - 10:44 AM
Posted 21 June 2012 - 12:51 PM
Posted 21 June 2012 - 01:12 PM
It said there was an upgrade to 2.2.1 available so I upgraded, it then said there was another upgrade available so I upgraded and now my site is completely down and to top it off I am unable to access Blogsense which is installed in a separate folder on the root domain to restore my backup.
Scrap that it appears to have sorted itself out after 5 minutes of being in Maintenance Mode, Still not impressed though.
Posted 21 June 2012 - 01:44 PM
I get the PageLines Custom LESS/CSS error. parse error: unclosed block. How do I get rid of this error? I am not noticing any issues due to the parse error yet, but it's obviously concerning.
Posted 21 June 2012 - 01:55 PM
Posted 21 June 2012 - 03:56 PM
Posted 21 June 2012 - 06:41 PM
Posted 21 June 2012 - 06:45 PM