Putting internal links in blogroll

it doesnt sound silly at all. BUT:

the word “client” always get my personal hackles up since I tend to believe that people that are working for clients are getting paid, and can handle the legwork necessary to figure out what they need to be doing. They are the ones being paid after all ?? Not us volunteers, ya know?

<rant>”Web designers” often get these “set up WordPress for me” jobs, and typically these designers dont know enough about WP to even tell that client the bare essentials about using it when they’re done. Frankly, people that post on here day in day out, are the ones that ought to get those jobs since we know WP in and out.</rant>

I mean no disrespect, I just thought I might point that out. You may or may not receive a cold shoulder here but I can say Im not alone in my feelings, so you never know.

I can definitely see your point there, but in this case, by “client,” I mean “friend of mine that does comedy music and I really like his stuff so I’m trying to set up a great site for him to increase his fanbase and I never expect to be paid for it,” and WordPress is exactly the kind of backend I need for this.

So, um, I think I’m still in some sort of volunteer category, too. ??

Admittedly this is my first WP site, but I’m trying to get my brain wrapped around it enough to eventually be able to help answer questions as well.

cool, thanks for clarifying. Now that thats out of the way, what trouble are you having with adding internal links to the blogroll?

As long as you use full urls there shouldnt be any trouble. Just dont use relative paths, ie, /download.html

Ah, okay. I was wondering if there was some way to do relative paths there, since I will be having 2 domains pointing at this single WP install, and I don’t want people to get confused if they come from one and the full URL comes from the other.

Honestly, it’s not that big a deal, but I like consistency. If I have to do full URLs, so be it.