I've been having a problem with MT-Blacklist 2.x for a while now; it stopped saving my preferences.
After loads of fruitless and frustrated (and frustrating) Google and code searches, I finally found an oblique reference to the same problem with someone using Postgres — and a workaround.
It turns out that it's another bug in MT 3.1: in the mt_plugindata table, the plugindata_data column is of type mediumtext. However, there's no binary-to-text conversion performed on a Storable freeze/thaw of this data inside MT::PluginData, so any plugin using binary data has a data loss.
David had a replacement for MT::PluginData::data already written that worked like a charm for mysql as well. In effect, all it does is perform a simple pack/unpack to convert the data.
David Raynes: Thank you, dude. Seriously.
Sixapart: That's two codebase mods I've made to 3.121. Please don't let this continue! I really hope at least the Storable fix is present in the forthcoming release (3.13) that Jay announced regarding the resource drain bugs on comment firehosing.
Comments (2)
You're welcome. :)
With every new release, I pester the folks at 6A about the problem with Postgres. Considering some of the other stuff they have to deal with out there, I can understand why this isn't exactly at the top of their priority list right now.
Posted by David Raynes | December 17, 2004 12:45 PM
Posted on December 17, 2004 12:45
Just a followup note: in 3.2, they did away with Storable, and thus also this bug.
Posted by Scott Swanson![[TypeKey Profile Page]](http://blog.truegeek.org/nav-commenters.gif)
|
October 23, 2005 11:14 PM
Posted on October 23, 2005 23:14