If I turn off caching in the TeraWurfl plugin, I get the following error:

Notice: Undefined offset: 0 in /web/umatterucanhelp.com/www_gethelp/plugins/mobile/terawurfl/TeraWurfl.php on line 333

If I enable it, I get this error:

Notice: Undefined index: id in /web/umatterucanhelp.com/www_gethelp/plugins/mobile/terawurfl/TeraWurfl.php on line 293

I'm only getting these errors in Firefox. They aren't showing in Safari, Chrome or IE.

I also did a fresh install on a local machine in a fresh install of J1.5 and got the same results.

Thanks,
Andy

Which option for "Force to use mysql4-compatible version" do you use?

Second issue most likely means that TeraWURFL's cache is corrupted, so you should remove all the entries from #__TeraWurflCache table.

We're on mysql 5.1, so we are using the mysql5 compat version

I'll try emptying the terawurfl cache table and see if that helps.

Thanks!

Andy

I emptied the #__TeraWurflcache and I'm still getting the same errors.

The errors are just Notices. I don't have access to add a php.ini file to change the error reporting on the live site and the Joomla error_reporting at None isn't bypassing this error for some reason. I'll continue to work on getting the error surpressed at that level, though.

Andy

Check that procedure jos_TeraWurfl_FallBackDevices exists in database.
As a workaround you can use mysql4 mode in terawurfl plugin settings.

The procedure does exist, so that's not the problem.

Changing to force to mysql4 works.

Thanks!
Andy

The first issue means that jos_TeraWurfl_FallBackDevices procedure returned no records. Then the only reason of it is incorrect WurflID parameter. Most likely this ID is "generic_web_browser" because of "SimpleDesktop Matching Engine". Corresponding entry in WURFL database is of DO_NOT_MATCH-type, so maybe this fact lead to abovementioned issue. To check it try to set in plugins/mobile/terawurfl/terawurfl/TeraWurflConfig.php

I was having the same issue with the "Undefined offset" error message. I checked my Joomla server configuration and found that error reporting was set to Maximum. When I changed it to "Simple" the error disappeared.

Wanting to solve the problem rather than mask it, however, I set it back to "Maximum" and then made the change recommended above, changing "public static $SIMPLE_DESKTOP_ENGINE_ENABLE" to "false". Even with error reporting set back to "Maximum", this solved the problem.