Learn More





Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogComments and Karma Failing with 404 ErrorComments and Karma Failing with 404 Error
New Post
7/22/2014 8:15 PM

DNN Platform v7.3.1

DNN Blog v6.0.7 upgraded from v4.1.1

Blog permissions:  All Users - View Comments and Add Comment

No users are able to add a new comment, or to like, dislike, report, approve, delete, or reply to an existing comment. In all cases a network trace shows errors along the lines of "<website>/DesktopModules/Blog/API/Comments/<action> 404 (Not Found)"

This happens with a host user, an admin user, a registered user, and an anonymous user.

Other modules, as well as DNN administrative modules, are able to make Web API calls with no error. I have verified that DotNetNuke.Modules.Blog.dll appears correct in the website /bin folder. I have peeked at the source code, and it is behaving as if the call to each of these services is failing the security check (I.E. -  <BlogAuthorizeAttribute(Services.SecurityAccessLevel.AddComment)>, etc.)

Is there some configuration step I am missing? The commenting buttons and links appear appropriately, in that anonymous users get the option to add a comment and administrative users get options to approve/delete comments. The blog owner can add new posts and edit existing posts. It is only the commenting features that seem to be failing, and again it appears to be due to permissions at the web service level.

Any suggestions would be much appreciated.


New Post
7/23/2014 9:31 AM
Some follow-up information: A clean install of the blog module on a different DNN instance on the same machine (also DNN Platform v7.3.1) works fine for comments and karma. So this is something to do with an upgraded blog vs a brand new blog.

Also, pulling the latest source of the blog module and replaced the BlogAuthorizeAttribute on the comment Add function with an AllowAnonymous attribute to see if it really was a security issue, and got the same 404 error.

I am at a loss as to how to troubleshoot this further.
New Post
7/23/2014 10:56 AM
More additional info: The routes are definitely being mapped. I increased the Log4Net setting to ALL and captured the following:

2014-07-23 10:40:50,377 [Sexy][Thread:10][TRACE] DotNetNuke.Web.Api.Internal.ServicesRoutingManager - Mapping route: Blog-Blogs-0 @ DesktopModules/Blog/API/Blogs/{action}
2014-07-23 10:40:50,379 [Sexy][Thread:10][TRACE] DotNetNuke.Web.Api.Internal.ServicesRoutingManager - Mapping route: Blog-Comments-0 @ DesktopModules/Blog/API/Comments/{action}
2014-07-23 10:40:50,380 [Sexy][Thread:10][TRACE] DotNetNuke.Web.Api.Internal.ServicesRoutingManager - Mapping route: Blog-Posts-0 @ DesktopModules/Blog/API/Posts/{action}
2014-07-23 10:40:50,381 [Sexy][Thread:10][TRACE] DotNetNuke.Web.Api.Internal.ServicesRoutingManager - Mapping route: Blog-Terms-0 @ DesktopModules/Blog/API/Terms/{action}
2014-07-23 10:40:50,383 [Sexy][Thread:10][TRACE] DotNetNuke.Web.Api.Internal.ServicesRoutingManager - Mapping route: Blog-Other-0 @ DesktopModules/Blog/API/{controller}/{action}

When trying to submit a comment, the error returned is:
"Unable to locate a controller for http:///DesktopModules/Blog/API/Comments/Add. Searched in namespaces: DotNetNuke.Modules.Blog.Entities.Comments."

So the route is being mapped, the call is to the correct route and namespace, and the action exists.
New Post
7/23/2014 10:20 PM
I found the solution. When upgrading the Blog module, the installer left an incorrect older version of CookComputing.XmlRpcV2.dll in the site /bin folder. In my case what was still there was v2.4.0.0. The version of that .dll in the installer package is v2.5.0.0. I do not know why the installer is not properly updating that file. In any case, as soon as I copied the correct version of that .dll to the /bin folder, all of the Blog Web API methods began working correctly.

For anyone interested, the way I found it was that I backed up the database and filesystem of the site where it wasn't working, and then I uninstalled and reinstalled the Blog module. With the new installation I created a new blog and verified that the Comments were working. Then I did a diff of the filesystem between the broken and working versions. The only file differences (aside from a log file) were DotNetNuke.Modules.Blog.dll (the only difference was DateModified), and then CookComputing.XmlRpcV2.dll. When I compared the two versions of that, I saw that the one in the broken version of the site had an older version number. At that point I restored the filesystem and database to where I started, verified the Comments were broken, copied over the newer version of that .dll, and verified that Comments were working with that single change.
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsBlogBlogComments and Karma Failing with 404 ErrorComments and Karma Failing with 404 Error

These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?