mukasama

I’m not sure if this helps. Still in incognito mode I get the following error when paging through pdb_record multi-page form:

Catchable fatal error: Argument 2 passed to Participants_Db::replace_tags() must be of the type array, boolean given, called in /–full-path-redacted–/wp-content/plugins/participants-database/participants-database.php on line 2942 and defined in /–full-path-redacted–/doyoncandidate/wp-content/plugins/participants-database/participants-database.php on line 2953

A thought: Some of these issues (especially the first?) may be explained by the same “lots-of-testing-on-the-same-computer” as your suggested in the related thread on weirdness. I tried testing in incognito mode, but was using the same IP at the time. However, it cannot explain the 3rd issue (showing one participant another participant’s info after submitting the form) which one of our user testers reported. She was only asked to submit one test application. Let me know if you have seen this before or have ideas on how to troubleshoot it.

Here are some PHP error log entries (I’ve redacted table prefix and email address before posting:

Participants Database Plugin: IP blocked for too many retrieval attempts from IP 216.115.113.24 in 24-hour period
—
WordPress database error You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ” at line 1 for query UPDATE participants_database SET date_updated = NOW(), first_name = ‘Jane’, middle_initial = ”, last_name = ‘Test’, suffix = ”, address = ‘456 Hwy Way’, city = ‘Fairbanks’, state = ‘AK’, zip = ‘99701’, length_of_time_at_residence_address = ‘3 months’, phone = ‘907-123-4567’, primary_phone_type = ‘Other’, alternate_phone = ”, alt_phone_type = ”, fax = ”, email = ‘redacted’, hometown = ”, photo_need = ‘I need my photo taken’ WHERE id = made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, Participants_Db::init, Participants_Db::process_page_request, Participants_Db::process_form

Thanks very much for taking a look. In this instance it worked because I finally decided at about 3 am rolled back the website to my last good backup from yesterday afternoon. Still not sure what I did to break it. If it happens again, I will try deleting the cookies.

I have a couple other questions on the multi-page form. If these are already covered somewhere I’m happy to dig through the documentation some more:

1) When a participant comes back to his/her record using their private link, is there a way to let them see their name as in “Welcome back, [first_name] [last_name]” so they feel confident they are in the right place?

2) It looks like the Browser “back” button works to see what is already entered. Is it possible to a) put a back link on the form pages, or b) put a “review screen” that includes all fields already completed before the final thank you screen? (Confession: we’ve mimicked this functionality by accident by calling on a field groups that doesn’t exist on the page that includes the action=”thank-you”)

2) On your example page (http://xnau.com/creating-multiple-page-forms-in-participants-database/) you show to make the shortcode on the first page: [pdb_signup groups=”main” action=”signup-page-2″ submit_button=”Next”].

3) We just have [pdb_signup] on our first screen, and it works well since this is a VERY long form (20 field groups) that no one would do in one setting. This gives them an early chance to stop and come back later, without waiting till the very end to get their private link. Is there a problem with not including a ‘groups’ and ‘action’ in the signup shortcode?

Thanks, we will definitely be making a donation for your great plugin and support.