Hello and good day,
When clicking Home on EasyBlog toolbar, I can see the home page but it is grayed-out by what I gather to be the Composer element. I have attached an image showing exactly what is seen when clicking the home button on the EasyBlog toolbar.
I see a red X at the top right and when clicking I am prompted "Are you sure you want close the composer?" and I can click close to remove the gray-out. The composer window does not actually load, just a full screen gray-out and the red X button.
I would expect that when clicking the Home button on the EasyBlog dashboard I would be taken to the home page without this gray-out screen or the composer automatically popping up. I hope I am not missing a setting!
I consider my debugging skills limited, but using the developer tools in Firefox I found that the gray-out appears to be happening due to this block of html:
<div id="fd" class="eb eb-composer-launcher is-loading" data-eb-composer-launcher="">
<div class="eb-composer-launcher-header">
<div class="eb-composer-launcher-close-button" data-eb-composer-launcher-close-button="">
<i class="fa fa-close"></i>
</div>
</div>
<div class="eb-composer-launcher-container" data-eb-composer-launcher-container="">
<div class="eb-loader-o size-lg">
</div>
</div>
</div>
=========Site Information===========
PHP Built On Linux CentOS server 2.6.32-504.16.2.el6.x86_64 #1 SMP Wed Apr 22 06:48:29 UTC 2015 x86_64
Database Version 5.1.73
Database Collation latin1_swedish_ci
PHP Version 5.4.41
Web Server Apache/2.2.15 (CentOS)
WebServer to PHP Interface apache2handler
Joomla! Version Joomla! 3.4.3 Stable [ Ember ] 2-July-2015 16:00 GMT
Joomla! Platform Version Joomla Platform 13.1.0 Stable [ Curiosity ] 24-Apr-2013 00:00 GMT
User Agent Mozilla/5.0 (Windows NT 6.1; rv:39.0) Gecko/20100101 Firefox/39.0
=========End Site Information=======
Joomla error reporting is set to Maximum, but no errors are thrown when this happens.
I am sorry, but this site is an internal portal and as such it has no access via the internet and I cannot allow administrative access to any support member. I do have complete access to the server and the site to try any suggested fixes.
Thanks in advance for any ideas or fixes!