Activating Pro 2.0.2 breaks backend
  • Stranger
    Posts: 16
    Topics: 4
    Sam January 6, 2012

    Just purchased Events Calendar Pro and installed 2.0.2 After activating the Pro component the wp-admin breaks and I cannot access any part of the backend of the website (error 500). Front-end still seems to work ok with the exception of the upcoming events widget being missing. I have been using events calendar for a while without pro. I have tried activating pro with the free part deactivated and the plugin activates no problem (of course its not useable without the free part active). Activating the free part after also breaks the backend.

    Edit: Im using WP 3.3.1

  • Gatekeeper
    Posts: 4184
    Topics: 77
    Answers: 467
    Rob January 6, 2012

    Hi Sam. Thanks for the note. This should definitely not be happening – are you by chance running Events Calendar PRO 2.0.2 against a non-2.0.2 release of Events Calendar, ie 2.0.1? You should have the two consistent. Let me know if that’s not the root of the problem here and I can keep looking into it for you.

  • Stranger
    Posts: 16
    Topics: 4
    Sam January 6, 2012

    Both plugins are at 2.0.2

  • Stranger
    Posts: 16
    Topics: 4
    Sam January 6, 2012

    Just tried deactivating all plugins and activating EC and EC Pro only and it worked so I am looking at a plugin conflict with Simple Google Connect which is in beta so I’m dumping SGC for now.

  • Stranger
    Posts: 16
    Topics: 4
    Sam January 6, 2012

    WPtouch also conflicts…will leave disabled for now but I would be really interested to see which is the plugin that is offending and how that could be fixed.

  • Gatekeeper
    Posts: 4184
    Topics: 77
    Answers: 467
    Rob January 6, 2012

    Thanks for confirming that it’s a conflict with another plugin, Sam. While we do what we can to provide integration tips with other plugins, it’s not an exact science so it’ll be hard to get everything 100% smooth. I would be happy to get a copy of PRO over to the dev behind WPtouch, and to work with them on whatever they need, to try and make things work…feel free to pass that along if you’re posting this same issue on their forum.

  • Stranger
    Posts: 16
    Topics: 4
    Sam January 10, 2012

    I’ve also now discovered that activating Simple Facebook Connect breaks the iCal feed. Running feed validator shows the feed not validating even with SFC disabled (http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.hcfsidney.ca%2Fevents%2Fical%2F). I checked another person’s site and they get the same syntax error I get.
    The only difference with SFC active is that the feed appears to be empty…weird!

    Conflict Report to WPTouch
    http://wordpress.org/support/topic/plugin-wptouch-plugin-conflict-1?replies=1

    Conflict Report to SGC/SFC
    http://wordpress.org/support/topic/plugin-simple-facebook-connect-conflicting-plugins?replies=1#post-2551533

  • Stranger
    Posts: 16
    Topics: 4
    Sam January 10, 2012

    Otto from SFC, SGC, STC suggested that something like this could be an issue:

    http://ottopress.com/2011/actions-and-filters-are-not-the-same-thing/

    I get the gist of it but it is still a bit over my head. Sorry I’m not more help :(

  • Gatekeeper
    Posts: 4184
    Topics: 77
    Answers: 467
    Rob January 10, 2012

    This is good to know, Sam – thanks. While we can’t guarantee anything, we’re always looking for plugins that ours conflicts with so we can try our best to rectify them for a future release. Appreciate you pointing this out.

  • Stranger
    Posts: 16
    Topics: 4
    Sam January 24, 2012

    Just thought I would make a note on this issue – I didn’t check until now but it seems that the update to 2.0.3 of Pro has resolved the conflict. Not sure what you did but everything is working just dandy in WPTouch, SGC, and SFC. Happy happy joy joy! Thanks guys.

  • Gatekeeper
    Posts: 4184
    Topics: 77
    Answers: 467
    Rob January 25, 2012

    Ah, excellent to hear that 2.0.3 did the trick! Thanks for confirming, Sam. If any other issues along these lines emerge in the future please let us know and we’ll look into it again.

  • Viewing 11 posts - 1 through 11 (of 11 total)

This topic is closed