Drupal 7.x

I am trying to input this into a theme site but the link is not working any ideas please???

script type="text/javascript">
<!-- 
camfrog_nick = 'NoDrAmaUk';
camfrog_domain = 'camfrog.com';
//-->
</script>
<script type="text/javascript" src="http://www.camfrog.com/js/get_status_picture.js">
</script

Pete

[Moved to support & added code tags - Heine]

We're in the process of rebuilding our website from the ground up. We currently have the site in off-line mode. Is there a way to allow users to logon and view the site without granting them administrator privileges? This functionality is needed so that employees can visit the site and make suggestions while it's still in development.

Thanks. :)

Are there many good modules available for D7? I am running a D7 test server and would like to try a few modules that I use in D6, like a Rich Text Editor, Smileys, image uploader, views/panels and Advanced Forums... Are any of these available yet?

Opera just released Opera Unite, a web server in your web browser.
unite.opera.com

Wouldn't it be great if you could get lots of little drupal bases in your web browser. Community module testing, and development would be so much easier.

Is there a way or a module to add fields to the user registration like inserting a email address twice and validate if they are the same using AJAX?

I'm really impressed with the automatic testing initiative and all of the unit tests that are being written -- it is surely paying off in higher quality releases of core and contrib. It got me wondering about capturing user testing feedback for core and contrib. A contrib module, for example, could pass all unit tests and still fail user testing due to a problem with backward compatibility or an incorrectly implemented feature. The nagging concern when upgrading anything with Drupal is how to thoroughly test each module's functionality with so many point upgrades. This especially becomes concerning when you are upgrading many sites in batch.

Maybe there would be a way to add a data field to the updates.drupal.org xml that gives some indication of confidence? Maybe the usage count for a given release or the usage count compared against the number of reported bugs for that release? That way, upgrade processes (manual or drush etc.) could upgrade modules that have attained a certain level of usage or confidence. I'm not propose a rating system -- to vague and prone to opinion. But usage, bugs and age might all factor together to give some level of confidence?