Hi Rik,

May I know where you try to delete the thread (backend or frontend)? and can I have create a dummy post and try to delete it in order to replicate the issue?

Thanks for your cooperation and understanding RIk

Hello Fadhli

Come to think of it, recently I have only been doing deleting posts from the frontend (pruning junk posts).

Feel free to delete any thread in this category.

Thanks. -- Rik

Hi Rik,

It seems I can replicate the issue in your site when I tried to delete a discussion in frontend.
As I want to try to replicate it through backend it seems it keep me redirect to your frontend homepage, thus I have asked my colleague to try access your backend and then we are hitting the error: https://take.ms/xGibq
Perhaps, the system block our IP as multiple user try to access your backend

Yes, after further testing, the delete is slow both from the backend and frontend. It is so slow that it times out after about a minute with an Apache 504 error message.

Regarding StackIdeas access:

We use Akeeba's "Admin Tools" component that automatically blocks access if one does suspicious things on the system. I have temporarily turned it off. Hopefully that will allow you to do what you need to do.

Also, if you have problems running MySQL queries remotely, I can easily run them from my side.

Thanks. -- Rik

Hi Rik,

It seems, I am still got the spammer error same as my previous screenshot

Sorry, that message is from the Akeeba Admin Tools, again.

I had disabled it during your timezone work hours but I guess that I re-enabled it too soon. I'll disable it again on Monday.

Thanks. -- Rik

PS: The Akeeba Admin Tools is a great component to have.

I've now temporarily disabled the Akeeba Admin Tools. So you shouldn't get locked out of the backend again (unless your IP address has somehow gotten banned elsewhere on our system such as in the host firewall).

Also, our system is set with a custom 500 server error so that it shows a static index.html file. That 500 error page is our true homepage (Joomla is located in the /en/ directory below our homepage directory. That is so that even if Joomla is down with a server error, our clients who come to book travel arrangements are still able to do so as the links on that homepage take them to our separate reservations server.

I hope that you can now get into the system without further problems.

Let me know if there are any other problems. Thanks. -- Rik

Hey Rik,

My colleague is not around today in office, I will follow up your current issue.

I have read your previous reply and see you did mentioned that we can delete any discussion under this category
https://travel.com/en/community/forums/index/234-windsurfing but when I trying to access this page, it seems like it goes to 404 error.

May i know which discussion post can be delete so we can check for this?

Is this the one category you mentioned? https://travel.com/en/forums/234-windsurfing

DELETE

Arlex:

I have read your previous reply and see you did mentioned that we can delete any discussion under this category
https://travel.com/en/community/forums/index/234-windsurfing but when I trying to access this page, it seems like it goes to 404 error.

May i know which discussion post can be delete so we can check for this?

Is this the one category you mentioned? https://travel.com/en/forums/234-windsurfing

Sorry, I guess that I've changed the ED layout a little since I left that message.

Here is the forum. Feel free to delete any message for testing purposes (they're quite old).

Thanks. -- Rik

Just FYI as I don't know if this could make a difference or not.

We imported most of our forums into EasyDiscuss from Kunena some years ago. The threads from people who were not already members I see were marked as "guest" in the database.

A few days ago, I did a query to see if there was a 1-to-1 correspondence with unique poster names and our total users. Unfortunately, there are about 2,100 users names in the EasySocial users table but I came up with about 23,000 poster names in the forums which are not part of our user base (these came from Usenet forums years ago).

I'm guessing that all of those user names from those messages didn't get created in our user base when we moved from Kunena to EasyDiscuss.

Could that be posing a problem as the delete query might be trying to update something in the user table for missing users?

Well, just thinking out loud, as they say.

After debugging long hour ago, I suspect one of the content plugin caused this issue because Easydiscuss allow trigger 3rd party content plugin to do something when delete discussion on the site.

I will continue to debug this at tomorrow morning.

This 3rd party plugin caused this "Content - Geek ElasticSearch" , I already disabled this plugin on your site, can you try delete one of the thread and see how it goes?

Arlex:

Fantastic! Yes, I can now delete threads to my heart's content.

Since the Geek ElasticSearch plugin was causing the problem (and we really need to keep it but I can disable it when necessary), is there anything that you think I should tell the developer besides that he is making EasyDiscuss thread deletions time out?

Thanks. -- Rik

You're welcome, I think you can explain to them like this :

When the user delete a discussion in Easydiscuss extension, it allow 3rd party content plugin trigger this "onContentAfterDelete" event function, it seems like when it trigger this event function from 'Geek ElasticSearch' plugin then it hit timeout.

And, with that, we'll call this ticket closed.

Thanks. -- Rik

Hi there,

You are most welcome. Glad to hear that your issue has been resolved now.

Just for your information, I have locked and marked this thread as resolved to avoid confusions in the future. Please start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiries.

Thanks for understanding.