Downloaded the newest version of ecto (2.0), and am less-then-whelmed. The rich text editor sounds nifty, but is kind of ugly to work with. I’m going to see what sort of answers I get on the support line as to whether I drop back to 1.8.8
Meantime, I’m also having problems (with both ecto and SharpMT) with getting posts to finish posting (the post gets up, but doesn’t finalize the rebuild or the category assignments. Annoying. And piss-poor timing with everything else I have going on right now.
33 view(s)
Yeah, I’m also less-than-whelmed with the supposed rich text editor – the handy formatting buttons work with one, but not the other. And then my HTML snippets only work with the HTML editor. WUPWD?
My HTML snippets work okay with the Rich Text editor — well, they work, but they tend to double up text and the like.
And I’m really irked by something relatively trivial — losing Ctrl-Ins, etc., for copy/paste. The editor now recognizes only Ctrl-C/Ctrl-V stuff.
Waiting to see some response to my notes before I decide whether to drop back to 1.8.8, go back to SharpMT, or look for another solution.
This error shows up in Google a fair amount associated with .NET 2.0 — which, coincidentally, the new versions of ecto and SharpMT both make use of.
Argh.
Randy (of SharpMT) avers it’s not a .NET problem.
Since Randy is both sharp (so to speak) and responsive, I believe he’s sincere and likely right. Though, again, the problem did hit when I changed to the .NET 2.0 versoin of ecto and SharpMT. And there’s a fair amount of Googly stuff that indicates if it’s not unique to .NET 2.0, it’s more common there (greater sensitivity to keepalive status or something in POST whatevers).
Which isn’t much help; at the moment, I’m posting things by editing them in ecto, copying the HTML code from there to an MT entry screen, and saving there. (That, at least, updates blogrolling and similar pings.) The alternative is to post it from ecto (or SharpMT), let it crash, and go into MT to edit the entry and save it from there.