In general this packaged doesn't just look for node ID's in text fields. It looks for links decorated with {localLink:##} or <img data-id='###' strings witch newer versions of Umbraco will include. This means that some data form older versions may not correctly display as a dependency. Other then that it will look at int and varchar fields for id's but only for specific data types. No matching should be happening on file names themselves or on any other text beyond the two examples in RTE fields.
I looked at the code, at least the version I have, it is checking of the string value of the node id being deleted (in my case 1560) exists at all in the datantext field by doing a simple string contains.
Maybe the contains string needs to be updated to include a better string to check, or updated to use a regular expression?
PUND is another project available here, when I first posted, I could not tell where the issue was, it is in the PUND codebase itself, and not within the linked content data type. (meaning it is definitely a bug, but not for Linked Content Data Type).
Linked shows no links, but PUND indicates that the node is used
I have a case where a node shows that it has no links, but when using PUND, it indicates that the node is used.
In my case the filename of a media image uploaded was "/media/1037/901560171272e44263e4b.jpg"
I was deleting node 1560
1560 appears in the string within the dataNText field, which makes this implementation invalid.
I'm not sure what the PUND your referring to is.
In general this packaged doesn't just look for node ID's in text fields. It looks for links decorated with
{localLink:##}or<img data-id='###'strings witch newer versions of Umbraco will include. This means that some data form older versions may not correctly display as a dependency. Other then that it will look at int and varchar fields for id's but only for specific data types. No matching should be happening on file names themselves or on any other text beyond the two examples in RTE fields.I looked at the code, at least the version I have, it is checking of the string value of the node id being deleted (in my case 1560) exists at all in the datantext field by doing a simple string contains.
Maybe the contains string needs to be updated to include a better string to check, or updated to use a regular expression?
PUND is another project available here, when I first posted, I could not tell where the issue was, it is in the PUND codebase itself, and not within the linked content data type. (meaning it is definitely a bug, but not for Linked Content Data Type).
Sorry for the confusion.
is working on a reply...