[Resolved] Split: Combining user form and post form as one
This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.
Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.
No supporters are available to work today on Toolset forum. Feel free to create tickets and we will handle it as soon as we are online. Thank you for your understanding.
What i would also like, is to combine the registration form, with the create post of the artists bio. including photo etc. And of course, they should only be able to create ONLY ONE artists profile post. I GUESS THAT MUST BE CLEAR?
- A user registers with your site.
- A WordPress profile (account) is created for him or her.
- The user logs in.
- User can use a front-end form to create Contractor profile now.
- The user waits for the site administrator to approve the contractor post. The Contractor post becomes public. It is available on the list of all Contractors so that other visitors can search for it.
- The contractor can use a front-end form to submit work/portfolio. The showcase entries become available to the public on the contractor’s individual page and on the list of all showcase entries.
You can make this even more streamlined by using a single page and view to create and edit a bio.
1. The page 'Bio Aanmaken', already shows the form to create a bio ('Bio aanmaken formulier'), when a bio post from the current user doesn't exist.
2. In the loop of the view 'Kunstenaarbio aanmaken' on this same page, I've added a form block for 'Edit kunstenaars bio post'.
Now this same page will show the form to add a new bio when it doesn't already exist. If it does exist, it will show the form to edit it, instead.
You can rename this page to something generic like 'Bio Management' and then you'll no longer need the other page 'Bio Bewerken'. Only one link to this updated page will be needed on the 'Mijn Kunstenaars Account' page.
peterV-17 confirmed that the issue was resolved on 2024-03-21 10:50:26.
This ticket is now closed. If you're a WPML client and need related help, please open a new support ticket.