The landing node has a default author specified and is saved and published. When you say "the default should be rendered by the macroScript automatically if there is no author set" do you mean just on the front end of the website? So the Author field doesn't get populated in the post node? That's not happening here either, but it would change where we need to look for a solution...
When you say "the default should be rendered by the macroScript automatically if there is no author set" do you mean just on the front end of the website?
Yes.
uBlogsyListAuthors.cshtml has a method called GetAuthorOrDefault
So the Author field doesn't get populated in the post node?
OK - so because my script files have been customised, and recent upgrades have only required the dll's it looks like my script files are still old versions - I've merged the changes now and they work ok, except that the default author doesn't seem to get included in the list of authors on the right of the page. Is that as intended?
I am working with version 3 on Umbraco 6.1.5 and the default author is showin on posts that do not have an author set, as described, but the search does not return any posts when you click on the author, unless you have manually set an author in the Post Info tab.
Default Author not populating
I'm using uBlogsy 2.1.1.1 on Umbraco 4.11.1 and have spotted 3 issues:
1. The default author in the Post Info tab is not being set when creating a new blog post
2. When the blog is located lower in the content tree (ie below level 2), creating a blog post does not open the content tree down to the new post
3. When saving and publishing a post with a change of date, the content tree closes - you have to save again to get the content tree to re-open
Has anyone encountered these issues and / or got any suggested fixed?
Thanks
Allan
1. The default author should be set after the first save, not on creation.
2 and 3 are umbraco tree issues.
Thanks Anthony
1 - isn't being set on first save either
2 and 3 - any suggestions for workarounds / fixes?
1 - isn't being set on first save either
Sorry, my mistake... that was a previous version. Now the default should be rendered by the macroScript automatically if there is no author set.
No idea about the tree. If it's an issue for you, perhaps log a bug? issues.umbraco.org
OK - any idea why the author isn't being populated for us then? We're using uBlogsy 2.1.1.1, now on Umbraco 4.11.4
Chekc the landing node for the default author settings. Ensure it is saved and published. Might have to delete umbraco.config and republish.
The landing node has a default author specified and is saved and published. When you say "the default should be rendered by the macroScript automatically if there is no author set" do you mean just on the front end of the website? So the Author field doesn't get populated in the post node? That's not happening here either, but it would change where we need to look for a solution...
When you say "the default should be rendered by the macroScript automatically if there is no author set" do you mean just on the front end of the website?
Yes.
uBlogsyListAuthors.cshtml has a method called GetAuthorOrDefault
So the Author field doesn't get populated in the post node?
Correct.
OK - so because my script files have been customised, and recent upgrades have only required the dll's it looks like my script files are still old versions - I've merged the changes now and they work ok, except that the default author doesn't seem to get included in the list of authors on the right of the page. Is that as intended?
default author doesn't seem to get included in the list of authors on the right of the page. Is that as intended?
Yes. You can manually add the default author there if you wish.
I am working with version 3 on Umbraco 6.1.5 and the default author is showin on posts that do not have an author set, as described, but the search does not return any posts when you click on the author, unless you have manually set an author in the Post Info tab.
Ah. You're the first person to flag that as an issue. I never considered that scenario.
It could be easily fixed with an event hook on the publish event. Just set the default author
is working on a reply...