zanshin

This “feels” like the pre 2.5 issues with TinyMCE and Safari. I suspect that what ever WP 2.7.x is using to power the visual edit mode uses some coding that is incompatible with the Nitro JavaScript engine in Safari 4.

Hopefully there will be a dot release sooner rather than later to address this issue.

Of course, if the code causing the problem is produced by a third-party outside of WP control, we may be in for another long wait before it is resolved.

I’m seeing the same problem – unable to use visual editor to add (or edit) links. In fact once the link icon is clicked, I’m unable to regain access to the page at all and have to close the tab.

Hopefully this isn’t the start of another TinyMCE bug type issue. The new Safari beta is considerably faster on my machine than version 3 was. Having to use a different browser to edit my WordPress site was painful until 2.5 fixed the TinyMCE problem.

Thanks. I had missed the bit about using wp-mail.php. Now I am getting database errors. I had some double quotes in the test message, and the parser barfed all over those. Now I can’t get the test message through even without the quotes.

Nerts

I’ve tried saving my “import.txt” in every format allowed by BBEdit. Every combination of “generic text file”, “generic OS X text file”, “BBEdit file”, “unix line breaks”, “macintosh line breaks”, “dos line breaks”, etc.

I am not able to import my entries at all and it is very frustrating. I’ve read several posting on the internet that all suggest I need to edit my entries individual to make sure they’ll import. With over 550 entries presently I don’t think I’ll be doing that.

I realize that ExpressionEngine is commercial, but their imported swallowed all 26000 lines of the import file without a hiccup. WordPress needs to improve their MovableType import facility if they want to capture those of us wanting to switch.

Hmm. I am running Apache on my machine, and I have mirrored as closely as I can the environment at my host. I suppose I could migrate my test to my host, but I really don’t want to add the difficulties of working remotely to this conversion.

What could be different between my machine and my host that might allow the import to work there while not working locally?

Manually editting over 500 entires to import them is not my idea of fun. I parced the file in to smaller and small chunks until the import worked… with exactly one entry in the import.

Free or not, I am not going to perform 551 imports just to switch to WordPress. There has to be a better way.