TOPIC: [SOLVED] Front-End errors...

Error reporting has been disabled but no luck, still gettin\' the errors?

Weird. The only other thing I can think of is to try enabling legacy mode. I have it enabled, maybe that\'s what\'s different. I have no idea *why* that would make a difference, I\'m just guessing at this point.

Running in legacy mode as well. Just from tracing the variables from the php file leads me to believe it\'s looking for a field in the MySQL table and not finding anything.

I dunno, those look like the same PHP errors I was seeing, and the ones you listed in the first post look like PHP errors.

Correct me if I\'m wrong, but that\'s a PHP error, for sure. Same for the \"property of a non-object\" errors.

My recommendation is to try to keep working on your site, ignoring the errors if possible. Sure, it\'s ugly, but these items shouldn\'t necessarily keep you from moving through the workflow, depending on how PHP is set up in your environment.

The fact that setting the joomla error reporting to \'none\' doesn\'t help make we wonder if your environment has the PHP error handling cranked up by default, and those global server settings are taking precedence.

I agree! It\'s my own personal server so I have total control over the environment, the script works as it should, just not very professional rolling a site out to a client with errors all over the place. Any way to get rid of them would be most appreciated.

Murph you would be what they call, in some areas of the world, the man. I tweaked some thing in /etc/php.ini and whaddaya know errors went bye bye. Thanks for the help.

c1scok1d, we just posted the solution to your ticket. This has been fixed on your site and was due to PHP configuration on your server. Everything should be good now. If not, please update your ticket. Thanks.