ovann86

Hey Scott – I’ve tried to add you as a contributor so you can do what you need to get this plugin working for you again (assuming that’s what you need).

Feel free to reach out to me at [email protected] if you want to take full/sole ownership of it.

I would be keen to hear if you have specific plans, interest, or capacity to maintain it.

I just had a quick look, and it does look like the ABR API supports searching by name – with a whole bunch of filters included.

How were you thinking it would work?

An ABN search is easy because you just need an exact match and you know it’ll be unique.

Searching by name is a lot more fuzzy – may be multiple people with the same name, people may not type their name correctly.

https://abr.business.gov.au/Documentation/WebServiceMethods – see ‘search by name’

• This reply was modified 3 years, 2 months ago by ovann86.

Hey,

The quick answer is – no.

I don’t recall their API being able to do reverse searches, but if I get the opportunity I’ll look back and see.

It would be a very useful feature.

Hi Both,

I recently updated the plugin to use the new form editor menus found in Gravity Forms 2.5.

You should be seeing a “ABN Lookup” menu in the right hand side when you select a “single line” text field. (you’ll also see this for a few other field types, for populating with the ABN’s info).

Do you see this menu? Or do you see the menu and it’s empty?

https://ibb.co/d74Y0HP

If not, and you’re still having troubles …

• Which version of Gravity Forms are you using?
• Which version of WordPress are you using?
• Do you have any customisations that change the Gravity Forms form editor (potentially a “disable gutenberg” type plugin)?

• This reply was modified 3 years, 2 months ago by ovann86.

Hey,

If I understand right – you haven’t yet registered for access to the API.

The registration form starts after reading and accepting the agreement

https://abr.business.gov.au/Tools/WebServicesAgreement

They will email you the GUID for accessing the service.

I forgot to reply to this message.

Version 2.3.0 introduced a new ‘Use Cache Buster’ setting – which should bypass cache plugins.

It won’t talk “live” to Disqus (like the recent_comments_widget.js) – as this would likely use up all your API calls.

But if that’s important for you – the ‘Cache Time’ setting can be adjusted to a lower amount.

Or as an extreme you can enable ‘Bypass Cache’ to talk “live” to Disqus – but again, each request will use up the limited API calls they allow per hour.

Let me know how you go with it.

Hey,

I’m not able to reproduce this issue.

Could you send a form export to [email protected]

Hey,

It looks like this issue is related to Gutenberg and the way this plugin was using GFAddOn to localize scripts – as the issue doesn’t happen when using Classic Editor.

I’ll release an update shortly which should resolve it.

Hey Jon,

I just resolved a conflict between the new Gravity Forms accessibility tweaks and this plugin – so if you install 1.7.2 of this plugin it should continue to play well.

Just a note on the relevance of this plugin … Gravity Forms are making great steps towards making the forms accessible – recently I’ve been able to remove a great deal of what this plugin does thanks to this.

I hope that one day I can stop maintaining this plugin but in the meanwhile I’ll keep doing what I can.

Personally, I think the most significant thing this plugin brings is improving the validation handling. If a user attempts to submit a form and it has validation errors they will get a list of those errors – no need to search through the entire form to find the error and solution.

Do let me know if you see any other issues.

https://oi65.tinypic.com/2qv8v7o.jpg

Hey Daniel,

Thanks for reporting this.

It looks like it was a conflict with accessibility enhancements added in Gravity Forms 2.4.7.

I’ve released an update of this plugin that should resolve it.

= 1.7.2 =
* Fix: resolve conflict with Gravity Forms 2.4.7 “Added accessibility enhancements”. The combination of this plugin and Gravity Forms 2.4.7 or higher would break the list field add and remove buttons
* Maintenance: improved targetting for making links in forms open in a new window

OK – give 1.8.5 a try.

Hey Zack,

Have you been able to reproduce the issue?

I just spun up a test site and tried various combinations of single and multi-column list fields with various calculations – both horizontal and vertical (totals) – but didn’t have any problems.

If you can, can you provide an export of a form or a description of how to set it up to reproduce the issue?

Thanks

Hey,

Thanks for raising this and providing the solution.

I’ve pushed the update out in version 1.8.3

I think I found the problem and released a fix in version 1.8.2 (or above)

Hopefully that does the job.

Hey,

Interesting !

I can reproduce it and should be able to look at it tonight (in about 12 hours time).

I’m wondering if it should have a proper placeholder feature – so that people can’t submit the form with the placeholder – “Select a colour” selected)