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!
  Support is offline
Hi,

Like a large number of other posters here, we have had the stuck-at-45% installation problem. By following the suggestion / description at http://stackideas.com/forums/upgrade-to-5-fails-stuck-on-45#reply-216613 we were able to apparently complete the installation and in the front end, everything except EasyBlog is working.

The outstanding issues are:
- even though the back end shows there are (still) many posts that were previously displaying correctly, post-upgrade no posts show in the front end.

- every access to a backend EasyBlog administration function is accompanied with a PHP warning message (this is a development server inaccessible from the Internet, so we have all such messages enabled) "Warning: Invalid argument supplied for foreach() in C:\<root of server>\administrator\components\com_easyblog\includes\acl\acl.php on line 49" From which you can conclude this is running on a Windows PC (W7 Ultimate), but using Apache 2.4, PHP5.5.17 & MySQL 5.6.25. The PHP warning message also shows when accessing a previously configured menu entry pointing to EasyBlog.

For reference, when the installation failed, I had tried both the "launcher" (com_easyblog_launcher_community_5.0.20_joomla3.0.zip) and then the full 18MB installer (com_easyblog_full_community_5.zip) by HTTP POST and via a directory - in all cases, the installation failed at the 45% stage (so the PHP upload limit is probably not relevant for the problems I experienced). By following the recommended MySQL table ALTERations and running the EasyBlog / Maintenance / Database / Start, the installation has completed, albeit with the now-not-displaying-any-article-in-the-front-end problem. I could understand that the PHP foreach warning is related / the cause of the no-articles.

I await your comments and help
The replies under this section are restricted to logged in users or users with an active subscription with us