Call to a member function getAlias on null

Hi,

The tests had been updated.

It covers:
- alias creation
- alias update
- alias deletion
- overlapping pid

See MR https://git.drupalcode.org/project/entity_share/-/merge_requests/47

and for tests only https://git.drupalcode.org/project/entity_share/-/merge_requests/38

I let people review if you want and will probably merge next thursday.

LGTM

And this is merged!

Thanks everyone!

Automatically closed - issue fixed for 2 weeks with no activity.

Grimreaper → closed merge request !34

Grimreaper → closed merge request !38

still getting the same issue with 8.x-3.x-dev, #42 💬 Call to a member function getAlias on null Fixed works for me.

See also https://www.drupal.org/project/drupal/issues/3210926 →
There is still a problem in path handling in core.

Hi, I have a similar issue when I try to sync the nodes with and without the path alias. When I create or update the node with a path alias after the synchronization the field keeps null. Using #42 the alias is created but with a wrong relation between the alias and node. Another way that I tried to fix this issue was to enable the enhancer for the path field but only works when I create a node with alias and sync. but if I try to create a node without an alias sync the node and after that add the path alias I have the same issue.

Hi, I have a similar issue when I try to sync the nodes with and without the path alias. When I create or update the node with a path alias after the synchronization the field keeps null. Using #42 the alias is created but with a wrong relation between the alias and node. Another way that I tried to fix this issue was to enable the enhancer for the path field but only works when I create a node with alias and sync. but if I try to create a node without an alias sync the node and after that add the path alias I have the same issue.

#42 works for me. For my use case, I turned off the pathauto pattern on the client side, so I'm dependent on whatever alias comes through from the server. The problem with this (likely what @grimreaper is referring to in #44), is that there's not a check on path aliases already on the site. So if the pulled node has the exact same path alias as one on the existing site, it just overwrites it. So this change is not ideal if there is existing content that may have the same path as new content.