Creating one-off post/page/pod

#1

Like most websites I don’t want people creating posts and stuff without proper credentials. However, I do have one instance when I want them to do this - a special page which contains form fields - so as not to put people off with having to register etc etc. I have password protected this page with WP so anyway if you don’t have the password you can’t access it. Is there a way I can give a non-logged in user the capability to create the content in this one page only?

I realise that I can give special viewing rights to non-logged in users but that’s not what I am talking about. I could give everyone the capability of creating any content but don’t want to do that - just fill in the form on one page. Nor do I want to create a special user because that would require registration. Anyway, hope this is clear.

#2

This isn’t really something that s2Member can provide because, by definition, s2Member is about regulating content for members.

I suggest you take a look at plugins designed specifically to enable users to create posts, such as User Submitted Posts and Frontend Publishing.

#3

I have been an S2member pro user for several years. I use it to regulate content. However, in this instance I need a user to create content - not a post or page but a Pod. Are you saying your plugin can’t be modified to break up the edit_post permissions so I could do this?

#4

It’s not my plugin. I’m just a user like you.

You can always make a custom modification, of course, but I’d have thought you’d be better off in this instance either talking to the Pods developers or looking at a dedicated forms plugin.

#5

Thanks. The problem is that in order for a logged in user to create a specific page/post - not a usual page/post (I don’t want that) there has to be a way to separate the permissions. For example, I have given a user a custom capability to create a pod through a pod form but the pod form is contained in the page through shortcodes so unless the user also has page rights he can’t access it.

#6

In that case, there’s no need to have the page protected by s2Member.

If, for some reason, you need to have both members and non-members apparently access this page, then I’d suggest setting up a redirect for those not logged in, which will take them to where they can compete your form.

#7

Well, it’s slightly more complicated than that given I didn’t want to give anyone page_edit access. However, I think I compounded my problem by giving the page a level access and a custom capability. It sufficed to have a ccap_ only.