[Mark Alderton]

Thank you Geoff, we love your product and your support. We have faith there will be a solution. Glad the bug was confirmed for the benefit of all and we’ll stay tuned for that fix.

[Mark Alderton]

This reply is private.

[Mark Alderton]

This reply is private.

[Mark Alderton]

This reply is private.

[Mark Alderton]

This reply is private.

[Mark Alderton]

Thank you for the quick reply, your code worked great.

For other readers, as suggested by Brian above, we do have a pre-built theme that was purchased from a designer who had also integrated Events Calendar Pro to their own preferences. They customized and overrode certain MT default CSS settings for this plugin.

Hunting for this code in our current Events Cal Pro CSS files and elsewhere found nothing. We then added MT’s code to the last line in our designer’s custom CSS file.

[Mark Alderton]

Thanks Geoff, your suggestions worked. Issue solved.

For anyone’s future reference,

Our site was in re-development on a new destination server during the initial installation of these plugins and during the domain association of their license keys. We were developing with an IP based URL, not the proper corporate domain name. Overlooked by us, when we installed the plugins the Tribe system automatically attached our keys to the work-in-progress IP based URL. We then failed to revise this setting in our Tribe Events licenses page post-launch.

A couple months after our launch (and domain name DNS modification,) Tribe’s recent updates then occurred naturally. But their system was still identifying our keys with the old IP based URL and thus not allowing plugin updates to occur in WordPress properly. It stated we were out of installs (thinking we were attempting to install on multiple domains.)

SOLUTION:
We disconnected the license keys in our Tribe license key settings, we then deactivated and reactivated the plugins in WordPress. The plugins reattached themselves to the license keys, in Tribe the keys then reflected the proper domain name for our site, we were then able to update our plugins in the usual “Update Now” technique on the Plugins page in WordPress.

Tested and solved.

Tip – When plugins fail you might have purposely deactivated them until a solution is offered. Make sure these plugins are activated in WordPress before this restoration effort to properly trigger the WordPress “Update Now” prompts and also the license key attachment between WordPress and Tribe.

Tip – In this scenario, update Events Cal Pro first, before updating WooCommerce Tickets.

[Mark Alderton]

Please know that we have since deactivated the Wootickets plugin until this issue is resolved. Now you will not see an example of my on-page error as stated in my initial post. Here’s a pasted copy of the on-page error when the plugin is active:

Warning: include(/home/wwwscbg/public_html/wp-content/plugins/wootickets/src/views/wootickets/tickets.php): failed to open stream: No such file or directory in /home/wwwscbg/public_html/wp-content/plugins/wootickets/classes/class-wootickets.php on line 485

Warning: include(): Failed opening ‘/home/wwwscbg/public_html/wp-content/plugins/wootickets/src/views/wootickets/tickets.php’ for inclusion (include_path=’.:/opt/php54/lib/php’) in /home/wwwscbg/public_html/wp-content/plugins/wootickets/classes/class-wootickets.php on line 485

[Author]

Posts