UPDATES EasyBlog 6.0.14 Released! Joomla 5.x and PHP 8.x compatible 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 offline
It is currently off working hours and most of us aren't around

Rest assured that we will get back to you as soon as the day starts tomorrow!
It is currently a public holiday for us from where we are at.

There may be a delay in our responses but rest assured that we will be back at full speed when we are back to the office.
  Support is offline

EasyDiscuss seems not to work properly under PHP 5.5

Tran Tuan · ·
10:00 PM Wednesday, 03 September 2014
None
Hello,

I am current using EasyDiscuss 3.2.9385 which is not the latest becuase my subscription expired a few months ago. Now, I want to renew my subscription to get the latest version. But I want to besure the latest is fully compatible with PHP 5.5.
My current version is not fully compatible with PHP 5.5. It raises a lot for notice and warning. Some of the issues are listed below:

  • Strict standards: Non-static method DiscussHelper::validateCaptcha() should not be called statically, assuming $this from incompatible context in /path_to_joomla/components/com_easydiscuss/controllers/posts.php on line 833
  • Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /path_to_joomla/components/com_easydiscuss/helpers/string.php on line 119
  • Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /path_to_joomla/components/com_easydiscuss/helpers/string.php on line 120
  • Strict standards: Non-static method FinderIndexer::index() should not be called statically, assuming $this from incompatible context in /path_to_joomla/plugins/finder/easydiscuss/easydiscuss.php on line 176
  • Fatal error: Cannot call abstract method FinderIndexer::index() in /path_to_joomla/plugins/finder/easydiscuss/easydiscuss.php on line 176


I don't know if such warning and fatal errors have been fixed so far....
The replies under this section are restricted to logged in users or users with an active subscription with us