WPUF Form and Custom Fields in Post Edit

Ok…if someone needs a solution, here ya’ go:

🙂

There might be a simpler way direct in WPUF Pro though…

You could turn off every single meta box from the screen options.

And this would reflect is the options for every non-admin users?

Then I must be a little silly. 😉

*in*

In other words, they wouldn’t be visible for them?

That would be based on every user. So may be it won’t be good for you. So you are better with that solution if that works for you.

Thanks, Tareq.

I ended up using Adminimize. I needed to add the wpuf form tag. ( #wpuf-select-form )

I would like to lift this question again.
I have a WordPress Multisite, with a custom theme where I also add custom post types with their own custom meta boxes (added via the meta-box plugin).
However, a bug I noticed was that content added via the front-end ran into some problems when edited via the backend. I had The ‘WPUF Custom Fields’ turned off in the screen options, but the problem seem to lie in the duplication of my custom fields ID attributes. They are added twice – once by my functions.php and then again by the WPUF Custom fields.

On content created via backend, I of course do not have these issues.

Is there anywhere in the plugin where I can turn off the creation of the backend meta-box ‘WPUF Custom Fields’? And can’t this be an option in the WPUF settings in the next version? I think this could be valuable for us who have other plugins or who code our custom post types and meta boxes by hand.

I run WPUF Pro 2.1.10

Greatful for any reply, and keep up the good work with this very solid plugin.

OK, after a bit of experimentation, I found the function add_meta_boxes() in /admin/posting.php. (row 51-57)

  function add_meta_boxes() {
 /*       $post_types = get_post_types( array('public' => true) );

        foreach ($post_types as $post_type) {
            add_meta_box( 'wpuf-custom-fields', __( 'WPUF Custom Fields', 'wpuf' ), array($this, 'render_form'), $post_type, 'normal', 'high' );
        }*/
    }

Commenting out the contents of this function helped remove the generated metabox WPUF Custom Fields from backend, and the conflict was resolved.

Still, would be nice to have this as an option in the settings though.