Forums / Cotonti / Extensions / Color Usernames

@diablo, your still thinking "single color".

@Lombi, I'm not trying to get offended or anything, it just seems silly that all kinds of features that I've been working on are becoming part of the cotonti core, but its not my work going in so it's obviously being redone which means, developer time wasted.

I remember downloaded 5 different version of Captcha for sedito and they all sucked ass, had the 5 guys came together to make 1 good one, it would have been awsome and worth downloading and using. I can deal with it though, If I can add to the core, I can take from it if I don't like features.

@oc, No, I don't think every code written gets used, and I don't write code to try and get in into the core, but all of them so far will likely become part of it(though im sure im far, far more complex and far less understandable code, such as AJAX). And my code will be hindered useless and I will be forced to chaulk it up as a learning experience. Which is great and all, but not as good as having people actually appreciate and use the code.

@Kilandor, it's all good.

-Sad Panda Out!

I never had any of them actually work prior to 121, I got it two weeks ago. The last time I used Sedito was two or more years ago, forget the actaul version it was on.. :(

I belive the other two I'm thinking of came from outside sources, as a last ditch effort to have a working captcha back then. The owner of the site couldnt get it going so it eventually closed and the captcha was the least of its worries.

I'm just going to hold off on building anything else for a while, because I'd rather be able to use it, than take a chance on it being in a future cotonti core release and my code being useless. Even though they are great learning experience and shouldn't really matter to me being on my website, but they do.

Maybe since Sedito is officially done getting new releases, I should just stick with it since I know what it does and does not have already included in the core. If I build something, it's not going to be replaced or useless from core upgrading.

I took a look at the link in your signature for things I could work on and with the methods I'm using to code, I think I'm a bit outdated for doing any of those. I would definately give the Profiles a go, with friends, recent viewers, ect... But I'm not sure I could do it in a way that you guys would accept.

# TwistedGA : I never had any of them actually work prior to 121, I got it two weeks ago. The last time I used Sedito was two or more years ago, forget the actaul version it was on.. :(

I belive the other two I'm thinking of came from outside sources, as a last ditch effort to have a working captcha back then. The owner of the site couldnt get it going so it eventually closed and the captcha was the least of its worries.

I'm just going to hold off on building anything else for a while, because I'd rather be able to use it, than take a chance on it being in a future cotonti core release and my code being useless. Even though they are great learning experience and shouldn't really matter to me being on my website, but they do.

Maybe since Sedito is officially done getting new releases, I should just stick with it since I know what it does and does not have already included in the core. If I build something, it's not going to be replaced or useless from core upgrading.

I took a look at the link in your signature for things I could work on and with the methods I'm using to code, I think I'm a bit outdated for doing any of those. I would definately give the Profiles a go, with friends, recent viewers, ect... But I'm not sure I could do it in a way that you guys would accept.

I've been using this system since LDU 603 and all versions have had working CAPTCHA solutions. I honestly can't remember any non-working scenario that has been put public and confirmed by users.

I dont think you should take the "i'm gonna use an obsolete system cause i know what's in it" however since that's kind of a shot in the foot for your site. we have many security holes patched that seditio doesnt and your site can get hacked by any of those.

I dont think you'd want that.

Cotonti is the system that's seditio 2.0 with all the security and functionality upgrades that people have been bitching about for years. Along with a myriad of features that have been keeping this CMS in the "dark ages" (mostly meaning in the old LDU ages logic).

Sounds good, let us know when you sort out the bug.

Working like a charm.
Using it live^^:)

Are you running cotonti release 0.0.3 or 0.0.2? The newest version(0.6.0) is built for use with 0.0.3.
Tested in both FireFox 3.0.5 and InternetExplorer 7 on multiple machines.

If you can, please take a screenshot of the effects/errors being shown when this hack is installed. If you are running cotonti release 0.0.2 I highly suggest updating to 0.0.3 and reinstalling. Or I can throw together a new build for 0.0.2 compatibility.

I will do my best to help solve these issues, no matter the cause. :)

So I took some time to retest this modification and ran into a 502 error on a fresh install of 0.0.3 and colornames 0.0.6. Not good. So I took some time and redid the entire thing from scratch. Using the same functions, but starting with fresh unmodified files. Build 0.0.7 is now ready and working flawlessly again. I'm thinking part of the problem was in the amount of releases due to little issues and additions, but I suppose thats just how it goes.

I deleted all my SQL databases and deleted all cotonti directories, cleared my history and temp files and started fresh for this round of testing, straight from the official .zip to my server with 0.0.7 on top. I've tested and included versions for both cotonti 0.0.2 and 0.0.3. Hopefully this will clear up all issues anyone has had. I appologize for the problems, it's been hard getting out of the habbit of using notepad to edit PHP files (HUGE NO,NO!)...I belive that was to blame for your issues.

Have a go at this and let me know how it works out. :D
http://rapidshare.com/files/205406077/ColorNames-0.0.7.zip

# TwistedGA : Colored Usernames. We've assigned them using CSS by GroupID(good for showing moderators, unfair to members). We've assigned them by UserID(fair to members, give moderators bold, or other style). These methods are very effective but require a lot of space in your CSS files, and lack a very nice feature to have. MultiColored names. Such as "nismo240". The ability to assign each individual letter's color, style, weight, ect.

Heres a screenshot of a username with random color change in it in action, I probably should have made them alternate but wheres the fun in that. Fades are awsome.



Link for 0.0.7:
http://rapidshare.com/files/205406077/ColorNames-0.0.7.zip

Not to sound rude, but your code isn't even efficient. It issues a SQL query to the database for each user name displayed per page. So say you were looking at a forum topic that had 10 posts that is 10 extra queries. I made a core hack for LDU/Seditio years ago, on my own site though I recycled the code and it doesn't issue a query for each user. You can see an example of what it, here:
http://vilegaming.com/league.x/standings1/3

# Spartan : Not to sound rude, but your code isn't even efficient. It issues a SQL query to the database for each user name displayed per page. So say you were looking at a forum topic that had 10 posts that is 10 extra queries. I made a core hack for LDU/Seditio years ago, on my own site though I recycled the code and it doesn't issue a query for each user. You can see an example of what it, here:
http://vilegaming.com/league.x/standings1/3

No, I don't find it rude at all man. I thought I had explained the reason for returning to this method. I can change it around and make it not add the extra queries, but it's far more invasive to the core and with future releases said to support this feature from the getgo, I find little reason to invade the core and remove the extra queries for use until then..