Error message after renaming the Laragon folder

[slolo2000]

Hello,

This is probably a stupid question but I get an error message when I start Apache since I renamed the Laragon folder from Laragon7 to Laragon

As noted on this web page, I thought Laragon was naturally portable (cf. https://laragon.org/docs/portable)

I know that I simply have to change the folder in the L:\Laragon\etc\apache2\mod_php.conf file but I would like to know if this is a bug or not?

# This file is auto-generated, so please keep it intact.
LoadModule php_module "L:/laragon7/bin/php/php-8.3.14-Win32-vs16-x64/php8apache2_4.dll"
PHPIniDir "L:/laragon7/bin/php/php-8.3.14-Win32-vs16-x64"
<IfModule mime_module>
    AddType application/x-httpd-php .php
</IfModule>

And as you can see on the image below, I do not have anymore PHP 8.3.14, I have replaced it by 8.3.15.
Maybe that's where the problem comes from?

After having renamed Laragon7 to Laragon in the previous file, I have also found Laragon7 in the following file:
L:\Laragon\etc\apache2\fcgid.conf (which is read only)

LoadModule fcgid_module "L:/laragon7/etc/apache2/modules/mod_fcgid-2.3.10-win64-vs16.so"

<IfModule fcgid_module>
FcgidInitialEnv PATH "L:/laragon7/bin/php/php-8.2.27-nts-Win32-vs16-x64;C:/Windows/system32;C:/Windows;C:/Windows/System32/Wbem;"
FcgidInitialEnv SystemRoot "C:/Windows"
FcgidInitialEnv SystemDrive "C:"
FcgidInitialEnv TEMP "C:/Windows/Temp"
FcgidInitialEnv TMP "C:/Windows/Temp"
FcgidInitialEnv windir "C:/Windows"

# 10 hrs: in case you have long running scripts, increase FcgidIOTimeout 
FcgidIOTimeout 36000
FcgidConnectTimeout 16
FcgidMaxRequestsPerProcess 0
FcgidMaxProcesses 50
FcgidMaxRequestLen 81310720
# Location php.ini:
FcgidInitialEnv PHPRC "L:/laragon7/bin/php/php-8.2.27-nts-Win32-vs16-x64"
FcgidInitialEnv PHP_FCGI_MAX_REQUESTS 0

<Files ~ "\.php$>"
AddHandler fcgid-script .php
Options +ExecCGI
FcgidWrapper "L:/laragon7/bin/php/php-8.2.27-nts-Win32-vs16-x64/php-cgi.exe" .php
</Files>
</IfModule>

And above all, am I not likely to have other files with this type of path problem?

Thanks in advance for your answer.

Edit:
I am so stupid, the read only attribute was made by myself (see this discussion: #484)

[leokhoa]

@slolo2000 : Thank you for your update. Making mistakes is part of our being human. As you mentioned the issue is due to the file being read-only, Can you confirm that Laragon is portable?

[slolo2000]

@leokhoa : As I explained in my post, the problem of read only file was due to a known bug (see this discussion: #484)
I have tested again with a fresh install of Laragon 7.0.3 (and 7.0.4 and 7.0.5) and I have no more problem when switching Apache version.

[leokhoa]

@slolo2000 : Gotcha. I have marked it as Fixed in Laragon 7.0.3. Thanks for re-testing & updating me.