rcwdm

Thanks, getting there!

What I am hoping to do is add the code to snippets.

And then use a PHP function condition in Oxygen Builder to hide the form or section depending on whether the logged in author has posted or not.

Thank you. Sorted.

I split fields into different forms, so the validation form was not longer present when updating the CPT.

Can we not just add this to snippets and then call on a php function maybe?

I’ve capped the areas I think I should be editing to ensure a customer can only post once to a specific form, can you advise if I am even remotely close?!

$user = wp_get_current_user();

// Check if current user has role 'CUSTOMER'
if(in_array('CUSTOMER', (array) $user->roles)){
    
    // Get posts of the current user (by post_author)
    $check_posts = get_posts(array(
        'post_type'         => 'POSTTYPENAME',
        'post_author'       => get_current_user_id(),
        'posts_per_page'    => -1,
        'fields'            => 'ids'
    ));

    // Display form if the current has less than 1 posts
    if(count($check_posts) < 2){
        
        // Call my form
        acfe_form('MY-FORM-SLUG');
        
    }else{
        
        ?>
        <h3>You already published a post.</h3>
        <?php
        
    }

}

Does it have to be on the specific page where the form resides?

Probably going to be best to look at my setup.

Best way to get in touch?

Really not sure how to resolve this, have you got any ideas please? Perhaps your forced to install the plugin before you begin working on the site…

Oxygen builder has some quirks when it comes to FA.

I solved it by reviewing these articles.

https://sridharkatakam.com/load-font-awesome-5-wordpress/

https://oxygen4fun.supadezign.com/resources/what-you-need-to-know-about-font-awesome-in-oxygen/

• This reply was modified 3 years, 4 months ago by rcwdm.

All I am doing is creating a site in Oxygen Builder as normal and then activating your plugin.

When I do this the Oxygen Templates become uneditable from the backend. Instead of the normal UI editor, you just see a page full of code.

Got it.

Hi thanks for coming back to me.

What about not showing if you’re not logged in as admin?

I can’t see the icons on the frontend unless I am logged in as admin. All other elements of the page are showing, for some reason the icons are not..?

Hi, I’ve got this to work…but…

So it validates the slug before allowing the user to submit the post.

The problem occurs when they come to update the form on the frontend — as the validation checks once again and won’t allow the update to happen as it’s treating it as a new post.

Is there a way to remove the ACF field from the ‘update post form’ that was completed and validated already in the ‘create post form’? But still allow the user to update other fields?

Thanks for this. Again, I just don’t understand what I am looking at.

Not sure why I struggle to grasp this stuff but, I wouldn’t know what to do with that information.

I’ve asked ACF directly too and they aren’t too sure what will work with the ACF extended plugin itself.

If you were to validate a field to make sure it is a unique slug, display a custom error message if the slug already exists, or publish the post with the validated unique slug. How would you construct that code to do this?

Thank you very much! ??

I’ve looked at this a few times and I just don’t understand what to do with that information. It could be in Japanese.

Could you please just explain to me in plain English what I need to do?

Thanks for that, its good to know we can do it.

I’ll be honest when I say, I have no idea how to do anything with that information.

All I want to do it redirect to a URL and I cannot understand how to even begin doing that with the text in that document.