cffunction access=public name=qry_unlock_items_for_paypal output=no
returntype=void hint=Unlocks items for paypal.
cfargument name=app_user_id type=numeric required=no default=0
cfargument name=cfuserid type=string required=no default=
cfif arguments.app_user_id neq 0
cfquery
Matthew,
the /cfcomponent tag at the end of the code should be removed OR a
cfcomponent tag should be added to the top of the file. the two tags serve as
bookends and work together. one cannot exist without the other.
Sent from my iPhone
On Jun 14, 2014, at 8:14 AM, Matthew Smith
Definitely depends on the content of the custom tag itself. The first
thing I notice is that none of the variables are scoped (not even the
query name), and that could just be all kinds of fun.
First thing I would do is, inside of that tag code, dump the
attributes.NetID value. Each run of
Hi!
So I added this code to increase our EXT grid timeout from 2.5 minutes to
10 minutes:
Ext.onReady(function(){
Ext.Ajax.timeout = 60;
});
So now, EXT grids will wait longer for CF to return the JSON to populate
the grids. Works great under about 5 minutes. The problem is: *above* 5
On Sat, Jun 14, 2014 at 10:16 AM, John M Bliss wrote:
So I added this code to increase our EXT grid timeout from 2.5 minutes
to 10 minutes:
Any ideas?
I am not sure I would try to work with AJax data that took that long to
return. You have so many variables with different browsers (with
How many records are returned to populate the grid? If itÂ’s taking 5+ minutes
to complete, then the number of records, the table or query optimization is
probably the more important issue.I would suggest the following:
1) Implement a paging solution with OFFSET/LIMIT - You can use AJAX to
Confirmed: only happens in Firefox. Thanks, Cameron.
On Sat, Jun 14, 2014 at 10:28 AM, Cameron Childress camer...@gmail.com
wrote:
On Sat, Jun 14, 2014 at 10:16 AM, John M Bliss wrote:
So I added this code to increase our EXT grid timeout from 2.5 minutes
to 10 minutes:
Any ideas?
7 matches
Mail list logo
