Michael

Thank you. I ran the update without any issues.

I appreciate your help.

James,

Thank you for your prompt reply. We’ve reverted the affected networks and will pause on updating until the new release

Thank you, HighRollerUSA for catching this error.

By changing the name of the function you’ll stop the error message, but the API key wont be passed in the next pull. Your data will be returned as null because the API key will be blank.

To fix this edit line 8:
old:
function Breeze( $passed_api_key ) {

New:
function __construct( $passed_api_key ) {

I’ll make this change and push an update today.

I appreciate your help catching this. Thank you!

Thank you for your message and kind words.

When dropping in the shortcode, just select the option to “Display The Sermon.net URL”

Or if you’re putting in the shortcode manually, just add/change this line:
sermonnet_url_display=”1″
making sure it’s a 1 not a 0

This will add a link to the item listed.

Thank you for your feedback. I appreciate your review.

Thank you for your message.

The API has not changed.

It takes a decent amount to go out to the sermon.net servers and grab all of your data. We lock all of these in a transient, so this only happens when the plugin is set to refresh or you manually run a refresh.

A lot of shared servers have very limited resources. You may want to either ask for an increase or upgrade your plan.

I hope this helps.

Version 1.3 has been released and supports the new block editor.

Thank you for your message.

As of right now, the plugins shortcode generator doesn’t support the new block editor. You need to use the classic.

We are working on an update that will fix this issue and hope to have that live in the next few weeks.

Jacob,
Thank you for catching this.
I’ve changed the base URL for those links to use get_admin_url();
This will grab the full domain even if it’s in a sub-directory.
I just pushed Update 1.2 that contains this fix and should be available soon.
Have a great day.

Glad we got that working

I just submitted an update that moves the needed jquery to only load where the donation shortcode is used (instead of where any breeze featured was used). I’ve also submitted a ticket to Breeze to see what we can do about the jquery version that is required and what other options we can use.

Thank you for your message.

Yes, I agree that using the installed version of jQuery is the way to go. We’ve just never gotten it to work.

We’ve run the enqueue script function with both Breeze’s script being remote and pulling it in locally (changing the “$” for “jQuery”).

add_action( 'wp_enqueue_scripts', 'wt_breeze_register_scripts' );
function wt_breeze_register_scripts() {
wp_enqueue_script('breeze-script-ui', 'https://www.breezechms.com/js/give.js', array( 'jquery' ));
}

or
`
add_action( ‘wp_enqueue_scripts’, ‘wt_breeze_register_scripts’ );
function wt_breeze_register_scripts() {
wp_enqueue_script(‘breeze-script-ui’, plugins_url( ‘/lib/script.js’, __FILE__ ), array( ‘jquery’ ));
}
‘
Either of these don’t load the donation form.

The only way we can get it to work is to use the exact script that comes from breeze by calling in jQuery remotely. I believe that WP 4.6 is using jQuery 1.12.4 Breeze is calling 2.1.4. My only guess is that the donation form needs this version to work.

I’m open to ideas or other approaches if have anything you’d like to try.

Neil,
Thank you for your message.

This sounds like a potential jQuery conflict. I’ve reached out to the Breeze Team to see if any changes have been made on their end that require me to update the plugin. We’ll see what they say.

In the meantime, you’ll want to check out your website using something like the Firefox Firebug addon with the console tab open (or any other debug program). There are quite a few JS errors that also may be causing this issue (or others). I couldn’t find one that points to the Breeze plugin, but that may be because you have it deactivated now.

If the plugin is currently deactivated, can you please activate it and ping me? That way I can run a test to see if/where the error is being generated from the plugin.

Take care.

Thank you for your messasge
“/wp-admin/options-general.php” is a core WordPress file that this plugin (and many others) will need to display an options page.

It sounds like your install of WordPress isn’t complete. You’ll need to re-upload WordPress to your server to fix this issue.

Thank you for your message.

I see the same issue on my end with your studio id.

It looks like no data is coming over. This most likely means there’s a permissions setting that needs to be enabled to send data.

I believe the setting is on the sermon.net side where you have to check to allow for external feeds. We’ve seen a few accounts that don’t have this selected by default.

Please try enabling this setting and let me know if it works for you.