[#40503] - [5.0] Error Message during installation
- Closed
- 29 Apr 2023
- Medium
- Build: 5.0
- # 40503
Steps to reproduce the issue
During the installation of Joomla 5.0.0-dev I got the following message:
Joomla\Filesystem\File::write(): Argument #2 ($buffer) cannot be passed by reference
The installation itself (frontend and backend) was successful
Expected result
No failure message
Actual result
See above message
System information (as much as possible)
Database Type mysql
Database Version 5.7.41-log
Database Collation latin1_swedish_ci
Database Connection Collation utf8mb4_general_ci
Database Connection Encryption None
Database Server Supports Connection Encryption Yes
PHP Version 8.1.16
Web Server Apache
WebServer to PHP Interface cgi-fcgi
Joomla! Version Joomla! 5.0.0-dev Development [ Schnitzel ] 29-August-2022 12:18 GMT
Additional comments
| Labels |
Removed:
?
|
||
joomla-cms-bot
- | Labels |
Added:
No Code Attached Yet
|
||
| Status | New | ⇒ | Closed |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2023-04-29 19:15:44 |
| Closed_By | ⇒ | Hackwar |
I think this issue happens also with 4.4-dev. I haven't checked yet, but from code review this should be the case. If someone is faster than me to check this, please do and report back here.
I just have tested and can reproduce the issue also on the 4.4-dev branch.
loaded 4.4.0-dev and confirm issue during installation
During the installation of Joomla 5.0.0-dev I got the following message:
I don't see an error message. Even a reinstall showed no error.
Did I miss something? Where was it seen?
System Information
php: Windows ....
dbserver: mysql
dbversion: 10.4.25-MariaDB
dbcollation: utf8mb4_unicode_ci
dbconnectioncollation: utf8mb4_general_ci
dbconnectionencryption:
dbconnencryptsupported: false
phpversion: 8.1.10
server: Apache/2.4.54 (Win64) OpenSSL/1.1.1p PHP/8.1.10
sapi_name: apache2handler
version: Joomla! 5.0.0-dev Development [ Schnitzel ] 29-August-2022 12:18 GMT
useragent: Mozilla/5.0 (Windows NT 10.0)
Thanks. This is completely new to me. Is there any documentation about that?
@sandewt It is like that since ages (3.4 or 3.5 or so) and there is some documentation but I won't have the time to search for it now. If you make a new installation and the database host is not equal to localhost or 127.0.0.1, that thing with the file happens. If you have your website since longer time and always updated it you won't have noticed that.
It was 3.7 when this was established.
It was 3.7 when this was established.
That's correct @richard67
"..... we require you to delete a file in the installation folder that was randomly created by the installer" (from your link)
Yes, that is known, but then you got a message similar to: delete the xzy.txt file. Only then did the installation go through.
But here it is different situation: it gives a different message than above and the installation still goes through, without deleting a txt file.
But here it is different situation: it gives a different message than above and the installation still goes through, without deleting a txt file.
Yes, I know. I was only answering @sandewt question. Due to the issue here, that text file is not written. When that error is fixed, it will work again. But it needs to close the browser between the 2 tests because when you have tested it before with the error and now fix the error, there is still the saved state of that localhost check in the session saved in the browser. But that's something for experts. Normally it works as described.
Please test #40504 if that fixes your issue. Since we have a PR, I'm closing the issue.