Set as post name and other problems

Hello,

Thanks for the feedback!

Unfortunately, “Set as post name” & “Browser Upload” for Gallery field settings are not ACF Extended features. I would recommend to contact the other plugin developer in order to fix the problem.

I understand the situation can be unconfortable for you, but ACF Front-End Form for Elementor essentially does what ACF Extended Form already does. It also use the ACF Extended reCaptcha Field & JS code without crediting me, so I hope you’ll understand I can’t spend time to debug someone else’s plugin.

Regards.

I totally understand.
I just wanted to pass on the info because I lost about 10 hours investigating and resolved by rolling back 1 version of ACF Extended.
By the way, the problem did enable me to discover your Forms and they are really great. To be honest I didnt even see them there, lost in the text menu up there. If I may suggest to make it more prominent in the UI.
Thanks for your great plugin!

Hello,

I’m sorry to hear that. Out of curiosity, I took a look a the plugin code, and in fact it comes from the plugin logic, as it doesn’t correctly handle the acf/update_value and incorrectly unset() the $field from the $_POST, when it should not.

ACF Extended now use the acf_setup_meta() & acf_reset_meta() functions which are quite advanced (also used in ACF Block Type preview mode), and invoke the acf/update_value filters.

Regarding the ACFE Form manu not being visible, some people already suggested me to move it to a top level position. I tend to be extremely careful when it comes to create new admin menu, especially top level menu items (I hate plugins doing it without any good reason). But I can see it making sense. I’m currently discussing with my community, to see how they would welcome that change.

I think you gonna like ACFE Form if you never used it before ??

Regards.

I hadn’t seen this message, sorry.
I think it would make great sense because the front end form is a major feature.

For the first part of your message, I didn’t quite follow.

Either way I am still having multiple mini bugs here and there and I can’t seem to actually find the culprit.

For example, when a field is “Taxonomy, it will not save as such. It reverts back to “Text” when I go back to edit.

If I disable Elementor, it stops.

All these multiple little problems signify something is wrong in the Elementor/ACF/ACFE trio… somewhere.

@julien_e we are going to release a fix to this issue in ACF Frontend 2.8.30

All the best

Hello,

Yeah the answer was kinda technical.

I think your bug with Taxonomy Field come from somewhere else, probably an another plugin or a custom code. The Taxonomy field works correctly on a fresh WP Install + Blank Theme + ACF Pro + ACF Extended + Elementor.

Video showcase: https://i.imgur.com/UZHVrep.mp4

I would recommend to disable your plugins one by one, until you find what cause it.

Regards.

@shabti great to hear thanks. Which one in particular? Also, since it came up in this post — and I am certainly not taking sides — please kindly make sure that all devs are credited, where credit is due ??

@hwk-fr I did debug, and found some of the issues are resolved when Elementor is disabled… hardly a fix ??

It’s true that most things work on a totally fresh install. In my case however, I have 4 sites experiencing bugs at the moment.

At this point I’m just waiting for all plugins to update with the hope it will help.

Hello,

Thanks for the feedback. As explained in my previous post and shown in the video, the problem doesn’t come from Elementor or ACF Extended. You have an another plugin which interact with Elementor and ACF which break the Taxonomy field.

This is why disabling Elementor seems to fix the bug, when it probably doesn’t, as the faulty plugin is most most likely automatically disabled when Elementor isn’t active, (this is a pretty common behavior for addons).

I agree that disabling Elementor isn’t a solution. In order to find the faulty plugin, try to disable plugins one by one (at the exception of Elementor / ACF Pro / ACF Extended).

It is important to find the source of the problem, so you will be able to contact the plugin developer and let him know. Otherwise you may never get a fix/update :\

Hope it helps!

Regards.

Thanks @hwk-fr and you are right. I have just debugged again and it turns out ACF Front end is causing the issue.

@hwk-fr indeed I do I owe you credit for the recaptcha php and js. It was a feature that many requested and I didn’t have time to build it from scratch. You are 100% right that I should have credited you and I apologise for not doing so.

Should I list you as a contributor to ACF Frontend or do you have some other idea.

@julien_e, is this taxonomy issue happening in ACF Frontend forms as well or only as a result of ACF Frontend?

The taxonomy issue — as I see it so far on 4 sites — happens only in admin, not in front end forms within Elementor.
Maybe we should then move this issue to another forum?

• This reply was modified 3 years, 8 months ago by julien_e.

Hello,

Yes please report & discuss the bug on the related plugin’s forum.

Regards.