By Rebel of Oz on Sunday, 12 April 2015
Posted in Technical Issues
Replies 12
Likes 0
Views 577
Votes 0
After upgrading jLike and jBolo! to the latest version this morning, links to EasyDiscuss threads suddenly no longer open, not from the Jomsocial status update, not from the EasyDiscuss frontpage or category list, not even when entering the URL directly into the browser. I've tried disabling, uninstalling and even reinstalling jLike and jBolo!, but it didn't help. Neither did reinstalling EasyDiscuss. The only thing I haven't tried as yet is uninstalling EasyDiscuss and installing it again.
Hello,

I am sorry for the delay of this reply.

I got the EasyDiscuss problem fixed by first uninstalling EasyDiscuss, repairing the entire database in the MySQL Database control panel and then reinstalling EasyDiscuss.

To be honest I've been searching high and low on how to resolve the database error that you and I facing during the re-installation of easydiscuss. So repairing the database from MySQL Database control panel does the trick. I will take note of that .

I noticed that EasyDiscuss is much faster now. I also noticed that - while before, there were many EasyDiscuss items listed when searching for "EasyDiscuss" - there is now only one, in addition to the jLike EasyDiscuss plugin. Any idea why? Did I miss anything in the installation?

I've checked the easydiscuss component in my local machine and I also only have one item named easydiscuss which is the type is component. The rest is just a module that I've installed for the testing purpose. Refer my local screenshot here, http://screen.stackideas.com/2015-04-15_1033.png . I believe this behavior is normal and nothing is wrong during your installation. Perhaps what you have before is the old component of easydiscuss which is not being optimized properly compare to the newer version of easydiscuss. Nothing to worry about

By the way I am glad that your issue has been resolved now. If there is anything related with jomsocial issue that associated with our easydiscuss components, kindly let us know and we will help you the best as we could
·
Wednesday, 15 April 2015 10:43
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

I am really sorry for the delay of this reply as it is a weekend for us here. The login credentials which you have provided doesn't seem to work. Not really sure how to reproduce this issue on your site though.
·
Sunday, 12 April 2015 22:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Here's a link for a video demonstration of the problem.

http://www.screencast.com/t/2vcnOKEYsDi

The password for the video is the same as for your user account.
·
Monday, 13 April 2015 09:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Rebel,

I have checked your site and it seems to have sql error:
Table './xxx_discuss_likes' is marked as crashed and last (automatic?) repair failed SQL=SELECT a.id as `user_id`, b.id, a.username AS `displayname` FROM `xxx_discuss_likes` AS b INNER JOIN `xxx_users` AS a on b.created_by = a.id INNER JOIN `xxx_discuss_users` AS c on b.created_by = c.id WHERE b.`type` = 'post' AND b.content_id = '75615' ORDER BY b.id DESC

So, I tried to login to your backend, I get this error. It seems you haven't activate our access yet.
Warning
Username and password do not match or you do not have an account yet.


I also tried to login to your FTP, I got this error.
Connection timed out or server hung up. The server you are connecting to may be configured to limit the number of connections you are allowed to make.


Can you please provide us with the correct credentials so that we can assist you further on this issue.
Please advise.
·
Monday, 13 April 2015 11:12
·
0 Likes
·
0 Votes
·
0 Comments
·
I've discovered another new problem that wasn't there before. I have four template layouts defined, two for English and two for German. (I need different templates for different languages because the template determines the main menu.) For each language I have a "home" and a "default" layout. The "home" layouts are used for the news page (http://therebel.is/en/news and http://therebel.is/de/news) to suppress the Joomla blog layout and display the "JA Featured New" and the "JA News Pro" modules instead, which are also assigned to the same news pages. After yesterday's upgrade, my site has suddenly stopped switching between the "default" and the "home" layouts. It ALWAYS displays the "default" layout.
·
Monday, 13 April 2015 13:38
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Rebel,

I am sorry as I unable to access your site: http://screencast.com/t/bi68a3QwgH . Can you please provide us with backend access and FTP access so that we can assist you further on this issue.

Please advise.
·
Monday, 13 April 2015 18:18
·
0 Likes
·
0 Votes
·
0 Comments
·
The site was down yesterday because it had run out of SQL pipes which had been set too low (initially 55, now 120) by the new hosting company and then got stuck during reboot. The joomla and ftp credential I had provided are correct. I'm providing them again. I have two main problems right now with my site:
1. The site no longer switches to the "home" template layout which is assigned to the http://therebel.is/en/news and http://therebel.is/de/news menus.
2. The site no longer opens EasyDiscuss pages (EasyDiscuss frontpage, EasyDiscuss category page, EasyDiscuss discussion page)
·
Tuesday, 14 April 2015 06:48
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello,

I am sorry for the delay of this reply.

It is possible for you to somehow give us access to your ftp without using any joomla 3rd party extension like extplorer? I can't access to your ftp due to the slow connectivity to your server and causing the timeout error. The reason why we prefer the direct ftp instead of using 3rd party joomla component is that to ensure in case something goes wrong during the debugging process we can restore it without having to login to your site.

I do notice that somehow easydiscuss component has been missing from both of your site frontend and backend. I've tried to reinstall easydiscuss via extension manager and after some time I receiving the following error,
1064 You have an error in your SQL syntax; check the manual that corresponds to your Ma###B server version for the right syntax to use near '' at line 1 SQL=SELECT * FROM `##_extensions` WHERE `extension_id`= 


Please advise.
·
Tuesday, 14 April 2015 12:12
·
0 Likes
·
0 Votes
·
0 Comments
·
Sure, you can ftp access the site with the details provided.

Btw, I've discovered a 3rd new problem. Status updates in Jomsocial are no longer possible.

The TechJoomla people, with whose jBolo and jLike software upgrades I got into this mess, are blaming EasyDiscuss for my problems. Not sure how this could have caused my template to no longer switch between layouts or Jomsocial to no longer store any status updates.

FYI, I have made a duplicate of the Top Menu English and Top Menu German, in case the EasyDiscuss ("Forum") submenu gets lost in the re-installation process.
·
Tuesday, 14 April 2015 12:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Just a quick update. I got the EasyDiscuss problem fixed by first uninstalling EasyDiscuss, repairing the entire database in the MySQL Database control panel and then reinstalling EasyDiscuss. As it turns out quite a few tables had been crashed, which hasn't been picked up by MySQL Admin before. The problems with Jomsocial status updates and the template not switching layouts and not displaying the German language main menu are still unresolved. I'm working with the respective vendors on those. Many thanks for your assistance on that matter.

Btw, I noticed that EasyDiscuss is much faster now. I also noticed that - while before, there were many EasyDiscuss items listed when searching for "EasyDiscuss" - there is now only one, in addition to the jLike EasyDiscuss plugin. Any idea why? Did I miss anything in the installation?
·
Tuesday, 14 April 2015 21:49
·
0 Likes
·
0 Votes
·
0 Comments
·
I'm glad you learned something from it. The site seems much faster now, after repairing the database and reinstalling EasyDiscuss. I wonder what made the database crash so badly. The only table that the MySQL Admin control panel recognised as crashed and was able to repair belonged to EasyDiscuss, but other tables were also affected. The MySQL Database control panel did better, it found and repaired them all. Maybe it had to do with all the old bits extension files from earlier EasyDiscuss versions.
·
Wednesday, 15 April 2015 11:27
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Rebel,

Thanks for the heads up. We will take note of this issue and will come up with a better solution in case similar issue is happening to others

I will mark this discussion as resolved.
·
Wednesday, 15 April 2015 11:57
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post