Thank you for your patience, everyone. We are actively addressing the issue.
Next week, we will release version 4.0.1.
This update includes fixes for the installer to ensure compatibility with environments where it may not have functioned properly before. Additionally, it will contain security enhancements aimed at identifying and mitigating common installation issues at the code level. This will resolve specific installation issues, including those related to .htaccess.
We also plan to release a Docker image with the updated system version (4.0.1) shortly after the main release.
Hello MrCellSbst!
Are you sure you replaced the “my-server” placeholder with the name of your server?
Please let me know what error response you get and what your PHP version is.
Hi,
We are adding additional validation to the “.htaccess” file; however, the validation will be included in the next release.
After unzipping/pulling/moving the MintHCM files into the destination folder, ensure that the .htaccess file exists. The file’s permission should be set to 644, and the owner of the file should be set to either www-data or apache, depending on your environment.
Before installation:
If you don’t see the file you can copy it from the repository.
The file should look like this:
Options +SymLinksIfOwnerMatch
RewriteEngine On
RewriteRule ^api/(.*?)$ install/index.php [L]
RewriteRule ^assets/(.*?)$ assets/$1 [L]
RewriteRule ^favicon.ico$ favicon.ico [L]
RewriteRule ^bg.jpg$ bg.jpg [L]
After installation, the .htaccess should look like this:
Options +SymLinksIfOwnerMatch
RewriteEngine On
RewriteBase /
RewriteRule ^assets/(.*?)$ assets/$1 [L]
RewriteRule ^legacy/(.*?)$ legacy/index.php/$1 [L]
RewriteRule ^api/(.*?)$ api/index.php [L]
RewriteRule ^bg.jpg$ bg.jpg [L]
RewriteRule ^favicon.ico$ favicon.ico [L]
RewriteRule .* index.html [L]
Replace with your directory name.
For example,
if your instance is in the directory: /var/www/develop,
and within the develop directory, you have files like this: .htaccess, index.html, and directories: legacy, api, assets…
In this example, RewriteBase is /develop.
Please make sure that you have the correct settings in the following files:
api/configs/mint/config_override.php
api/app/Config/AppConfig.php
legacy/config.php
legacy/config_override.php
Thank you Vincent for the suggestion! We will keep this in mind. 🙂
Abhishek, did you try to clear the cookies too just like Vincent?
Hello Mesfin! MintHCM 4 is not available for PHP 8.2, only version 7.4-8.0. You can find all the requirements in the Installation Guide: https://minthcm.org/support/minthcm-installation-guide/
Hello Vincent!
We need information from the dev tools in the Network tab to check if any of the requests failed. Could you tell us if any of them are highlighted in red? Also, could you provide information about what came in the response to that Request?
Did you manage to finish the installation despite the warning? The warning doesn’t stop the code from running, so the installation should proceed smoothly.
If the installation goes well, you can carry on with your work. We’ll look into the issue and make any needed improvements in the next system update.
Thank you for your question, and I apologize for the delay in our response due to the holiday season.
Regarding your inquiry about installing MintHCM on Plesk, while we do not have a specific manual for this installation, you should have access to all the necessary server settings required for the installation. To get started, please ensure that your server meets the minimum requirements for running MintHCM as outlined in the MintHCM documentation. Then, follow the standard MintHCM installation instructions and configure any Plesk-specific server settings as needed.
If you encounter any issues during the installation process, please don’t hesitate to reach out to the MintHCM community for assistance. There are many experienced MintHCM users who are happy to help and provide guidance on any installation issues you may encounter.
If you have any further questions or concerns, please let us know.
Hello!
The answer to what happened should be in the minthcm.log file, which can be found in the instance’s main directory, on the same level as index.php. You should also be able to find the install.log file there as well.
Hello!
Yes, we are planning to upgrade PHP in MintHCM. PHP 7.4 should be supported by the end of the first quoter of 2023. Then, PHP 8.1 would be supported by the end of the third quoter of 2023.
We will keep you informed on our forum when the PHP is upgrade up to PHP 7.4 and 8.1.
Hello! Thank you for contacting us! We’re glad that you want to use MintHCM in your company.
To book a consultation, please send us an email at contact@minthcm.com. Our consultants will schedule a meeting with you. 🙂
Hello! Can you send us on contact@minthcm.org your minthcm.log file, install.log file and (if it is possible) php logs.
It allows us to find a problem and solution.
Hello,
Can you send minthcm.log file, install.log file and (if it is possible) php logs.
It allows us to find a problem and solution.
Please, send them to contact@minthcm.org.
Best regards!
Hi Raja!
There are only warning messages. It means that isntall process can work correctly.
Has install process finished well? If not I need also logs from minthcm.log, and install.log. The files are in main folder of MintHCM instance.
Best regards!
Hello,
Thank you very much for sharing this!
We are sure, it will help a lot.