Skip to main content
added 18 characters in body
Source Link
Richard Seal
  • 20.8k
  • 5
  • 44
  • 79

We have deployed our project on Azure Staging CM and CD and everything works fine. We then moved to production instance CM/CD. CM works fine but on CD site freeze on ajax calls and browser prompts to stop running script in jqueryjQuery lib (hosted on cdnCDN).

We also noticed that '@URL.Action'@URL.Action is returning empty string while on CM it is returning an actual URL. Any ideas?

Update Calling hostname/api/sitecore/controller/actionhostname/api/sitecore/controller/action on CM throws an exception when trying to access the RenderingCOntextRenderingContext: Attempt to retrieve context object of type 'Sitecore.Mvc.Presentation.RenderingContext' from empty stack', which

Attempt to retrieve context object of type Sitecore.Mvc.Presentation.RenderingContext from empty stack'

Which means it started executing the action. However hostname/api/sitecore/controller/action

However hostname/api/sitecore/controller/action on CD redirects to our page not found page. So

So my question is: are there mvcMVC routes differences between CM and CD?

We have deployed our project on Azure Staging CM and CD and everything works fine. We then moved to production instance CM/CD. CM works fine but on CD site freeze on ajax calls and browser prompts to stop running script in jquery lib (hosted on cdn).

We also noticed that '@URL.Action' is returning empty string while on CM it is returning an actual URL. Any ideas?

Update Calling hostname/api/sitecore/controller/action on CM throws an exception when trying to access the RenderingCOntext: Attempt to retrieve context object of type 'Sitecore.Mvc.Presentation.RenderingContext' from empty stack', which means it started executing the action. However hostname/api/sitecore/controller/action on CD redirects to our page not found page. So my question is: are there mvc routes differences between CM and CD?

We have deployed our project on Azure Staging CM and CD and everything works fine. We then moved to production instance CM/CD. CM works fine but on CD site freeze on ajax calls and browser prompts to stop running script in jQuery lib (hosted on CDN).

We also noticed that @URL.Action is returning empty string while on CM it is returning an actual URL. Any ideas?

Update Calling hostname/api/sitecore/controller/action on CM throws an exception when trying to access the RenderingContext:

Attempt to retrieve context object of type Sitecore.Mvc.Presentation.RenderingContext from empty stack'

Which means it started executing the action.

However hostname/api/sitecore/controller/action on CD redirects to our page not found page.

So my question is: are there MVC routes differences between CM and CD?

added 403 characters in body
Source Link
TamerM
  • 1.7k
  • 13
  • 26

We have deployed our project on Azure Staging CM and CD and everything works fine. We then moved to production instance CM/CD. CM works fine but on CD site freeze on ajax calls and browser prompts to stop running script in jquery lib (hosted on cdn).

We also noticed that '@URL.Action' is returning empty string while on CM it is returning an actual URL. Any ideas?

Update Calling hostname/api/sitecore/controller/action on CM throws an exception when trying to access the RenderingCOntext: Attempt to retrieve context object of type 'Sitecore.Mvc.Presentation.RenderingContext' from empty stack', which means it started executing the action. However hostname/api/sitecore/controller/action on CD redirects to our page not found page. So my question is: are there mvc routes differences between CM and CD?

We have deployed our project on Azure Staging CM and CD and everything works fine. We then moved to production instance CM/CD. CM works fine but on CD site freeze on ajax calls and browser prompts to stop running script in jquery lib (hosted on cdn).

We also noticed that '@URL.Action' is returning empty string while on CM it is returning an actual URL. Any ideas?

We have deployed our project on Azure Staging CM and CD and everything works fine. We then moved to production instance CM/CD. CM works fine but on CD site freeze on ajax calls and browser prompts to stop running script in jquery lib (hosted on cdn).

We also noticed that '@URL.Action' is returning empty string while on CM it is returning an actual URL. Any ideas?

Update Calling hostname/api/sitecore/controller/action on CM throws an exception when trying to access the RenderingCOntext: Attempt to retrieve context object of type 'Sitecore.Mvc.Presentation.RenderingContext' from empty stack', which means it started executing the action. However hostname/api/sitecore/controller/action on CD redirects to our page not found page. So my question is: are there mvc routes differences between CM and CD?

Source Link
TamerM
  • 1.7k
  • 13
  • 26

Site freezes with javascript execution on CD instance only (Azure WebApp)

We have deployed our project on Azure Staging CM and CD and everything works fine. We then moved to production instance CM/CD. CM works fine but on CD site freeze on ajax calls and browser prompts to stop running script in jquery lib (hosted on cdn).

We also noticed that '@URL.Action' is returning empty string while on CM it is returning an actual URL. Any ideas?