function ‘give_load_admin_scripts’ not found

Hi there,

That’s not normal at all! It feels like your update didn’t finish completely. I’d suggest trying our free WP Rollback plugin to roll back to Give 2.0.6, then use the WordPress updater to update to 2.1 again. Make sure you have a full-site backup before doing any of this though (as always).

Let me know how it goes.

Hi Matt,

Tried that out, when I rolled back to 2.0.6 the error message went away, after updating it back to 2.1, same error shows back up. Error only shows in the admin not the front end.

I’m using the Philanthropy Theme, with their Child Theme, seems that might be causing this issue by not loading the ‘give_load_admin_scripts’. When I switch the theme back to twenty Seventeen, it goes away as well, but both the Philanthropy Parent and Child show the error. Is there a function perhaps to add to the child theme functions.php to force this to load?

HI @bittennails — I have one other user reporting this in our Priority Support channel, and I have their full system info. I’m going to try to reproduce the error now. I’ll keep you posted.

In the meantime, if you are seeing that Warning on the screen, then for now make sure that in your wp-config.php that you have WP_DEBUG set to false, like so:
define(WP_DEBUG, false);

Thanks!

Hi Matt,

Were you able to reproduce the error, any update on this, issue still persists at my end, let me know, thanks!

Hi @webdevmattcrom,

Another update, I did try updating to 2.1.1 that I saw you just rolled out, but the same error shows up again.

Followed your steps to double-check it as well, rolled back to 2.0.6, error disappeared, and then updated straight to 2.1.1, skipping 2.1.0, but the error came back.

Let me know, thanks.

@bittennails — this isn’t actually an “error” but a warning, and it’s most likely because you have addons that are either not updated yet, or we are about to update them. Once all the addons are updated for compatibility with 2.1 then that warning will go away.

As I mentioned previously, you would only see that warning physically on the screen if you have WP_DEBUG set to true. Set it to false and it’ll go away. Then of course, when the addon update is released, the warning won’t exist at all anymore.

Thanks!

Hi Matt,

I am getting this exact same warning message after the latest Give update. I get that it won’t show if WP_DEBUG is false, but my OCD nature doesn’t like to know these things are there and I don’t know what’s causing it.

Hopefully it goes away soon.

Cheers
Mark

@watzupmark — you can enabled the WP DEBUG LOG with this:
define( 'WP_DEBUG_LOG', true );

Then those warnings will go into a file in your root folder that you can check whenever you like. Most likely you’ll see plenty other warnings there as well that you maybe weren’t already aware of.

As I mentioned, we have several more addons to update to be 2.1+ compatible. I’d expect that to take the rest of this week.

Hi Matt,

Just a follow up so you are aware, the update to 2.1.2 today, does not fix this issue either.

If you could update us as to when the add-ons have been updated that would be great.

I could move this to priority support if you’d like? I purchased the recurring donation plug in so do have an account on your website now, but considering this thread is open, it may be best to leave this here for others.

@bittennails — sorry if that wasn’t clear, but I did not intend to suggest that a Give Core update would fix this issue. The addons have to be updated to have our new updated hooks. Once that is done the warnings will go away. But again, we’ve built backward compatibility into this, so the addons that are not yet updated will continue to work as intended, but you’ll have those warnings until they are updated.

You can move it to priority support if you like, but the response will be the same. Thanks!

Hi @webdevmattcrom.

We are seeing this same issue on our WP dashboard. Is there a recent fix for this as of today?

Thanks always for your help.

Arvin

• This reply was modified 6 years, 3 months ago by opensesame.

Actually after updating the Core Theme and the Unyson active extensions, the error no longer pops up. ??