9e9ab23e1f
Under MySQL, new tables will be created as InnoDB with UTF-8 (utf8/utf8_bin) same as core tables. Existing plugin tables will have table engine and default charset/collation updated, and string columns will have charset updated, at checkschema time. Switched from 'DESCRIBE' to INFORMATION_SCHEMA for pulling column information in order to get charset. A second hit to INFORMATION_SCHEMA is also needed to get table properties. Indices were only being created at table creation time, which ain't so hot. Now also adding/dropping indices when they change. Fixed up some schema defs in OStatus plugin that were a bit flaky, causing extra alter tables to be run. TODO: Generalize this infrastructure a bit more up to base schema & pg schema classes. |
||
---|---|---|
.. | ||
actions | ||
classes | ||
extlib | ||
images | ||
js | ||
lib | ||
locale | ||
scripts | ||
tests | ||
theme/base/css | ||
OStatusPlugin.php | ||
README |
Plugin to support importing updates from external RSS and Atom feeds into your timeline. Uses PubSubHubbub for push feed updates; currently non-PuSH feeds cannot be subscribed. Configuration options available: $config['ostatus']['hub'] (default internal hub) Set to URL of an external PuSH hub to use it instead of our internal hub. $config['ostatus']['hub_retries'] (default 0) Number of times to retry a PuSH send to consumers if using internal hub For testing, shouldn't be used in production: $config['ostatus']['skip_signatures'] (default use signatures) Disable generation and validation of Salmon magicenv signatures $config['feedsub']['nohub'] (default require hub) Allow low-level feed subscription setup for feeds without hubs. Not actually usable at this stage, OStatus will check for hubs too and we have no polling backend. Todo: * fully functional l10n * redo non-OStatus feed support ** rssCloud support? ** possibly a polling daemon to support non-PuSH feeds? * make use of tags/categories from feeds