Blog Sections Open
Troubleshooting getUserDocGroups in Evolution CMS
If a documented API example does not work in your build, check the runtime context and the exact user/document scope before assuming the function is broken globally.
API helpers such as getUserDocGroups often look trivial in documentation, yet still fail in real projects because they depend on context, session state, or the exact permission model of the current request.
What to verify
- who the current user is in this request
- whether the function is being called in manager or web context
- which document group scope the helper expects
- whether the build you use matches the documented behavior
Recommendation
When an API helper does not behave as expected, test it in the smallest reproducible context first. Many “broken API” reports turn out to be context mismatches.
Designing a Federated Search Across Multiple Agency Sites
A “global” search across several travel sites is not just one snippet call — it is a federated search problem that needs a source strategy, normalization, and ranking rules.
Fixing Resource Creation Permissions in a Restricted Manager Role
If a manager can edit existing resources but cannot create children inside a container, the issue is usually the resource policy type, not the role rank alone.