Location handling in content preview has a few edge cases. The main one is that when the first version of a Content is previewed, it does not have a location yet.

In 5.3, this was worked around by returning a fake Location object, with a draft status. It covered some of the use-cases, but not all, as discussed in EZP-23589.

This can be improved by fetching node assignment data for the content when applicable, and improving the fake location with this data (parent location id, depth). This should make more override rules behave as expected.

The location's id should still be empty, as it really doesn't have one.