slakethirst

Brilliant! Everything was dandy with my blog until I upgraded to 2.6 this evening, upon which my cura?aos and cafés, mères and gemütlichs grew garbled, UTF-8 notwithstanding. Commenting out the charset line in my wp-config straightened everything out nicely. An unexpected solution, to be sure, but whatever works.

I had a problem with stats not liking my identity… Turned out that my girlfriend had logged into wordpress.com and WP Stats was paying attention to the cookie (I assume… Open ID?) and denying me access, even with the API Key. Once I logged her out of wordpress.com and logged in as myself, everything went swimmingly. Let this be a lesson to you all: sharing is bad.

Incidentally, why can’t WP Stats store my API key? Whenever I disable the plugin (which is not infrequently in these early days of testing WP 2.5), it forgets the key. Akismet has no problem storing the key across plugin deactivations, so I just cut and paste it from the Akismet field.

Here’s something I don’t fathom. I’m using SimpleTags 1.5.3 (and WP 2.5), and when I perform some administrative actions, like activating or deactivating a plugin—tasks that perform a redirect on submit, I think —the redirect fails. I’m left with a completely blank page, no content, no source. In the case of activating/deactivating a plugin, the url of the page I get includes a nonce (e.g. https://example.com/wordpress/wp-admin/plugins.php?action=deactivate&plugin=no-www.php&_wpnonce=5f54e4f7c2) which normally I never see. If I’m updating a link via the Link Manager, it stalls on https://example.com/wordpress/wp-admin/link.php. This isn’t interaction with another plugin, as it happens when Simple Tags is the only running plugin.

So, something in Simple Tags appears to be breaking my administrative interface with 100% reproducibility. I’ve uninstalled it for the time being, but look forward to future updates.

genesteinberg: Simple Tags 1.5.2 was released today (April 1), and purports to address performance issues.

Hmm. But wp_get_links now seems to be displaying descriptions — which I don’t want — and the codex doesn’t indicate that wp_get_links accepts an argument about that one way or the other. ?? Gadzooks.

Say, that half-way worked. Now it’s definitely getting category names. However, the code I have to display links (by category) is wp_get_links($link_cat->cat_id); ? and it’s returning emptiness. Do you know what would have changed there?

Sorrow. I see that the original poster has, indeed, gone to MT due to the lack of historical date support. I, too, am interested in achieving dates before Jan 1, 1970 for historical purposes. While I’m game for installing the adobdb date functions, I’d much rather not have to alter core functionality (and then maintain it, through successive upgrades).

Unfortunately, I see that ticket #2149 has had its priority set to low ??

For what it’s worth, the WP Cat-Posts plugin will nicely list all titles in a given category. You may be able to achieve what you’re looking for with that.

Then again, if your site is going to be that small, have you considered using sub-pages beneath parent pages, instead of posts within categories?

On the more general subject of effective means of eliciting support and assistance, Wikipedia may prove instructive.

I have noticed similar issues with Google Analytics, in which it lists two entries for some of my pages — once with the title interpreted properly, and a second time with entity codes for non-ascii characters in the title. I’ve no idea what’d be causing it (theoretically I’m serving up UTF-8), but you’re not alone in wondering what causes it.

Google Analytics of my own traffic has about 13% at 800×600, 46% at 1024×768, and the rest > 1024 … I get a lot of search-based traffic, as opposed to regular readers, so I’m inclined to view it as an almost random sample. Were I redesigning for increased width, I’d shoot for a layout no wider than 960 or there ’bouts, to support the 1024 majority while allowing room for scrollbars and a bit of window tiling. But your mileage will most definitely vary.

Yes. I haven’t used it myself, but try the Viper’s Plugins Used plugin. It generates output like this.

nice. and particularly handy for me, since I am an Alberta Streetian. i look forward to it fleshing out. are you not listing hours because you don’t want to keep up with seasonal changes etc? ‘cos I think it’d be useful to provide a general sense of “closed around 6” or “open lateish.” A man needs to know that La Bonita is closed on Mondays, and that Sirenita is generally open an hour later, for stragglers.

Sorry, I don’t. Certainly you can setup a feedburner feed for foo.com/category/feed, but i’m not dab enough with htaccess to tell you what format the redirect would take. My wordpress theme doesn’t support autodiscovery for category feeds — it just announces the main feed — so this hasn’t been an issue for me.

The feedburner plugin from orderedlist.com seems to work well. It redirects requests for your current feeds to FeedBurner, so things oughtn’t break. works for me, afaik.

As for autodiscovery, well, in theory even autodiscovered requests should be re-routed to FeedBurner, but if not, editing your header.php file should do the trick.

This post in the FeedBurner forums explains what to looks for and replace, to ensure that autodiscovery points folks to you at FB.

The publicize tab in your feed’s page at FB has several helpful links to assist you, too.

Tony, you may find Eric Meyer’s Color Blender handy for generating colors related to your theme, though I suppose you’ll have to just trust it to a certain degree.