Qurius
-
Posts
53 -
Joined
-
Last visited
Reputation Activity
-
Qurius got a reaction from Paul in 500 error with just one client ID
Thanks Paul -
Pilot error...when I checked the uploads directory in Settings> System > General earlier it looked correct ending in uploads/ . The fields visual portion was truncating the full path and it actually had /system added to it. Sorry, I feel stupid for not fully double checking that earlier.
Thanks again for your help
-
Qurius got a reaction from Paul in Piping stopped working
When I did the manual pipe it was clear that IMAP and Mailparse weren't enabled after all on the server. Looks to be working now so thank you for the help.
-
Qurius reacted to Paul in Piping stopped working
Check also that PHP IMAP and Mailparse are in your CLI PHP. Your ../logs_blesta/ error logs may have more information. Trying to pipe manually via SSH as in the test case described in the docs should help to narrow it down.
-
Qurius got a reaction from Paul in 4.4.0 dashboard issues
Thanks for the help. I used FileZilla for the upload and didn't get any upload errors so assumed everything was good. I did a compare and indeed that one app.min.js file was missing on the server and after adding it the issue resolved. However, also noticed that other file sizes were mismatched so I think I'll do another upload to be on the safe side.
Thanks again for everyone's input
-
Qurius got a reaction from Michael in PHP 7.1upgrade issues
Thank you BlestaStore and GosuHost for your offers of help but I think I can see what's happened and feel kinda stupid for not realizing this sooner. I believe that the error was related to the cron job which was using the old path to php (/usr/local/bin/php) and that would have used PHP 5.6 since after the upgrade was set as the default PHP version. When I changed the path to be /usr/local/bin/ea-php71 it doesn't look like the error is repeating.
Thanks again!
-
Qurius got a reaction from Beav in PHP 7.1upgrade issues
Thank you BlestaStore and GosuHost for your offers of help but I think I can see what's happened and feel kinda stupid for not realizing this sooner. I believe that the error was related to the cron job which was using the old path to php (/usr/local/bin/php) and that would have used PHP 5.6 since after the upgrade was set as the default PHP version. When I changed the path to be /usr/local/bin/ea-php71 it doesn't look like the error is repeating.
Thanks again!
-
Qurius got a reaction from MineHarvest66 in PHP 7.1upgrade issues
Thank you BlestaStore and GosuHost for your offers of help but I think I can see what's happened and feel kinda stupid for not realizing this sooner. I believe that the error was related to the cron job which was using the old path to php (/usr/local/bin/php) and that would have used PHP 5.6 since after the upgrade was set as the default PHP version. When I changed the path to be /usr/local/bin/ea-php71 it doesn't look like the error is repeating.
Thanks again!
-
Qurius got a reaction from Paul in PHP 7.1upgrade issues
LOL... Paul I missed your post before I did mine and you are right
-
Qurius got a reaction from Paul in PHP 7.1upgrade issues
Thank you BlestaStore and GosuHost for your offers of help but I think I can see what's happened and feel kinda stupid for not realizing this sooner. I believe that the error was related to the cron job which was using the old path to php (/usr/local/bin/php) and that would have used PHP 5.6 since after the upgrade was set as the default PHP version. When I changed the path to be /usr/local/bin/ea-php71 it doesn't look like the error is repeating.
Thanks again!
-
Qurius got a reaction from Michael in Cpanel module not retreiving packages
OK...upgraded and I see the server group and cpanel packages are now appearing when creating a package. Thx
-
Qurius got a reaction from niyo in Invoice "pay Now" Timing Out?
Yes...I see the documentation about the Root Web Directory pertaining to sub-domains was just updated and that helps.
-
Qurius got a reaction from Michael in Invoice "pay Now" Timing Out?
Yes...I see the documentation about the Root Web Directory pertaining to sub-domains was just updated and that helps.