Fixing Missing Child Resources in the Tree After Updating to Evolution 1.4.11

One of the more unnerving upgrade bugs is when the data is still there, but the manager tree suddenly behaves as if whole branches are missing. That is what happened in this donor case after updating from an older Evolution build to 1.4.11.

The root resources remained visible, but the expansion control disappeared. At the same time, the “View child resources” tab still showed the underlying documents correctly.

Why this matters

That combination usually tells you the problem is not data loss. It points instead to a manager-side rendering, permission, plugin, or cache issue affecting the tree UI.

A reasonable troubleshooting order

• Disable manager-side customizations such as ManagerManager or custom modules.
• Clear caches and verify tree-related scripts were updated correctly.
• Check whether the issue is isolated to the tree renderer while child resources remain queryable elsewhere.

The donor author had already ruled out some customizations, which makes the case especially useful as a reminder: tree bugs after an update are often interface-level regressions, not content corruption.

That distinction matters because it changes your recovery strategy completely.