Drupal 10 beta 2 mysql database installs wrong port on xampp

Created on 15 October 2022, about 2 years ago

Updated 23 February 2023, over 1 year ago

This is my very first report so please be merciful if I made mistakes and let me know how to do better next time.
Step 1.)
I installed Drupal 10-beta 2 by downloading it and it shows by default the mysql port 5432 (or some port similar in the 5000s).
This causes always an error, because on my xampp on linux I get port 3006 by default.
Changing the port on the xampp config file (and restarting it of course) did not help.
What are the steps required to reproduce the bug?
install Drupal from files only without composer installs
What behavior were you expecting?
A proper automatic selection of the active mysql port
What happened instead?
Port 5432 was fillled in into the installer form and changing that port to 3006 did not change a thing.
2.)
Drupal 10 beta 1 (not beta 2) by the wa installs perfectly when using the installer from the downloaded files, port 3006 preconfigured.
So here lies the issue: You only have to compare beta 1 & 2 for the mysql database connections in the installer.
Having taken those php files from beta 1 and put it into beta 2 did however not work so the issue is more complex.
3.)
So I then did install both Drupal 10 beta versions with composer which worked perfectly (after upgrading all php dependencies).
Thereafter the file-installer for Drupal 10-beta 2 works perfectly, giving me port 3006 filled out in the form perfectly.
Since then beta 2 works perfectly in all ways and I use it daily.
I just wanted to let you developers know because else you might run into trouble when releasing it to folks who don't use composer.
I hope this helps, and please contact me to let me know how to help the Drupal community further.

🐛 Bug report

Status

Closed: outdated

Version

10.0 ✨

Component

Install →

Last updated 3 days ago

No maintainer

Created by

true pal

Live updates comments and jobs are added and updated live.

Bug Smash Initiative

Incomplete comments

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Comment over 1 year ago →
🇳🇿New Zealand quietone
@true pal, thanks for reporting this problem with the install of Drupal 10 beta 2. I see that you posted in the Drupal forum about feedback and also successfully updating without composer. Congratulations! I take it from those post that this issue does not need to remain open. If that is incorrect, re-open and explain what needs to be done.

The bug here was not confirmed. It was reported against Drupal 10.0.0-beta 2, which is not supported. I will close this as outdated.

If you are experiencing this problem on a supported version of Drupal reopen the issue, by setting the status to 'Active', and provide complete steps to reproduce the issue → (starting from "Install Drupal core").

Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024