conflict with store exporter deluxe

  • Resolved emilysparkle

    (@emilysparkle)


    8 years, 9 months ago

    i’ve been working with the developer of store exporter deluxe and he identified an issue in your code that is causing conflict between the plugins. see below:

    —

    >Widget Countdown… I added the following lines to that Plugin, wpdevart-countdown.php on line #74
    >
    > $screen = get_current_screen();
    > if( !empty( $screen ) ) {
    > if( in_array( $screen->id, array( ‘woocommerce_page_woo_ce’, ‘scheduled_export’ ) ) )
    return;
    > }
    >
    >
    > What I added within their Plugin is to not load their jQuery
    > resources on the Store Export or Scheduled Export screens of the
    > WordPress Administration, they should only be loading their
    > resources when it’s needed so I’d raise this with the developer of
    > that Plugin and get them to conditionally load their resources when
    > required instead of globally.

    —-

    i noticed there’s an update today. by any chance does it address this issue?

    https://www.ads-software.com/plugins/widget-countdown/

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author wpdevart

    (@wpdevart)

    Hi dear user.

    Thanks for your notice.

    Can you contact us st [email protected] and send us more details ?

    We will update our plugin within 2-3 days.

    Best regards,
    WpDevArt support team.

    Hi WpDevArt, just helped a customer this morning regarding this. It’s still an issue.

    There is a CSS conflict of the “datepicker” HTML class. This affects not only our Plugin but any HTML element within the WordPress Administration that uses the “datepicker” HTML class.

    Within your Plugin you are loading your CSS styling globally across the WordPress Administration and not limiting your use of CSS styling to select screens or even better single elements so the .datepicker {display:none} is being applied to all datepickers.

    Just came across this issue as well. Seems to be a conflict with the WooCommerce Bookings extension, which uses the .datepicker class, but the CSS is cascaded (so it targets the correct section), and designed to work only on the Booking admin pages.

    This needs to be addressed on this plugin in order to fully work. Meanwhile, i’ve actually commented out the enqueued stylesheet in the plugin and it still works fine.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘conflict with store exporter deluxe’ is closed to new replies.