Re: [Phpslash-devel] phpSlash 0.8 punch list (Update)

[Joe S. <joe...@us...>]

on 10/07/04 10:52 Joe Stewart said the following:
> Anyone got any bugs that need fixing before starting a Release Candidate?
> 
> Here is what I've got so far:
> 
> - [ 1034553 ] [0.8] - Title is not correct for Articles
> - [ 1034554 ] [0.8] - Title is not correct if no section forced. 
> 
> 
> 
> - [ 1035199 ] [0.8] - upgrade script doesn't upgrade all sections.
>                      It only upgrades the sections that exist in a
>                      default installation.  Need to gather all sections
>                      and install new blocks.
> 

Closed these.  Reopen if new problems found.

> 
> - No printer friendly choice for articles yet. - Anybody created a 
> printer css?  This may require a change that would allow css switching 
> from the url.  Probably could pretty much be done already.  The previous 
> method wouldn't be as straight forward because the article generation 
> doesn't dictate what the rest of the page looks like.
> 

Added CSS tag to slashHead.tpl - Filled with either the skin or css GET 
variable to allow changing css on the fly.

Added print media css for basic, basiccurves, and ShankZen.

The ShankZen_print.css is broken in that the botton navbar and comment 
change view is still shown.

> - Need to get away from god/password in the setup wizard.  A screen in 
> the wizard setting the username/password should work OK.
> 

TODO

> - How many skins should be in the release?  Most available are simply 
> ported from other applications and not maintained too well.
> 
> We've got:  ShankZen
>              Funkatronic
>              basic
>              basiccurves
>              default - hasn't been maintained and I'm not interested in 
> 
>                        spending time with it.
> 

These are the ones in the current development release, except for 
funkatronic.  I'll try to get it up to date first.

> Chime in with your thoughts or any other changes needed before 0.8 release.
> 

A couple more that would be nice:

1. Separate sql file into a core set to install the minimum necessary 
and another set to install the example data.

The install wizard was built for Back-End which already has this setup. 
  Should be simple to reenable.

2. RSS2.0 and Atom output from backend.php.

These will probably come in during the RC testing.

Joe

> If you can take any of these on that would be great.  I've got an idea 
> of how to solve the page title issue and will try to get that done.
> 
> Joe
>