Error Editing page

Question

The concept of InContext editing is phenomenal - If only I
could get it to work. I followed all the tutorials making sure to
note the DIV tags etc. Created my account - Set up FTP etc upon
signing on and when I press CTRL-E the page opens perfectly - THis
is where the problem starts, after signing in, I immediately get
the "Page Not Found" page from the parent site?
The InContext editing toolbar is there - The Current page
lists:
http://www.myiste.ca/subsite/sitemap.htm.
The address bar lists
http://www.mysite.ca/subsite/includes/ice/ide.html#page=sitemap.htm.
The Includes directory is on the root of
http://mysite.ca/subsite which
is the FTP root that was set up.
It should work but the page not found issue assumes that the
needed files are not there?
Can you offer any help?

Answer 1

Hello Steve,
Sorry to hear you are having problems. It sounds like the
issue you're experiencing is related to the HTTP HEAD request
method.
Take a look at the following Tech Note which discusses the
issue:
http://www.adobe.com/go/kb406749
Error: "The operation could not be performed because a
problem occurred while attempting to connect to the server" when
trying to edit a page using Adobe InContext Editing
Issue
After successful login in InContext Editing or when
navigating to a page in your website while the InContext Editing
toolbar is displayed, you receive the error "404 File or Directory
Not Found", or, depending on the server configuration, a custom
error page is displayed instead.
If you try to edit the page you will receive the following
error message: "The operation could not be performed because a
problem occurred while attempting to connect to the server. Please
check your Internet connection and try again. For more details,
please visit the InContext Editing Support Center".
Reason
InContext Editing requires the HEAD HTTP request method to be
enabled and functioning properly for a registered web site.
InContext Editing will not function properly if the HEAD HTTP
request method is disabled or if it does not function properly.
InContext Editing is using HEAD requests to check the
existence of the draft and published versions of the current page.
If those calls do not work as expected (the HEAD should return
status code 200/304 if the checked page exists, 404 otherwise) then
you will experience this behavior. In most cases the problem
appears on web servers running IIS 6 or 7 with PHP installed as
CGI, but this problem may occur with other server configurations as
well.
Solution
Contact your web hosting provider for assistance. This may
require changes in web server configuration.