I just looked at FluentCRM....and well....do please follow WP standards.
When I look at a plugin I look for how close to the standard/default method it uses. Which means comparing a plugin to for instance Akismet.

• Installed plugins list.
  Look at how Akismet has when activated Settings l Deactivate. Those are important. After installing a plugin one should have a hint to where to go. Settings is a default method used for many years to help direct a user to the correct plugin location.
  Top level items: Some plugins should not have top level items but should instead be inside the top level WP menu. Even though a plugin has a top level menu link it still should follow the WP standards for UI as close as possible meaning adding a Settings link.

  Description below installed plugin details. Is not to be packed with links. This is not the right place to add links. Look again at Akismet. Less is more in this space.

• Menu and submenu
  How to structure a plugin submenu items. Look at how clean the WP submenu is in general. I would say max 5-6 items. These same top level items can also be added into a menu containing submenu items inside each of the pages.

• Be professional.
  Howdy, username seen in the top right on any WordPress backend. Is not professional, so do not follow that example. Look at how to stay as professional as possible. The WordPress web site needs to fit with many kinds of people. Keeping this professional means most often keeping things without humor or any other extra thing not needed. I would basically go through each plugin and look at how it adds extra things to create a sense of humor etc and then remove it.
  There are likely other things as well, but this is what I can think of right now.

For many WPManageNinja products, the licensing model is structured by the number of domains. A single‑site license works well for in‑house teams, while multi‑domain licenses are clearly designed with developers in mind. In fact, this creates a natural tiering such as a free version, a Pro version for single‑site use, and a Developer version for multiple sites.

Shahjahan Jewel with that in consideration, I would like to suggest introducing a full white‑labeling feature specifically for developer‑focused licenses. This would allow developers to freely use their own branding across both the backend and frontend, and if feasible, even within the view‑source output.

Providing this level of white‑label flexibility would significantly strengthen developer loyalty and make WPManageNinja products an even more appealing choice for agencies and professionals ✌️😎

How many of you discovered that you're now Legacy customers with a large billboard on your WordPress menu now?

My old purchases no longer show up on the new portal. Submitting a ticket doesn't provide a number or email confirmation, and it's not there when I check the support area of the new portal.

Man, what a way to botch a new buyout.

Im considering buying some type of teble management system for creating my own medical records, apps and stuff like that. I see that fluent has the posibility with ninja tables, I was also considering baserow which looks pretty awesome. Since I own basically all the wpmanage ecosystem, the ninja tables makes sense but dont know if its the same or less capable than baserow. Has anyone tested both or has some type of comparisson? Also, ninja tables should be on the left menu also, I dont see it on the product discussions list.

Just curious if there are any updates on this much expected new product from the Awesome WPMN Team? 😀

Hi

We love Fluent comments : ajax, spam protection, easy to setup

https://wordpress.org/plugins/fluent-comments/

Any idea when it can be compatible with FSE (block themes) ? Shahjahan Jewel

thank you 👍🙂

Trying to stay in the fluent ecosytem, and need a subscription membership control to all site content... both WP Posts/Pages & Fluent Community, Support & CRM. One aspect it also needs to be AffiliateWP aware (Fluent Affiliate doesn't support 2 tier)

The site will need public areas, along with m'ship levels.

How is everyone achieving this? What suggestions do you have.... it's doing my head in trying to find a simple solution!

fluent auth actually has a big bug: if u change the default wordpress email to give access to users, no email is sent.

ticket #143808

6 months, no news.

Hello!

I would like to suggest a feature request for FluentAuth: the option to allow login only with email, instead of allowing both username and email.

Why this would help:

• It reduces a large number of low quality login attempts that target common usernames such as admin, test, info, or the site owner's name
• It makes brute force and credential stuffing attacks slightly harder, because the attacker must know the exact email address
• It matches how many users already expect to log in today, especially on business and membership sites
• It gives site owners more control over the login surface without needing custom code or extra security plugins

Suggested implementation:

• Add a setting in FluentAuth to choose:
  1. Username or email
  2. Email only
  3. Username only
• Ideally this could apply both to the default WordPress login and FluentAuth custom login forms

This would be a small feature, but it could have a real security and UX benefit for many sites.

It's something typical from fail2ban plugins, but I think it will be a good addition to auth!

Thanks
cc: Shahjahan Jewel 

I clicked the "Upgrade to Pro" button in the FluentPlayer WordPress backend admin dashboard under the settings tab and it took me to a 404 error page. I need to upgrade to the Pro version so that I can embed playlists from my YouTube channel into my site.