When clicking “Check for Updates”, the screenshot below is showing the first portion of what shows in the network tab, but I’m not seeing any reference to workspace/packages/update-remote
I apologize for my ignorance on this, but where should I be looking? Should I click on the name of one of these specific items and looking at the “Headers” tab?
When you click the “Check for Updates” button, it should add only one new request at the bottom of the list.
(Maybe delete the list before clicking the button or filter it to only show “XHR” requests).
Then when you click the request in the list, a new window opens (on the right side) with different tabs. You can see the request parameters in the “Request” tab and the JSON-response in the “Response” tab.
In your browser, it probably looks slightly different.
Thanks for the clarification. I switched to Firefox from Chrome, so now we are on the same page.
When I click “Check for Updates”, it did load an additional request with the action you had mentioned, but this request along with a few others are 404. In the Headers tab, it says that it is posting to /connectors/index.php, which has the 404 status, but that file is in place on the server.
Every AJAX-request goes to this “connector”. The action parameter then determines what “processor” gets executed. In this case it’s the file core/model/modx/processors/workspace/packages/update-remote.class.php.
In the processor the code makes a request to the MODX API to check if there are updates.
The URL is something like this https://rest.modx.com/extras/package/update?signature=ace-1.9.3-pl (there are additional parameters). Can you open this URL in the browser?
Here’s what was added to the error log after making your suggested changes, and “checking for updates”. It appears these same errors were happening before as well, as they are showing in the error log as well.
[2023-03-01 21:19:44] (ERROR in xPDO::getService @ /home/mysite/core/xpdo/xpdo.class.php : 1235) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:44] (ERROR in modRestCurlClient::__construct @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 26) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:44] (ERROR @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 42) curl request to https://rest.modx.com/extras/package
[2023-03-01 21:19:44] (ERROR in xPDO::getService @ /home/mysite/core/xpdo/xpdo.class.php : 1235) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:44] (ERROR in modRestCurlClient::__construct @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 26) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:44] (ERROR @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 42) curl request to https://rest.modx.com/extras/package
[2023-03-01 21:19:46] (ERROR in xPDO::getService @ /home/mysite/core/xpdo/xpdo.class.php : 1235) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:46] (ERROR in modRestCurlClient::__construct @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 26) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:46] (ERROR @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 42) curl request to https://rest.modx.com/extras/package/update
[2023-03-01 21:19:50] (ERROR in xPDO::getService @ /home/mysite/core/xpdo/xpdo.class.php : 1235) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:50] (ERROR in modRestCurlClient::__construct @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 26) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:50] (ERROR @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 42) curl request to https://rest.modx.com/extras/package/update
[2023-03-01 21:19:52] (ERROR in xPDO::getService @ /home/mysite/core/xpdo/xpdo.class.php : 1235) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:52] (ERROR in modRestCurlClient::__construct @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 26) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:52] (ERROR @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 42) curl request to https://rest.modx.com/extras/package/update
[2023-03-01 21:19:52] (ERROR in xPDO::getService @ /home/mysite/core/xpdo/xpdo.class.php : 1235) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:52] (ERROR in modRestCurlClient::__construct @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 26) modRestClient::__construct is deprecated since version 2.3.0. Use the modRest classes instead.
[2023-03-01 21:19:52] (ERROR @ /home/mysite/core/model/modx/rest/modrestcurlclient.class.php : 42) curl request to https://rest.modx.com/extras/package/update
I did apply that other change mentioned as well. After I made the changes you mentioned to that PHP file, I cleared the cache and refreshed before trying the Installer page again.
I added this as a snippet called “testSnip”, then added [[testSnip]] to the bottom of one of our web pages. When I refreshed the page, I got a 503 error.
Nothing appears to have been logged, but based on the date/time stamps on the error logs, is it possible that the error log files are only updated once a day by the host (godaddy)?
I’ve tested this by forcing the same 503 error again, and a few moments later downloading the error log to see if it had been changed, but it is the same as the copy I downloaded 10 minutes ago.
When you go the “System Info” page in the MODX manager (manager/?a=system/info) and click the “View” link in the line “phpinfo():”, is there a cURL section on the phpinfo page and is cURL support enabled?
Maybe you could also ask your host if they changed anything recently concerning cURL.
It’s been a few weeks, but I finally had a chance to chat with GoDaddy for support on my issue.
They created a cURL test file, and it appeared to be working fine. They said there were no issues on the Godaddy server & also checked the system logs and the server is functioning fine.
After that, I tried again to use the code below, which generated a 500 error, but the error logs still did not show any issue. When I brought this up to GoDaddy, they said I may need to change things to access the proper error logs. I’ve listed their instructions below as well - please let me know if you have any other advice on where to go from here. Thanks!
Abid A at 8:04, Mar 21:
Let me check what’s best can be done on this.
You can review the error logs by going to Cpanel admin > File Manager > error_log file
You can also follow the below link article to set up PHP error log : Setup PHP error logging | Linux Hosting (cPanel) - GoDaddy Help US
You at 8:07, Mar 21:
Thanks for the link and suggestion, but I do not see the “.user.ini” file in the location suggested