Andrew Tibbetts

Yep.
The table row repeater is working.

One more: Field Type Matching in Admin.
I’m using the post functionality strictly for admin / backend reference.
So, I don’t need to use the raw data on the front-end.
It would be great if in the admin:
– checkbox submissions displayed as checkboxes
– repeated table row fields repeated as individual entries
– files uploaded would prepopulate a file input
etc.
Or am I missing something about the way this can work?

Aaaah.
So the receiving post field should be a text field not a file field.
Thanks!

https://swellgallery.com/call-for-artists/

My form has the ability for the user to add an infinite number of a certain field.
They click “Add a link” and a URL field is inserted into the form, and they can do this multiple times so that I can collect more than one link but not restrict them to a certain number of links.
So, PmCF7 can’t “see” these fields for mapping because they don’t exist until the user creates them.

So…

Request: Support for repeaters.
User can create multiples of a field (creating an array field) on the form and they get mapped to a repeater.

Request Alternate: Support for ‘non-existent’ fields.
Let me say what the form field(s) will be instead of them having to exist already and be chosen from the dropdown.

Love the plugin.
Really excited to possibly ditch CFDB.

Version 4.8.1 has brought back an init function with wpcf7.initForm.

Version 4.8.1 has brought back an init function with wpcf7.initForm.

Version 4.8.1 has brought back an init function with wpcf7.initForm.

Quick workaround for now: simply reload the JS file onto the page after the form is created.

jquery:
$('<script type="text/javascript" src="' + your_custom_base_url + '/your_path_to_wp/wp-content/plugins/contact-form-7/includes/js/scripts.js"></script>').appendTo('head');

plain js:

var head = document.getElementsByTagName('head')[0];
var script = document.createElement('script');
script.type = 'text/javascript';
script.src = your_custom_base_url + '/your_path_to_wp/wp-content/plugins/contact-form-7/includes/js/scripts.js';
head.appendChild(script);

• This reply was modified 7 years, 9 months ago by Andrew Tibbetts. Reason: added plain js solution
• This reply was modified 7 years, 9 months ago by Andrew Tibbetts.
• This reply was modified 7 years, 9 months ago by Andrew Tibbetts.

Quick workaround for now: simply reload the JS file onto the page after the form is created.

jquery:
$('<script type="text/javascript" src="' + your_custom_base_url + '/your_path_to_wp/wp-content/plugins/contact-form-7/includes/js/scripts.js"></script>').appendTo('head');

plain js:

var head = document.getElementsByTagName('head')[0];
var script = document.createElement('script');
script.type = 'text/javascript';
script.src = your_custom_base_url + '/your_path_to_wp/wp-content/plugins/contact-form-7/includes/js/scripts.js';
head.appendChild(script);

• This reply was modified 7 years, 9 months ago by Andrew Tibbetts. Reason: added plain js solution
• This reply was modified 7 years, 9 months ago by Andrew Tibbetts.

+1 For those maintaining a state vs loading a page, being able to initialize / connect a script to a dom element on the fly is crucial.

In case this never goes anywhere, here is my js-/jquery-based hack:

$('.d4p-bbp-attachment').html(function(index,html){

	html = html.replace('[', '<ul><li>');
	html = html.replace('|', '</li><li>');
	html = html.replace(']', '</li></ul>');

	return html;
});

I have found the reason.
To make ACF’s acf_form() work, acf_form_head() needs to be called.
I was calling it without any checks for environment at the top of my buddypress.php master template file.
I have now reduced it’s call only to where I have acf forms and things seem to be working again.
Sorry for the run-around, and much thanks for the quick replies and assistance.

Thanks Brajesh.
I’ve been trying to track this down for days with nothing to show for it.
This wp.media object is quite mysterious.
Your superior hustle is ever appreciated.

Try [wpuf_sub_info] via https://docs.wedevs.com/docs/wp-user-frontend-pro/getting-started/subscription-payment/