New capability not working as hoped

#1

I have set up a new capability so that a user of a certain level can create and edit a pod (Pods Frameworks) - I am using the enhanced capability plugin. I have the option to ADD from the toolbar but it is redirecting to the members page. What have I done here?

Just to clarify - if I deactivate S2 the capability and functions work as they should. It seems that S2 is requiring the edit_posts capability which is not what I want since I only want the user to edit the Pod. Is there a way to exclude some of your settings based on post type.

#2

I suggest you use one of the plugins I referred to in my reply to your other post in order to get what you want.

#3

Didn’t need the plugins and there are better ones in my view eg Frontier Post can handle CPT without being a premium member and AccessPress Anonymous Post - although the good functionality also comes with a price tag.

#4

Good! I’m not a fan of Frontier Post myself: it’s as ugly as sin and I can’t stand looking at it!

I don’t care about paying for something worthwhile either: if it works just as I want, it’s almost certainly going to pay me back in spades.

#5

OK, wow, I’m like “this” close to getting where I want to be but also miles away. I can get a user to create pod data using a pod form. I can see the listing, and if I click on the entry in a list of entries I get the specific entry and also an ‘Edit’ button. This is good because if I click on another entry which the user did not create there is no ‘Edit’ button. I am using a custom capability which I have linked in to S2Member which is what I use to control content drip etc. This all works fine.

So it seems the user is tied to the data he created (because there is an edit button). BUT when I click on the Edit button for the specific entry relating to the user the authority disappears and I’m sent back to a generic members’ page…

Any ideas?

#6

What I’d suggest is that you set this up on a test site without s2Member running. That way, you’ll see exactly what is supposed to happen and what other posts and pages are being generated by whatever you’re using to create the pod form.

I suspect that it’s auto-generating some form of edit post or page, and deactivating s2Member should enable you to see what it is. Then you can work out how to make that work with s2Member.

#7

Thanks Tim but it’s a little too complex to run it down to a simplistic site and it won’t help - one is better off, IMHO, working within the structure etc and taking each point in turn. I have troubleshooted this and worked it out. It’s a shame S2 Member won’t support any of us here because some the issues we discuss might be worth them considering for other troubleshooting upgrades etc. The issue was the selected option in Member Profile Modifications. The commentrary says it all “Recommended setting (Yes). Note: When this is set to (Yes), s2Member will take an initiative to further safeguard ALL /wp-admin/ areas of your installation; not just the Default Profile Panel.”

On another note. In exploring front end customisation - as you suggested - I didn’t really find a plugin that did the job. It’s not worth spending the money on a premium plugin with the added options until one knows it will work the way one wants and one doesn’t necessarily have that option with the unpaid versions. Instead, I preferred to look at using a backend solution - let’s face it most of us want to go front end because the backend is scary for contributors and we don’t want them meddling in stuff they shouldn’t. So WP Admin UI Customize is a significant step forward…

Thanks for your input Tim.

#8

Glad you got it sorted out, Nigel! So you’re saying you turned that setting off?

That’s an interesting solution, and complementing it with WP Admin UI Customize. I haven’t tried that.

As you say, if we can keep users on the frontend, that’s generally going to be preferable. I have used Frontend Publishing Pro extensively, and it’s been outstanding for my own needs.