My question is about allowing the subscriber user to edit their listing on the frontend.
I have custom post types called “listing” which subscribers can create for their listing.
In this example, Ada Windows created a listing and a blog. The blog is okay in the frontend as the subscriber can edit the blog as in this image: image 1
Originally, the admin created the listing, but then associated the subscriber to the listing. However, the listing is not visible to the subscriber as in this image: image 2
I am using Members – Membership & User Role Editor Plugin but I cannot figure out if I have to set certain capabilities like here: image 3 or if I have to make changes to the frontend panel like here?: image 4
Hi,
I tried doing that now, with the same user role plugin. I added capabilities to the subscriber but still as an admin I can’t transfer the post to a subscriber.
The easier way would be to temporarily make that subscriber an author, then transfer the post. Then downgrade the user to a subscriber. I tested this now and it worked, the post remained associated with the subscriber.
But if you already managed to transfer the post, and the subscriber is the author now, then it should have appeared in the posts list. Not sure what to suggest unfortunately.
Is this something that you plan to do regularly? Or what’s the purpose of doing it like that? Normally the subscribers submit the content directly.
Thank you!
Hi Simon. Yes this will be a regular thing. When a new user subscribes on a paid plan, they will be able to create their own listing or ask their existing business on the directory to be transferred to them.
By the way, I tried changing to author and back to subscriber, it did not work unfortunately.
But currently, the reason is that these particular new users who purchased a plan, created a new listing but couldn’t do anything (users Ada Windows and Whitefield Windows) . Although the listing was ALREADY associated to the user in the listings page like in this image, the listing is not visible in the frontend account page and they could not access it because they were a “subscriber” user. So I am looking for ways to give access to the subscriber to edit their own listing.
To clarify, the problem is not associating the subscriber user to the listing. They are already associated. The problem is the subscriber users cannot see or access their own listings on their frontend account after creating the listing.
This is why it will be regular, as my members increases they will all have the same problem. So we need to figure out a simple way to give them access to their own listing, without admins inference in changing to “author” and then back to “subscriber”.
Let me know please
Something must be wrong. Because all the theme features that we added for directories and listings are based on user submitted content, meaning subscribers submit content that they can publish and edit at any time. I don’t recall seeing such an issue before, in normal circumstances.
I tried it again with the plugin.
After adding the capabilities for subscribers using the Members plugin, I used the quickedit option to assign a listing (post type is called Menu, and created with the ACF plugin -> https://prnt.sc/4IyHbHOwkgq3) for a subscriber -> https://prnt.sc/IMIH2FOrvK9H -> https://prnt.sc/La9n5oqJgt2H I figured it out eventually that it’s the correct way to do it from there, or using the classic editor.
Then I logged in and checked with that subscriber account and the listing was visible in the posts list -> https://prnt.sc/vlTKFH873U9-
Seems to work correctly. And I think you are doing it in the same way. Also the post type is set correctly here -> https://www.pasteboard.co/7yWn9yqMuE6F.png So the respective subscriber should see the transferred post. I tested it in the same way two times, worked both times.
Not sure where the problem could be. If it worked for me it should work for you. If you want I can take a look at it on the website, I’ll need admin login, you can send an email at contact@tagdiv.com with the details. Maybe I can figure out what the problem is.
Thank you!
