Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author xnau webdesign

    (@xnau)

    Yes, the only difference in your first page will use a [pdb_record] shortcode instead of a [pdb_signup] shortcode.

    Thread Starter bw3em

    (@bw3em)

    Ah OK makes sense!

    However I can’t quite get it to work yet! Can I just check a possible mistake on the page i linked to above? On 2. you have pdb_signup and 3. pdb_record…

    2. On the first page, add a signup shortcode that defines the group of fields to show on that page. Put the name (slug) of the next page in the action attribute:
    [pdb_signup groups=”main” action=”signup-page-2″]
    3. On page “signup-page-2″ put in a record shortcode showing the second page of form controls:
    [pdb_record groups=”address” action=”signup-page-3″]

    I have used pdb_record on all my pages but it only outputs the code. I have changed the ‘Participant Record Page’ to the new page I’m testing. What else could I be missing?

    Plugin Author xnau webdesign

    (@xnau)

    Only outputs the code? You mean you just see the shortcode, and not the form?
    If you are seeing the shortcode, check it closely in text mode for syntax errors. Visual mode can fool you by hiding things.

    The instructions are for a multi page signup form, and they are correct. You are constructing a multi page “record” form because the record already exists. The signup form is only for creating a new record. So, on yours, the first page will have a “pdb_record” shortcode. It also must be accessed with a private link but I’m sure you know that.

    Thread Starter bw3em

    (@bw3em)

    Ah yes it had copied the span color, but I’ve removed that and still it only shows the shortcode [pdb_record?groups=”personal” action=”edit2″] and yes, accessing it via the private link ??

    Plugin Author xnau webdesign

    (@xnau)

    If it shows the shortcode, and the shortcode is in a regular content area, that means there is a syntax error. Check it closely in text mode, something is still interfering with the shortcode getting recognized. Also make sure there is no space after the first bracket.

    Thread Starter bw3em

    (@bw3em)

    Phew, well I’ve no idea what it was but I retyped it by hand and it is now working ??

    The ‘thanks’ page is for registering. I can’t remember where an updated profile should lead to ultimately. How do I specify a ‘congratulations’ or ‘failure’ page as I’m receiving a ‘new registration’ email instead of an ‘updated’ email!

    I’m also getting an ‘updated’ message 10 times – one for each page!

    Also, can the participant be sent an automatic email (just one!) when they’ve updated their profile, as well as admin?

    Plugin Author xnau webdesign

    (@xnau)

    With a multiple-page form, you must use the [pdb_thanks] shortcode on the last page to complete the submission. It is that thanks shortcode that is generating the notification email, so make sure they only hit it at the very end of the series.

    There is a hook that can be used to create a custom function for sending an email to a user when they update their record. The plugin doesn’t normally do this, there is only the option to have an email sent to the admin.

    Thread Starter bw3em

    (@bw3em)

    There’s a ‘save’ button on each of the multiple-pages and each is generating an admin email!

    I have put ‘save and continue’ but would like ‘save’ only on last page?

    Last page [pdb_thanks] also loads the final multiple-page below the ‘Your information has been updated:’ text – can this not be shown again please?

    Can you explain or show me where to read up on ‘a hook that can be used to create a custom function for sending an email to a user when they update their record’ please?

    Sorry to be so much trouble (again!)

    Em x

    Plugin Author xnau webdesign

    (@xnau)

    Hmm something is not right. There will be a save button on each page, but clicking that shouldn’t be generating an email. I would say make sure each page of your multiple page form has only one shortcode. For instance, it’s not possible for the “thanks” shortcode to show a form, so there must be another shortcode on that page doing that.

    By the way, you can customize the button text with the “submit-button” attribute in the shortcode.

    Wait–are you using the latest version of the plugin? It’s gotta be 1.5.4.9 or it won’t work.

    Sending an email to a user when they update their record requires a plugin script that is fired on the “pdb-after_submit_update” hook. You’d need to set up the email and send it out in the script, so it would be fairly involved, unless you just wanted send them a simple notice that wasn’t personalized.

    The callback on that hook is provided with an array of all the field data from the updated record.

    Thread Starter bw3em

    (@bw3em)

    Each page has only one shortcode on it and I have the latest version installed.

    submit-button=”Next” – in the shortcode doesn’t appear to do anything!

    Plugin Author xnau webdesign

    (@xnau)

    oops…should be “submit_button” with underscore….

    You’re probably going to just have to put up with the multiple emails, the admin notification emails are getting send with each form submission. Got this fixed in the next release.

    Thread Starter bw3em

    (@bw3em)

    That’s a relief – any idea when it will be released? You know I’d love to test it for you but can’t risk breaking my site ??

    BTW submit_button="Save and continue" still doesn’t register

Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Creating Multiple-page Forms in Participants Database’ is closed to new replies.