Hi,

I'm having the same thing happen with uBlogsy v4 installed under Umbraco 7.01 and no uLoremsy package installed.The only change I made was to place the Blog folder direrctly under Content.

v4 also doesn't seem to be showing the summary for a post on the landing page even though Use Summary On Landing is selected in the settings. It is showing the full post body.

Thanks in advance for your help.

Hi Joshua,

I don't have a solution for you on the double blog post but for the summary issue look at like 71 of Views\Partials\uBlogsy\Landing\uBlogsyLandingShowPost.cshtml

change from:

if (useSummary.ToLower() == "1" && d.GetPropertyValue<string>("uBlogsyContentSummary").Trim() != string.Empty)

to

if (useSummary.ToLower() == "true" && d.GetPropertyValue<string>("uBlogsyContentSummary").Trim() != string.Empty)

and that will now show the summary.

For uLoremsy and double post issue I've disabled uLoremsy which stops the double post from happening but then there's an issue with PostDate not validating (I'm assuming it doesn't get set correctly on node creation). Changing it to a non-required field kinda works but then the date and folder it's stored in is all wrong. So even though above will fix your summary issue this package is just not compatible with v7 and you probably want to stay away until it is as it will cause more headaches than it's worth, I know I've already wasted too much time trying to get it to work. I've hit a road block where PostDate is required when node is created so that it can create the post in the correct structure but from what I've been able to find so far setting a default value is not yet possible as of 7.0.2.

Good luck, update if you find any solutions your self!

Hi, Phill. For myself, I have disabled uDateFoldersy as well. General idea is that since umbraco 7.0 have builtin folder-list thing (when contents of folder are not in tree to the left, but in the list to the right), there is no actual need in a blog structure /year/month/day. It does not present any SEO benefits as well.
It may be a nice thing to have, but you can surely live without it. 

Hi Dima,

Good point, I was so focused on trying to get uBlogsy to work that I didn't think about disabling more of it. However it's true that uDateFoldersy isn't needed for the organization in the backend, the part that works really well is the front end url generation with date included. Now I could write a custom controller to handle the date and custom url for me but the whole point packages and using uBlogsy is to not have to re-invent the wheel every time. The more I use it the closer I am to having a custom blog solution, c'est la vie...  v7 is really nice, but it's a shame that it didn't just break all packages, it destroyed them ;)

I confirm the error. I've the same problem.

Thanks for the bug report.

Regarding date folders...I need to think about the best way to handle this. It should be pretty straight forward to add a route when the folders are disabled. How this url is formatted, and how to render the links every time a post url appears might be an issue.

btw, I replied to this post regarding uloremsy http://our.umbraco.org/projects/starter-kits/ublogsy/ublogsy-bugs/47569-uBlogsy-plus-v7-=-duplicate-empty-post-created?p=1

You can resolve the issue by making the following change to the uLoremsy.config file (located at aumbraco-root-folder/Config/uLoremsy.config):

Step 1

Replace this line:

<documentType nodeTypeAlias="uBlogsyPost,uBlogsyContainerComment,uBlogsyFolderDay,uBlogsyFolderMonth,uBlogsyFolderYear,uBlogsyContainerPage" enabled="true">

with this

<documentType nodeTypeAlias="uBlogsyContainerComment,uBlogsyFolderDay,uBlogsyFolderMonth,uBlogsyFolderYear,uBlogsyContainerPage" enabled="true">

Step 2

Comment out the following:

<documentType nodeTypeAlias="uBlogsyPost" enabled="false">
             <property alias="uBlogsyPostDate" enabled="true">Document.DateCreated</property>
             <property alias="uBlogsyContentTitle" enabled="true">Document.Name</property>
             <property alias="uBlogsyNavigationTitle" enabled="true">Document.Name</property>
             <property alias="uCommentsyArticleDisableComments" enabled="true">0</property>
</documentType>

so it looks like:

<!-- <documentType nodeTypeAlias="uBlogsyPost" enabled="false">
             <property alias="uBlogsyPostDate" enabled="true">Document.DateCreated</property>
             <property alias="uBlogsyContentTitle" enabled="true">Document.Name</property>
             <property alias="uBlogsyNavigationTitle" enabled="true">Document.Name</property>
             <property alias="uCommentsyArticleDisableComments" enabled="true">0</property>
</documentType>-->

If you'd rather wait until for a patch or the next version, you can - in the meantime - remove the blank entries and make them editable / delete-able.

You will need access to the SQL database.

1. Try to delete the blank node so you can see the node ID in the error message (Server error: Contact administrator, see log for full details. Failed to delete item ####nodeid####). Alternatively, you can see the node ID in the log file.
2. If you need to get the error from the log, connect to the database, and view the most recent entry in the umbracoLog table. This will reveal the node ID in question.
3. Once you have the node ID, view the umbracoNode table.
4. Within the umbracoNode table, locate the node ID in the list. You'll see that it will not have a value in the "text" column.
5. Type in some text (a short amount will do - we just need something to be visible in the Umbraco admin panel).
6. Go back to the Umbraco admin panel and reload the nodes for your blog.
7. After reloading, you can then click on the previously-empty node (which will now have the text you just typed in)
8. Fill in any empty fields and save/publish.
9. You can now continue to edit or delete it successfully instead.

Note: It seems that the node will continue to be impossible to delete until you enter in as much info as required to save it (after making the update to the node name in the database in step 5). Once you save the node with a name and required fields, it seems to be delete-able.

That was my (hopefully temporary) workaround.

is working on a reply...