Martin Davies
Martin Davies

Reputation: 4456

Can't Open Web forms for marketers Form Designer or Security Manager

I have had WFFM running on a Sitecore instance for a while, but it has recently stopped working. When I go to "Form Designer" on an existing form, I get the standard Sitecore "The requested document was not found" page.

Requested URL: /applications/modules/web

User Name: sitecore\admin

Site Name: shell

If the page you are trying to display exists, please check that an appropriate prefix has been added to the IgnoreUrlPrefixes setting in the web.config.

Note that the requested URL is stated as /applications/modules/web instead of /applications/modules/web forms for marketers.

A lot of development has occurred on this site recently, so I'm not sure when exactly this started happening.

Additional: info:

EDIT

This also seems to be affecting the Sitecore Security Editor:

Requested URL: /appl

User Name: sitecore\admin

Site Name: shell

If the page you are trying to display exists, please check that an appropriate prefix has been added to the IgnoreUrlPrefixes setting in the web.config.

EDIT 2

Further investigation with this is making me think it is related to the Requested URL. I originally thought the the "Not found" page was displaying the requested url incorrectly. However, if I attempt to goto mysite.com/sitecore/shell/applications/fake folder with spaces/fake page with spaces I get this error message:

Requested URL: /applications/fake folder with spaces/fake page with spaces

User Name: sitecore\admin

Site Name: shell

If the page you are trying to display exists, please check that an appropriate prefix has been added to the IgnoreUrlPrefixes setting in the web.config.

As you can see the Requested Url is correct in the error message. So in relation to my problem, I think maybe Sitecore is requesting the wrong URL in the first place.

Additionally if I go to the go the following url by typing directly into the browser, then the Security Editor opens as expected: mysite.com/sitecore/shell/Applications/Security/User-Editor

Upvotes: 1

Views: 1586

Answers (2)

Martin Davies
Martin Davies

Reputation: 4456

This is quite old now but I thought I'd provide an update for anyone else who encounters the problem.

Unfortunately, Sitecore support weren't able to help beyond pointing out that setting the addAspxExtension attribute to 'true' in the link provider seemed to solve the problem. This may have been acceptable except that extensionless URLs were important to the customer.

In the end I had to amend my link provider so that addAspxExtension is set to 'true' in the web config, and then I set it to false inside the GetItemUrl method for specified sites only.

So now whenever the context site is 'Shell' or 'Admin' etc, the extensions are added by default, but switched off in my main website.

Of course, this is a work around. I still don't know how to actually fix the problem

Upvotes: 1

divamatrix
divamatrix

Reputation: 1126

So the first thing that I am going to tell you is that I suspect that there is something wrong with your site declaration for Sitecore Modules. In your web.config, there's a site declaration for "modules_shell" and "modules_website". Those are where the code files that run the modules are usually located... a shell folder to run the parts that run in the Sitecore shell and a web folder to run the part that is accessed by the externally facing site. Please check your site declarations (and the form.config file) to make sure that you're not in live mode or something like that. I would definitely say that this is where you should start looking.

The next thing is to say that your comments about Sitecore not serving a url in the /sitecore/shell directory is really not surprising. Sitecore processes all requests unless you specifically tell it to ignore requests (like setting it in the IgnoreUrlPrefixes in web.config), it's going to try processing it. Like going to /sitecore/shell/applications gives me a layout error because it doesn't have anything set to handle that request. Now your error suggests that there is something wrong with Site declarations.. however, even if they were all right, it still wouldn't work.

Upvotes: 0

Related Questions