 | scribu on Migration project for GSoC |
 | Bryan Petty on Summer of Code Revisions |
 | adamsilverstein on Summer of Code Revisions |
 | Weston Ruter on JSON REST API |
 | Chuck Reynolds on JSON REST API |
Plugins using date('U') or time() may have been expecting a timezone offset in previous versions of WordPress, and depending on the server setup this was true. This has changed in 3.0. We now tell PHP to not factor in timezones to ensure maximum portability across PHP versions and server setups, thus you’ll end up with UTC time when using those functions.
Use current_time('timestamp') to get the Unix timestamp with a timezone offset.
Another reminder that escaping rules for options and transients changed a bit in 3.0.
btw as i am reviewing mails in pluggable.php and hooks on mails in wp-login.php
in wp-login.php we have :
if ( is_multisite() )
$blogname = $GLOBALS['current_site']->site_name;
else
// The blogname option is escaped with esc_html on the way into the database in sanitize_option
// we want to reverse this for the plain text arena of emails.
$blogname = wp_specialchars_decode(get_option(‘blogname’), ENT_QUOTES);
in pluggable.php, we have :
// The blogname option is escaped with esc_html on the way into the database in sanitize_option
// we want to reverse this for the plain text arena of emails.
$blogname = wp_specialchars_decode(get_option(‘blogname’), ENT_QUOTES);
what is the right sequence of code ?
Please could you open a ticket for this.
The special_chars_decode probably needs applying in the is_multisite() case above for the same reason it was applied in pluggable.php
done #13618
done #13618
not sure this line
$blogname = $GLOBALS['current_site']->site_name;
is usefull !?
Check out register_nav_menu(), register_nav_menus(), and the theme_location argument to wp_nav_menu() for a means of associating custom navigation menus with particular “locations” in your theme. The Twenty Ten theme offers an example.
During plugin activation, WP 3.0 checks to see if the plugin generates any output. If any output is generated a warning is shown to the user. Generating output during activation is usually a good sign that the plugin has spaces before the opening php tag or that it generates warnings. This extra output can break feeds and cause “headers already sent” warnings. Please test your plugins against 3.0 and make sure your they do not generate unexpected output.
The whitespace issue can usually be alleviated by not ending your script with ?>
It seems wrong, but Zend Framework, Drupal and many other projects have adopted it as a standard, and nobody actually has a problem with it from a technical angle from the PHP side when I’ve ever asked.
I am having the same problem during activation.When i try to activate the plugin i get the message “The plugin generated 560 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.”
So where can i edit the plugin to get rid of this.It works in all of the lower wp-versions.
If you are still having an issue, I found a spot in a plugin I was developing, which may be the same issue with this plugin. Check that the “add_option” method does not contain a “description” parameter of, if it does, that it is an empty string or null. “Description” was deprecated with version 2.3 of WordPress. Good luck.
Hey guys I’m having the same issue. However, I’m getting the following message:
“The plugin generated 3 characters of unexpected output during activation. If you notice “headers already sent” messages, problems with syndication feeds or other issues, try deactivating or removing this plugin.”
I’m crap at editing code, was this what you was hinting at Jeff Lamberth?
Please advise.
arena and 
gaurab, and 1 other are discussing. 
Best should be to clean up code in
wp-login.php
$user_login = $user_data->user_login;
$user_email = $user_data->user_email;
and in wp-pluggable.php (several times)
$user_login = stripslashes($user->user_login);
$user_email = stripslashes($user->user_email);