Hi,
Seems I didn't do a proper testing after installing the latest update. Only today I found out that opening a topic now throws a set of error messages before showing each post. The set is always the same and are repeated for each post (the posts are shown as well):
---
Warning: array_combine() [function.array-combine]: Both parameters should have at least 1 element in /home/dev/domains/oorzaak-develop.nl/public_html/opt01/components/com_chronoforums/chronoforums/helpers/user_tasks.php on line 52
Warning: array_intersect_key() [function.array-intersect-key]: Argument #1 is not an array in /home/dev/domains/oorzaak-develop.nl/public_html/opt01/components/com_chronoforums/chronoforums/helpers/user_tasks.php on line 54
Warning: array_map() [function.array-map]: Argument #2 should be an array in /home/dev/domains/oorzaak-develop.nl/public_html/opt01/components/com_chronoforums/chronoforums/views/posts/index.php on line 104
Warning: implode() [function.implode]: Invalid arguments passed in /home/dev/domains/oorzaak-develop.nl/public_html/opt01/components/com_chronoforums/chronoforums/views/posts/index.php on line 104
---
Hope you can detect what causes this.
Kind regards, Frits
Seems I didn't do a proper testing after installing the latest update. Only today I found out that opening a topic now throws a set of error messages before showing each post. The set is always the same and are repeated for each post (the posts are shown as well):
---
Warning: array_combine() [function.array-combine]: Both parameters should have at least 1 element in /home/dev/domains/oorzaak-develop.nl/public_html/opt01/components/com_chronoforums/chronoforums/helpers/user_tasks.php on line 52
Warning: array_intersect_key() [function.array-intersect-key]: Argument #1 is not an array in /home/dev/domains/oorzaak-develop.nl/public_html/opt01/components/com_chronoforums/chronoforums/helpers/user_tasks.php on line 54
Warning: array_map() [function.array-map]: Argument #2 should be an array in /home/dev/domains/oorzaak-develop.nl/public_html/opt01/components/com_chronoforums/chronoforums/views/posts/index.php on line 104
Warning: implode() [function.implode]: Invalid arguments passed in /home/dev/domains/oorzaak-develop.nl/public_html/opt01/components/com_chronoforums/chronoforums/views/posts/index.php on line 104
---
Hope you can detect what causes this.
Kind regards, Frits
Hi Frits,
I'm not sure exactly what causes it but setting the site Error Reporting to System Default or to None should hide any PHP Warnings or Notices.
Bob
I'm not sure exactly what causes it but setting the site Error Reporting to System Default or to None should hide any PHP Warnings or Notices.
Bob
Hi Bob,
Do you mean the Joomla built-in error reporting? This is disabled.
Or do you mean the php error reporting?
Kind regards, Frits
Do you mean the Joomla built-in error reporting? This is disabled.
Or do you mean the php error reporting?
Kind regards, Frits
Do you mean the Joomla built-in error reporting? This is disabled.
I mean: System > Global configuration > System > Debug settings.
Hi Frits,
I mean: System > Global configuration > Server > Error Reporting
Bob
I mean: System > Global configuration > Server > Error Reporting
Bob
Hi Bob,
I always forget about this option. It was set to Default, I switched to None and now the error messages are gone.
This cleans up my pages a lot, thanks.
I trust you in that we can ignore these messages safely...
Kind regards, Frits
I always forget about this option. It was set to Default, I switched to None and now the error messages are gone.
This cleans up my pages a lot, thanks.
I trust you in that we can ignore these messages safely...
Kind regards, Frits
Hi Fritz,
You can almost always ignore PHP Notices and Warnings, if you start seeing blank pages or really odd behaviour then, as part of the debugging process it's worth setting Error Reporting back to Maximum (or maybe even Developer) for a few minutes to see if any meaningful 'Fatal Error' messages show up.
Bob
You can almost always ignore PHP Notices and Warnings, if you start seeing blank pages or really odd behaviour then, as part of the debugging process it's worth setting Error Reporting back to Maximum (or maybe even Developer) for a few minutes to see if any meaningful 'Fatal Error' messages show up.
Bob
This topic is locked and no more replies can be posted.