Conflict between chosen.jquery.js (TCE) and select2.js (premium theme Striking)

Home Forums Calendar Products Events Calendar PRO Conflict between chosen.jquery.js (TCE) and select2.js (premium theme Striking)

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #64847
    Thomas Bügel
    Participant

    For a wesite project for one client I use the Striking theme from Kaptinlin (themeforest.net) and therefor I baught from you The Events Calendar PRO and WooCommerce Ticket plugins.

    But there is a conflict in the used JavaScript libs concerning the backend.
    The admin settings of “The Event Calendar” Plugin will get corrupted.

    In that case no country is selectable. Clicking on “Select an Option” drop down list has no effect, there is no country listed at all. A simlar issue is in the event settings panel with predefined venues, they can’t be selected.
    I first posted the problem to the theme developer Kaptinlin.

    Here is the last answer from Kaptinlin:

    Yes, you are correct, the Events Calendar Plugin is incompatible with Striking. Actually, its up to plugins to be theme compatible not the other way around fyi.

    Events Calendar uses Chosen js, which conflicts with select js we use in Striking. In fact regretfully it will conflict with many premium themes that rely on select js for nav select funtions in both the front and admin of their themes.

    The response you quoted above from one of our support team members is correct – we are finalizing the build out of Striking Responsive, after which we are going to attempt to see if we can build custom “bridges” to enable certain plugins that are not compatible with Striking “out of the box” to work. But normally such work cannot be done until the core theme is finished, which Striking Responsive is still in beta, although what we are doing at this time is code smoothing – a final stage prior to our final themechecks, plugin checks and official release.

    As a multipurpose theme, Striking Responsive is compatible with thousands of plugins, and users have posted a huge list of compatible plugins in a forum thread. In fact we suspect we are compatible with more plugins then most high level premium responsive themes as we have done lots of work in the buildout to ensure widespread plugin compatibility – we are confirmed compatible with a wide variety of ecommerce, form, forum, SEO, and translation plugins (and they can be used at the same time in the theme). When I view the most popular downloads over at the codex, I think we are compatible with every plugin on that list. …

    This statement implies that you as the plugin developer are responsable for the problem. It now seems that I can use eather the theme or the plugin but not the combination.
    For me its quite easier to change the plugins (then I would ask you for the refund of the purchase price.)

    Or have you a solution to the problem?

    #64863
    Barry
    Member

    Hi t3admin,

    Actually, its up to plugins to be theme compatible not the other way around fyi.

    That does imply we are responsible for the problem – but I don’t agree, especially when the problem affects the admin environment, as it seems to do here.

    Whether we are talking about themes or plugins doesn’t really matter: if one component (Striking) impacts adversely on the admin screens of another (such as those that our own plugin generates and is responsible for) – perhaps by enqueuing scripts and styles that don’t belong there – then it would seem clear that the responsibility lies with the component which adds those unwanted scripts.

    That said, we want to support you as best we can and if in this case it means providing a refund so you can move on to a plugin that isn’t affected in this way we will happily consider your request. Please email us, including a link to this thread, and one of the team will help you as quickly as they can: pro (at) tri (dot) be

    Sorry it didn’t work out for you.

    #64893
    Thomas Bügel
    Participant

    By the way, here are the links to the discussions with Kaptinlin:
    http://kaptinlin.com/support/discussion/comment/34658#Comment_34658
    and the latest:
    http://themeforest.net/item/striking-premium-corporate-portfolio-wp-theme/discussion/128763

    For myself I’m not sure what realy conflicts, cause TEC seams to use the select2 Library too but in an earlier version (3.2)
    I discovered when not loading the select2.min.js (version 3.4.1, from the Striking theme) when in the scope of TEC, then TEC admin pages are working as expected and it doesn’t concerns the Striking issues.
    I’m looking for a workaround to implement that. If that would be possible I could use Striking and TEC. If not I guess I have to use an other Event Manager plugin, or you will find a solution.

    With regards Tom

    #64895
    Thomas Bügel
    Participant

    Because I cannot correct misspelling in the last comment I post the correct version too.
    By the way, here are the links to the discussions with Kaptinlin:
    http://kaptinlin.com/support/discussion/comment/34658#Comment_34658
    and the latest:
    http://themeforest.net/item/striking-premium-corporate-portfolio-wp-theme/discussion/128763

    For myself I’m not sure what really conflicts, because TEC seems to use the select2 library too but in an earlier version (3.2)
    I discovered when not loading the select2.min.js (version 3.4.1, from the Striking theme) when in the scope of TEC, then TEC admin pages are working as expected and it doesn’t concerns the Striking issues.
    I’m looking for a workaround to implement that. If that would be possible I could use Striking and TEC. If not I guess I have to use another Event Manager plug-in, or you will find a solution.

    With regard Tom

    #64918
    Barry
    Member

    Hi Tom,

    Thanks for linking to those. It does seem to reinforce what I was saying earlier, however, with regard to this note from Paul (who I think is part of their support team):

    i have to talk to kaptinlin if it is possible not to load that script while in the screens of the the events calendar.

    It’s not the responsibility of our code to proactively tidy up after other plugins and stop their code from running where it shouldn’t be. We have already spent some time looking at compatibility with Striking and the result was that, at least for the foreseeable future, we simply view Striking as being incompatible with The Events Calendar.

    We’re sorry we can’t do more to help with this one but we can definitely offer you a refund if you want to follow the steps I outlined above 🙂

    Thanks again,

    Barry

    #65250
    Thomas Bügel
    Participant

    I wrote a very little plugin to fix the problem without warranty, but my tests have been OK! May help some one, so you can use Striking and The Events Calendar together!
    Download it from: http://kaptinlin.com/support/uploads/FileUpload/32/62244839c922c6a67c40d1812cc47f.zip

    With regards Tom

    #65260
    Barry
    Member

    Excellent, thanks for sharing Tom 🙂

    #980729
    Support Droid
    Keymaster

    This topic has not been active for quite some time and will now be closed.

    If you still need assistance please simply open a new topic (linking to this one if necessary)
    and one of the team will be only too happy to help.

Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘Conflict between chosen.jquery.js (TCE) and select2.js (premium theme Striking)’ is closed to new replies.