Gavrisimo Posted November 13, 2009 Posted November 13, 2009 I really dont see the point of not parsing url's and emoticons in comments on profile page's. :) So i would sugest that you make comments on profile pages more like posts in topics or comments on IP.Content pages where if you put this: You would get this: :) http://www.invisionpower.com/:) http://www.invisionpower.com/
Gavrisimo Posted November 13, 2009 Author Posted November 13, 2009 Of course i didnt report this as a bug. This is how prfile page's work since 2.3.x but there was some small fix i found somewhere which enabled emoticons to be parsed. ;) Cant remember how links worked, but this not parsing links in IPB 3 is just weird. That is why i opened this topic in "IPS Company Feedback" forum, so maybe they change this url & emoticons not parsing issue for next versions.
bfarber Posted November 14, 2009 Posted November 14, 2009 Right now we run a special routine to parse out b, i and u tags only. When the feature was originally built we avoided using the bbcode parser to prevent someone from leaving a bunch of crazy bbcode-formatted content on profiles. I'm not really for or against the suggestion myself.
ssslippy Posted November 14, 2009 Posted November 14, 2009 I am for parsing code on profiles. It confuses people when they can use a smiley one place and not in another.
Gavrisimo Posted November 14, 2009 Author Posted November 14, 2009 [quote name='bfarber' date='14 November 2009 - 12:22 AM' timestamp='1258158148' post='1879032'] Right now we run a special routine to parse out b, i and u tags only. When the feature was originally built we avoided using the bbcode parser to prevent someone from leaving a bunch of crazy bbcode-formatted content on profiles. I'm not really for or against the suggestion myself. How about putting in some setting like "Allow only friend to leave comments?" which would be default "Yes". Or just make it so that you can add comments if you are friend of that person.
Recommended Posts
Archived
This topic is now archived and is closed to further replies.