14oangus

Merry Christmas, Konrad!

I will for sure submit a 5 star review once the service reopens after the holiday break.

Thanks again for the on-point support.

Angus

Hi Konrad,

Thanks for getting to me and for the continuous work on the plugin.

I’d found that part of the docs before you mentioned it but it’s still not clear to me where the sample code should go and what it replaces.

if(has_flexible('flexible_content_field_name')):
    
    the_flexible('flexible_content_field_name');
    
endif;

I tried to change the code for each layout use its own template file for rendering but couldn’t figure how to integrate the above sample code. Since my current flexible content field has lots of layouts under it, I thought I’d reach out again to clear this up before I make a bunch of changes that don’t work.

Using the same example:
flexible_content_field
layout_1
layout2

Now I don’t need the old flexible-content.php file, right?
So I assume I should start each layout template file with the above sample code. For example:

layout-1.php

if(has_flexible('flexible_content_field')):
    
    the_flexible('flexible_content_field');

    // should I get the layout's fields as before from here?
    if (get_row_layout() == 'layout_1') : ?>
        <div>
            Layout 1 HTML here
        </div>
    <?php endif;

endif;

I think I just need to know what each layout template file should look like.
Feel free to let me know if you need more information about my setup.

Thanks again,
Angus

Hi Peter,

Thanks for taking the time.

I had indeed enabled the debug option and this was what was shown (a backtrace)

#Debug backtrace for the developer:
# apply_filters(‘wp_redirect’)
wp_redirect
wp_safe_redirect
wordfence::lostPasswordPost
do_action(‘lostpassword_post’)
LRM_AJAX::lostpassword
do_action(‘wp_ajax_nopriv_lrm_lostpassword’)
LRM_Core->process_ajax
do_action(‘wp_loaded’)

Don’t let WordPress reveal valid users in login errors turned out to be the key. When it’s on, WF is trying to redirect to the checkemail page even when the entered username/email doesn’t exist which is great. But it looks like the plugin only modifies the redirect (or maybe I should say, removes the redirect and makes an ajax request instead) with an existing username/email.

PS: I actually just found out when entering an existing username/email, it works perfectly without the issue.

Anyways, I’ll contact the form plugin developer and see if they can address this.
Also, I’m marking this post as resolved. Thanks so much for the clue!

Best,
Angus