This PR fixes the resolving of node names. When the NameResolver::resolveName got passed a $forNode which was already suffixed with an increment (e.g. foo-1) it didn't recognize it as the same node. That means that saving a page with an already incremented node name always switched between two increments (foo-1 gets foo-2 when being saved, and turns back to foo-1 when saved another time).
This issue made some problems in combination with the publishing, because it moves a node in the session. Since this is neither necessary nor the desired behavior, changing this seems like a valid fix.
This PR fixes the resolving of node names. When the
NameResolver::resolveName
got passed a$forNode
which was already suffixed with an increment (e.g.foo-1
) it didn't recognize it as the same node. That means that saving a page with an already incremented node name always switched between two increments (foo-1
getsfoo-2
when being saved, and turns back tofoo-1
when saved another time).This issue made some problems in combination with the publishing, because it moves a node in the session. Since this is neither necessary nor the desired behavior, changing this seems like a valid fix.