Frequently Asked Questions

Home » FAQ » Known plugin conflicts

Known plugin conflicts

We do our best to avoid conflicts with plugins by other developers, but sometimes we find situations where the problem cannot be solved from our end, and the conflicting plugin’s authors have not solved the problem. The following is a list of known conflicts with other plugins and/or themes.

Last updated September 8, 2020

Plugins

  • Hummingbird / Hummingbird Pro by WPMU Dev

    This plugin forcibly removes Thickbox (JS library bundled with WordPress) from Sliced Invoices’ quotes and invoices templates. This makes it impossible to accept a quote, decline a quote, or make a payment on an invoice. At present we are not aware of any way to prevent Hummingbird from doing this, short of deactivating their plugin entirely.

  • Elegant Elements for Fusion Builder by InfiWebs

    This plugin is breaking the normal result of the core WordPress function get_the_ID(), causing it to return an ID that is different from the real ID of the post. This causes all functions in Sliced Invoices which need to know the post ID (i.e. the ID of the invoice or quote) to break. (ref.#102847)

Themes

  • ThemeFusion Themes in General

    ThemeFusion themes including Avada and probably many others, as well as their “Fusion Core” plugin, use a deprecated jQuery function which was removed as of WordPress 5.5. This will crash the JavaScript on many WP Dashboard pages, including Sliced Invoices’ pages, and probably many other plugins too. As a result Sliced Invoices will not work correctly.

    As a temporary workaround, you can install the Enable jQuery Migrate Helper plugin. This will restore the pre-WordPress 5.5 functionality, avoiding the error. (That said, a permanent solution will require the Fusion theme to update their code.)

    UPDATE 2020-09-08: For Avada theme, their latest version (7.0.2) apparently solves the issue, so it seems ThemeFusion is working on the problem. If you are using some other ThemeFusion product besides Avada, please watch the changelogs for an update from them which mentions “compatibility with WordPress 5.5”.