Another type of "Possible Attack"

In Admin>Basic settings;

Tried using custom HTML block with the following HTML

<p>
<style type="text/css">
.style1 {
 font-family: Verdana, Arial, Helvetica, sans-serif;
 font-size: 14px;
 color: #0000FF;
}
</style>
<marquee class="style1" direction="left" behavior="alternate"> Come meet everyone in the Chat Room Tuesday at 9pm GMT</marquee></p>

This works fine on 6.1.4 and would be nice if it also worked on D7.

Here is another little item that triggers the possible attack message.

In admin>advanced settings>variables>currency sign (for display purposes only):

The default is &#36; which is for the dollar sign but when I tried changing it to &#163; for the pound sterling sign it triggered a POSSIBLE ATTACK.

These problems are already fixed in current version, you will be able to test it in RC version.

 Ah hello!

Could you please tell us what to fix as would really like to test it now and not when the RC is out? I thought the purrpose for us to try out beta versions was so that we don't have to chance it with an RC on a live site.

Please send a link to the fix. Thanks in advance.

Friendly warning: RCs are not intended to be used on live sites.

 Thanks for the heads up!

Thanks for that heads up, i wondered why i was getting so many errors, much appreciated

No problem.

To newcomers: If you are starting out with Dolphin (great choice BTW!), you have 2 options: stick with the current stable release product (Dolphin 6), or wait for D7 to be released.

Currently, Dolphin 7 is at Beta status, which means it is still a work-in-progress. RC (Release Candidate) versions are not stable public distribution-ready solutions neither. So, if you are new to the Dolphin framework, you should stick with D6, keep an eye on the developments in these forums/online demos for Dolphin-education purposes, and upgrade later on (i.e., when Dolphin 7.0 is released).

The beta process allows users to test the framework as its being produced to spot bugs, errors, recommend enhancements, etc. While some [experienced] developers are using/will use the beta and RC versions for their own live sites, the normal route to go is to wait for Dolphin 7.0 to be out.

Note to BoonEx: Perhaps you guys should post a warning/disclaimer somewhere as newcomers may get/are getting? confused about which version to download.

I found this posted on another site and thought it may help.

The vocabulary of CTP, Beta, RC, RTM

There is probably some official page somewhere that defines these terms better.  But since I toss them around around all the time, I probably owe it to some readers to explain what they mean.  Here goes, from least to greatest:

CTP - community technology preview - this is just a point in time release to get more bits into hands of customers between beta releases, for those hard core people who want to be as close to the action as possible. 

Beta - these releases get special attention from the QA Team, we plan for them, treat as a milestone, etc.

RC - release candidate, this is the one we hope will become an RTM.  Testing additional RC candidates can get to be like a baseball game in extra innings.  When we finally say "ship it" everyone celebrates.

RTM - release to manufacture, this is the RC that gets shrinkwrapped

Here is a bad car wash analogy. 

CTP quality assurance is like driving through the self-serve car wash, or maybe like having it rain so often that a car wash is not necessary.  One of the perks of living in Washington state. 

Beta release quality assurance is like driving through the self-serve car wash and splurging for self-serve vacuuming (during the beta stage you really do have a chance to participate in the process and influence quality). 

RTM quality assurance is the deluxe full service car wash.

The main fix is here:

http://www.boonex.com/trac/dolphin/changeset/13117