Hi,
lol I think I know my own code. :)
You've missed seeing the call to $this->_normaliseServerEnvironment() a few lines before the abort code you refer to is encountered. :)
Please do send login details so I can debug the server environment.. may as well have Ceon URI Mapping cope with such broken servers, can only be good to be as compatible as possible!
I'm sorry to hear that, I hope you are on top of things and well on the way to beating them! :)
Unfortunately, yes, as historical URIs can have used the same URI as a current URI but with the current URI referring to a different product etc.
Also, multi-lingual sites can have the same URI but with different language IDs.
It's for these reasons that the uri column can't be made a key in the "standard" edition of the software.. but if you override the DBLookup and Admin classes and create a new edition, storing the historical URIs in a separate table, and not using other languages, you can indeed key the table by the uri column.
Hope that helps!
All the best...
Conor
ceon
Bookmarks