I have been checking your site for 2 days now and I still can't figure out why it is indexing it twice. On my local instance, it works perfectly fine but not on your site. However, what I did noticed is that there are many modified files in the core and I am unsure if these core modifications that you made is affecting the indexer.

Can I perform a clean re-installation of EasySocial so that I can run some further tests?

Hello

Yes, you can.

There is something not right with your Joomla instance. Calling the controller seems to be rendered twice and I have no idea why your instance of Joomla is doing that Was your copy of Joomla modified?

The only work around that I have added is to add the id's as static to prevent the indexer from rendering more than once (This is not a clean fix and I am not really happy with such a fix) but oddly, this does not happen with my instance of Joomla.

I will apply the same fix to prevent such duplicates from happening on a single page request

OK, thank you.

No, my Joomla was not modified. And I noticed no object (other than ES Events) that make duplicate entries in Smart Search index... That's strange indeed.

Yeah, very strange because when I was debugging the site, it seems like the "save" is being triggered twice.

Hello

I tested this on ES 1.4.9 and unfortunately, the fix does work so well...

When I create the "Index Test" event, an index entry is created for the following URL:
index.php?option=com_easysocial&view=events&id=90:&layout=item

Then, if I modify the event, another index entry is created for the URL:
index.php?option=com_easysocial&view=events&id=90:index-test&layout=item

So in the end, I get 2 entries in the index again...

Okay, managed to find the root cause after a massive debug session. It seems like this is what is actually happening,

1. You do not have the permalink field for the event category.
2. When the event is created, the system only stores the alias after the event is indexed, hence the indexed url is incorrect.
3. Therefore when you edit the event, it generates a new item because the url isn't matching.

To fix this, I have modified the codes so that before saving the event, it will then check if the alias is empty and generate one for it accordingly.

If anyone else needs this fix, download the attached file and upload it into /administrator/components/com_easysocial/models/

Thank you Mark, this is working perfectly

You are most welcome This will be fixed on the next release.