Could XML-RPC Turn Evolution CMS into a Remote Publishing Backend?
This donor captured an interesting ecosystem idea: using XML-RPC to edit and publish Evolution content from external tools such as Sublime Text or mobile clients.
Release notes, extras updates, guides, videos, and practical Evolution CMS knowledge in one place.
This donor captured an interesting ecosystem idea: using XML-RPC to edit and publish Evolution content from external tools such as Sublime Text or mobile clients.
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.
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.
A zero query count in parser stats does not always mean truly zero database-related overhead; some measured timings can still include framework or connection-layer work.
If AjaxSearch falls back to the whole site when a category has no direct keyword hits, the category constraint needs to stay part of the query even in the empty-result path.
If an AJAX-heavy catalog starts turning into a maintenance nightmare, moving the front-end state into an SPA and treating Evolution as the data provider can be the cleaner architecture.
Watermarks are easy when the position presets match your design, but centered overlays require understanding how the gallery tool interprets placement codes.
A blog listing becomes easier to scan once each post has a dedicated preview image strategy instead of relying only on text.
If a region switch is driven by URL parameters, the best event is the one that sees the request early enough to store the choice before page-specific logic depends on it.
Turning a form submission into a new resource becomes much easier when the field-to-document mapping is declared in one readable array.
A test server is useful only if deployment back to production is deliberate, repeatable, and does not overwrite live data blindly every night.
If antispam seems to “do nothing”, verify what fields it actually injects and whether your template or theme is hiding them.
An “unknown column alias_visible” error during migration usually means the database schema and the codebase are no longer from the same Evolution generation.
If a menu counter should ignore hidden resources, include the hidemenu condition in the document query instead of counting every child indiscriminately.
If the site renders correctly but phpMyAdmin shows mojibake, do not migrate blindly — first identify how the data was stored and which connection settings are masking the issue.
Dependent filters are easiest to reason about when each selection narrows the available values for the next step instead of trying to solve everything in one giant query.
When a project needs cleaner product URLs without moving the data model into resources, an OnPageNotFound router can bridge the gap — as long as URL rewriting stays predictable.
If a TV must never be left empty, the save flow should stop before persistence and show the editor a clear message instead of silently accepting bad data.
This manager prototype explored a much cleaner admin shell: no frameset, better full-screen overlays, and a more modern path for future interface work.
If an external PHP script needs MODX or Evolution CMS functions, bootstrap the CMS first instead of trying to call API helpers in isolation.