Matt Ryan

Sorry. Something must have happened when I posted the link. The FAQs page
is working fine. It’s the FAQ on the front page that is the problem.

Thanks,
Matt

Hi @renzms

Thanks for getting back to me.

The report is generated when the PHP Compatibility plugin (https://wordpress.org/plugins/php-compatibility-checker/) is run on a website with your plugin activated. The report is generated regardless of the state of WP_DEBUG.

A few hosting companies I work with, Liquid Web, Flywheel, WP Engine, for example, all recommend using that compatibility report when deciding whether or not the website can run on PHP 7.2. Liquid Web runs this automatically when you try to upgrade to PHP 7.2 and will not process the upgrade until the plugins marked as failing are either fixed, or removed.

Some plugins, like yours, do report false positives if the code that does not meet PHP 7.2 spec, and the code is not generally executed. Not saying your code won’t work on 7.2, its just that it references PHP functionality that has been deprecated.

The whitelist for the compatibility plugin enables you to insure your users that can can safely update their sites to 7.2 and still keep your fine plugin activated.

You can close this out. I performed tests to insure the plugin works and let my customer’s host know it was okay to permit the PHP 7.2 upgrade to move forward.

All the best,
Matt Ryan

The exact error message is

RuntimeException thrown
Error while making ‘tickets.handler’: ‘tickets.handler’ is not a bound alias or an existing class.

I am running Events Calendar 4.7.0.1
Events Tickets Plus 4.8.3
Event Tickets 4.8.4.

When trying to upgrade Event Tickets to 4.9.0.1 the error is thrown.

Hi,

Yep, that’s the culprit. Disabling Nimble Portfolio v3.0.1 allows your plugin to work.

We have been running Nimble Portfolio for more than two years and have been on v3.0.1 for 11 months. Both plugins co-existed just fine, prior to v1.8.7.

I’ll need to troubleshoot why the latest version of WP Video Lightbox is just now conflicting with Nimble portfolio.

Thanks.
Matt

Ah, looks like my HTML code got stripped out. I did point out in my original message that I am using HTML for the video display. Here it is:
<a title="These Wingspan™ battery-free AGVs have synchronized lifts and a tight turning radius. Their main control panel allows them to communicate with the AGV PLC, and they're easily integrated with existing equipment." href="https://www.youtube.com/watch?v=wG45VcgHGKo" rel="wp-video-lightbox"><img src="https://www.example.com/wp-content/uploads/2017/02/Battery-free-AGV-with-synchronized-lifts.jpg" alt="Battery-free AGVs with Synchronized Lifts" width="293" height="21"></a>

Yes, the site is using an SSL cert. We’ve been running on the SSL for quite some time. This page worked fine on previous versions of the plugin. All links and URLs are secured. The problem is that when using the plugin the youtube url is changed from https to http by the plugin. That change results in a mixed content error on the page when using the code inspector console to view script activity.

Hi Caleb,
Thanks for the feedback. I noted that PayPal Pro is being used for non-subscription products. My question is regarding the use of the standard PayPal gateway that is included with Woo and does support recurring payments in subscriptions. You can check that link you sent me to confirm this.

Any ideas about PayPal (not PayPal Pro)?

Thanks,
Matt