[imp] IMP 2.2.7/RH 7.1/PostgreSQL

[Brent J. Nordquist]

On Sat, 1 Dec 2001, Eric Jon Rostetter <eric.rostetter@physics.utexas.edu>...:

> > > Warning: 5 is not a valid PostgreSQL link resource in
> > > /var/www/html/horde/imp/lib/db.pgsql on line 113
> 
> So my point is, you might try to remove the persistent pgsql
> connections and see if they go away.  Some old messages on the list
> can help you do this, but basically it is removing the "p" character
> from some calls (I think it means changing pconnect to connect, but my
> memory may not be 100%).

That's it exactly.  Check the lists; remove the "p".

-- 
Brent J. Nordquist <bjn@horde.org> N0BJN       / OPN: #horde
Yahoo!: Brent_Nordquist / AIM: BrentJNordquist / ICQ: 76158942



>From chuck@horde.org Date: Sat,  1 Dec 2001 13:57:52 -0500
Return-Path: <chuck@horde.org>
Mailing-List: contact imp-help@lists.horde.org; run by ezmlm
Delivered-To: mailing list imp@lists.horde.org
Received: (qmail 21906 invoked from network); 1 Dec 2001 18:58:32 -0000
Received: from h00104bc60b3c.ne.mediaone.net (HELO marina.horde.org) (24.91.196.127)
  by clark.horde.org with SMTP; 1 Dec 2001 18:58:32 -0000
Received: by marina.horde.org (Postfix, from userid 33)
	id 1991039E9; Sat,  1 Dec 2001 13:57:53 -0500 (EST)
Received: from 192.168.0.113 ( [192.168.0.113])
	as user chuck@localhost by marina.horde.org with HTTP;
	Sat,  1 Dec 2001 13:57:52 -0500
Message-ID: <1007233072.3c092830e5642@marina.horde.org>
Date: Sat,  1 Dec 2001 13:57:52 -0500
From: Chuck Hagenbuch <chuck@horde.org>
To: imp@lists.horde.org
References: <LKEDKBHIPIPMIFJFACFHOEOICGAA.mcoughlan@gothambroadband.com>
In-Reply-To: <LKEDKBHIPIPMIFJFACFHOEOICGAA.mcoughlan@gothambroadband.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 4.0-cvs
Subject: Re: [imp] "Illegal or malformed form data" for upload_max_filesize

Quoting Mike Coughlan <mcoughlan@gothambroadband.com>:

> Is it possible to give a more verbose error than when you hit the
> upload_max_filesize limit for attachments?  Is this direct output from php?

No, but php doesn't give us much of a chance to handle it gracefully. I've 
tweaked the error reporting; the possibility of the file being too large is 
mentioned in all cases now, and the max filesize is included in the error 
message.

> Finally, I might suggest making the error.gif and message clickable, so that
> it takes you to the help, someplace that explains the error in detail.

That's a pretty cool idea, but it won't happen anytime soon without some help.

-chuck

--
Charles Hagenbuch, <chuck@horde.org>
"What was and what may be, lie, like children whose faces we cannot see, in the
arms of silence. All we ever have is here, now." - Ursula K. Le Guin