Progress Report:
I have some updates to share. One of the data elements passed to Zapier included the filename of the file uploaded from the form. This filename might originally have been in Japanese before the upload, and the form program converts the filename to alphanumeric characters during the upload.
It seems there was an issue with this conversion method, and after changing the conversion method and passing the data to Zapier, the nature of the error changed.
Previously, the following error was encountered:After changing the filename conversion method, the error changed to:Since this error change, when a Joomla article is created via the API, the article can now be confirmed in the backend as well. Data is also being created in the #__workflow_associations table.
It seems the issue I reported earlier, where data was not being created in the #__workflow_associations table, was not due to Joomla Core APIs but rather due to the filename conversion method.
However, despite the change in the nature of the error, the HTTP Status Code: 500 error persists, so it is still important to monitor the possibility that there might be a bug in the Joomla Core APIs.
I have some updates to share. One of the data elements passed to Zapier included the filename of the file uploaded from the form. This filename might originally have been in Japanese before the upload, and the form program converts the filename to alphanumeric characters during the upload.
It seems there was an issue with this conversion method, and after changing the conversion method and passing the data to Zapier, the nature of the error changed.
Previously, the following error was encountered:
Code:
Exception Type: Joomla\CMS\MVC\Controller\Exception\SaveFile: /home/XXX/public_html/libraries/src/MVC/Controller/ApiController.phpLine: 452Message: Save failed with the following error: Error loading menu: apiCode:
Exception Type: RuntimeExceptionFile: /home/XXX/public_html/libraries/src/MVC/Controller/ApiController.phpLine: 154Message: View not found [name, type, prefix]: articles, html, apiIt seems the issue I reported earlier, where data was not being created in the #__workflow_associations table, was not due to Joomla Core APIs but rather due to the filename conversion method.
However, despite the change in the nature of the error, the HTTP Status Code: 500 error persists, so it is still important to monitor the possibility that there might be a bug in the Joomla Core APIs.
Statistics: Posted by 4creator — Fri May 24, 2024 12:42 am