Posted by jrglasgow on September 9, 2009 at 5:46pm
| Download | Size | md5 hash |
|---|---|---|
| wlw_blogapi-6.x-1.7.tar.gz | 15.86 KB | 891026666e3d290093b6f53f79c07497 |
| wlw_blogapi-6.x-1.7.zip | 17.01 KB | c741d3abb59e8065a0a201d5a6acd2a8 |
Last updated: December 25, 2010 - 00:12
Changes since DRUPAL-6--1-6:
- #566418 by bkraegelin: Fixed wrong table in SELECT.
- #371400 by mcload: Fixed Windows Live Writer BlogAPI Error.
When the server has E_NOTICE turned on every little thing like checking the value of an uninitialized variable throws a notice.The is especially harmful when the expected result for the page request is to be parsed by a program that is not very good at ignoring notices that break the expected syntax of the XML it is expecting to receive.
The module was checking the value of a couple of possibly uninitialized variables in this function and causing notices to be thrown.
I have changed the function to use the empty() function which
empty() is the opposite of (boolean) var, except that no warning is generated when the variable is not set.
FYI - production site should never have E_NOTICE set.
- added a validation hook - hook_wlw_blogapi_user_authenticate to allow third party authenticatin modules that provide Drupal authentication to work with WLW Blogapi.