Quote Originally Posted by hira View Post
I downloaded solution of Numinix.
'\includes\classes\ssu\cores\link.php' included in it overwrites with a same name file of SSU.
This resembles measures to Ceon URI.
Quote Originally Posted by hira View Post
Yes!
Your reporting contributes to the fact.
I thank you very much.
Based on these posts it sounds like you have used Numinix solution as the basis of the newest version of WOZ???

Quote Originally Posted by hira View Post
Is it that an author is the same?
I am lacking in my recognition.
Numinix is NOT the author of SSU. Rubiks Integration (Yellow) is the author of the SSU module. The SSU file you found included with the Numinix solution was written by the author of the SSU module NOT Numinix.

From the Numinix blog:
I’ve been in contact with the author of Magic SEO URLs and he is going to get back to me next week with either providing a rewrite rule that will allow the module to work properly with MSU (currently nothing passed the homepage will work) or to add the ability to disable MSU on a per page basis.

I’ve also contacted the author of SSU who has modified his code to work better with the method described in this article. His changes are live on the Numinix Blog and at the moment all of the URLs that we’ve checked are working properly. Once he has a solid solution, he is going to either include this in future releases of the SSU module, or provide us with the necessary changes. For those using SSU, the current issue is that the comment links, such as those in the footer of this blog, will redirect to the store root and are therefore inaccessible. As you can see, the SSU author resolved this issue for us, and will post his update soon.
In other words Numinix did not take it upon himself to write changes for other author's module's. Instead he reached out to the original authors so that they could work TOGETHER. Which IMHO is how you should have approached dealing with modules which conflicted with WOZ.. This way the module author is not BLINDSIDED by support requests due to other module authors making changes (or suggesting changes) to their modules that they were unaware of..