Re[2]: 1.3 release soon
qMax <[email protected]>
| Newsgroups | gmane.comp.cms.bitflux.general |
|---|---|
| Message-ID | <[email protected]> |
Thursday, December 29, 2005, 5:17:35 PM, Christian Stocker wrote: CS> On 27.12.2005 13:42 Uhr, qMax wrote: >> Friday, November 25, 2005, 2:16:35 PM, Christian Stocker wrote: >> >> CS> Hi >> >> CS> We plan to soon release Flux CMS 1.3. We will most certainly not branch >> CS> that right moment (too much work to maintain 2 branches), but as soon as >> CS> we will bc-break something important or add new - potentially >> CS> "dangerous" - features, which will need more than "rm tmp/* and >> CS> admin/webinc/update", we will branch. No idea, when that will happen. >> CS> But until then, it should be safe to "svn up" from HEAD. >> >> CS> So, the big question now is, is anyone aware of any important >> CS> showstopper bugs, which should be fixed before we release 1.3.0? >> >> check for UTF8 support in all plugins. >> (some still use utf8_decode which avoids using utf) CS> It's mainly mail-related stuff and I'm too lazy right now to look it up CS> and fix this (encoding in mails is not something I like my holidays to CS> spend with :) ). CS> If you find something webrelated, which uses utf8_decode, please tell me CS> where exactly. That's usually way easier to fix filters/formwizard.php filters/formwizard/methods/blogcomment.php They utf8_decode strings and store them as '????' into sql database. I failed to find quick way to fix it, as it was with mail stuff. but this is NOT in trunk code. -- qMax -- bitflux-cms mailing list [email protected] http://lists.bitflux.ch/cgi-bin/listinfo/bitflux-cms