vy name

@hwk-fr , BTW, considering this point and more and more of us are creating increasingly large forms with multiple ACF fields, would you kindly consider bringing in this feature of Multi-page (multi-Tab or multi-stage) module for your Forms module UI? Perhaps in the next few releases, if possible? While the code you highlighted above is easy for developers, it is a challenge for non-developers (just designers) like some of us.

Thanks in advance.

• This reply was modified 10 months, 1 week ago by vy name.

@hwk-fr Many many thanks for such a quick response to this! Wow!

You saved me several hours of trial-and-error. I agree, many of these AI solutions have been hit-and-miss for me too – BTW, I did not know that these AI LLMs invent code along the way. Damn, that is very untrustworthy, to say the least. Thank you for the warning.

@sstaples99 sorry if my reply to your query put you to unwanted work. Thanks to @hwk-fr reply above, we are both saved from an avoidable adventure.

I too was looking at this today and found the following answer from the help of Brave AI. I will be trying this out today/this week. Perhaps it would help you?

To create a multi-stage form using the Advanced Custom Fields (ACF) plugin, you can follow these steps:

First, you need to create a field group that will contain the form’s fields. You can do this by going to the ACF > Custom Fields menu in your WordPress dashboard and clicking on the “Add New” button.

Next, create a new form from the ACF > Forms menu and assign the field group to the form. Once saved, the form will now map the fields from the field group. This means those fields will be usable directly from the UI.

To create a multi-stage form, you can use the Dynamic Forms module in ACF Extended. This module allows you to create a form with multiple stages, each with its own set of fields. You can configure the form to navigate between stages based on user input.

Here’s an example of how you can use the Dynamic Forms module to create a multi-stage form:

// Create a new form
acf_form(array(
    'post_id' => 'your_post_id',
    'form_name' => 'My Multi-Stage Form',
    'fields' => array(
        array(
            'key' => 'field_1234567890',
            'label' => 'Stage 1',
            'type' => 'text',
            'required' => 1
        ),
        array(
            'key' => 'field_9876543210',
            'label' => 'Stage 2',
            'type' => 'text',
            'required' => 1
        )
    ),
    'dynamic_form' => array(
        'stages' => array(
            'stage_1' => array(
                'fields' => array('field_1234567890'),
                'next_stage' => 'stage_2'
            ),
            'stage_2' => array(
                'fields' => array('field_9876543210'),
                'next_stage' => 'done'
            )
        )
    )
));

// Add a hook to handle form submission
add_action('acf_form_submitted', 'my_form_submitted');
function my_form_submitted($form) {
    // Get the current stage
    $current_stage = get_current_form_stage($form['post_id']);

    // Check if the form is completed
    if ($current_stage == 'done') {
        // Do something when the form is completed
    } else {
        // Navigate to the next stage
        wp_redirect(get_permalink($current_stage));
    }
}

In this example, we’re creating a form with two stages: stage 1 and stage 2. Each stage has its own set of fields. The form will navigate to the next stage based on user input. When the form is completed, it will trigger the my_form_submitted hook and do something when the form is completed.

Note that you need to have the ACF Extended plugin installed and activated to use the Dynamic Forms module.

Thank you for your response.

I have gone through your website in detail and I find that only in your Pro version you offer a customizable 2FA code page (for user to enter 2FA code after username/password). Thus, I withdraw my question and will close this as resolved.

Steps to reproduce what I am describing.

• WP login page = custom page or standard wp-login.php. Enter username/password. (We are able to customize a page for this login action)
• If 2FA enabled, browser redirects to wp-login.page, but this time will show a form to enter 2FA code. (This is the page we are NOT able to customize as this is system-generated or your plugin-generated and is not available for our builder to customize). I understand this “page” is customizable only in your Pro version from your website.

Hi @sebastianklaus

Hope to hear from you on this please.

Thanks.

Greetings

Just checking with you if you had any update?

Can you check your database if there are some of theses custom entries in the _posts or _postmeta?

My apologies… I forgot to respond to this query from you – Yes, indeed there were entries in wp_post & wp_post_meta tables for the CPT post submitted, but these were NOT found in the CPT table itself.

Hoping to receive an update from you. Your plugin will make a big difference to our project.

Thank you in advance.

With regards

Vy

Hi,

Just checking if you had a chance to evaluate/recreate the problem reported here. I request you to kindly suggest a fix/solution to this.

Your plugin has a lot of promise and can be a game-changer for large content sites with many CPTs (as in the case of the project we are at the start of) and especially when they are non-profit (as in my case). Front-end posting is the only non-working part in your wonderful plugin (at this time).

Grateful for an early response.

Vy

Just to add, I am using ver 1.2.4 of your plugin. Win 11, Local by Flywheel, PHP 8.19, MariaDB 10.4.10

I am happy (and I suppose the Author would also be) that I upgraded to 1.2.3 just now, and the upgrade went butter smooth! No issues whatsoever and all data is intact as it was before the upgrade. Very nice and thanks @sebastianklaus . I have become a believer!

Best wishes to continued success with your plugin!

Many many thanks, Herr @sebastianklaus !

Thank you!

I did upgrade to 1.2.1. Here are my observations and experiences:

1. On plugin upgrade, all “migrated” db tables did not show up in the CPT Tables menu link.
2. All CPTs created had their “migrated states” reverted AND their content reset to zero.
3. Within each CPT menu item, all example “posts” did not show up.
4. When I migrated these tables “again”, this was successful – AND, the previous posts started showing up in the custom tables.
5. Being a non-techie, and a WP newbie, the only data that I could catch as being different is the slug for your plugin’s SETTING – earlier it was showing as /wp-admin/options-general.php?page=wp-cpt-tables but in 1.2.1 it is showing as /wp-admin/options-general.php?page=cpt-tables. Could this change in slug have caused this anomaly in behaviour observed in points 1-3 above?
6. No other errors or warning were displayed on the screen.

Here is the screenshot that I got in the interim step (4) describe above.

View post on imgur.com

After migration

View post on imgur.com

Best regards.

I just tried to go back to prev versions of your plugin. 1.7 worked out and am continuing testing using that version.

Thank you @natekinkead
Very kind of you.

Appreciate any inputs here. Thanks.

Yes, just did. Thanks in advance.