[wp-hackers] WordPress 2

[David House]

I uploaded a patch to the bug that Denis started (2106):
http://trac.wordpress.org/attachment/ticket/2106/2106.diff

On 20/12/05, Ryan Boren <ryan at boren.nu> wrote:
> > Some bugs are fun, e.g. when you add a child to 'a page with a very very
> > very long page title'.
>
> Elaborate.

In the patch. The problem was that the select box gets very wide.

> > Others are just annoying, e.g. TinyMCE randomly adds spaces in FF.
>
> Hmmm, I don't notice random spaces.  I'll play with it.

I skipped this altogether, tinymce is a bit over my head :)

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

I couldn't replicate.

> > 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.

Kind of what I said on the bug report.

> > 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.

In patch to make it not white-screen in the mean time.

> > 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.

These could be bugs still. Denis, we need info on where you got these
fatal errors.

--
-David House, dmhouse at gmail.com, http://xmouse.ithium.net