It seems like I was unable to access your Joomla backend, you can check my attached screenshot below.

I made sure that the login and password I for the backend of my joomla site matches the site details so the stackideas login should work now. Actually I am surprised it didn't but hopefully you can get in now.

Also, I just did a test indexing from the command line as follows:

-sh-4.1$ php finder_indexer.php
Smart Search INDEXER
============================
Starting Indexer
Setting up Smart Search plugins
Setup 1033 items in 0.048 seconds.
PHP Notice: Use of undefined constant JDEBUG - assumed 'JDEBUG' in /mnt/data/vhosts/casite-505587.cloudaccess.net/httpdocs/libraries/cms/module/helper.php on line 155
PHP Notice: Use of undefined constant JDEBUG - assumed 'JDEBUG' in /mnt/data/vhosts/casite-505587.cloudaccess.net/httpdocs/libraries/cms/module/helper.php on line 272
PHP Notice: Use of undefined constant JDEBUG - assumed 'JDEBUG' in /mnt/data/vhosts/casite-505587.cloudaccess.net/httpdocs/libraries/cms/module/helper.php on line 155
PHP Notice: Use of undefined constant JDEBUG - assumed 'JDEBUG' in /mnt/data/vhosts/casite-505587.cloudaccess.net/httpdocs/libraries/cms/module/helper.php on line 272
* Processed batch 1 in 7.296 seconds.
* Processed batch 2 in 10.494 seconds.
* Processed batch 3 in 11.054 seconds.
* Processed batch 4 in 14.814 seconds.
* Processed batch 5 in 17.087 seconds.
* Processed batch 6 in 17.797 seconds.
* Processed batch 7 in 18.077 seconds.
* Processed batch 8 in 13.423 seconds.
* Processed batch 9 in 17.326 seconds.
* Processed batch 10 in 15.286 seconds.
* Processed batch 11 in 5.237 seconds.
* Processed batch 12 in 8.556 seconds.
* Processed batch 13 in 8.249 seconds.
* Processed batch 14 in 15.141 seconds.
* Processed batch 15 in 30.911 seconds.
* Processed batch 16 in 32.928 seconds.
* Processed batch 17 in 28.425 seconds.
* Processed batch 18 in 15.037 seconds.
* Processed batch 19 in 9.04 seconds.
* Processed batch 20 in 8.763 seconds.
* Processed batch 21 in 6.751 seconds.
Total Processing Time: 311.743 seconds.

You have new mail in /var/spool/mail/drcarne2
-sh-4.1$

The answer I received from my host is as follows:

Hi Sean,

These are only PHP warning messages, they could stay that way.
JDEBUG has been defined in the framework.php file by the Joomla! developers and the framework.php has nothing to do with the CLI tools of course. You could safely ignore these messages.
Anyway, I have added the line define('JDEBUG', false); in your finder_indexer.php file and now these errors are gone.

So, that is good I guess. It does not explain why the Smart Search indexing fails on EasyBlog Posts for me though. But, I was able to try a bunch times on the command line and I believe the site has been indexed again. :-)

Still I thought you would like to know about this just in case there is something going on in your code that might have something to do with this.

Thanks for your consideration about what could be going on.

Sean

I spent quite a bit of time with Derek and Jonathan from CloudAccess.net today. They had never seen this problem before but have narrowed it down to the Smart Search - EasyBlog Posts plugin.

The symptoms we are seeing are as follows:

Indexing appears to stop at the letter W
Urls are being changed to swap out domain name out with another string.

We have been running the indexing command from the shell prompt in
/httpdocs/cli/

I was using the command "php -d memory_limit=256M finder_indexer.php"

I am not sure they were using the same command.

This is a url path that was created by the Smart Search indexer after the failure while indexing EasyBlog Posts:

http://domain.comfinder_indexer.php/blog/entry/vegetable-consumption-being-sidelined&highlight=WyJjYXJyb3QiXQ==

Our correct URL paths have been changed to replace our domain name with http://domain.comfinder_indexer.php/ instead of https://www.drcarney.com/

Jonathan and Derek tried a few tests to see if the failure was being caused by any one particular blog. They noticed that the last blog indexed ended with the letter W so they tried to look at the files that started after the letter W but were not able to find a particular blog that might be causing the problem.

You can ssh into the site using my ftp login and password.

I just upgraded EasySocial, Komento, EasyDiscuss and EasyBlog in hopes that might help fix the Smart Search problem. Well, the problem did not fix. But, it did CHANGE.

Here is what the urls look like now:

https://www.drcarney.comhttp//domain.comfinder_indexer.php/blog/entry/protect-your-prostate-from-cancer

So, now all that has to be removed is the http//domain.comfinder_indexer.php string.

Sean

I had run the indexer to intentionally break the EasyBlog search urls. But, the kind folks at CloudAccess.net actually came behind me and 'fixed' it all again. So, I can run the indexer with the Smart Search - EasyBlog Posts plugin enabled if you want me to in order to break the search urls. Right now there are NO EasyBlog posts indexed. If we run the updater they will be indexed but the URLs will be broken.

You have my permission to turn on the plugin and run the updater script in order to see the problem. '

Sean Carney

I wonder if the fix for this ticket:
https://stackideas.com/forums/smart-search-generated-urls-to-user-profiles-give-404-errors

might actually be what broke the Smart Search - EasyBlog Posts links?

Sean

I am sorry for the delay of this reply is because yesterday we pushed release 4 components + 2 app at yesterday,

I've checked in your site, it seems like this plugin causing the issue "System - Highlight", I already help you disabled it and re-index again with those Easyblog post from your smart search, can you check again is it work fine now?

It looks to be working now. Do you know if System - Highlight is a core Joomla plugin?

Or, do you think this is something I must have added at some time in the past?

I am sure curious how you figured this out. We were baffled but the guys at cloudaccess.net were pretty sure you would get to the bottom of things. :-)

Thanks, Sean

Hello Sean,

This plugin is shipped with Joomla by default. Not entirely sure why this plugin is conflicting, but will check with Arlex tomorrow.

Thank you very much. To be honest I do not even understand the function of that plugin and whether or not it is something we want to use. But, for now I am grateful to have the Smart Search working properly.

You're welcome Sean, currently I am not really sure why this plugin conflict with this, but when you disabled this plugin from backend, it will not cause any other issue.

As a gentle reminder, kindly start a new thread if you have any other issue in the future so it will be easier for us to manage your inquiry. I will lock and mark this thread as resolved.