General Questions/New to Joomla! 4.x • Indexing articles with Sourcerer code results in HTTP 500 status

Hi everybody,

I have recently (mostly) successfully updated my J!4.4.6 site first to J!4.4.7 and later to J!4.4.8. Thanks to the team. Due to the pagination issue that was reported by Phil in viewtopic.php?f=9&t=1011270. I decided to switch from the old "Search" to the new "Smart Search". However, while indexing the articles of my website, the indexing process was always prematurely terminated by the following error:

Smart Search Indexer

The following message was returned by the server:
An error has occurred while fetching the JSON data: HTTP 500 status code.

Unfortunately, I found no further hint on the root cause of that error. However, my website uses sourcerer code in some articles. So, I wondered if maybe the sourcerer code may have caused or contributed to the problem. Indeed it turned out, when the sourcerer code was removed, the indexing process succeeded without any error. However, this is not the whole story.

Configuration of my website

• PHP8.2
• Joomla!4.4.7/8 (both are affected)
• Sourcerer 10.1.3
• Bilingual website (1st language German, 2nd language English)
• The website has for each language 3 articles that include sourcerer code in order to create custom forms

Example of Sourcerer Code in German article (ID = 123)
<p>{source}&lt;?php include JPATH_SITE.'/sourcerer/demo_de.php'; ?&gt;{/source}</p>

Example of Sourcerer Code in corresponding English article (ID = 124)
<p>{source}&lt;?php include JPATH_SITE.'/sourcerer/demo_en.php'; ?&gt;{/source}</p>

Inspection of the indexed article shows,

• that the last successfully indexed article is the one with ID=123 (German article)
• that indexing is overall successful, if the sourcerer code is completely removed from all English articles (as 2nd language the IDs of the English articles are always larger than the IDs of the German articles).

I have already informed the developer of sourcerer, but also thought that it may be helpful for the Joomla community in general to learn about this problem. Maybe somebody can offer a simple solution?

Kind regards
Tom

Statistics: Posted by Tom6293 — Thu Aug 29, 2024 6:34 pm

---