Home Forums Author Posts Author Post Box displaying CSS in sidebar – broken

Tagged: , ,

This topic contains 4 replies, has 3 voices, and was last updated by  Anthony Zeoli 1 year, 1 month ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #21987

    Anthony Zeoli
    Participant

    Hi,

    I’m mortified that I bought this plugin and for some reason, it’s displaying all the plugins CSS right in the sidebar widget.

    Why is this plugin broken?

    See this page: https://vrmexico.staging.wpengine.com/agents/alex-aquino/

    #21988

    Charlie
    Keymaster

    Hi Anthony – Sorry to hear. We haven’t had any reported issues for this plugin, so let’s figure out what’s going on your site.

    I took a look at the source code and was not able to decipher anything unusual.

    1) Can you let us know if you used a wodget or shortcode to add to the sidebar?
    2) Do you have any javascript compression plugin? caching plugin?
    3) Is this a custom / modified theme?

    We’ll get it sorted in a jiffy once we know more info. Thank you!

    #21989

    Anthony Zeoli
    Participant

    There is no caching on WP Engine Staging, so that’s not it.

    I used the Widget to add to the Sidebar.

    I’m using the Content Aware Sidebars 3.7 to add the Widgets to the sidebar.

    This is the theme, Realtyspace, available through ThemeForest. It does use Visual Composer on layouts/pages, but there’s no need for VC in a sidebar.

    I do have Autoptimize installed and active on staging though. I dumped the Autoptimize cache and that didn’t help.

    #21994

    Jay Gajjar
    Keymaster

    Hey Anthony,

    We looked into your issue, and we haven’t been able to replicate it on our side.
    After exhausting all other forms of debugging it might be best to check for plugin or theme conflicts.  Plugin or theme conflicts can cause our product to function unexpectedly or not at all, which is why testing for this conflict is very important.

    ​We recommend that you perform this test on your staging site and that you backup your site.  If you do not have a staging site then you might not be able to perform this test as deactivating plugins or your theme will greatly impact the look and functionality of your site.

    Before you perform this test please make sure you have the latest version of our productWordPress and PHP.

    1. Deactivate all other plugins on your site besides our plugin
    2. Test to see if the plugins features work as you would expect.  If they do work then you have a plugin conflict.  You should now activate each plugin on your site one by one until our plugin’s features do not work.  This will help you determine what plugin exactly is causing the conflict.
    3. If our product still is not functioning properly, then you can try to deactivate your theme to see if there is a theme conflict.  This is a last resort and should only be done if you have a staging site or your site has not gone live yet.  If our product works after deactivating your theme then you have a theme conflicts, but if our product still does not work then it appears that our product has a bug.
    4. If you have completed all of these tests and our product does not function properly with a default WordPress theme like twenty twelve and all plugins deactivated, then it seems that our product has a bug and we will continue to work with you to solve this issue.

    Please let us know if you have any questions about this conflict testing procedure.

    #22009

    Anthony Zeoli
    Participant

    My developer was able to hide the exposed CSS.

    He said: Line 239 of author-posts-widget.php — I commented it out.

    Not sure what that is, but that fixed the issue for now.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic.

Pin It on Pinterest