headers
Chris Meller | 1 Feb 2006 04:36
Gravatar

Re: Fail to upgrade wp2.0.1 RC1

Little late to the conversation here, but did anyone with this  
problem try dumping their cache? Sounds suspiciously like a bad cache  
copy to me...

On Jan 29, 2006, at 12:20 PM, Rob wrote:

> Zhao Jason wrote:
>> It is disturbing! I test RC1 in my localhost, but the same problem is
>> present. I am sure I didn't delete wp-config.php or change the  
>> table prefix
>> value.
>>
> This happened to me with 1.5.2, except the posts were only  
> invisible in Firefox, showing up fine in Opera and IE.  
> Unfortunately, I fixed it by upgrading to 2.0 so I can't say what  
> caused or fixed it :(
>
> -- 
> Rob Miller
> http://robm.me.uk/ | http://kantian.co.uk/
>
> _______________________________________________
> wp-testers mailing list
> wp-testers@...
> http://lists.automattic.com/mailman/listinfo/wp-testers

--
Chris Meller
chris@...
(Continue reading)

Permalink | Reply | 15 comments |
headers
owlservice | 1 Feb 2006 07:30
Picon

auhtor poast though moderation queue?

Over tha last year or so there has been a few requests for author posts to
go though the moderation queue so admin can check posts before going live.
Is this something that is in WP2? If not is there any plans to do so?

Thanks
Permalink | Reply | 1 comment |
headers
Aaron Brazell | 1 Feb 2006 07:41

RE: auhtor poast though moderation queue?


> Over tha last year or so there has been a few requests for author posts to
> go though the moderation queue so admin can check posts before going live.
> Is this something that is in WP2? If not is there any plans to do so?
> 
> Thanks

Author, Editor and Admins can publish their own posts. Contributors are the only ones that cannot (with the
obvious exception of subscribers who can't write their own posts either and thus cannot publish).

Of course, if you want to change this, there is a plugin for just that purpose.

http://redalt.com/wiki/Role+Manager
Permalink | Reply | 0 comments |
headers
Muskie Mckay | 1 Feb 2006 14:00
Picon
Gravatar

Error message

I'm now running something resembling the latest code base, I still am having
problems with my permalinks though.  That is not why I am writing, I just
published a post, actually edited a just published post and noticed at the
bottom of my main page an error.

I took a screen capture of it, but I'm not sure that was really necessary.  Here
is the text:

WordPress database error: [You have an error in your SQL syntax; check the
manual that corresponds to your MySQL server version for the right syntax to use
near '' at line 1]
SELECT COUNT(DISTINCT ID) FROM

I can't say for sure if my code is right up to date, but I'll endeavor to make
it so.

Muskie
--
Technological capability breeds social and political ignorance by seeming to replace knowledge.
               -- Brian Fawcett
Permalink | Reply | 0 comments |
headers
blogger | 1 Feb 2006 15:14

RE: Can we delete this code from classes.php?

I am a little frustrated that 2360 was changed to "wontfix" without any dialog
to fully understand the issue.  I don't mean to get into a status war, but I've
reopened it with substantial comments.  I hope that there will be a real dialog
before it gets closed again.

I won't repeat all of my comments here.  I do give links to graphically
illustrate the error in my Trac comments.

http://trac.wordpress.org/ticket/2360

Thanks,
Kirk
Permalink | Reply | 20 comments |
headers
Andy Skelton | 1 Feb 2006 16:53
Picon
Gravatar

Re: Can we delete this code from classes.php?

On 2/1/06, blogger@...
<blogger@...> wrote:
> I am a little frustrated that 2360 was changed to "wontfix" without any dialog
> to fully understand the issue.  I don't mean to get into a status war, but I've
> reopened it with substantial comments.  I hope that there will be a real dialog
> before it gets closed again.

Kirk, I closed it but you're right, it bears more discussion. I saw
this issue listed on the WPG2 wiki, too.

I'm not very familiar with it but from a quick look, WPG2 is including
wp-blog-header.php, which is where wp() is called and the 200 status
code is set. I don't know why WPG2 doesn't simply include
wp-config.php. Would you mind trying this change on line 31 of
wp-gallery2.php?

Thanks,
Andy
Permalink | Reply | 19 comments |
headers
Aylwin Cal | 1 Feb 2006 17:55
Picon

Re: Can we delete this code from classes.php?

Hi,

I've tried changing line 31 from:
require('./wp-blog-header.php');
to:
include('./wp-config.php');

I no longer get stuck with the 200 but I get the following error on every
single Gallery page:

Warning: extract(): First argument should be an array in
/var/hometemp/aylwin/public_html/wp2/wp-includes/functions.php on line 2109

Aylwin

On 2/1/06, Andy Skelton <skeltoac@...> wrote:
>
> I'm not very familiar with it but from a quick look, WPG2 is including
> wp-blog-header.php, which is where wp() is called and the 200 status
> code is set. I don't know why WPG2 doesn't simply include
> wp-config.php. Would you mind trying this change on line 31 of
> wp-gallery2.php?
>
> Thanks,
> Andy
>
Permalink | Reply | 18 comments |
headers
Santanu Misra | 1 Feb 2006 18:07
Picon

Re: Can we delete this code from classes.php?

I tried the same change on my test server

At revision 3502.

 And there is no problem. I am using blix theme.

-Santanu

On 2/1/06, Aylwin Cal <aylwin.cal@...> wrote:
>
> Hi,
>
> I've tried changing line 31 from:
> require('./wp-blog-header.php');
> to:
> include('./wp-config.php');
>
> I no longer get stuck with the 200 but I get the following error on every
> single Gallery page:
>
> Warning: extract(): First argument should be an array in
> /var/hometemp/aylwin/public_html/wp2/wp-includes/functions.php on line
> 2109
>
> Aylwin
>
>
> On 2/1/06, Andy Skelton <skeltoac@...> wrote:
> >
> > I'm not very familiar with it but from a quick look, WPG2 is including
(Continue reading)

Permalink | Reply | 0 comments |
headers
Kirk Steffensen | 1 Feb 2006 19:23

Re: Can we delete this code from classes.php?

Andy,

Thanks for the reply and the dialog.  I appreciate your insight into
wp-blog-header.php vs config.php.  I'll do some testing tonight to try to
figure out a way around the errors that Aylwin has seen.

Assuming we can fix the problem this way, I'll be happy to close the ticket.

Regardless of whether WPG2 can be fixed easily, I'm not convinced that forcing a
200 HTTP status at the end of classes.php is the best long-term solution for
WordPress.  I don't know how many other folks are affected by this, but it took
the WPG2 community several months to narrow down the error to classes.php,
because the error looks like it's coming from Apache or PHP-CGI.

I read Owen's outstanding article on submitting patches and installed XAMMP last
night.  I've been doing all of my development testing on my webhost's system,
but I'll start working directly on my laptop so that I can submit productive
patches instead of just submitting requests for someone to change the code.

Cheers,
Kirk
Permalink | Reply | 501 comments |
headers
Kirk Steffensen | 1 Feb 2006 23:49

Re: Can we delete this code from classes.php?

Andy,

WPG2 gets it's coordinated look-and-feel between WP and Gallery2 in one of two
ways:
1.  Use a custom wpg2-header.php and/or wpg2-footer.php file, or
2.  Use the current WP theme's headers and footer.

If WPG2 mandated custom headers and footers, we could get away with 
only calling
wp-config.php.  But the user experience for the the average Joe user would not
be great, because it's extra work to create these extra custom headers and
footers.

Because WPG2 calls get_header() and get_footer() to get the current WP theme
headers and footers, wp-blog-header.php must be called with the current WP
architecture.  This gets a little convoluted, but here is the stream:

1.  If WPG2 only calls wp-config.php, the key API call that is missing from
wp-blog-header.php is wp();

2.  Without wp(); the WP class never gets initialized [in classes.php], and
hence the WP-Query class never gets initialized [again, in classes.php].

3.  When get_header() and/or get_footer() are called [in
template-functions-general.php], they in turn call load_template( TEMPLATEPATH
. '/header.php'); [in functions.php]

4.  In load_template(...), the extract($wp_query->query_vars); chokes because
the WP-Query class was never initialized, so $wp-query doesn't exist.
(Continue reading)

Permalink | Reply | 503 comments |

Gmane