Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Bug list for Techdocs
Date: Tue, 23 May 2006 10:48:11 +0200
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCEA35424@algol.sollentuna.se>
Thread-Topic: [pgsql-www] Bug list for Techdocs
Thread-Index: AcZ+K17BNeFmTNDISt+3uPjk6hy+UwAFSx2A
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Josh Berkus" <josh@agliodbs.com>, <pgsql-www@postgresql.org>

> 1) Styles missing from Techdocs CSS, or somewhere:
> 	<b> (or <strong>)
> 	<p align=3D"center">
>    These are supported by the WYSWYG editor, but techdocs=20
> rejects them as invalid styles and won't save the page.

These are both fixed.


> 2) Styles missing from the WYSWYG editor but *not* from CSS/wherever
> 	<h1> <h2> <h3>
>     That is, these can be done in HTML mode and do not get=20
> rejected, but cannot be selected in the WYSWYG editor.

Fixed.


> 3) Styles missing from both places:
> 	<dl> =20
> 	<code>
>     These can be neither done through the WYSWYG editor nor=20
> will be accepted in HTML mode.  Both are used frequently for=20
> HOWTO articles.

Hmm. This is enabled in the editor, but doesn't show up for some reason.
Will require further investigation :-(


> 4) After the page is saved, wwwmaster shows "invalid page"=20
> until the page is approved.  This means that the user cannot=20
> go back to the page and re-edit if their session is=20
> interrupted; it *has* to be approved before anyone can=20
> examine it meaningfully.  This is a real issue for docs we=20
> want to go up at a specific date.

I was planning to stick this on the "profile" page - a list of all
checked out pages. Seems I never got around to it :-(=20
Does this seem like a reasonable thing to do?

(We can't stick them in their permanent place, since they might conflict
then)


> 5) The approval interface does not show a readable preview of=20
> the page.  How do we know what we're approving?  If I'm=20
> approving my own stuff, that's not an issue, but someone else's edits?

Uh, what about the preview button?
(The main reason it's not in there by default is so you can check the
code for possible XSS before you load it in your browser)


> 6) There is no way to re-assign "parent" pages.   This is a=20
> problem if you=20
> create pages out of order; you can't clean them up.

Yup, this would probably not be a bad thing to have. Is it ok to have it
just in the admin intface? It's going be a *pain* if we have to put
actual versioning on it,. and I'd like to keep the "public interface"
fully versioned.

//Magnus