Hey @francesco,

The file you’re referencing there, “acf-input.min.js”, is a part of ACF core, not ACF Widgets. I assume you’re trying to use some sort of frontend form powered by ACF? (Personally, I’ve never been a fan of doing things that way.)

It’s been a while since I’ve done any substantial ACF work, but I think it’s safe to say the error is somewhere in your implementation. You may need to bootstrap your js files earlier/later so everything can mount properly.

Good luck!

Hello,

I’ve issued the refund with PayPal.

Thanks for trying out the plug-in!

Jackie,

What version do you have? You can also download the latest version from the site here. I’ll be honest that it hasn’t been updated in over a year, so whatever version you have is likely good.

I’m busy with my day job this week but I’ll take a look when I can!

Let me know if you get it sorted out.

• This reply was modified 12 months ago by Daron Spence.

Hey Rick.

Sorry about that, your messages must have slipped through the cracks in my inbox. Thanks for reaching out again. Since nobody else had reached out about the same issue, I must have assumed you figured out whatever was going on.

Do you have the debugging option turned on in the plugin settings? I’m sorry I didn’t think of that first. That was an oversight on my part.

Sorry you’ve had this much trouble.

Hmm that’s weird. It shouldn’t show that message for widgets that weren’t created from the plugin. Can you see if they’re still there with a default theme and no other plugins active?

Glad you got it figured out Ken! Please let me know if you need help with anything else.

I’m going to mark this thread as resolved 🙂

Thanks for supporting ACF Widgets!