Scott Hendison

PS – Two of the sites were WP3.20 and one 3.21

We ONLY get the word “Error:” and no more details – however – no dialogue box opens to download the settings. After the first one failed i found this post – then tried on two more sites on other servers and get same result. No error details – just blank – and no way to download settings.zip…

Any news or a planned release for .8 version? Maybe making targeting urls simpler?

Hooray, our “updated date” has finally changed with todays update – it was stuck on December 2010 despite 3 or 4 other updates in 2011…

I would love to see the plugin get updated – It’
s mandatory on every site we do now…

Actually, @kaspars I wonder if you might allow us to integrate your installation with our own plugin? – We’ve added a couple of other indispensable plugins too (with their permission of course) – https://www.ads-software.com/extend/plugins/seo-automatic-wp-core-tweaks/

We are experiencing the same problem, and we do have an .htaccess file that’s functioning fine, 301 redirecting all the old .html pages to the new WP page, etc.

This answer makes no sense to me, because the 404 page server response seems fine, it’s just EDITING the text in the 404 template that causes the problem.

In fact, I can edit it mildly, changing “Apologies” to “Sorry” but once i add an extra few words, (it seems to be about 8 more words) then the think breaks and goes to the default browser message.

That’s not really an .htaccess / permalinks issue, is it?

Aha! –

everything but the http and domain name.

It DOES seem to work correctly. I’m likin’ this a lot, it came installed on a new clients site, so just stumbled across it – I’m donating the author something right now, (and you should too) ??

It “turns on” the ability to have a meta kw tag on any page or post, however, after checking the box, you need t odefine the “template” code for each section here –
https://DOMAIN.com/wp-admin/admin.php?page=wpseo_titles

For example, use %%tag%% in the page and post meta kw template for specific tags you add to work, or use something else, all the examples are there on the page.

If you REALLY want sitewide identical tags, then they too COULD be entered there, (in each of the four areas posts, pages, categories and tags) – all separated by commas. However, site wide tags are not “recommended” for use by anyone…

Bummer – we need this in a few places… Hmm, I wonder if we could build this function into our own Core Tweaks setup plugin, simply adding a checkbox option to the post write / edit screen. We should add it to our wishlist…. Better yet, maybe Joost @ Yoast.com will add it to his WordPress SEO plugin?

It also seems odd that as the developer, I saw no notification that someone poster here at WP for help. Maybe I missed it, but I dont think so… Anyway, this has also been put in our forum…

For what it’s worth, Robine took this issue to our email support, and we recreated the environment, giving him access to upload his theme and his plugins, but the problem was unable to be recreated. This led him back to his hosting, and we’ve had no update from him yet…

We have tried EVERYTHING but cannot find any method of compression that works NEARLY as well for speeding up a site as this code –
<? ob_start("ob_gzhandler"); ?>

Unfortunately, this breaks the All in One SEO plugin. REALLY a shame, and I sure hope there’s a solution coming some day. We want to build this into the Core Tweaks plugin…

We solved with creating the second tree manually, using links (the blogroll), then the links widget

We moved and changed nothing, other WP sites on this same hosting server are fine, but we have the same symptom. Cannot add or edit existing static pages.

Firefox just shows a blank page, and the page remains unchanged (or added.

View source shows nothing either after a notice that its going to resend the request.

Chrome shows this error:
Error 324 (net::ERR_EMPTY_RESPONSE): Unknown error.

Just venting / bumping this thread –

I’m seeing the exact same issue – “Premature end of script headers: post.php” and it’s totally intermittent – I think it’s not a webhost problem, it’s a WP 2.9 problem.