Hi,
I hope you had a relaxing weekend.
While the topic has already been resolved, I wanted to add a few notes that may be helpful.
If you’d like users or vendors to purchase a membership plan before performing any actions, and you have multiple plans with different restrictions (such as listing limits, message limits, featuring limits, etc.), you can create a dedicated Plans page by adding the Membership Plans block to a new page and then include this page in your header or footer menu: How to add plans page | Loom. This page will display all available plans.
When a vendor clicks the Post a Job button, they will only see plans that include a listing submission limit. This is intentional, as it keeps the flow clean and prevents users from seeing plans that are not relevant to the action they’re trying to perform.
Regarding the Post a Job button label, as Chris mentioned, the button serves multiple purposes. Depending on the user’s status, it may redirect them to complete their vendor profile, prompt them to purchase a membership plan, or take them directly to the listing submission form. You can also configure category-specific plans, allowing vendors to post for free in some categories while requiring a paid plan in others. Because of these different scenarios, the button uses a generic label by default.
If you’d prefer a different label, you can change it using the Loco Translate plugin. Alternatively, if you’re comfortable with coding (or using AI tools), you could implement a code snippet that changes the button label dynamically based on the user’s role or whether the vendor already has an active membership plan.
Finally, if you decide to add additional membership plans in the future (not only for listing submissions), please make sure to test them using a regular user or vendor account. Administrator accounts bypass all membership restrictions by design.
I hope this helps clarify how the membership flow works.