Hi Cindy, many thanks for that explanation and for the time and effort you have put into this issue. I am often slow on the uptake so just checking that I have got this right
I appreciate it being a best guess given your inheritance of the plugin! .... and I do not see it as a plugin issue anyway.
Here is how I see it. USU worked like a charm in v1.5.1 with the /includes/init_includes/overrides/init_canonical.php included the file package and SitemapXML files were generated correctly using USU generated url's.
USU v2
does work in v1.5.5f in that it does create the user friendly URL's as it is designed to - the problem is that those URL's are not generated in the SitemapXML files - given that USU and SitemapXML versions were the same (as used in v1.5.1, and still valid) at the time of upgrade to v1.5.5f, it appears something is not correlating between ZC core files in v1.5.5f and USU and SitemapXML - given that USU is generating the files correctly then it appears something is not telling SitemapXML to produce USU generated URLs in its files. The only change in the process is changes to ZC core files in v1.5.5f - so what changed in the core of v1.5.5f to create this 'imbalance' ? If that change could be isolated it may (should) solve the issue

- I really do not want to upgrade to v1.5.6 any time soon (still recovering from 155f upgrades).
I have converted all my v1.5.5f sites to CEON URI Mapping so to test your theory of removing /includes/init_includes/overrides/init_canonical.php from USU v2 I will need to look at how I can do that without creating chaos
I haven't checked it out but maybe I can have both plugins installed without creating conflict and switch between them - in your opinion is that likely to be possible?
cheers and thanks for your continuing help,
Mike
Bookmarks