Hmmm...
I tried using the specialIDList.push(specialID) approach, and I get the
correct
output in console.log, [ 27, 28, 26 ], but I also get the error in
Firebug,
500 Element SPECIALIDLIST is undefined in ARGUMENTS.
I also tried using specialIDList = specialID.join(', ') and I still get the
On Thu, Jan 16, 2014 at 9:54 AM, Rick Faircloth r...@whitestonemedia.comwrote:
Hmmm...
I tried using the specialIDList.push(specialID) approach, and I get the
correct
output in console.log, [ 27, 28, 26 ], but I also get the error in
Firebug,
500 Element SPECIALIDLIST is undefined in
Here's the client-side code:
$(document).ready(function() {
$('#newsletter_preview_button').click(function() {
var emailNewsletterGreeting = $('#email_newsletter_greeting').val();
var specialIDList = [];
$('.special_title_checkbox:checked').each(function() {
var specialID =
Inside your .each loop you want to push specialID to your array like so:
specialIDList.push (specialID). Afterwards when you are preparing your
values object to be sent to the server you do specialIDList.join to put
them into a string.
On Jan 16, 2014 12:32 PM, Rick Faircloth
Hi, Steve...
I just gave that a try, but still get an error in Firebug:
500 Element SPECIALIDLIST is undefined in ARGUMENTS
Also, in the console, I still get what appears to be the same when I use
console.log(specialIDLlist):
[ 27, 28, 26 ].
Perhaps something is missing on the cfc method side?
Hold the horses!
I changed the join from:
specialIDList.join();
to:
var specialIDList = specialIDList.join();
and it worked!
I think the var, specialIDList, was not available to the ajax function
since it was being recreated
in the .each loop.
So, now do I have to loop over the multiple
You cant break the string into individual arguments. It will be one
argument that contains a string with comma separated values, which can be
easily handled with CFs list functions. I'm not sure what you want to do
with them in your CFC, but you can loop through the values like so:
cfloop
Hi Folks
I am looking at changing VPS providers to maintain and upgrade CF
I have an option of Windows 2008 or 2012 server.
The reccommendation is 2008 and was wondering what others think.
I spent a week a year ago migrating from 2003 to 2008 and would rather not go
thru that hassle again in
You could just run your form through this tiny plugin, prior to
submitting your ajax request
https://github.com/cutterbl/CFQueryToForm/blob/master/resources/scripts/jquery/jquery.serializejson-0.2.js
Steve 'Cutter' Blades
Adobe Community Professional
Adobe Certified Expert
Advanced Macromedia
if your starting from scratch then you may as well start with 2012, there
is no reason not to except the elarning curve if your not used to it, but
you will have to do it at some point anyway, so may as well be now.
On Thu, Jan 16, 2014 at 7:27 PM, Rob Voyle robvo...@voyle.com wrote:
Hi
A payment processor changed one of their certificates which is causing CF
to throw an exception when we try to connect via CFHTTP using SSL.
The error message is: *I/O Exception: Name in certificate
`internetsecure.com http://internetsecure.com' does not match host name
`test.internetsecure.com
If I remember correctly, the JVM keeps it's own cache of certificates. I'd
search for the commands to remove a cert from the built-in java keystore.
It's pretty simple using the keytool app but you might need to restart CF
to make it take.
-Jake
On Thu, Jan 16, 2014 at 2:05 PM, Jason Durham
Is it a 2048 bit cert? I seem to remember CF8 needing a patch to handle those.
Jon
On Jan 16, 2014, at 3:05 PM, Jason Durham jqdur...@gmail.com wrote:
A payment processor changed one of their certificates which is causing CF
to throw an exception when we try to connect via CFHTTP using
I dealt with this same problem. In my case, solution was to edit hosts file
on server(s) so that internetsecure.com and test.internetsecure.com both
have the same IP and then, in your cfhttp, use the name that matches the
cert.
On Thu, Jan 16, 2014 at 3:05 PM, Jason Durham jqdur...@gmail.com
Agree with Russ. Having used both, I prefer 2012 now - once I got used to the
new interface.
-J
On Jan 16, 2014, at 2:54 PM, Russ Michaels r...@michaels.me.uk wrote:
if your starting from scratch then you may as well start with 2012, there
is no reason not to except the elarning curve
Can anyone provide assistance as to why CF 8.0.1 isn't happy
with this certificate?
It sounds like they're using a certificate with multiple embedded
hostnames (known as alternative names) which is not supported by Java
6. Importing the cert into the java cert cache won't help. You will
need
The main thing about 2008 is compatibility. You know more things are
going to be compatible with it because it's been around longer. If you
know everything you'll be using is compatible with 2012, then it
shouldn't be a problem to make the jump to it.
Warm Regards,
Jordan Michaels
On
I am looking at changing VPS providers to maintain and upgrade
CF I have an option of Windows 2008 or 2012 server.
Server 2012 is a solid platform though it takes some getting used to
the GUI interface updates. It's grown on me since I started dealing
with it. Server 2008 still feels new,
btw if the url rewrite problem is an issue for you, then you could perhaps
use Helicon APE instead.
On Thu, Jan 16, 2014 at 8:31 PM, Justin Scott leviat...@darktech.orgwrote:
I am looking at changing VPS providers to maintain and upgrade
CF I have an option of Windows 2008 or 2012 server.
I would do 2012, as the end-of-life for the OS would be further out, and
pushes any kind of required upgrade out to a further date. The learning
curve is not beyond an experience with 2008, IMHO.
OS version matters little with PCI compliance. If anything 2012 should be
more up-to-date and
You will need to import the star (*) certificate into the keystore for the
java instance ColdFusion is running upon.
Basically ColdFusion doesn't like to speak to *.domain.com certificates (I
think CF10 doesn't mind so much), as it is not an exact match to the URL it
is attempting to access.
You will need to import the star (*) certificate into the keystore for the
java instance ColdFusion is running upon.
Basically ColdFusion doesn't like to speak to *.domain.com certificates (I
think CF10 doesn't mind so much), as it is not an exact match to the URL it
is attempting to
OS version matters little with PCI compliance. If anything 2012
should be more up-to-date and secure (HA, Windows joke contained
within).
I'd add that this will depend on your QSA. Some are beginning to
nitpick the SSL cipher sort order which older versions don't allow you
to specify.
Apologies, Justin is correct. I tested this on one of our CF 8 servers and
the host file/IP manipulation worked as stated.
I'm so used to dealing with the * certificate issue, I wasn't aware this
wasn't the case for the new certificates with the multiple names.
FYI, I tried things out on CF 10,
FYI, I tried things out on CF 10, and it appears to accept these types of
certificates without issue.
What's the JVM version you're using on that installation?
-Justin
~|
Order the Adobe Coldfusion Anthology now!
Simply stating it works on ColdFusion 10 is meaningless. ColdFusion 10 installs
with Java 1.6 by default. So unless youve patched CF10 and explicitly
installed Java 1.7 and edited your jvm.config to use Java 1.7 you are still on
Java 1.6.
Wil Genovese
Owner / Sr Web Application
26 matches
Mail list logo
