After some head scratching and cursing, wondering why tags where no longer working in uBlogsy I've discovered that they don't play nicely if the content type which is the parent of the posts is set to list view (in Umbraco 7.2 - I'm not sure if this is also the case for earlier versions or if this is new).
Symptom: show all tags doesn't show anything, and when new tags are added they aren't persisted when the post is saved (no tag added to the tags container, tag not present on post if you go back into it).
When show all tags is clicked this is sending a malformed querystring to the server - the list view appends ?page=1 (etc.) to the edit URL, e.g. /umbraco/#/content/content/edit/2909?page=1. The URL requested by uTagsy is getting this appended to the end, incorrectly: /umbraco/api/uTagsyApi/GetAllTags/?currentNodeId=2909?page=1. This returns the error:
The parameters dictionary contains a null entry for parameter 'currentNodeId' of non-nullable type 'System.Int32' for method 'System.Collections.Generic.IEnumerable`1[System.String] GetAllTags(Int32)' in 'uTagsy.Web.Controllers.WebApi.uTagsyApiController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.
Which is, of course, entirely correct - the currentNodeId will be seen as 2909?page or 2909?page=1, which is not going to parse to an integer!
I'm not sure whether this is a bug in the way uTagsy is generating the URL or in Umbraco (I'm leaning towards the latter - that looks to me like Umbraco is automatically tagging ?page=1 on the end of all URLs without checking for existing querystring parameters.
There's presumably something else at play when the post is saved.
It's not a showstopper on this site - list view isn't really necessary so I've just switched it off - but this could be a problem on sites with a large volume of posts that aren't split into date folders.
Note: there is an issue with uloremsy, which may cause various random issues. You should delete the dll if it's causing ghost nodes or if you experience a random issue like this. That may be the cause.
uTagsy Broken on Umbraco 7.2 with List View
Hi,
After some head scratching and cursing, wondering why tags where no longer working in uBlogsy I've discovered that they don't play nicely if the content type which is the parent of the posts is set to list view (in Umbraco 7.2 - I'm not sure if this is also the case for earlier versions or if this is new).
Symptom: show all tags doesn't show anything, and when new tags are added they aren't persisted when the post is saved (no tag added to the tags container, tag not present on post if you go back into it).
When show all tags is clicked this is sending a malformed querystring to the server - the list view appends ?page=1 (etc.) to the edit URL, e.g. /umbraco/#/content/content/edit/2909?page=1. The URL requested by uTagsy is getting this appended to the end, incorrectly: /umbraco/api/uTagsyApi/GetAllTags/?currentNodeId=2909?page=1. This returns the error:
The parameters dictionary contains a null entry for parameter 'currentNodeId' of non-nullable type 'System.Int32' for method 'System.Collections.Generic.IEnumerable`1[System.String] GetAllTags(Int32)' in 'uTagsy.Web.Controllers.WebApi.uTagsyApiController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.
Which is, of course, entirely correct - the currentNodeId will be seen as 2909?page or 2909?page=1, which is not going to parse to an integer!
I'm not sure whether this is a bug in the way uTagsy is generating the URL or in Umbraco (I'm leaning towards the latter - that looks to me like Umbraco is automatically tagging ?page=1 on the end of all URLs without checking for existing querystring parameters.
There's presumably something else at play when the post is saved.
It's not a showstopper on this site - list view isn't really necessary so I've just switched it off - but this could be a problem on sites with a large volume of posts that aren't split into date folders.
Works fine for me. I just tested on umb 7.2.1
Note: there is an issue with uloremsy, which may cause various random issues. You should delete the dll if it's causing ghost nodes or if you experience a random issue like this. That may be the cause.
is working on a reply...