I upgraded my Mac to Mavericks over the weekend and I had CF 10 working
yesterday, by using the modified mod_jk.so that someone posted on the net
(since there isn't a fix from Adobe yet).
This morning, it stopped working after trying a CF restart, so I went
through the process again and still
I just tried and it worked for me - the download I mean. What problem did
you have with the link?
As for Mavericks - I updated yesterday and CF is running fine for me. Note
though that I do not use the OSX Apache but rather MAMP.
On Mon, Oct 28, 2013 at 9:10 AM, Scott Brady dsbr...@gmail.com
I did the mavericks fix for cf this morning and a reinstall and I am working
fine using apache and cf10. I already had the dmg for cf so I never messed
towing it.
Sent from my iPhone 4S.
On Oct 28, 2013, at 10:15 AM, Raymond Camden raymondcam...@gmail.com wrote:
I just tried and it
We were getting a fairly generic Error processing your request with a
number of links to the home page and to contact Adobe. It's still
happening (after a restart). Someone else was able to get me the file, so
now just to try to get it up and running again. Isn't Adobe in Apple's
developer
My guess, and I speak here as just Ray, not Adobe Ray, heck, I'm not on
that team anyway, is that they have a certified list of web servers they
support, and adding one involves significant effort, and is probably only
done in major releases, ie, CF11 may support Apache 5 or somesuch. The CF
Funny how the ONLY apps that are not ready for Mavericks are Adobe's.
Adobe has a failed history of being ready for new OS releases whether is be OS
X or Windows. So please do not insult users for Adobe failing to be ready for
new OS releases.
Regards,
Wil
On Oct 28, 2013, at 11:22
And TBH it is pretty daft to just upgrade your OS without first checking
that all your apps are compatible and then moaning about it.
On Mon, Oct 28, 2013 at 4:19 PM, Raymond Camden raymondcam...@gmail.comwrote:
My guess, and I speak here as just Ray, not Adobe Ray, heck, I'm not on
that
Funny how I'm running CF right now. On Mavericks. As I said elsewhere (in
reply to you I believe), maybe since it takes 5 minutes to install your own
Apache at a level that CF supports, perhaps they feel time is best suited
elsewhere.
As for outside of CF, we have responded to questions about
Ok, I'll bite ...
I am running Windows 8.1 on my primary laptop, and now an app that I need
no longer runs. Actually, I've been running Windows 8.x for about a year
now, and a few apps that I need (including one really critical one) still
don't run. But that's a choice I made, I could have
So Will, you are claiming that you have tested every single app with
Mavericks (of which there are thousands) and only Adobe's did not work ?
I wonder how you found the time and the money to do this.
On Mon, Oct 28, 2013 at 4:27 PM, Wil Genovese jugg...@trunkful.com wrote:
Funny how the
I hesitate to jump in on this post as it seems to have generated some vitriol,
but I would have to wholeheartedly agree with Ben Here.
I upgraded to Mavericks and rolled back to Snow Leopard after 12 hours because
of the mod_jk issue. This weekend, thanks to some footwork by Sean Coyne and
That said, I would never deploy a production CF Application to and OSX server
because, as servers go, itÂ’s not as
high on the priority list for bug fixes and maintenance - no matter which
CFML server you are using.
This is my sentiment exactly. And since you should be developing on
the
Actually, I DID check for compatibility and it seemed like there was a
workaround (provided by the community) that had been working. Obviously, I
couldn't test it without actually upgrading it. And we're not talking about
a major apache version change (2.2.21 to 2.2.24).
As far as working in
It's been forever since I setup MAMP, but if I remember right, there is a
place for httpd.conf mods that it won't touch. Try moving the lines there.
Going by memory here though.
On Mon, Oct 28, 2013 at 1:38 PM, Scott Brady dsbr...@gmail.com wrote:
Of course, now I'm in MAMP hell, because it
As far as working in the same environment as we deploy to, that's easy if
you work for a single client, I suppose. But, that's not something that's
always possible.
Dave, not all of us have the luxury of developing only on the platform that
gets deployed to. We have a number of clients
On Mon, Oct 28, 2013 at 2:06 PM, Dave Watts dwa...@figleaf.com wrote:
I guess what I'm getting at is: the code I'm writing is almost
certainly not going to be running on OS X, so why should I care that
much about the details of the development environment on OS X? Are you
doing any
I use 2 features of Apache (that I don't *think* the built in web server in
CF handles):
1) virtual hosts
I used to care a lot about this, but honestly nowadays I find I'm only
working on one project at a time, so I just switch the root directory
around when I move from one local project to
Ditto to what Ray said.
Plus, the client I'm working with now has a set httpd.conf (and SSL) setup
that is fairly standard for the developers, and going off of that makes it
harder.
Of course, MAMP is already going off of that standard, but I'd be happy
just to see the CF Admin show up at this
On Mon, Oct 28, 2013 at 12:34 PM, Ben Forta b...@forta.com wrote:
Bottom line: The CF team is working on ColdFusion 11 and 12. Going back
to make changes to CF10 to support an OS that was released post CF10 is
a business decision that they will have to make, one that will
undoubtedly have
19 matches
Mail list logo
