>> Strangely, once I've upgraded to 3.2.2 I can't >> revert back to the old functionality with restoring from a backup TW.
Damn- WITHOUT restoring from... ;) > Now that *is* strange! Note that the problem started with v3.2.0... > is it possible that you had already installed a broken revision (3.2.0 > or 3.2.1), but didn't notice until now? In any case, the latest > update should make this problem moot. Indeed. We'll find out shortly. But to answer said moot point (long intake of breath)... While you and I were swapping code/bugs about this, I was working from a test TW - the "production" TW where I had planned to use CT later was kept on the sidelines waiting... Later, once you'd got sparse working and all the other goodies, I decided I'd split the production TW in two - only today I discovered that I had forgotten/neglected to upgrade the TW that makes the most use of CT (how dumb is that). It has version 3.1.3+RTFix - which, as you might guess was your 313 code plus my cobbled-together fix. I now don't know nor can I determine what 313 became (314? 320?). Either way, I can assure you Eric, If I upgrade 3.1.3+RTFix to 3.2.2, and revert back to 3.1.3+RTFix, I've a broken CT as described above. If I a restore last night's backup, it's fine. Twilight Zone? ;) Off to get the update - back soon. R --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
