Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-users
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Netdot-users digest..."
Today's Topics:
1. Re: Netdot 1.0-git CNAME issue (Carlos Vicente)
----------------------------------------------------------------------
Message: 1
Date: Fri, 14 Sep 2012 20:56:24 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Netdot 1.0-git CNAME issue
To: Vincent Magnin <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Hi Vincent,
I believe that your fix is correct. I will apply it.
Thank you.
cv
On 9/13/12 8:28 AM, Vincent Magnin wrote:
> Hi,
>
> I've a possible fix (this might break other things) for my CNAME issue:
>
>
> diff --git a/htdocs/management/host.html b/htdocs/management/host.html
> index 02e22bd..7019d76 100644
> --- a/htdocs/management/host.html
> +++ b/htdocs/management/host.html
> @@ -124,7 +124,7 @@ if ( $submit ){
> # Also, if RR was just updated, this re-reads it
> from the DB
> # to avoid the old values from showing up
> my $newrr = RR->retrieve($newid);
> - $rrs{$newrr->id} = $newrr if defined $newrr;
> + $rrs{$newrr->id} = $newrr if (defined $newrr &&
> $id == $newid);
>
> }
> })
>
> This will prevent a second RR to be displayed (on my issue, %ret
> contains the RRCNAME id instead of RR id).
>
>
> Regards,
>
>
> Vincent
>
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
>
--
cv
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 46, Issue 12
********************************************
