massacre

I don’t know how exactly it’s messing up with my styles, but on single post page, the title became different – bigger and, I believe, with a different font. Couldn’t find anything with firebug tho.

Anyway, I had to disable the plugin and install few other. I am actually using the integrated SEO settings, and I needed Yoast to strip ../category/.. from URL as well as generating an XML sitemap.

Yes, of course! I forgot about it, thanks!

Thank you very much, jesin!

Should I upload a video ot it works with video links (e.g. YouTube videos)?

Guys, I think I found the problem!

After all night browsing over the Net, installing new blog, re-installing my current one, creating new DB, migrating, starting everything from the scratch, installing test-server on virtual machine, etc…. few minutes ago I clicked once and now my RSS is working perfect!

The problem is with the plug-in GD Press Tools and especially with the RSS delay option. Start it – and you don’t have a feed with pretty permalinks. Stop it and it’s validated perfectly!

WP and GD Press Tools are the latest official versions available.

I don’t think that this is the main reason, but at least, it works for me just fine.

Little update – works like a charm on my second blog. with /feed – the RSS stream is there. I guess that after using a Feedburner, the problems begin. But I am not sure!! I think so, because lot of people complains of the same problem with WP + feedburner installed.

Thanks for the help, arkain283, but this is not working (for me).

I even tried to delete the .htaccess so the WordPress is creating it as a new one. Still, with pretty permalinks I have error 404. I am still working on it and if I succeed, I’ll write back.

Hello!

I have the same or similar problem. I am using Feedburner (the plugin site is not working righ now).

My feed are there, I mean – when I click the RSS icon, the content is there. I wanted to validate my feed when I saw the 404 error. I opened Feedburner and tried to change few settings – same thing – 404 error. I am trying to find something for 5 hours now and I am really pissed off already.

Altho i love Google, I will stop using Feedburner, but.. even if I deactivate the plug-in, the problem exists. Sadly, I don’t have these things in my .htaccess so I am at the dead-end again.

I will appreciate any help and advices.

The main reason for me to use Feedburner is that with <!– more –> tag, even with “full feed” set in options, I am getting only the content before “more”, but I am sure that it would be easier to fix this.

Hello! Since few days I got the same error. I am not sure, but it happens after exact number of plugins – if I delete one of the already installed and upload new one – in 99% everything is fine. My memory_limit is set to 32MB. Really, it would be nice if mjnbrn tell us how he fixed the problem. Thanks in advance!

After update of the plugin (current version is 1.3.5), everything seems to be fine. Thanks!

Still nothing in WordPress 2.7-RC1-10026. I hope it would be fixed for the final version.

Finally! I found the “fix”, although I am not sure what exactly was the problem. I had 3 unupdated plugins: WP-Stats, Yet Another Related Posts Plugin and Search Everything. I will search through changelogs, but I assume that either YARPP or Search Everything was the reason for the encoding problems. Now everything seems to works fine!

Work’s fine for me with 9841 too. Probably this one should be set to [resolved]?

Hi again!

I don’t want to be boring, but I really need some help. Or at least some ideas how to fix this problem. I am updating to every nightly build, but still can’t resolve this strange problem. Thank you in advance!

And one more update: On fresh installation of the latest beta of WP 2.7, Cyrillic in comments seems to be fine. Please, if someone have an idea how to fix my older comments, I will really appreciate it! I know it’s not a good idea to install beta versions over working finals of previous versions, but.. it’s too late now and I really would like to have my comments back and readable.

P.S. On different themes, there are some problems with encoding even in the sidebar.