WordPress.org

Ready to get started?Download WordPress

Forums

Codestyling Localization
Woocommerce 1.6.6 conflict (3 posts)

  1. pricklepantz
    Member
    Posted 1 year ago #

    Helo, after installing Codestyling, woocommerce settings page has problems:
    1. Color picker not working
    2. Icons beside tabs are missing (Settings, Reports, Coupon, Notifications)

    Enable low memory mode is activated
    Other known notices:
    PHP runtime error reporting detected !
    Reason: some executed PHP code is not written proper | Originator: unknown (probably by Theme or Plugin)
    Below listed error reports has been traced and removed during page creation:
    NOTICE Error: [8] Trying to get property of non-object /.../public_html/wp-content/plugins/always-edit-in-html/always-edit-in-html.php on line 39
    Malfunction at 3rd party Plugin detected!
    Name: WordPress SEO | Author: Joost de Valk
    Below listed scripts has been automatically stripped because of injection:
    http://.../wp-content/plugins/wordpress-seo/js/wp-seo-admin-global.js

    http://wordpress.org/extend/plugins/codestyling-localization/

  2. codestyling
    Member
    Plugin Author

    Posted 1 year ago #

    I have intensivly tested my plugin against a lot well known and wide range used public plugins. My plugin only protects it own pages and doesn't have any influence to any other pages in Admin aera except its own pages.
    So the issue you may see is not caused by my plugin. For sure I have checked it within my local environment with woocommerce 1.6.6 and all works as expected (images before tabs and also color pickers working as expected).

    Because my plugin shows at its own pages a PHP warning like you wrote:
    wp-content/plugins/always-edit-in-html/always-edit-in-html.php on line 39
    I would say, the plugin "always-edit-in-html" causes at least some problems at other backend pages too. You can only find out, which plugin is causing the error by deactivation plugin by plugin.

    If you did lately upgrades of plugins/theme (more than one) or core, any of those updated components can potential cause issues afterwards.

  3. pricklepantz
    Member
    Posted 1 year ago #

    Thanks, I guess the only way now is deactivating it.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags

No tags yet.