ColdFusion 10 Update 16 prerelease build available

February 20, 2015 / Piyush Kumar Nayak

ColdFusion 10 Update 16 early access build is now available for your testing and feedback. Please note that this is a test build and should not be used in a production environment.

Refer this document for the list of bugs fixed in this update.

Follow the steps below to apply this update.

  1. Navigate to ColdFusion Administrator -> Server Updates -> Updates.
  2. Under Settings tab, check "Automatically Check for Updates" check box
  3. Change the Site URL to https://cfdownload.adobe.com/pub/adobe/coldfusion/PR/updates.xml. 
  4. Click Submit to save your changes.
  5. Under the "Available Updates" tab, click on the “Check for Updates” button.
  6. "ColdFusion 10 Update 16" should be listed under the "Available updates" tab. 
  7. Click on the "Download and Install" button to install the update.

The build number after applying this update should be 10,0,16,293351(PreRelease).

In case, you have configured local site for receiving the update notifications, then please take back up of the URL before changing it to the prerelease URL.

We will look forward to your valuable feedback and suggestions.


ColdFusion 11 Update 5 prerelease build now available

February 20, 2015 / Piyush Kumar Nayak

ColdFusion 11 Update 5 early access build is now available for your testing and feedback.  Please note that this is a test build and should not be used in a production environment.

Refer this document for the list of bugs fixed in this update.

Follow the steps below to apply this udpate.

  1. Navigate to ColdFusion Administrator -> Server Updates -> Updates
  2. Under Settings tab, check "Automatically Check for Updates" check box
  3. Change the Site URL to https://cfdownload.adobe.com/pub/adobe/coldfusion/PR/updates.xml. 
  4. Click Submit to save your changes
  5. Under Available Updates tab, click on “Check for Updates” button.
  6. "ColdFusion 11 Update 5" should be listed under "Available updates". 
  7. Click on "Download and Install" to install the update.

The build number after applying this update should be 11,0,05,293351(PreRelease).

In case, you have configured local site for receiving the update notifications, then please take back up of the URL before changing it to the prerelease URL.

Please share your valuable feedback and suggestions.

ColdFusion 11 Update 4 released

February 19, 2015 / Piyush Kumar Nayak

ColdFusion 11 Update 4 is now available for download.

This update includes bug fixes related to JSON, Imaging, Websockets, Charting, Language and Database.

For the list of bugs fixed in this update and the installation instructions please refer this technote.

For those who have applied the early access release (pre-release) build of Update 4, follow the steps below to reinstall Update 4.

  1. Uninstall Update 4 (PreRelease). 
  2. Reinstate the update URL by clicking on the "Restore Default URL" button in the "Server Updates" section in the ColdFusion administrator.
  3. Switch to the "Available Updates" tab and click on the "Check for Updates" button.
  4. Download and install Update 4.

 



Custom Error + onMissingTemplate + CF + IIS = confusion?? Not Exactly

February 16, 2015 / Milan Chandna

I have seen many customers getting confused in custom error pages and onMissingTemplate feature in ColdFusion and IIS. So I thought of blogging it for the use of larger audience. Before starting let me setup a platform.

Customer Eddard(name assumed) is using ColdFusion10(valid for ColdFusion11 too) configured with IIS. He has setup onMissingTemplate in Administrator of ColdFusion. Now Eddard expects ColdFusion to run this error page(mentioned in onMissinTemplate), let's call it 404.cfm, whenever user hits a page which doesn't exist. But suprisingly his browser is not showing the contents of 404.cfm and instead showing IIS 404 error page which is a static file(html file). After a lot of struggle he finds another confusing behavior that when he access the non existing page from machine where server is running(localhost) then his 404.cfm is getting executed. It's clear from the behavior that there is somehting in IIS which is handling this behavior.

.

.

.

You guys must be thinking what is the right approach then. I will give three scenarios and you can chose any one depending upon your requirements.
1. Custom error page - Simply use custom error page and do not use onMissingTemplate. You have to opt for "Custom error pages" in "IIS->site->error pages->edit feature settings". And give a 404.cfm url against required status code like 404 in "IIS->site->error pages". This cfm will be executed whenever that error has been hit like a user requested for non existing page. The page will not be executed twice since you have not mentioned anything in onMissingtemplate.

