follaky

Thanks, I opened a ticket.

Hi!

Sorry for delayed reply.

The problem was caused from a conflict with my page builder (Nicepage in my specific case). I had to modify the code like this and hope it isn’t unsafe to do it that way:

add_action( 'wp_footer', 'wpmudev_radio_field_auto_selection', 9999 );
function wpmudev_radio_field_auto_selection() {
    global $post;
    if ( is_a( $post, 'WP_Post' ) && !has_shortcode( $post->post_content, 'forminator_form' ) ) {
        return;
    }
    ?>
    <script type="text/javascript">
    (function($) {
        $.noConflict();
        $(document).ready(function() {
            setTimeout(function() {
                $('.forminator-custom-form').trigger('after.load.forminator');
            }, 1000);

            $(document).on('after.load.forminator', function(event, form_id) {
                if ( event.target.id == 'forminator-module-XXX' ) {
                    let _title = $('input[name="postdata-1-post-title"]');
                    _title.prop("readonly", true);

                    let _text = $('input[name="text-1"]');

                    $(_text).on("input", function() {
                        _title.val( $(this).val() );
                    });
                }
            });
        });
    })(jQuery);
    </script>
    <?php
}

Maybe this can help other people facing a similar issue.

Cheers

Olivier

Same issue here!

Hi @wpmudevsupport12

Thanks for the code! What’s shown in your example is exactly what I’d need. I tried to add a snippet with the code provided (changing the ID to match my form), but it doesn’t seem to work:

Forminator Post Title from Text Field

As you can see, the text from {text-1} isn’t copied over to the post title. However, the new post is created as expected, I’m getting mail notifications and so on.

Am I missing an important point?

Thanks again!

Olivier

I’m having exactly the same issue on my site, line per line.

Did you find a solution?

Marked as solved.

Hello Alex,

Sorry for late reply.

I tried with HTTPS enabled on both sides and it worked!

Thanks for helping!

Cheers
Olivier

Hello Alex,

Thanks for your reply!

I changed the line as instructed but am still getting the same error message.

Does the fact that my installation is using https and the localhost WordPress not have an influence?

UPDATE: tried with a production WordPress that will get reinstalled and had the same problem. Forgot to specify that the standalone install is v. 1.4.2.