Ryan Mitchell

Hi @mattpramschufer,

The current author selector is designed to pick the author for a post, and it’s Ajax-based, meaning it only queries the database when a user starts typing to search for an author. This ensures the process is efficient and doesn’t load unnecessary data upfront.

We’re curious to understand why having two separate selectors would be beneficial in your case. If the goal is to streamline the selection process, you can already disable user roles (e.g., subscribers, customers, etc.) that won’t be used as authors. This would limit the search results to only relevant users, making the process more efficient.

Could you provide more details about the specific challenges your client is facing with the current setup? Understanding their workflow better would help us determine if there’s a workaround or if this is something we can consider as a future feature request.

Wow, thank you for your fantastic feedback! It’s incredibly rewarding to know that Molongui has become a go-to solution in your projects. We work hard to ensure a seamless experience, and knowing you find it both reliable and easy to use truly means a lot. We also appreciate your trust in recommending it to your clients! If there’s ever anything we can do to enhance your experience, don’t hesitate to reach out.