gregmulhauser

I’d recommend having a peek at the ‘Instructions’ tab on GHPSEO for details on how to add calls to your theme to display your titles the way you would like. (Alternatively, if you feel that is risky in any way, then I would recommend just sticking with the default WP titles and calling it good.)

All the best,
Greg

Have tested with IE7 on Windows XP Pro and WP 3.2.1 and seems to work fine; the box is inserted via standard WP calls for doing that sort of thing, so it’s unusual that only that one box would give you troubles, with the others in the editing interface working correctly.

I would guess there’s something else at work here — something unrelated to IE7 vs. GHPSEO per se, since as I say, it appears to be working fine on an IE7 test install.

All the best,
Greg

I would recommend reading the ‘Instructions’ tab of GHPSEO, where you’ll find details on filtering the GHPSEO output function. By filtering the GHPSEO output function, you are not filtering anything else except that function — in particular, you are not filtering the head meta description. If you’d like to filter the head meta description, you’d need to remove the plugin’s built-in wp_head action ‘head_desc’ and provide one of your own instead (which could of course use the filterable GHPSEO output function).

All the best,
Greg

I’d recommend reading the ‘Instructions’ tab on GHPSEO and learning about what you can do with legacy SEO plugin data.

All the best,
Greg

Hi Arne,

Also, not sure why hide_empty is set to true with hierarchical then set to false in the call to get_terms (also in BuildTaxonomies in sitemap-builder.php — but the result is that no sitemap entry will be generated for categories which happen not to have any posts directly in them but which do contain sub-categories which have posts in them.

For many folks using WP in ways that place a lot of importance on categories, it seems like it would be better either not to be making this exclusion decision for them (i.e., err on the side of including these categories rather than excluding them), or enable them to specify for themselves which way they’d like these categories to be handled.

All the best,
Greg

Hi Arne,

Looks like priorities for categories are always set using $gsg->GetOption("pr_tags"), even when it should be pr_cat… See function BuildTaxonomies in sitemap-builder.php.

All the best,
Greg

Hi folks,

This is Greg, speaking on behalf of the SPSN.

As indicated (I hope clearly) in our privacy policy, mentioned earlier in this thread: “No individually identifiable information of any kind will be collected or retained about sponsorship messages delivered at websites using a sponsored plugin.”

I’m sorry if this is unclear in some way, but the subsequent statement that we accept individually identifiable information from plugin authors and sponsors means that we (obviously?) accept their own personal information.

Stating clearly who we accept personally identifiable information from and what we do with it is a requirement for us due to both UK and European legislation.

We also require that all participating plugin authors disclose fully that their plugin is participating in SPSN and provide either a summary of or a link to our privacy policy (or both).

So, again, unless you are a plugin developer or a plugin sponsor: we do not collect, track or retain personal information. And it should go without saying, but if you are a developer or a sponsor, it would be pretty darned difficult for us to pay you money (developers) or accept your sponsorships (sponsors) if we did not have your personal information.

As far as I am aware, we maintain a vastly higher standard of privacy protection and full disclosure than the example set by Automattic and www.remarpro.com itself — with the automatic plugin update mechanism responsible for the transmission and collection of vast amounts of information about individual WordPress installations without any disclosure about what information is being transmitted, what will be done with it, how long it will be kept, etc., and without any opportunity to opt out.

All the best,
Greg

Hi vanhorn,

Do have a peek at the instructions, as they’re pretty straightforward — they explain what needs to be done. Give me a shout back, preferably via my own site (if you’d like a reply this calendar year) if that doesn’t do the trick.

All the best,
Greg

Hi maxmanus,

Generally this is due to the plugin’s magical ability to detect whether the admin has followed the plugin’s installation instructions… ??

Do have a peek at the instructions, as they’re pretty straightforward. Give me a shout back, preferably via my own site (if you’d like a reply this calendar year) if that doesn’t do the trick.

All the best,
Greg

You can always add and remove it on a page by page basis yourself programmatically:

global $ghpseo;
remove_action('wp_head', array(&$ghpseo,'canonical'), 5);

All the best,
Greg

This sounds like the same underlying problem as in this topic.

All the best,
Greg

This sounds very much like a theme issue, especially given that GHPSEO does not insert anything into any of the body section of output — unless called to do so directly by the theme — and that is where the header image would be appearing.

All the best,
Greg

Uh, no — GHPSEO is generating the meta description in the following order of preference: 1) your specified meta description, 2) your specified excerpt, 3) the WordPress auto-generated excerpt, which WordPress creates by snipping off the first bit of your content. If you have not specified either 1 or 2, and some other plugin is messing directly with your post content via a filter (not the nicest way to insert things into page output…), then naturally you’ll get that turning up in your head description.

All the best,
Greg

Hi,

Yipes, sorry about that — and good catch! The bug is fixed in version 1.4.5, uploaded a few seconds ago. The instructions tab of the plugin’s config pages details the addition of an extra parm for the function which will ensure it is returned quietly. (I had to do it this way for backward compatibility — otherwise, existing code using the function on the assumption it would echo automatically would stop working properly.)

All the best,
Greg

As I mentioned in your other post about the comment numbering plugin, the display of comments is entirely up to your theme — the comment numbering plugin can do nothing more than make additional information available to your theme.

All the best,
Greg