{5} Assigned, Active Tickets by Owner (Full Description) (9 matches)
List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.
lmajano
| Ticket | Summary | Component | Milestone | Type | Created | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Description | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #331 | Newbies Ultimate Guide | Documentation | task | 01/22/08 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Create the newbies ultimate guide. Some good pointers are below by Josen Ruiseco:
All of this being done in the ColdBox way of course, and being very elementary in its approach (i.e. Detailed explanations of everything - A view is a snippet of code that does...) The ColdFusion Application Development books are what I cut my teeth on years ago. Perhaps matching that progression in terms of difficulty might be a good approach. A good set of very basic tutorials could go a long way in helping folks choose ColdBox as their framework of choice. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #464 | Enable multi threading for Railo | Architecture | 2.7.0 | task | 06/06/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
As Railo3 support to cfthread so ColdBox should enable multi-threading for caching, logging etc. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #525 | Implement onException interception announcement for ColdProxy when invalid event occurs. | Coldbox Proxy | 2.6.2 | defect | 08/18/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Now uses the cfthrow facade |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #287 | Resource bundles must use cache now to load and unload from the coldbox cache. | Plugin Resource Bundle | 2.7.0 | enhancement | 11/03/07 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Resource bundles must use cache now to load and unload from the coldbox cache. This way languages can be unloaded if not used. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #515 | New Validation Plugin | Plugins General | 2.7.0 | enhancement | 08/12/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This plugin idea comes thanks to Josh Giese. The idea behind the validation plugin is to be able to create rules to validate incoming data. You can define the rules in a simple structure that can be sent to the validation plugin for validation. The plugin would read the RC and validate against these rules, producing an results structure as each rule is validated. Rules can also be created as validation beans (cfc). Where you can share validation rules for certain criterias. Examplerules["username"] = "required" rules["password"] = "required" Cascading rulesrules["username"] = "required|minlength[2]|maxlength[10]" rules["date"] = "trim|required|valid_date" rules["content"] = "trim|required|xssclean" You are basically giving a set of commands to the rules key. The validation plugin will read this rule and create all the necessary rules for each incoming element. Custom UDF ValidationYou will be able to do custom UDF validation also by passing a UDF reference into the rule like "udf_isMyElementValid" These UDF's must all accept an incoming string variable and return a boolean variable. <cffunction name="isMyElementValid" returntype="boolean" access="public"> <cfargument name="Str" type="string"> <cfscript> if ( trim(str).length() gt 10 and trim(str) neq "whatever" ){ return true; } else{ return false; } </cfscript> </cffunction> Validation RulesHere are some validation rules that could be used
Cleanup/Setup Commands:
CF Commands:Any cf udf that takes in a string parameter. Below are some useful ones
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #138 | ColdBox Extension Archives | Architecture | ideas | 05/05/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
This is preliminary and just ideas for brainstorming. The ability to create reusable handlers,layouts/views and simple configs for extending applications. This would give the developer the ability to package their application or sub-set of applications into one single archive (zip). This way a developer can distribute this archive and a user can place it on a special directory on their application called extensions or archives and the dashboard or the developer will unzip the archive here. On app startup, the framework will read the extensions and register their events and location. The special config file here, could declare some URL matching filter to trigger the events, or just trigger the events according to extension name. For example, the extension folder can be called: blog Which has a handlers directory, layouts, views, etc. The framework will register this extensions' handlers for execution. Then when I pass the event: blog.entries.dspAll The framework will recognize the extension package name blog and then look for the entries handler and execute the dspAll method. The framework detects this extension point and presents the layouts and views used here. In order to also connect to the parent, there could be be extra logic here, to actually set views to render from the parent. The only things that could be available to these extensions could be views/layouts. However, the whole point of the extensions is for them to be agnostic of their environment. The scopes are all in the same scope, so single sign-on and application,session scopes can be shared. This idea could promote more community involvement in creating coldbox extensions. It is also a great place to connect to via the Dashboard Application. This way, I can generate an application and actually query the community db and download extensions for my new app. RAD to the MAX. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #354 | fwreinit from allowed IPs | Coldbox (cfc-cfm) (Front Controller) | 2.7.0 | ideas | 02/18/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Is this possible to have another security layer for fwreinit command. At the moment fwreinit is protected by password. <setting name="fwreinitIP" value="192.168.1.10"/> We could do this in Application.cfc but might be this is useful feature for coldbox. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #470 | Cross Site Scripting (XSS) | Architecture | 2.7.0 | ideas | 06/09/08 | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
add official/core support for [Cross Site Scripting (XSS)] AntiSamy? (XSS) plugin is available in code-depot. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| #237 | CFFrameworks Plugin XML Update | Eclipse CFFrameworks | enhancement | 08/31/07 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Update the Plugin XML to include the new 2.1.0 features |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
