Tell us what you are trying to do? I Have cred content submission forms for users of membership to submit content, the forms show up when logged in as Administrator but cannot get them to show on other member roles
Is there any documentation that you are following? https://toolset.com/documentation/user-guides/access-control-for-cred-forms/
Is there a similar example that we can see? no sorry
What is the link to your site? hidden link
Hi Michael,
Thank you for waiting while I looked into front-end form settings.
On your website, I noticed that "Restrict User Access" plugin is active, which is overriding the user roles and capabilities settings from the Toolset Access plugin.
Can you temporarily disable this plugin and then check the form editing again?
If this is fixed, I'll recommend to keep that plugin disabled and use Toolset Access plugin for creating custom user roles and hiding/showing content based on those user roles.
Following are the useful guides on these topics:
https://toolset.com/documentation/user-guides/managing-wordpress-admin-capabilities-access/#creating-custom-roles
https://toolset.com/documentation/user-guides/limiting-read-access-specific-content/
https://toolset.com/documentation/user-guides/setting-access-control/
If you feel you'll be missing out on any specific feature, without "Restrict User Access" plugin, please let me know and I'll be happy to guide with a solution or a workaround accordingly.
regards,
Waqar
Waqar,
Thank you, and it worked, I would preferably NOT have that "Restrict User Access" plugin either, but ..........
This may be somewhat long description, try to stay awake !
That plugin allowed me to convert the category choice in the front end CRED form from the user and assign it to a particular "role" that role was then only allowed to view all current membership level custom post types with that particular chosen Artist Taxonomy and below BUT NOT ABOVE.
I could not work out how to achieve the same results in Toolset Access, I would prefer to keep and use "TOOLSET ACCESS" as I paid a lot of money for it and it seems a waste if I didn't.
So to give you a run through on the intended Process of the USER.
Guest registers and becomes a "GBY-Member" at this stage they can see ALL pages, ALL Archive Pages, Blogs, Contact Forms etc, BUT NOT the Single Artist custom Posts.
At that level they are also able to submit content via the CRED forms, in doing so they answer the question- "at what level membership do you wish this Artist Entry to be in- Bronze, Silver or Gold" but to see the individual ARTIST SINGLE POSTS they must have the relevant Paid Membership . if they pay for Bronze then only Bronze is Visible NOT Silver or Gold, Pay for Silver and both Silver and Bronze are Visible but NOT Gold, Pay for Gold and they get ALL content all levels.
I really hope that makes sense to you.
Regards
Michael
Is there anyone that is able to help integrate toolset access to allow for the above scenario?
Hi Michael,
Thank you for sharing further details.
You can assign different roles to users, through a CRED form, by using the "cred_save_data" hook:
https://toolset.com/documentation/programmer-reference/cred-api/#cred_save_data
You'll find a good usage example with code in the following reply:
https://toolset.com/forums/topic/change-user-role-with-cred-form/#post-450977
The login that you've shared earlier no longer works, so I'm not entirely sure what solution/plugin you're using to accept payments for the paid memberships.
But based on the plugin that you're using for accepting payments, you can use that plugin's own hook to change user role, when the payment for a certain product is successfully processed.
In that case, you'll not even need the users to fill and submit the cred form. You'll only present them with an option to choose the relevant product and once they've paid for that product, their user role can be updated using the "wp_update_user" function.
( ref: https://codex.wordpress.org/Function_Reference/wp_update_user )
You can consult your payment/membership plugin support and documentation to see which hooks are supported.
I hope this helps and please let me know if you have any further questions around this.
regards,
Waqar
