When I go to
http://127.0.0.1:8500/index.cfm
on Chrome, coldfusion throws an error saying that page/path doesn't exists.
How do I see the page on my browser?
Make sure it's inside ColdFusion11\cfusion\wwwroot directory. 127.0.0.1:8500/projectfoldername/index.cfm
Related
I'm trying to setup custom CFX tags for Coldfusion 11 but when I try to make a call to one of them the server just throws this 502 error:
I've already looked at the logs in Colfusion administration panel but am getting no entries for this specific issue. This only happens if I call a page with a custom tag... other CFM pages work fine.
Does anyone know how to debug this type of error in Coldfusion 11?
I had a Mura 5 site, Admin stopped working with CF11 update.
I downloaded Mura 6, pasted site content in it, applied updateDB from url to the old database and it updated the DB.
Now admin area is working but i am getting the following error on client area.
Could not find the ColdFusion component or interface C:\sites\mura\test_site1\includes\servlet.cfc.
Ensure that the name is correct and that the component or interface exists.
The only problem is it is looking in old folder name mura instead of root folder of site which I named mura-6.
I don't know where can i change that to fix it. I didn't find any settings in tsetting nor in settings.ini.cfm(this has an abort tag on start btw)
I have also applied appreload, fuseboxreload and there is no mapping i found.
please guide.
I've installed October cms on Wamp with Composer. All seemed ok- I have tables in my database, but can't enter /backend. When I type file:///C:/wamp/www/october/backend (place of my project) I get blank page.
In order to access the PHP compiler you MUST run your site as if it were on the internet i.e. using the browser address bar and NOT click on the php file using explorer. Like this
localhost/october
or
localhost/october/backend
If you dont go via Apache then nothing will spot the <?php tags. It is Apache that recognises these tags and passes the script to PHP for interpretation and execution.
I have inherited a couple established links ending in .jsp. The domain of these links is pointing to my coldfusion 9 / iis 7.5 server.
I have rewritten the functions in cf. I just need the cf/web server to run link with .jsp as a .cfm.
I was unsuccessful using a url rewrite.
I tried to add .jsp to the Handler Mapping using the same config settings as .cfm.
The 500 error that came back in both cases said:
You tried to access a restricted feature for the Standard edition: JSP
I don't want to "run" jsp with Coldfusion which from the error is not in the Standard license. I would like it to run like a cfm file.
Is there a setting in CF Admin to turn off the .jsp recognition?
Thanks,
Gary
Issue resolved:
The first step was to disable *.JSP references in all the default-web.xml files
Then apply a url rewrite. ^(.*)jsp$ which redirects to {R:1}cfm{R:2}
Thanks for your comments and help.
Gary
The first step was to disable *.JSP references in all the default-web.xml files
Then apply a url rewrite. ^(.*)jsp$ which redirects to {R:1}cfm{R:2}
I just deployed a new site, call it SiteA, that uses cftooltip, but the tooltips are not displaying. When I hover over the link, nothing happens. SiteB has been running on the same server for a long time, and it's tooltips display fine. The folders for SiteA, SiteB and CFIDE are all in inetpub/wwwroot.
My browser reports the following when trying to display tooltips on SiteA:
'ColdFusion is undefined'
'YAHOO' is undefined.
It would seem that SiteA can't find what it needs in cfide/scripts, but SiteB doesn't have this problem. In the CF Admin, I have a mapping to cfide.
Any ideas? Thanks in advance for help.
Peter
It's not exactly a solution, but you can cut and paste the CFIDE/scripts folder into the webroot of SiteA, which should at least get it working until you work it out!
Things to check are the mappings (obviously), but also any URL rewriting etc; look into chrome dev tools or firebug to see what is being returned from the missing .js call (i.e is it an IIS or apache 404, or something else?)