ifelse

Ifelse,stupid ? but how do I remove the bold tag from the sidebar exept for the titles?

I hope you weren’t implying that I’m stupid:-)

Anyways, what you need to do is add the following to style.css

#sidebar a{
font-weight:normal;
}

Jeremy, the credits are fine:-) As I said before, I’m glad you found the theme useful and in turn, I’m sure other people benefit from your work.

Good job!

Do you mean the one I’m using on my site? Unfortunately, I’m keeping that one for personal use but the theme should be fairly easy to restyle.

As Jeremy has done, I’d prefer it if everyone try to stamp a bit of their own individuality on things. Of course, feel free to learn from others and to use published themes as a starting point.

Glad you’ve found my theme useful:-)

Posts will be retrieved via site.com/year/month/day/slug but pages will be retrieved via site.com/slug

There is no issue with a page and a post having the same slug (I’ve just tested it out on my sandbox and pages trump posts).

Underneath it all, WP is still using page/post id’s as the unique identifier. Slugs and date info are secondary information and can be used for archival purposes (whether by htaccess rules or WP itself).

Madie,
If you’ve got ftp access to the server, have a look to see if there’s a file called .htaccess in the wp directory. If so, see if the contents of the file changes if you do the following:

1. login to the WP admin panel
2. Navigate through options > permalinks
3. enter /archives/%year%/%monthnum%/%day%/%postname%/in the Structure text field
4. click update.

Do a force refresh your browser i.e. CTRL F5. This will make it reload the css file.

Incidentally, Matt mentioned that future WP releases will have a differently numbered CSS file so that you won’t need to do this in future.

Pages are written by default without the time structure i.e. example.com/page-slug regardless of what structure has been specified for posts.

The WP panel automatically writes out the .htaccess file for you (in fact it’s probably better if you start from a blank slate and not try to work on top of an existing file).

The best way to see if it suits you is to try it. You can always go back and adjust things if it’s not quite right for you.

Well at the rate he is going ifelse is going to be ahead of me
Not likely:-) I’m really just trying stuff out for fun so there’s not really a schedule or plan in my case. In the long term, what I’d plan to do is build on the framework that you’re working on.

The coloured sidebar is provided by the following background image:
https://www.diapason.bo.it/wp-content/themes/default/images/kubrickbg.jpg

“Also, what happens to any links people have bookmarked or set up as links in their web pages, to existing posts if I change the permalinks now midstream?”
Think of the friendly permalink structure as shortcuts. The underlying page (and links) still work as before. In short, there’s no risk for you at all in moving to this format.

That I believe is the secondary purpose. What permalinks will do is organise your pages to be easily memorable.

I agree. A cruft-free permalink provides context and description. For example, https://www.example.com/2005/03/26/football-match

• let’s me know when it was posted
• gives me an idea what it’s about before even going to the page
• provides a meaningful uri for people to link to
• provides cues to search i.e. I can try navigating to https://www.example.com/2005/ for all the posts in 2005
• is independent of the platform i.e. the fact that it’s using MT or WP, or if it’s on windows/linux is irrelevent

the contact form (ryan duff’s) pushes itself waaaay down to the bottom of my left menu…
It’s probably the clear:both on the .contactleft class.

If you post this in the MY WORDPRESS section, you might get better response since that is where people hang out who will do what you are asking. It’s more problem solving with specific design issues here.
Someone needs to write descriptions for each of the areas. It’s not that clear what goes where and often, the topics overlap.

I agree. Looking forward to the official release of Aphrodite!

Nice design. Well done with the indentation; I tend to indent the php code as well as the html which means that that a view-source on the end result always tends to look a bit of a mess ??

Good job!