Getting a Full List of Users Programmatically in Evolution CMS

Once a project needs user reports, migrations, or automated account checks, manually browsing the manager is no longer enough. At that point you need a repeatable way to read user data in PHP.

What the task really means

“Get all users” can refer to manager users, web users, or both. That distinction matters in Evolution CMS because the data lives in different structures and serves different workflows.

Typical direction

Use the database API or the relevant user classes to load the dataset you need, then map it into a normal PHP array for processing. For small admin scripts, a direct query may be enough. For reusable project logic, a wrapper snippet or service layer is cleaner.

What to decide first

• Do you need web users or manager users?
• Do you need profile fields, group membership, or just basic IDs and names?
• Is this a one-off report or recurring application logic?

In real Evo projects the main mistake is not the query itself. It is treating all user types as one interchangeable list. Be explicit about which user population you actually need before you write the retrieval logic.