Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Downloads
Download wlw_blogapi-6.x-1.7.tar.gztar.gz
15.86 KB
MD5: 891026666e3d290093b6f53f79c07497
SHA-1: 1e2ba4462a5a2272bd7069e14c9d716f57ca13b4
SHA-256: 3b73501ef2dd0e616c332635accd6319f0b030c510bf9d319fb2acb8097b7d61
Download wlw_blogapi-6.x-1.7.zipzip
17.01 KB
MD5: c741d3abb59e8065a0a201d5a6acd2a8
SHA-1: e386cb8037d2f540878bd45780fd03abf543c726
SHA-256: 8648d4a2ff3bf33cfe6c857504d2fdd001f6a2655b9a52603b7844fe4a7738a0
Release notes
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.