Hello!
We have processes that assemble reports from as many as 6 individual queries.
Currently the queries run sequentially so the related report cannot be
assembled and displayed until after all queries have completed. Users often
have to wait several minutes for their report. They are not
We have processes that assemble reports from as many as 6 individual queries.
Currently the queries run sequentially so the
related report cannot be assembled and displayed until after all queries have
completed. Users often have to wait several
minutes for their report. They are not happy
If you cannot afford to Upgrade CF then I would suggest switching to Railo.
the problem with sticking with an old version of CF is that you are
vulnerable to all these recent hacks and any future ones as CF8 will not
be getting anew new security hotfixes.
On Tue, May 21, 2013 at 3:51 AM, Al
1. Load a page
2. Use an ajax call and jQuery to populate a select (verified that the value
I'm seeking is loaded)
3. Using a passed parameter (stored in a hidden field), set the proper option
to selected (and this code could be optimized, before anyone mentions it)
I've done this many times
Are you getting an error? If so, what is it? If not, I suspect the
large number of values for the form select may be killing your page
render. Are you having the same results in all browsers?
On Tue, May 21, 2013 at 7:54 AM, Stephens, Larry V steph...@iu.edu wrote:
1. Load a page
2. Use an
No error but I don't think it kills the render - just delays it. It works okay
when I insert what amounts to a delay with the alert().
Only tried it in Firefox so far.
-Original Message-
From: Maureen [mailto:mamamaur...@gmail.com]
Sent: Tuesday, May 21, 2013 11:54 AM
To: cf-talk
Use the complete/success/callback of your ajax call to run this code block:
var x = $('#TheBldg').val(); // storage of passed parameter
alert(x);
if ( x.length 0 ) { $('#bldgID').val(x).prop('selected',true); }
That should ensure the select is available to jquery before attempting to
set it to
Also, keep in mind - and I'm speculating a bit here on your process - if
you have just 6 individual queries that run in a single threaded, linear
fashion and they take 6 minutes to execute, running them all concurrently
may take just as long as it's sounds like your DB server may be taxed or
Hey everyone,
I have a very old site that has a basic form. All of a sudden, the form is
requiring all form form fields to be filled out? The form is a basic form
action=, and I've got required=no on the fields.
What's interesting is that the validation results are quite nice looking,
Link(s)?
CF cannot do anything on the client side (i.e. in the browser). JavaScript
is required for any validation to take place on the client side. Without
seeing code / markup it's impossible to say beyond that.
On Tue, May 21, 2013 at 6:30 PM, Jeff F cftalk_l...@fongemie.com wrote:
Hey
are you using CFFORM or just FORM ?
On Tue, May 21, 2013 at 11:37 PM, Matt Quackenbush quackfu...@gmail.comwrote:
Link(s)?
CF cannot do anything on the client side (i.e. in the browser). JavaScript
is required for any validation to take place on the client side. Without
seeing code /
You'll want to check what mode your page is being rendered in and
which version of HTML it's applying. In HTML 5 the required
attribute is binary meaning that if it's present, the field will be
treated as required regardless of the attribute's value (e.g.
require=no doesn't make the field
As Justin mentioned, if the page was recently changed to an html 5 doctype
setting required to any value evaluates to true. Try remove the required
attribute completely. You can also add novalidate to the form tag.
On Tue, May 21, 2013 at 6:41 PM, Russ Michaels r...@michaels.me.uk wrote:
It sounds like the browser's built in validation is kicking in. Try it with a
different browser and you would most likely get different results. Get rid of
the required attribute in your input fields and it should work like it used
to. Unless you want the browser to handle some of the
Sorry if this is a repost. I'm not sure if the form is submitting.
It sounds like the browser's built in validation is kicking in. Try it with a
different browser and you would most likely get different results. Get rid of
the required attribute in your input fields and it should work like
Good point..
I looked into it... I set up ralio and tested the website. A lot of
pages didn't work.. such as cfform. I know it is easy to replaced
that validation with jquery.. just not enough hours in the day. I
will work on it now as I
have to replace the donation forms anyway..
16 matches
Mail list logo
