Closed (fixed)
Project:
Hosting
Version:
6.x-0.4-alpha3
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
24 Feb 2010 at 11:57 UTC
Updated:
12 Jun 2014 at 08:59 UTC
Jump to comment: Most recent
Using the latest Aegir install (latest provision (provision-0.4-alpha5), drush (3.0-beta1), drush_make (2.0-beta6) and aegir (0.4 alpha 5) with all the correct modules)
When trying to save an existing site node (to add a redirection), it complains "You have not specified a valid port for this site."
Anyone encountered this? The port is just fine, says 80, db looks fine, it installed fine when I entered the info during the node creation, site works.
Comments
Comment #1
robin van emden commentedFound the solution to this problem:
In a recent migration, for some reason there was no "default platform" defined any more.
Since the code uses this info this when creating the "port" form element, this broke the site form.
Relevant code:
Might also, in general, be useful to check for a default platform show a warning if it isn't there?
Comment #2
butler360 commentedSo how did you fix this? I'm getting the same issue with alpha6.
Edit: Spoke too soon. You edit the platform you want to be the default and there's a checkbox there to make it the default. After that I can add aliases again. Thanks for spotting this problem!
Comment #3
Ian Ward commentedI believe the actual bug is not calling _hosting_site_form_port() with $node->platform here:
See the last line there - which should be called like:
Comment #5
adrian commentedFixed in head.
http://git.aegirproject.org/?p=hostmaster.git;a=commitdiff;h=7f4ba9a11a5...
with modifications.