Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 6C4CC98F703 for ; Tue, 5 Jun 2012 03:07:49 -0300 (ADT) Received: from mail-lpp01m010-f46.google.com ([209.85.215.46]) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1Sbmvk-0003wB-BT for pgsql-www@postgresql.org; Tue, 05 Jun 2012 06:07:49 +0000 Received: by lahd3 with SMTP id d3so3529143lah.19 for ; Mon, 04 Jun 2012 23:07:33 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=Dhh3IbecdsszNbZ3cjifLdMAs3nB5Uxr5QeeRxieyO8=; b=ChngyJ0kMfu/QiJ2488+zzKNo633/7q5xVJ7AzfTpF5L+izVrEkli/v+HGq75KdgUY yOxqvInSSUZV/jMSLbojjlFdD8U3/gQSj6ZrNImBwHmF6Mit963ZN+XsDnZkmX3jElFr aRqmHkMSPCXq8drCqHZnfj5/xU06cODk87Rc+0my1+URXZYoFTMEeRZ5DU3+2Tk/+h4a BofEDLLjV3Dvo+mPMqzhPP0tcFOLOoSJyYwb2LHaalQbTlwIQYBBeW0P/Zf5JiyfMYIm R5Tet9tAhT5MRhlFJJCE4sKIIg2CXfBLOkxU/8yTeXj50bD3yLSpinSAic2N6bD+tLTd Ti0A== MIME-Version: 1.0 Received: by 10.112.32.35 with SMTP id f3mr7352257lbi.47.1338876453719; Mon, 04 Jun 2012 23:07:33 -0700 (PDT) Received: by 10.152.21.234 with HTTP; Mon, 4 Jun 2012 23:07:33 -0700 (PDT) In-Reply-To: References: Date: Tue, 5 Jun 2012 08:07:33 +0200 Message-ID: Subject: Re: Broken links From: Magnus Hagander To: Emanuel Calvo Cc: PostgreSQL WWW Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlGhdhR6Hk3NCwGqM3oneCFeFqAxC4JO5Xo0FGEegVTYh2DMMhTCgu4S7fxQ/BUZS9AAFOO X-Pg-Spam-Score: -2.6 (--) X-Archive-Number: 201206/4 X-Sequence-Number: 20698 On Mon, Jun 4, 2012 at 1:46 PM, Emanuel Calvo wrot= e: > The html for links seems broken in the news pages: > > http://www.postgresql.org/about/news/1393/ > http://www.postgresql.org/about/news/1396/ Hi! Those are uploaded by the respective company, so it's up to them to make sure it's fixed. I can see that one of them has been fixed already. Of course, they should probably not have been approved by the moderator in the first place - goes to show that it wasn't sufficiently checked. But there's not much to do about that. I've added a ticket for making it more obvious (as in, giving a proper error message and not just instructions for not doing it) when HTML markup is used in a field where HTML is not allowed. That should decrease the risk of it happening more times. --=20 =A0Magnus Hagander =A0Me: http://www.hagander.net/ =A0Work: http://www.redpill-linpro.com/