UPDATES EasyBlog 6.0.11 Released! Update to the latest version now!

Helpdesk

Your Time
Our Time
Response Time
24 — 48 hours
We strive to provide the fastest ever response possible. However, we are not super beings.

Allow at least 24 — 48 hours
  Support is online
Our support specialists is available now. We will attend to you as soon as we can.
  Support is online

Strict Standards: Errors

Kevin Morrison · ·
10:23 PM Thursday, 31 July 2014
None
I am having some issues with the categories module that I cannot resolve. I have updated all the modules and am using the latest version of everything yet the errors persist. Below is a list of the errors I am seeing and was wondering if someone could shed some light on what is wrong. I just updated my servers Apache and PHP so it may be something to do with a misconfiguration that needs to be addressed but I am not sure what?

This error is the first one before any of the posts are listed:
Strict Standards: Non-static method modEasyBlogCategoriesHelper::accessNestedCategories() should not be called statically in /home/*****/public_html/modules/mod_easyblogcategories/tmpl/default.php on line 18

All the rest of the categories that have content show this error:
Strict Standards: Non-static method modEasyBlogCategoriesHelper::accessNestedCategories() should not be called statically in /home/*****/public_html/modules/mod_easyblogcategories/helper.php on line 310

Something to do with nested categories but there is only one category that has a parent.

Also the calendar module is throwing a similar error:
Strict Standards: Non-static method modEasyBlogCalendarHelper::_getMenuItemId() should not be called statically in /home/****/public_html/modules/mod_easyblogcalendar/mod_easyblogcalendar.php on line 42

All this tells me I may need to make some changes to the php.ini file. I have display_errors turned off and error_reporting is currently set to E_ALL but I have tried every possible combination with no luck.

Here is a link to the offensive code: http://leagueses.org/blog

Not sure if it is worth noting but the same errors are showing up on the sites error_log file as well.
The replies under this section are restricted to logged in users or users with an active subscription with us