On Mon, Jun 25, 2012 at 4:38 PM, Craig Ringer <ring...@ringerc.id.au> wrote: > On 06/25/2012 11:10 PM, Dave Page wrote: > > On Mon, Jun 25, 2012 at 5:41 AM, Craig Ringer <ring...@ringerc.id.au> wrote: > > Dave: Is there any chance the installers link to that page from their error > dialogs, or a static-and-sanitised version of it in docs? If you're ok > updating the installer messages I'll collect up a sanitized version that > doesn't link to other wiki pages (or make it clear they're external) and > convert it for the docs. > > We can't do clickable links in those message boxes, so I'm not sure > how useful it'll be in practice. > > Argh. I've been in the browser-based app too long, I simply forget that URL > handling isn't everywhere. > > The main ones that IMO need a where-to-go-next hint are the messages that > arise when an external process step fails, like initdb, failure to install > the runtime, etc. It's always necessary to ask a poster asking for help for > the installer log - and how many people don't post or ask for help, just get > stuck and confused?
Any ideas for a one-liner to add? I'm struggling to find nice wording, that doesn't invite people to report issues without investigating themselves first: * If you need help, please review http://xxxxxx before seeking further assistance. -- Dave Page Blog: http://pgsnake.blogspot.com Twitter: @pgsnake EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
