[wp-hackers] WordPress 2

[Ryan Boren]

On Tue, 2005-12-20 at 19:05 +0100, Denis de Bernardy wrote:
> I've set up a WordPress 2 test site this afternoon.
> 
> Some bugs are fun, e.g. when you add a child to 'a page with a very very
> very long page title'.

Elaborate.

> Others are just annoying, e.g. TinyMCE randomly adds spaces in FF.

Hmmm, I don't notice random spaces.  I'll play with it.

> Others are merely uncaught cases, e.g. the implode error in the file list
> when no .htaccess file exists.

Error message?

> Others are misleading, e.g. there is no error or warning when you mess
> around with permalinks without a valid editable .htaccess file.

If it's not editable, the suggested structures should have index.php/
prepended so that PATH_INFO is used instead of .htaccess.  If you use a
custom structure, you're own your own.

> Some make WordPress go wiiiiild, e.g. if you delete the active theme's
> directory, wp does not fallback to the default theme.

The theme will be reset if you visit the Presentation page.

> And I've bumped into fatal errors:
> 
> Fatal error: Call to a member function get_page_permastruct() on a
> non-object in
> c:\Inetpub\wwwroot\semiologic2\wp-includes\template-functions-links.php on
> line 92
> 
> Fatal error: Call to a member function get_category_permastruct() on a
> non-object in
> c:\Inetpub\wwwroot\semiologic2\wp-includes\template-functions-category.php
> on line 24
> 
> Manually deleting every static pages in the DB eventually fixed the first
> issue. I've yet to pin down the second one. This is likely due to my
> checking against permalinks somewhere in a plugin too early, so I'll
> ultimately be fixing both at once.

$wp_rewrite is not available until just before the 'init' action.

> In any event, however, though, this kind of thing is not what I'd go like to
> go through with someone in the support forum.
> 
> And the bug list in trac looks scary enough for me to suggest against such a
> release this week.

Much of that is deferred or won't fix.  If we waited until the bug
tracker were empty, we would never release again.  If you see a bug that
you think is "must have" for 2.0, mention it here and we can discuss
including it in 2.0.

Ryan