The first one is strange. We need to merge 7.4.1 and 7.4.30, along with 8.0.0 and 8.0.22, in the app, and that is a ticket the team is working on right now. (Let me know if you think there is value to keeping multiple patch versions of the same major/minor around!). It could be a side effect of Local having two options right now, but we’ll confirm and fix if it is a bug in the flow.
On the second - looking at the diffs, we didn’t make any changes to the Apache config this go around, so I believe it was like that previously. Have you tried removing that line and trying it out? There aren’t any issues off the top of my head, but I’ll go through past changes and see if I can find when that #unless apache got added.
Hi @emmtre - chiming in here on the first point about storing old configs in the wrong folder.
I did some digging, and it seems like this is in fact an issue with there being two different patch versions of PHP available and on your machine at the time of the swap. It will only occur when swapping between two patch versions (same major.minor versions).
However, it doesn’t look like we currently use these old config files again, even when swapping back to that older version. So this shouldn’t cause any bugs aside from confusion if you ever reference those files again. If you think you will, you should be able to just change the folder name - I’m curious, do you ever manually reuse those old configs files?
@adamperry I also noticed that the standard php config file have been adapted for the different php versions so you also have to consider that if you create custom php config files and change between different php versions within Local. I don’t see that you can do something differently to avoid that but maybe a warning text in the Local app that the config files will be overwritten when you apply a change of php version to a site?