i have an umbraco application that is developed in 4.9.0 version. i
upgraded successfully to 4.11.1. Now i am trying to upgrade to 6.2.1 .
Umbraco already upgraded. but some of my functionality not working.
what is my umbraco project?
Through my umbraco web application i am interacting with microsoft dynamic crm.
How i implemented my project?
My all logic Placed in separate class project (.cs files). i am calling those methods from my .cshtml file through JSON.
What is issue?
in my understanding c# methods are not calling from .js files.
Thanks for your feedback. To be detail, I am including .js files from Masterpages . When a button is clicked it is loading the .js file which has the code to call the Login( ) method in the MemberService class. Here is the JSON code for calling
Well, it might still work but it's not recommended to use it, which the comment below the link to the /Base documentation also says here https://our.umbraco.org/documentation/reference/ - "/Base has been superseded by Web API above", which is the WebApi stuff :)
But if you got it working in other scenarios then it might still be working of course - But if possible I think it's better to consider switching to using Web API.
Don't know if the other scenarios work because your controllers have been setup differently or something like that perhaps?
upgrade from 4.11.1 to 6.2.1 json issue
i have an umbraco application that is developed in 4.9.0 version. i upgraded successfully to 4.11.1. Now i am trying to upgrade to 6.2.1 . Umbraco already upgraded. but some of my functionality not working.
what is my umbraco project?
Through my umbraco web application i am interacting with microsoft dynamic crm.
How i implemented my project?
My all logic Placed in separate class project (.cs files). i am calling those methods from my .cshtml file
through JSON.
What is issue?
in my understanding c# methods are not calling from .js files.
$.ajax({
type: 'POST',
url: '/base/MemberService/Login',
dataType: 'JSON',
cache: false,
The above showing the code sample. "MemberService" is the class file (.cs) and "Login"
is the method inside the memberservice.cs
I Check the error in Fiddler. Here is the error.
"<error>Extension not found or permission denied</error>". when running the '/base/MemberService/Login'.
Please share your ideas. It will Help me to Go far.
I am also facing the same issue. Please help
Hi Binoy and welcome to our :)
I think you get that error because it's not possible to use /base anymore on v6.
Instead I think you should consider using WebApi to generate the JSON you need.
You can read much more about that in the documentation section here https://our.umbraco.org/documentation/Reference/WebApi/
Hope this helps.
/Jan
Thanks for your feedback. To be detail, I am including .js files from Masterpages . When a button is clicked it is loading the .js file which has the code to call the Login( ) method in the MemberService class. Here is the JSON code for calling
$.ajax({
type: 'POST',
url: '/base/MemberService/Login',
dataType: 'JSON',
cache: false,
While calling the script, it is showing extension not found or permission denied.
Are you sure that in Umbraco 6.2.1, this functionality wont work because we are using the same for all the methods.
Hi Harideep
Well, it might still work but it's not recommended to use it, which the comment below the link to the /Base documentation also says here https://our.umbraco.org/documentation/reference/ - "/Base has been superseded by Web API above", which is the WebApi stuff :)
But if you got it working in other scenarios then it might still be working of course - But if possible I think it's better to consider switching to using Web API.
Don't know if the other scenarios work because your controllers have been setup differently or something like that perhaps?
/Jan
Hi jan,
Thanks for your reply. i cleared the issue. There were modifications in web.config.
https://our.umbraco.org/forum/using/ui-questions/40055-Media-Preview-basefolderbrowserservicegetchildren-basefolderbrowserservicegetchildren
cheers.
Hi Binoy
Aaah, ok - Good to hear you managed to solve it. Then you can always consider making the switch to WebApi when it feels like the right time for it :)
Those steps Sebastiaan mentions in his post are also part of the upgrade documentation btw.
Happy coding!
/Jan
is working on a reply...