Jump to content

Archived

This topic is now archived and is closed to further replies.

admin50

PageLines Sections LESS/CSS error

Recommended Posts

admin50    0
admin50
I have just updated to WP 3.9, using Pagelines 2.4.4 and now seeing at top of Dashboard the following. No idea where this code resides. Have deactivated all plugins to see if any are the cause. Nothing helps. Any advice very appreciated.

PageLines Sections LESS/CSS error.
parse error: failed at `(~"> .span@{index}") { .span(@index); }` line: 907

PageLines CORE LESS/CSS error.
parse error: failed at `(~"> .span@{index}") { .span(@index); }` line: 907

PageLines Custom LESS/CSS error.
parse error: failed at `(~"> .span@{index}") { .span(@index); }` line: 907

Share this post


Link to post
Share on other sites
Danny    1,327
Danny

HI,

 

Can you remove all custom CSS/LESS you have added and then flush your CSS which is under DMS Toolbar > Settings > Reset. If this doesn't resolve your issue, please disable all third party sections and see then flush the CSS again.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
admin50    0
admin50
I am using 2.4.4 so I don't have the flush CSS option.
I don't have any code in the Custom CSS/LESS, only added CSS in the child theme style.css, and nothing
in that code related.
I don't use any third party sections, only Pagelines. Have tried deactivating/activating those.
The errors disappear briefly when I re-save from Pagelines site options, but reappear quickly

Many thanks for helping on this.

Share this post


Link to post
Share on other sites
admin50    0
admin50

I do have DEBUG active, and I see "LESS Compile Error!" at the end of the top menu bar. I assume that might be where the Flush LESS button would appear in 2.4.4.

Share this post


Link to post
Share on other sites
Danny    1,327
Danny

Can you provide a link to the site in question please.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
admin50    0
admin50
www.atpam.com

the error doesn't seem to be affecting the site -- as far as I can tell.

Share this post


Link to post
Share on other sites
Danny    1,327
Danny

You need to disable all active plugins, we can not provide support to users when they have cache plugins active, as this is likely the cause. Please disable all active plugins and see if this resolves your problem.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
Danny    1,327
Danny

Your pages are still cached, we can't provide support if you have cache pages, as it could well be the likely cause. Please disable all active plugins and make sure your cache is flushed.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites
admin50    0
admin50

I believe the issue is somehow related to the Timely All-In-One Calendar plug-in we rely on. The cached error code (starting with the "~") seems to be from that.  Deactivating the plug-in removes the error after flushing the code in the View Site mode (which I didn't notice earlier since my user hides the admin menu when previewing the site). Re-activating the plug-in brings the error back.  I will look for a replacement if that plug-in isn't updated to work properly with Pagelines and WordPress 3.9.

 

I hope this is the solution.  For now I will have to live with the ongoing error.  I do appreciate the assistance, in any case.

Share this post


Link to post
Share on other sites
James B    436
James B

I'm sure there was an issue with this plugin before, that or the all in one calendar. I'll speak with our Developer as from what I can remember they were in contact with the plugin author previously and managed to resolved the previous problem (unrelated to this one) quite quickly.


Kindly search the forum and read the documentation before posting. It will help you resolve many issues.

For CSS help be sure to check out W3Schools first and be sure to download FireBug for FireFox for troubleshooting.

James B

Share this post


Link to post
Share on other sites
admin50    0
admin50

Finding an online search reference to this error at https://reviews.apache.org/r/14110/diff/

-- after backing up the original -- I carefully made the same changes to the /themes/pagelines/less/mixins.less --

The errors have disappeared after flushing the LESS. The All-in-One calendar plug-in remains active and functioning normally.

 

Not sure what the issue was exactly, but it seems to be the resolution, in case anyone else using 2.4.4 has a similar situation.

Share this post


Link to post
Share on other sites
greenfly    230
greenfly

Finding an online search reference to this error at https://reviews.apache.org/r/14110/diff/

-- after backing up the original -- I carefully made the same changes to the /themes/pagelines/less/mixins.less --

The errors have disappeared after flushing the LESS. The All-in-One calendar plug-in remains active and functioning normally.

 

Not sure what the issue was exactly, but it seems to be the resolution, in case anyone else using 2.4.4 has a similar situation.

 

Nice! Thanks :)

 

Framework uses a heavily customized version of Bootstrap for it's less implementation. Bootstrap changed the way it syntax or some of its structure is written. (for want of a better phrase)  So may need to be updated. I will add an issue to the tracker and hopefully your info will help. 

 

- Actually - although the above is true. This is because the Timely plugin implements a compiler that runs before the Framework LESS does. This would need to be reported to the Plugin author as the issue is coming from the plugin. 


The answer to many issues can be found by searching in the forum before posting as someone else  may very well have had the same problem before you have.  Also, reading the documentation can help you gain a good understanding of how everything works. 

 

Please do not send me private messages. Occam's razor - The principle states "Keep things simple!"

Share this post


Link to post
Share on other sites
pixelsrzen    1
pixelsrzen

This is a long-standing issue. I'm thankful that someone found a way to work around this issue, although digging around in delivered code that should be tested and verified feels a little odd.

 

Frankly, I don't give a hoot whose 'fault' this is. It needs to be fixed. Time.ly and PageLines developers need to play nice and make this work. The sooner the better.

Share this post


Link to post
Share on other sites
Danny    1,327
Danny

PageLines Framework works fine out of the box, if a plugin doesn't work with PageLines Framework then you will need to contact the developer of the plugin.


Please search our forums, before posting!

Share this post


Link to post
Share on other sites

×