Call modResource refreshURIs() when clearing site cache

[pixelchutes]

pixelchutes created Redmine issue ID 9129

Many times it can be a huge time-saver to edit the MODx database directly, specifically if you're working with multiple MODx instances and need to copy resources between databases, or creating resources via SQL directly.

Since Revolution, the uri column on modx_site_content makes this process slightly more difficult, as the uri for reach resource must be regenerated, especially if the alias or hierarchy has been altered.

Is there any implication from adding a refreshURIs() call for modResource as part of clearing the site cache? This would simplify this process for quite a few users and prevent some of the current work-arounds required to make this process as easy as it could be.

More info here:
http://forums.modx.com/thread/80495/edited-alias-but-front-end-still-using-old-alias

[pixelchutes]

pixelchutes submitted:

I have submitted the following PR: #442

This seems to take care of the problem of desynchronized URIs as a result of Evo migrations (e.g. empty uri field), direct database edits against alias / hierarchy, etc. It places the automatic uri generation call in the Clear Cache command, which most people presumably try while troubleshooting.

[theboxer]

Should be resolved by #442