Blog Sections Open
Troubleshooting TinyMCE After Updating an Evolution Build
If TinyMCE breaks right after an update, the problem is often in editor assets, config drift, or mismatched manager-side paths rather than in the content itself.
Editor failures right after an update are especially disruptive because content editing is often the first thing users notice. In the old case behind this post, TinyMCE stopped working after a build update even though the manager itself still loaded.
What to Check First
- whether TinyMCE assets were updated completely
- whether editor config files still match the current build
- whether plugin paths or file manager integrations changed
- whether browser cache is holding stale editor scripts
Why This Happens After Updates
Editors are one of the easiest places for partial updates to show up. If the manager core and the editor assets are out of sync, the page may render but the editor initialization fails.
Practical Recommendation
When TinyMCE breaks after an update, verify the asset set first, then check integration points such as file manager connectors and custom toolbar plugins. In many cases the fix is consistency, not a full rollback.
Speeding Up or Replacing `getImageList` for MIGX Workloads
Why image-heavy MIGX setups can feel slow with getImageList and when it makes sense to rethink the rendering strategy.
Understanding Link Format Rules in Evolution CMS
A short practical note on link_tag_scheme, slashes, and why generated URLs may look different from expected section paths.