Resolved LESS Compile Error! leading to dashboard whiteout

[sanjayvenkat23 0]

Hi, our pagelines interface has been whited out. It says there's a LESS Compile Error. We set wp_debug on per some of the other posts and are seeing the following error:

Notice: Undefined index: post-trashed in /home/elder/public_html/blog/wp-content/plugins/disqus-comment-system/disqus.php on line 936

I guess it's an issue with our Disqus plugin? Unclear how to proceed. Any help much appreciated.

thanks,

[Simon 248]

ok, the site listed in your profile is not even running wordpress.

Disable the disqus plugin 1st.

What was the compile error?

[sanjayvenkat23 0]

Sorry, the wordpress part is in www.elderbranch.com/blog. We can't seem to disable the disqus plugin because the plugin menu (along with all other menus) are blank.

Compile error is: Error in custom LESS code: parse error: failed at `

(we tried to add some custom code for css styling of tables in our posts - not sure if that caused all this or if it's 2 separate issues).

thanks,

[Simon 248]

do you have ftp access? if so, rename the pagelines folder to pagelines_ the go to wp-admin, login. Wordpress will switch to the default theme as it cant fint the active theme (pagelines)

Now your in admin, disable the plugins. Then rename the folder back to pagelines and in appearance/themes re-activate it, then go to the custom css area and remove the broken css.

[sanjayvenkat23 0]

Ok, followed those steps. Unfortunately, when we go back into pagelines after renaming the folder it is still all white. So, we can't remove the broken CSS. No longer getting the Disqus error but still seeing the compile error. Do you know what file the custom code piece is in? Perhaps can open that file directly off ftp and delete the code segment there? Thanks,

[Simon 248]

The css is stored in the database. But that would not cause a 'white page' and if you have WP_DEBUG on the error should be shown. Do you have any other plugins active?

[sanjayvenkat23 0]

No, no other plugins are active. Disqus was the only one we had active and we disabled it. WP_debug not showing any other issues.

[Simon 248]

So all admin pages are still white?

[sanjayvenkat23 0]

Yes - still all blank. See attached picture. Thanks,

[Simon 248]

And the site options tab?

[sanjayvenkat23 0]

Sorry for late response - I finally resolved the issue. We had to go into the database and do a search for the CSS code segment there. Realized we had a line of html code there on accident and it was causing the CSS compile error. Deleting the code solved it. Thanks for the help.

[Danny+ 1,327]

The topic was marked as resolved.

[bpjerseyboy 0]

Sorry for late response - I finally resolved the issue. We had to go into the database and do a search for the CSS code segment there. Realized we had a line of html code there on accident and it was causing the CSS compile error. Deleting the code solved it. Thanks for the help.

There is another open topic on this as well. It appears all 3 of us are having the same problem. Where was the css file in the in the database? I looked for the most recently updated file, but as I had just done an update, I had no luck locating it since several files had the same date.

[Rob 547]

There is no CSS file in the database. The information is stored in the database. We don't support editing the database, which is why Simon recommended the solution posted above.

[Simon 248]

There is another open topic on this as well. It appears all 3 of us are having the same problem. Where was the css file in the in the database? I looked for the most recently updated file, but as I had just done an update, I had no luck locating it since several files had the same date.

So are you saying the 3 of you added HTML into the CSS box?

[marius42 0]

will make new post

[Danny+ 1,327]

If you receive a Parse error, it means your CSS is incorrect and you have an error(s).

 

Have you add this to your custom CSS:

 

 

<style type="text/css">

<!--

.moth {

    font-family: "goudy Old Style";

    font-weight: bold;

}

-->

</style>

 

In this format, if so this is the cause of your issue.