Miklos

I have the same problem – unable to add a post in visual mode – but ONLY when accessing the backoffice with IE9 on Windows 7. Using Opera (in Windows 7) or IE8 in Windows XP works fine. I am running WP 2.9.1 and do not upgrade, because the cut-and-paste from MS Word in more recent versions is broken.

Thanks, I’ll look into it, but from the webpage, it is clear it is a copout for a bug in WP (it’s been here in previous versions).

It may indeed be useful for some to preserve Word styles, if you format your entries in MS Word. This is what I do, and that allows me to control first indents, paragraph spacing etc., without having to specify each one manually, and preserve them when pasting in the blog, see e.g. here.

In order to be able to do so in 2.9.1, one needs to modify a few parameters in the $initArray of file wp-admin/includes/post.php.

I have upgraded to 2.9.1, and this is even worse than in previous versions (truncation occurs much earlier).

For me (with 2.9.1) it does not work, manual update returns error 500. The file is not created.

I have the same issue, and there have been questions about this in this forum for a year or so, without a solution.

Any news on this issue? It is still broken, as far as I know.

Same problem here. My blog: blog.le-miklos.eu. Export created a file with items up to #662 (3/8/2009), while the current one is #871. The last exported item (662) is truncated right after the content:encoded opening tag. Resulting XML file is ca. 4.5Mb long.

I had tried setting

upload_max_filesize=15M
post_max_size=15M
memory_limit=48M
max_execution_time=600
max_input_time=600

to no avail (it slightly increased the output from 4Mb to 4.5Mb).

I haven’t seen any answer to this anywhere, while there seem to be recurring questions about this problem.

Thanks,
Miklos

Thanks, this may solve the problem indeed, except that it would require reprogramming the sidebar.php file of that particular layout (classic), in which it just calls get_links_list() which obviously doesn’t do the job.

I got around this by modifying the style.css file of that layout:

1. added to the #menu ul ul li entry the following lines:
text-align: left;
text-indent: -7px;
margin-left: 7px;

2. added to the #menu ul ul ul.children the line:
margin-left: -7px;

Thanks. It does not change anything locally: the encodings in the local MySQL database are definitely odd to my eye (4 characters or more for “simple” special characters) but it works locally; i.e., WP knows what they are. However, they are not UTF-8.

I have been able to find that it may have something to do with the remote PhpMyAdmin, when trying to import data which I dumped locally: characters such as “??” (e acute), which are coded in 4 characters, import correctly, but the French apostrophe (which has a longer encoding) does not.

I am totally lost, now. I wouldn’t like to go through 200 articles and fix them by hand…

Ah, that’s it, works like a charm! Thanks a lot, podz.

Thanks podz, but from looking at the code you pointed me to, I am not sure it solves my problem. The one I have is not having too many comments for individual entries, but looking at all the comments of the site and not being able to go through them.

This is exactly what I had, and used SQL to change that. If you want to allow comments to all your posts, the SQL command is of the following form:

UPDATE wp_posts SET comment_status = “open” ;

Now, it depends if the tables making up your installation indeed start with the “wp_” prefix (this is the default, but you can set this to anything else at installation time, so check this).

As to how to use the command, it depends what type of interface to MySQL you use. It could be in command mode (via a shell window), or through an interface such as phpMyAdmin (you may have to backquote the name of the table, like so: wp_posts, as well as that of the column: comment_status).

Good luck