Quote Originally Posted by AnglersCorner View Post
Hello,

I have installed this module and while everything seems to work fine I have seen a couple of errors in my logs as follows:

PHP Fatal error: Call to a member function add() on a non-object in /home/anglersc/public_html/includes/classes/class.CeonURIMappingHandlerBase.php on line 131

and

PHP Fatal error: 1267:Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ci,COERCIBLE) for operation '=' :: SELECT uri FROM zen_ceon_uri_mappings WHERE main_page = 'account_history_infoℴ_id=577' AND associated_db_id IS NULL AND query_string_parameters IS NULL AND language_id = '1' AND current_uri = '1' LIMIT 1; ==> (as called by) /home/anglersc/public_html/includes/classes/class.CeonURIMappingDBLookup.php on line 166 <== in /home/anglersc/public_html/includes/classes/db/mysql/query_factory.php on line 155

The module appears to work fine and do what is expected of it but these errors had me worried so I have deactivated it for now. I'm not really clued up on PHP sadly so I was just wondering if these errors are harmless or not, can I ignore them? ...if not is there an easy way to sort it or should I just forget about ever using this module?

Thanks in advance :)
Couple of things going on here. For one it looks like your database is not using UTF-8 collation, would suggest following the instructions of the Convert db2utf8 plugin that converts the database to UTF-8, there are also some files through the system that would need changing to recognize/handle the db as UTF8/UTF-8, etc... The next thing is that the rewrite that is being attempted there has scrambled some of the information pushing &order_id into: ℴ_id as part of the main_page. Such a parameter should not be in the main_page but instead in the query_string_parameters field. The first error may be some sort of result of the second, but the error message generated (which btw is generated before the $messageStack has been initialized to actually present that error) indicates that there is server information missing to be able to support mapping URIs. If that issue is not generated each and every time the site is visited, then there may be something intermittent with your host's server(s) and would suggest inquiring to them why the REQUEST_URI server variable is not present or wasn't present at the time of the error. (Provide them log times of that first error.)

Perhaps there is other assistance also suggested, but that is what I see of what has been reported. Assuming that the database conversion and file modifications to support goes successfully, then the only other issue is to address whatever host problem(s) are generated. Perhaps it would help the community if you were to identify with whom you host your site?