public inbox for [email protected]  

help / color / mirror / Atom feed

From: Dave Page <[email protected]>
To: Robert Treat <[email protected]>
To: Josh Berkus <[email protected]>
Cc: Bruce Momjian <[email protected]>
Cc: PostgreSQL www <[email protected]>
Subject: Re: Event item duplication
Date: Thu, 12 Aug 2004 08:39:10 +0100
Message-ID: <E7F85A1B5FF8D44C8A1AF6885BC9A0E41A76D2@ratbert.vale-housing.co.uk> (raw)

 

> -----Original Message-----
> From: [email protected] 
> [mailto:[email protected]] On Behalf Of Robert Treat
> Sent: 11 August 2004 19:35
> To: Josh Berkus
> Cc: Bruce Momjian; PostgreSQL www
> Subject: Re: [pgsql-www] Event item duplication
> 
> I noticed the same thing last night and figured someone was 
> editing it... well, for some reason the event page is not 
> rebuilding properly, though I don't see anything particularly 
> wrong with it...Dave, do you see anything in the logs?  I've 
> manually hacked it for now, let's see if the problem comes back.

It's caused by this:   

  // The following line was added by Devrim on July, 29th, 2003
  if ($summary != $details) {
    $data .= str_replace("\n", "<br>", $summary);
    $data .= "<br>";
  }
  $data .= str_replace("\n", "<br>", $details);


In other words, unless the summary is identical to the main body, it
will display both. I'm not sure why Devrim added that, but there was
probably what seemed like a good reason at the time.

I've changed it to only display the summary if there is no body (as per
the news).

Regards, Dave.

view thread (8+ messages)

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Event item duplication
  In-Reply-To: <E7F85A1B5FF8D44C8A1AF6885BC9A0E41A76D2@ratbert.vale-housing.co.uk>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox