Have created 2 sites from different blueprints in 2.3.3. In both new sites, the original domain from the blueprint remains. Easy enough to fix after a minute or two head scratching. During the new site creation, the status does stay on “updating domain name” for more than a few minutes.
Same here, after upgrading from 2.2.4 to 2.3.3.
When adding new sites from blueprints created in 2.2.4, the newly-created website keeps the blueprint’s Site Title and address. And I can’t get into admin dashboard at all, since it redirects to ‘blueprint.local’.
The workaround is going to Adminer and edit wp_options to the new address, which makes me able to access the dashboard.
But I’m not comfortable using this blueprint since there might other issues caused by the update.
The issue doesn’t happen with blueprints created on 2.3.3. I also can’t tell about blueprints created on other versions since 2.2.4 and 2.3.3 were the only ones I’ve ever used.
Edit: Unlike OP, I don’t see anything unusual during site creation and it’s pretty quick. Granted, my blueprints’ tables are pretty much vanilla with not a lot of entries.
Update: I said previously that new blueprints created on 2.3.3 worked. But that’s only if they’re made from sites created on 2.3.3. Creating a new blueprint from an old site also brings up the same problem when this blueprint is used.
Also, updating the old sites’s environment to 1.3.1 makes no difference.
Had to reply in a new post to be less confusing.
Following the last update on ‘old vs new’ websites, this time I tried just to change the sites domains straight from Local interface:
Sites created on version 2.2.4 or from a blueprint from 2.2.4 or cloned from a site created on 2.2.4: Domain change on Local is not applied to DB.
Same as above but 2.3.3: Domain change works well.
Environment: Apache, PHP 7.2.0, MySQL 5.6.34
This is the log for both cases:
====CHANGE DOMAIN OF OLD SITE===
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/wpSearchReplaceDomain] Changing database domain for 06fccc4cff0a45399e516ec1cfd29f0541fd181260964a6eafafe8297d74a761
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/addApacheHtaccess] .htaccess already exists at C:\Users\dalmo\Local Sites\aa2
Sep 6, 2018, 4:11 PM GMT+12 - info: [EnvironmentCustom] Changing Apache conf for 06fccc4cff0a45399e516ec1cfd29f0541fd181260964a6eafafe8297d74a761
Sep 6, 2018, 4:11 PM GMT+12 - info: [EnvironmentCustom] Restarting Apache
Sep 6, 2018, 4:11 PM GMT+12 - info: [EnvironmentCustom] Output after restarting Apache
{ stderr: '',
stdout: 'OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \\"service, apache2\\": executable file not found in $PATH": unknown' }
Sep 6, 2018, 4:11 PM GMT+12 - info: [EnvironmentCustom] nginx conf does not exist so it doesn't need changed.
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/docker-router] getRouterContainers()
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/docker-router] teardown()
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/docker-router] Removing router container 18dae46d4448d8daa9580181981ae8b0bc74e8b89713a10a96165665429d19f0
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/docker-router] updateProxyManager()
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/hosts-helper] hostsHelper: Updating hosts with 192.168.95.100 true
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/hosts-helper] hostsHelper: Updated hosts.
{ stdout: '', stderr: '' }
Sep 6, 2018, 4:11 PM GMT+12 - warn: [main/SiteModel] wpInstalled not returning "installed"
{ stdout: 'Deprecated: Directive \'track_errors\' is deprecated in Unknown on line 0\ninstalled',
stderr: '' }
Sep 6, 2018, 4:11 PM GMT+12 - warn: [main/SiteModel] wpInstalled not returning "installed"
{ stdout: 'Deprecated: Directive \'track_errors\' is deprecated in Unknown on line 0\ninstalled',
stderr: '' }
and
====CHANGE DOMAIN OF NEW SITE===
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/wpSearchReplaceDomain] Changing database domain for 2ad5926814b8e29c93e2cacfcae0233bd27e84d7b3689e65464c889456745a0b
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/docker-router] getRouterContainers()
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/docker-router] teardown()
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/docker-router] Removing router container 2edfee9fa9130308f087e0cff8d756bc0117d81701a3462c15d4412f6ab28ebe
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/docker-router] updateProxyManager()
Sep 6, 2018, 4:11 PM GMT+12 - info: [main/hosts-helper] hostsHelper: Updating hosts with 192.168.95.100 true (...)