Its still not replacing the $post[fieldx] with anything. (Yes, I changed the 'x' to a #, which is unique)

My Postbit:
<p><font face="Arial" size="2" color="$post[field42]">$post[message]</font>
</p>

Output of a post:
<p><font face="Arial" size="2" color="">
Output
</font>
</p>
I mean, please tell me if I'm being retarded and doing something wrong. I don't think I have... but I probably did.

Remember, this is searching for the custom profile field content of the POSTER, not your own.

So to test this, fill out a color in your OWN custom profile field, then post something, and look at it.

If you want your color to affect ALL posts by OTHER posters, replace $post[fieldx] with $bbuserinfo[fieldx]. Otherwise, if you look at posts by other posters, and they haven't filled it out, their post will remain normal ie. color=""

Make sure you have the profile id correct too. To get the profile id, put your mouse over the link - the number at the end of the URL is the profile id number.

I think I'm calling the field wrong, because I have filled out the field, and its not showing up in threads I've posted in.

When I made the field, I set it up as following:
Max Input, and field length are both 25, I set the display order to a number to 6 (we have 5 other custom fields), its required, visible, and editable by the user.

I think my problem is I was calling $post[field6], but that's the display #.

This may sound stupid, but how do I go about finding the field#?

I figured it out, but I'm curious to know if there's a more conventional way than reading the output source of my profile page.

Sorry to have made this simple thing so much trouble!

The custom profile field id is NOT the display number!!! That is what I was trying to tell you in my posts! :)

You get the custom profile field id number by putting your mouse over the link to the custom profile field, and looking at the number at the end of the URL. Or opening the link to that custom profile field in a new window, and looking at the number at the end of the URL.

It should work now that you are using the CORRECT field number. :)

Sorry about that. I just woke up, and I must have scrolled past it. *bleh*

Thanks for all your help though.