I downloaded the 2.1.1.1 zip from the our.umbraco.org package page. Then when I installed the package, it installed uBlogsy under my top root site. It placed all of the content below the existing site. Yet it didn't install the uBlogsy landing (root) page. I would get .net errors when trying to access one of the installed posts.
I got it going. I made a copy of root node 1, then deleted the root node that kept getting renamed. Then I reinstalled uBlogsy and all is well. Then I just resorted/renamed my copy of root node 1 to get everything back to it's original state.
Install for v2.1.1.1 not working
I downloaded the 2.1.1.1 zip from the our.umbraco.org package page. Then when I installed the package, it installed uBlogsy under my top root site. It placed all of the content below the existing site. Yet it didn't install the uBlogsy landing (root) page. I would get .net errors when trying to access one of the installed posts.
I uninstalled the package.
Anyone that can help with this?
Thanks,
Trent
Sorry, forgot to mention umbraco version
I'm running umbraco v 4.8.0 (Assembly version: 1.0.4583.15483)
Trent
I think i've seen this happen before when a root content node has the same name as the root of a node which is installed through a package.
Make sure that your existing root node is named something different.
Thanks Anthony but renaming didn't help.
I have 2 root nodes.
Node #1 name is 'Coming Soon' Node #2 name is 'OUBC Website'. My problem was happening with this setup. I was expecting a 3rd root node to be created.
I renamed node 1 to 'Trent'. I still have the same problem.
After installing, node 1 is renamed to 'My Blog'. See below.
It didn't replace the content in node 1. My doctype and content in the root node remained unchanged. Weird...
I got it going. I made a copy of root node 1, then deleted the root node that kept getting renamed. Then I reinstalled uBlogsy and all is well. Then I just resorted/renamed my copy of root node 1 to get everything back to it's original state.
Thanks Anthony.
Trent
is working on a reply...