.

.

.

Read More


Migrating from ColdFusion 9 to ColdFusion 11

February 13, 2015 / Sandip Halder

Migrating from ColdFusion 9 to ColdFusion 11

Since we have been getting lot of calls/queries around migration these days, I thought it would make sense to make a blog post on it. Now, since Migration is a very broad subject we need to keep in mind the Technology, Hardware, Operating System, Settings, Application Server, Web Server, Code compatibility.

Migrating from ColdFusion 9 to ColdFusion 11 can be done by more than 1 way. In this article we will discuss ways on how to migrate from ColdFusion 9 to ColdFusion 11.

There are 2 ways to migrate from ColdFusion 9 to ColdFusion 11

       1.       Migrate via Car files

       2.       Migrate via migration wizard

Migrate via Car files:

ColdFusion archive files (.car) files can be generated and deployed only if both the version of ColdFusion are in enterprise edition. Out of all the differences between standard and enterprise edition, one of them is that you cannot create a .car file in standard edition (generation of car file feature is available in ColdFusion 11 standard edition now). So, if you have ColdFusion 9 enterprise edition and ColdFusion 11 enterprise edition you can migrate via these method. In the ColdFusion 9 admin page please go to packaging and deployment >> ColdFusion Archives. In the ColdFusion archives page you will find two options

         ·         Deploy an Existing Archive

         ·         Create an Archive

Now, since we are creating the archive file we will select create an archive option. On the Archive name option let us give a name say “test” and click on create. Once the archive is created it will be listed under Current Archive Definition List. In the actions bar please click on the pen icon (refer to the image below):

 

When you click on the icon, a pop up page will open up where you can select all the settings that you want to migrate (refer to the image below)

After you select all the required settings you can click on close window button. After closing the pop up window, let us click on the build archive button (refer to the image below)


 

When we click on that button, a pop up page opens up where it gives you a summary of the selected settings (refer to the image below)

Please select next after you have reviewed the settings. In the next page, we will be asked to select the .car file. Now, let us create a folder in say “C” drive and name it test. Now, inside the folder let us create a file with extension .car . Let us name it migrate.car. Now, in the page let us browse to the that folder and click on okay and add the file name, the path should look like C:/test/migrate.car (refer to the image below)

Now, let us click on next and we should get a popup message saying “Build Successful” (refer to the image below). 


Click on okay and close the window. Now, let us go to ColdFusion 11 admin page and go to the same place that is  packaging and deployment >> ColdFusion Archives. Let us remember that we have already created the .car file and now we need to deploy it. So we will work on the first option that is deploy an existing archive. Click on the bowser server option and browse to the migrate.car file which we have created earlier. (Refer to the image below)

After entering the path click on deploy button and a pop up window will appear. Click on next and the next page will give you the option to deploy and it will specify the Deploy Locations as well (Refer to the image below)

Once you click on the button deploy, you will get a pop up message saying Deploy successful (Refer to the image below)

 

When you get the above message you have deployed the .car file successfully and with it migration from ColdFusion 9 to ColdFusion 11.

 

Migrate via migration wizard

In case you have a ColdFusion Standard installation or moving to one and both the versions are on the same server, then you need to modify the adminconfig.xml within ColdFusion. The location for adminconfig.xml is \ColdFusion11\cfusion\lib\

Now, if we are trying to migrate from ColdFusion 9 to ColdFusion 11, please follow the below mentioned steps:-

        ·         Navigate to adminconfig.xml for ColdFusion 11 and open it with text editor.

        ·         Change the value from “false” to “true” at

                          <Runsetupwizard>false</runsetupwizard>

                          <Runmigrationwizard>false</runmigrationwizard> and

                          <migratecf9>false</migratecf9>

        ·         Save the file and restart ColdFusion Service.

After restarting the service, you will get the migration wizard. Follow the on-screen instructions to continue.

 


Blue Mango Theme Design By Mark Aplet

Super Powered by Mango Blog