ColdFusion 10 Documentation (READ ONLY)

Report · Sep 22, 2012

The "ColdFusion 10 CFML Reference" is currently Read-Only and denies additional comments.

I get a "Not authorized to create discussion in forum" error when attempting to add a comment to this page: http://help.adobe.com/en_US/ColdFusion/10.0/CFMLRef/WSc3ff6d0ea77859461172e0811cbec22c24-7c6e.html

The forum thread (http://forums.adobe.com/message/4281818) for that doc is marked (READ ONLY) w/ the following doc path: "Adobe Community > Adobe Labs > ARCHIVES > ColdFusion 10 (READ ONLY) > ColdFusion 10 Documentation (READ ONLY) > Discussions"

I'll just add my comment here and then I'll try to remember to add it to that doc page when and if this issue is resolved:

----

The 'file' attribute's description should probably also note the following: "The file can only have a .txt or .log extension by default. You can add more extensions in cfusion\lib\neo-cron xml."

This restriction and workaround is new to ColdFusion 10.

---

Thanks,

-Aaron

Report · Sep 24, 2012

Yeah, I got caught out by this last week too. It seems to be fixed now (I just added a comment successfully). This seems to happen about once a month, for some reason..?

--

Adam

Report · Sep 24, 2012

Hi Adam,

I still get the same error. The error I'm seeing seems to only affect the "ColdFusion 10 CFML Reference" section of the docs. Are you able to successfully add a comment against a tag or function doc?

Thanks,

-Aaron

Report · Sep 24, 2012

Yep, I added a comment to CFCHART this morning:

http://help.adobe.com/en_US/ColdFusion/10.0/CFMLRef/WSc3ff6d0ea77859461172e0811cbec22c24-7930.html

I was not able to add said comment last week.

--

Adam

Report · Sep 24, 2012

I was also able to add a test comment to CFCHART just now (and promptly deleted it =P). Now I see the issue..

CFCHART - http://forums.adobe.com/thread/1060096

CFSCHEDULE - http://forums.adobe.com/message/4281818

Just compare the title and breadcrumb trail at the top of both pages =P Looks like some docs are archived in Adobe Labs while CFCHART is "live". That's odd, b/c CFSCHEDULE _used_ to be live (I was previously able to post comments to that one).

Thanks very much for confirming btw.

-Aaron

Report · Sep 24, 2012

@Aaron,

Thanks for the tip on the file extensions! Under CF9, I was capturing the results of scheduled tasks to .htm files (CFDump outputs) for review. Under CF10, I had to write to .log files and then remember to try to use "Open with" to open in a web browser instead of my default text editor. I added .htm as a valid file type in neo-cron.xml, and now I can double-click those .htm result logs and open them in my web browser.

-Carl V.

Report · Sep 24, 2012

@Carl,

You're very welcome! I learned of it from an engineer's comment on a ticket I saw in the tracker. Your use case makes good sense and, IMO, Adobe should just include .htm/.html by default. I've just filed #3336106 in case you want to vote for it.

The only documentation of this is on the following page, under the description for the "Overwrite" CF Admin Scheduled Tasks option: http://help.adobe.com/en_US/ColdFusion/10.0/Admin/WSc3ff6d0ea77859461172e0811cbf3638e6-7ffc.html#WSc... (I've also filed a doc bug for that misplacement).

Thanks!,

-Aaron

Report · Sep 24, 2012

My vote:

Yeah, I encountered this as well. The reasoning was that it was a potential security breach to have a browsable file extension on the log file. I contended that that was not ColdFusion's concern, that was *my* concern, and should be left up to me. Which fell on deaf ears. I stand by what I said, and this should be remedied.

I didn't realise this was a change from previous versions in CF10. It makes their rationale even more bogus, and indeed is a backwards compat issue. And we know what Adobe is like about backwards compat (admittedly only when it suits them...)

--

Adam

Report · Oct 03, 2012

@Adam,

I agree this is a backward compat issue. I recall your discussion regarding log file extensions, but didn't catch the whole security/non-browsable part of it. I added a note suggesting that if Adobe's going to break backward-compat w/ a setting change, then perhaps the changed setting should be editable via CF Admin than via undocumented/improperly documented (both are the case in this issue) modifications to CF's internal files.

Thanks,

-Aaron

Report · Sep 25, 2012

@Aaron - I just voted on that ticket.

@Adam - couldn't agree with you more.

Thank you,

-Carl

Report · Oct 03, 2012

Just noting here that Adobe fixed the cfschedule doc so that it again allows new comments. Hopefully this also fixed any other docs that were also denying comments.

Thanks,

-Aaron