@Komal-Sharma thanks, the question is when will be.
-
RE: Please add support for PHP 8.1 and PHP 8.2
-
Please add support for PHP 8.1 and PHP 8.2
Currently the PHP error log show deprecation notices and errors if PHP 8.1 or PHP 8.2 is in use, also the cron for manage ticket by email gives error if the PHP used is 8.2
Is time to support those PHP versions, please made a fix and an update asap.
-
RE: File permissions in the case you have throbles installing UVdesk
Check the below these cases and make changes accordingly:
- A web server might don't have permission to allow overriding of the Apache config on a per-directory basis. Allow Override needs to be set to All for the directory block as mentioned below:
<Directory /home/users/var/www/htdocs> Options Indexes FollowSymLinks AllowOverride All Require all granted
-
If your database password contains some special character(such as #$%@) then change your password and make it without special characters.
locate the .env file in your project and make sure APP_ENV=dev when you are doing your setup. -
Allow read-write permission for the below file & folder:
For .env file – chmod 777 -R path of .env file of UVdesk project
For Var folder -chmod 777 -R path of var folder of UVdesk project
For Config folder – chmod 777 -R path of config folder of UVdesk
For Public folder – chmod 777 -R path of the public folder of UVdesk
For Migration folder – chmod 777 -R path of the migration folder of UVdesk -
It happens mainly because of less execution time in the php.ini file.
By default, max_execution_time is 30 sec you need to increase it and restart your server.
Check here how to increase the max-execution time and restart your server.And clear your project cache by:
php bin/console c:c
Now try to install your project.
=> Also, run the below commands in your project root directory:
php bin/console doctrine:migrations:diff php bin/console doctrine:migrations:migrate
And clear the cache of the project:
php bin/console c:c
=> Once you try with the manual installation of uvdesk from here.
-
RE: uvdesk installation stucks at stage 2
@Komal-Sharma Thanks for your help.
Maybe if you cannot improve the fact uploading by FTP create files and folders permission issues, you can evaluate to show an error message if the installation wizard take too long with a link to a guide or instruction about what the issue can be and how to fix it... so user never need wait a support reply to figure out how to continue the installation -
RE: uvdesk installation stucks at stage 2
@User25 Great, I'm happy to read you have now resolved
-
RE: uvdesk installation stucks at stage 2
@User25 this happen some times and we need wait a reply from the UVdesk staff as I'm not a developer. You can try to do again the installation with maybe a database password that has not special characters. I always believe the setup process and the upgrade process should be improved as sometimes create issues, on my point of view and seems you are confirming that.
-
RE: Open ...customer/login throws AuthenticationCredentialsNotFoundException
@IwataNeo I'm happy to read you have updated your PHP because PHP 7.4 is risky as is no more supported and it is old!
I am also happy to read the upgrade of your PHP version from 7.4 to 8.1 resolve the issue!
Thank you for the update!
-
RE: Open ...customer/login throws AuthenticationCredentialsNotFoundException
Ok thanks.
As you invited to follow the user by ticket I am marking this issue as solved here in the forum. Fell free to upddate the discussion when you have debugged the issue by the private ticket @IwataNeo -
RE: Open ...customer/login throws AuthenticationCredentialsNotFoundException
Not at the moment. I've looked into the issue but haven't found anything concrete pertaining to this specific problem. @IwataNeo if it's possible for you to share access to your server hosting the project, please raise a ticket by emailing us at support@uvdesk.com or visiting support.uvdesk.com. We would have to debug at vendor code level and figure out the complete stack trace to see exactly where things went wrong, as at the moment I'm not able to reproduce this issue. I would also suggest you to share your composer.json & composer.lock file so I can test this against the exact packages you have installed.
The only other relevant log message i found in the shared logs was a deprecation notice indicating there might be a update in the flow of symfony's authentication system which I would need to look into, but if that was the case the issue would have been a lot more noticeable across other installations as well.