Downloads
Download tar.gz
24.76 KB
MD5: 4d37df0f2a794a2ebaebbeaa62ffb4d2
SHA-1: 26e4ea68f9dd3a0d7f7306d5a3147b683194de1d
SHA-256: f0ce159e756279d3dd494160442c2498f76a2e639c6c79070c32b23bde755fb7
Download zip
28.32 KB
MD5: 729fcabbf76c22c2091832ebc287c6a1
SHA-1: a0b97bb207a125c39063b294a6a0cba286ec71c7
SHA-256: 64459bafcef0d442c8eaf440932b584718aa4d8711fa0a2b3f9ff3fa461f131b
Release notes
Updated
- Module code
- READ ME instructions ("Basic configuration" (step 3), "Limitations")
New Feature
Previously, if an event was removed from the Evanced Events software (or unpublished), it was deleted from Drupal only if cron was run manually. Now, the event will be removed from Drupal regardless of how cron is run -- whether triggered manually or by a scheduled process on your server. NOTE: This only works if the user account that imports these events (specified on the "Main configuration" screen of the Evanced Events Importer) has "administer nodes" permission.
Bug Fix
Sometimes, this module erroneously deleted event nodes, which existed the day before the earliest event in EXML feed. This phenomenon only occurred when cron was run manually. This bug should now be corrected.
