WP strikes back
If you can’t get access to archive pages at the moment, me neither, and it’s because I’m trying to do the smart permalinks thing, which seems to cause nearly everyone trouble… Back to the support forum I go… Bah.
Ten minutes later… Still no joy, and I swear that I can’t see what’s wrong. The scripty thing that does the rewrite works, as you can see in the status bar if you point at the link. Path looks right, I think, and the .htaccess file looks good compared to the ‘do it this way’ posts at the support forum.
Bloody bloody bloody hell. And I wanted to do a good resources post today, not get bogged down in code stuff.
Another ten minutes… Well, I found one way that seems to work, but I’m not sure that I like it too much (that extra /index.php/ in the URL), or that it should be necessary. But if it works, what the hell… Individual, monthly and category links all seem to take you where they should and it’s getting too hot to worry about it any more.
I don’t know what effect this has on any hyperlinks you may have created to the original archive URLs, whether they still work or not.
Next task: stats plug-in (OK, will leave that for a bit. The readme makes my brain hurt). And page-by-page navigation (that sounds like another thing that can go horribly wrong… and for single post pages has just turned out to be really really easy, thanks to the scripty goddess! But for archive pages, hmm, more complicated…) And another look at that menu column in Netscape. Any requests?
2 Comments »
The URI to TrackBack this entry is: http://www.earlymodernweb.org.uk/emn/index.php/archives/2004/08/wp-strikes-back/trackback/
RSS feed for comments on this post.
Leave a comment
Line and paragraph breaks automatic, e-mail address never displayed, HTML allowed: <a href="" title="" rel=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>
looks like your server does not support mod_rewrite. neither does mine which is why I am still in MT hell. The workaround of index.php? is the only way to go until they release 1.3 which is supposed to fix this problem.
Comment by sepoy — Monday, 9 August 2004 @ 3:42 pm
Thanks. It’d sort of occurred to me it must be something to do with that. Still on the learning curve… But at least I can go to the support forums and quickly realise that a) everyone has exactly the same problems and b) there are always some people who have much worse trouble than me… Reassuring somehow.
Comment by Sharon — Monday, 9 August 2004 @ 9:58 pm