colinj

Ok, that doesn’t work either. If I had the rewrite rules like I describe above then I can’t get to the admin scripts because apache then tries to rewrite /wp-admin/

damn damn damn!

Ok, here’s my solution. Since I don’t really need the permalinks to be of the format /%category%/%postname%/ I set the permalink format back to the sample on the permalink page. I then added the rewrite generated when the format was /%category%/%postname%/

So, WordPress now generates permalinks based on the date and postname and I can use https://digitaldetritus.org/%category%/ to point folks at specific content. Which is really all I wanted.

Oh, but now I realize that if I have multiple categories in the permalink I still get a 404.

Man, now I have to make up new cards. ??

Just to be clear this works:
https://digitaldetritus.org/musings/republicans-think-that-weather-shouldnt-be-free/

and this doesn’t
https://digitaldetritus.org/musings/rants/republicans-think-that-weather-shouldnt-be-free/

The latter is what wordpress generates as the permalink.

ColdForged,

Your link to this post did the trick.

Any chance this change in the rewrite rules might make it into the next version? Unless of course it breaks something else.

Here’s an example (of it working):

https://digitaldetritus.org/teched-2005/

Oh, and you can use that link to follow any blogging I do about this years TechEd.

lawtai,

Nope /%category%/ as the permalink setting means that I get the same behavior as I described above.

matt,

My service provider is running Apache 2 that was one of the things that I checked first ??

I’m getting on again off again outgoing trackbacks.

I tried using the URL listed here as a test but that doesn’t work. But I have successfully posted trackbacks to friends blogs hosted on typepad.

I’m confused.

I have downloaded the nightly build for April 2nd and put those files in place.

I’m still not having any luck with ecto and posting to wordpress. It looks like it’s applying the offset for GMT to anything that I post with Ecto. And then it only shows up in list of posts to manage but not actually on the blog itself.

Anyone got any idea why this might be happening? I’m guessing it’s something about the interaction of ecto and xmlrpc.php. But I’m not at all sure where to look.

I really like ecto and being able to blog from my desktop w/o having to log into the blog itself. So I very much want to figure out what’s going on.

I did ask on the ecto support forums. I pretty much posted the same question in both places. So far I haven’t gotten anything back.

I’ve tried using both metaweblog and moveabletype api settings in ecto and I get the same behavior.

I’m willing to admit that it could be something really obvious that I’m just not seeing. It wouldn’t be the first time.

I’m seeing exactly the same behavior.

In my case I get an incorrect time on the blog but the correct posting time in the RSS feed.

I’m going to amend part of my previous post. When linking to files hosted on archive.org I actually see two different behaviors.

Explicit enclosure keys of the form:

[audio src="https://www.archive.org/download/csr049/csr049_wcwc_01-nick-chapman_take-me-now.mp3" /]

do not get their information updated with file size and type. However enclosure keys of the form:

[audio src="https://audio32.archive.org/3/audio/csr049/csr049_wcwc_01-nick-chapman_take-me-now.mp3" /]

do get updated with file size and type.

Here’s my guess, the first URL is what the folks at archive.org tell folks to use. The second URL is what you are redirected to but I’m also going to guess that the folks at archive.org reserve the right to change things behind the scenes so that the second URL isn’t likely to work consistently over time. I’m going to guess that WP doesn’t know what to do with that redirect and so can’t look up the data for the file.

Oh, neither form, when added to the post as a normal link, gets automagically transformed into an enclosure.

And just for giggles I tried adding two enclosure keys and that does work.

Hi all,

I’ve done some testing and this is what I’ve discovered.

1. It does seem to be the case that when a link points to something on archive.org WP won’t include it in the rss feed as an enclosure unless the enclosure is expressly added.
2. When I do add an explicit enclosure with a URI to a file on archive.org it does add the enclosure but only the URL portion of the enclosure. It does not seem to grab the specific file size or type.

With the advent of ourmedia.org I’m gonna guess that we are going to see a lot more data hosted on archive.org (ourmedia partner).

While I’m at it, here’s the format and behavior I’d like to see.

• use the rel= attribute in the <a> tag for enclosures. It would look something like <a href="example.org/sample.mp3" rel="enclosure">sample.mp3</a>.
• WP could then look for tags marked specifically as enclosures.
• WP checks the filetype and size per the URL provide and spits out a proper enclosure tag.

This is the format that they use at feedburner. Oh, and though I’ve not seen anyone do it, by my reading of the rss2.0 specs it should be possible to include multiple enclosures in a single rss item. That would be cool as well.