Subtree limitations are stored as path (/1/2/67) in ezpolicy_limitation_value table

Moving locations that are listed in subtree limitations have several bad side effects:

1. subtree limitiaions are broken. (the path specified in the limitation will no longer match anything)
2. The user is not notified when a subtree limitation is broken after moving/removing a location.
3. It is not possible for administrators to see which roles have policies with broken subtree limitations

Once you have a broken subtree limitation, it can be fixed by editing the policy and save it again ( without doing any changes ). However, the problem is finding the broken policies due to #3 mentioned above.

Steps to reproduce

• Create a role with policy limitation : content/create subtree(/1/2/50/60)
• Move location 60 to somewhere else

Experienced behavior:
Experience that you are no longer able to create objects below location 60

Expected behavior:
The best solution is if affected subtree limitations could be automatically updated when locations are moved. The bear minimum would be give user notification about the problem and administrators a simple interface for fixing broken subtree locations.

In regards to deleting locations.
When locations are deleted, there is no way of fixing affected subtree limitation (except of deleting the whole policy. However I think that is a bad idea.) Instead, the policy should be flagged somehow in admin-ui so that admin user can easily fix it. Since location is deleted, it would be nice to see the name of the deleted location, but not sure if that is possible (maybe it is possible before location is removed from trash at least....)