By Sam Famma on Saturday, 01 October 2016
Posted in Technical Issues
Replies 4
Likes 0
Views 369
Votes 0
Hi guys

The EB composer can take up to 2 minutes to open on the front end the back end is fine.
Trying to resolve the issue I deleted all server cache stopped cdn cleared browser cache with no success.

The update was installed in conjunction with ES 1.4 I don't know about ES 2.0 beta. But I had to re install my backup which immediately resolved the issue.

No other changes were made to the site just the EB update.

You might want to do some further testing on this update.
Hey there,

I am really sorry for the delay of this reply as it is a weekend for us here.

I have checked in your site (main domain and subdomain site), but i realised you have revert back to 5.0.37 version right?

Actually I would like to check you reported that load composer need to spend 2 minute++ issue. Because it quite hard to replicate this in locally, every site also have different setup. Perhaps you can setup a test site so we can check it from there?
·
Sunday, 02 October 2016 10:49
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Arlex

Yes I did reinstate back to 5.037.which cleared all data. But I will setup a replica site and reinstall EB on it for you to test on. I will let you know once Ive done it.

The other ongoing issue that I would like you to test is the easydiscuss back end it still does not work and continuing to drive me crazy to the point of dropping it all together.
·
Sunday, 02 October 2016 12:23
·
0 Likes
·
0 Votes
·
0 Comments
·
I finally found the issue with easydiscuss not opening on the backend

I changed the cdn url in db - discuss_config / system_cdn_url="url " cleared the cdn url value.

The back end worked immediately I checked the cdn again to ensure it was true and correct and it was.
I'm using the same cdn in Easysocial that has no issue.

Re entered the cdn url in settings / advanced / Content Delivery Network (CDN) and it locked the back end again.

Went back to the DB deleted the value again and it opened the back end once more.

Can you please check the code for errors.
·
Sunday, 02 October 2016 19:39
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey Sam,

I am sorry for the delay of this reply,

Yes I did reinstate back to 5.037.which cleared all data. But I will setup a replica site and reinstall EB on it for you to test on. I will let you know once Ive done it.

Alright, keep us update once you have done.


I finally found the issue with easydiscuss not opening on the backend

I changed the cdn url in db - discuss_config / system_cdn_url="url " cleared the cdn url value.

The back end worked immediately I checked the cdn again to ensure it was true and correct and it was.
I'm using the same cdn in Easysocial that has no issue.

Re entered the cdn url in settings / advanced / Content Delivery Network (CDN) and it locked the back end again.

Went back to the DB deleted the value again and it opened the back end once more.

Can you please check the code for errors.

Regarding with your Easydiscuss issue, I was unable to access your Joomla backend, this is the error what I hitting now :
An error has occurred.
500 Unable to load the page you requested

Is it need to add my current IP address into your server white list?
·
Monday, 03 October 2016 11:52
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post