[wp-hackers] Re: wpblogmail fails when mail contact plugins present

[David Chait]

all plugins are included any time wp is loaded up -- it is up to the plugins 
to 'decide' whether or not to execute (i.e., I have some that turn 
themselves off when the page loading is under wp-admin/).

Process goes something like:

wp-blog-header.php
-> wp-config.php
-> wp-settings.php
-> setup wp caching stuff
-> twenty other files...
-> all plugins
-> setup query and rewrite objects
-> init main object, parse the request, send headers, run db query for 
posts...
-> template-loader.php

This is why when people ask if they should directly include WP in order to 
show recent entries on a home page or something, I tell them to use a 
caching feed-aggregator script, as including WP has a ton of overhead even 
if only looking at code loaded... ;)

-d

----- Original Message ----- 
From: "Scot Hacker" <shacker at birdhouse.org>
To: <wp-hackers at lists.automattic.com>
Sent: Monday, June 26, 2006 12:22 PM
Subject: [wp-hackers] Re: wpblogmail fails when mail contact plugins present


|
| On Jun 26, 2006, at 5:01 AM, Sam wrote:
|
| > The Dagon plugin runs session_start() when it's loaded, which tries to
| > set a session cookie. It probably shouldn't, but there's nothing you
| > can do about it.
|
| But what's calling the Dagon plugin to begin with? Shouldn't it only
| be called when user clicks through to a page that includes a contact
| form? Same deal with PXSMail. Or are all WP plugins called on all
| page requests? (If so, that seems very innefficient - is there any
| way to suppress that behavior?)
|
| >
| > You get "headers already sent" warnings because you've echoed
| > something in your script before the other plugin tries to send the
| > cookie header.
| >
| > Do you still get them if you don't 'echo $header;' until *after*
| > including wp-blog-header.php ?
|
| Yep, tried that - same problem :(
|
| Thanks,
| Scot