Added uBlogsy to an existing Umbraco 6 installation and relocated it as a child node to sitename.com/blog
If I try to click the Content node to get to the dashboard menus, I get the below error. If I comment out both CreatePost and Admin user-controls from Dashboard.config the page will load.
I just pulled the source but haven't had a chance to step through everything yet. Anyone have any quicker suggestions? Happy to provide more details.
TruthBrew
[NullReferenceException: Object reference not set to an instance of an object.]
umbraco.cms.businesslogic.web.Document.get_Text() +6
uBlogsy.Web.usercontrols.uBlogsy.dashboard.CreatePost.InitBlogRoots() in D:\_PROJECTS\Personal\uBlogsy\uBlogsy\uBlogsy\uBlogsy\usercontrols\uBlogsy\dashboard\CreatePost.ascx.cs:46
uBlogsy.Web.usercontrols.uBlogsy.dashboard.CreatePost.OnLoad(EventArgs e) in D:\_PROJECTS\Personal\uBlogsy\uBlogsy\uBlogsy\uBlogsy\usercontrols\uBlogsy\dashboard\CreatePost.ascx.cs:20
System.Web.UI.Control.LoadRecursive() +70
System.Web.UI.Control.LoadRecursive() +189
System.Web.UI.Control.LoadRecursive() +189
System.Web.UI.Control.LoadRecursive() +189
System.Web.UI.Control.LoadRecursive() +189
System.Web.UI.Control.LoadRecursive() +189
System.Web.UI.Control.LoadRecursive() +189
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3063
Even better, as I was trying to integrate my MVC site with a webforms master template to use ublogsy too. Wasn't pretty but worked for the most part until I ran into these issues.
Not being pushy here, but any timeframe on ublogsy3 release? Any specific areas of code that could be helped with to speed dev?
Uninstalled everything from the prior install and loaded 3.0 beta 2.
When I click on the Blog node in the backend the browser just sits there waiting. As such, I monitored server usage and notice that for the next 3-4 minutes CPU usebumped to a fairly constant 50% and running SQL Profiler over ~500k queries were run against the database for that install of umbraco. Backend eventually comes back with a YSOD "Request Timed Out" error and when that happens CPU returns to 0%.
I changed the "[uBlogsy] [MNTP] Author Picker" to text and the issue seemed to go away. Now have to figure out what the values were to reset it. Whoops
Add it back to see if the issue returns. If it does, unpublish and republish the author container and children. Even try deleting and creating new ones.
Also try restarting your application.
Also, can you please report this bug to Umbraco: issues.umbraco.org. I'm pretty sure it's the xpath in MNTP.
Yea, I'll try. Also important to note is that currently I have both a "Home" node (my site) and the current "Sample Site Root" (unpublished) node under content so that might play into this as well.
I'm trying to move "Blog" under my Home node but it keeps yelling about that content tyle not being allowed as a child even though I modified the DocType to allow it.
Republishing the entire "Sample Site Root" node tree seems to resolve it. So, it appears that if you have elements unpublished underneath the Blog node and click on the blog node, it's gets stuck in some infinite loop
"I'm trying to move "Blog" under my Home node but it keeps yelling about that content tyle not being allowed as a child even though I modified the DocType to allow it."
Strange. Ensure that you have allowed the uBlogsyLanding node under your home node, and not something else by mistake. Also, try refreshing the content tree before trying the move.
It was all related. Because the Blog was timing out, even though it looked like it selected the "Blog" node it really wasn't so when I relocated it it was trying to move an incorrect node which failed (good).
Whew... if nothing else it's a good one for an FAQ... don't click on Blog unless there are children published.
uBlogsy Dashboard controls fail on u6 / non-root blog
Added uBlogsy to an existing Umbraco 6 installation and relocated it as a child node to sitename.com/blog
If I try to click the Content node to get to the dashboard menus, I get the below error. If I comment out both CreatePost and Admin user-controls from Dashboard.config the page will load.
I just pulled the source but haven't had a chance to step through everything yet. Anyone have any quicker suggestions? Happy to provide more details.
TruthBrew
Hmmm...Add that to the list of things that dont work in Umbraco 6.
New ublogsy will be out soon.
Thanks Anthony.
I am a C# / ASP.NET / MVC dev by profession so hoping to eventually contribute once I learn the code base more.
ublogsy 3 will work with umbrco 6 but will be mvc only.
ublogsy 2x works with umbrco 4.7.1 - 4.11.4.1
Even better, as I was trying to integrate my MVC site with a webforms master template to use ublogsy too. Wasn't pretty but worked for the most part until I ran into these issues.
Not being pushy here, but any timeframe on ublogsy3 release? Any specific areas of code that could be helped with to speed dev?
A beta should be available in a matter of days. Just got a couple examine quirks to deal with
Hey Anthony, just checking in for any updates to the uBlogsy MVC 3.0 release.
Should I attempt using the 3.0 beta or is it not far along/stable enough for use?
Jeff
Releasing beta 2 today in a couple hours... it's much better and more stable.
A couple hours was an understatement.
9 hours is what it took, but beta 2 is up now.
ps. please let me know if you come across any bugs.
Great, will do. Thanks AD.
Uninstalled everything from the prior install and loaded 3.0 beta 2.
When I click on the Blog node in the backend the browser just sits there waiting. As such, I monitored server usage and notice that for the next 3-4 minutes CPU usebumped to a fairly constant 50% and running SQL Profiler over ~500k queries were run against the database for that install of umbraco. Backend eventually comes back with a YSOD "Request Timed Out" error and when that happens CPU returns to 0%.
I have a sql trc file if that helps.
Thoughts?
A post is just a normal node in umbraco.
It has a custom tag editor and 2 multinode tree pickers.
I suspect it could be a faulty property editor...
Are you able to replicate this issue? Could you try to change the datatypes of those 3 property editors to text to see if that solves the problem.
Do it one by one to see which one could be causing the issue.
I changed the "[uBlogsy] [MNTP] Author Picker" to text and the issue seemed to go away. Now have to figure out what the values were to reset it. Whoops
I knew it!
Ha, I meant to change the doctype property, not the datatype.
Original value is:
$currentPage/ancestor-or-self::uBlogsyLanding//uBlogsyContainerAuthor
Add it back to see if the issue returns. If it does, unpublish and republish the author container and children. Even try deleting and creating new ones.
Also try restarting your application.
Also, can you please report this bug to Umbraco: issues.umbraco.org. I'm pretty sure it's the xpath in MNTP.
When I restore that datatype to it's default settings the problem returns.
If I can find some time I'm going to try this on a fresh u6 install to see if I can reproduce.
Basically I think the xpath is never resolving.
Can you try to unpublish and republish the author container and children. If that doesnt work, try deleting and recreating them.
Yea, I'll try. Also important to note is that currently I have both a "Home" node (my site) and the current "Sample Site Root" (unpublished) node under content so that might play into this as well.
I'm trying to move "Blog" under my Home node but it keeps yelling about that content tyle not being allowed as a child even though I modified the DocType to allow it.
More soon.
Republishing the entire "Sample Site Root" node tree seems to resolve it. So, it appears that if you have elements unpublished underneath the Blog node and click on the blog node, it's gets stuck in some infinite loop
"I'm trying to move "Blog" under my Home node but it keeps yelling about that content tyle not being allowed as a child even though I modified the DocType to allow it."
Strange. Ensure that you have allowed the uBlogsyLanding node under your home node, and not something else by mistake. Also, try refreshing the content tree before trying the move.
It was all related. Because the Blog was timing out, even though it looked like it selected the "Blog" node it really wasn't so when I relocated it it was trying to move an incorrect node which failed (good).
Whew... if nothing else it's a good one for an FAQ... don't click on Blog unless there are children published.
Thanks for the help, now back to actual testing.
OK, found another thing... start a new thread or keep on going here?
"don't click on Blog unless there are children published."
You specifically mean the authors (and probably the category nodes) right?
If so, this is likely a bug with MNTP.
"start a new thread or keep on going here?"
new please
"don't click on Blog unless there are children published."
You specifically mean the authors (and probably the category nodes) right?
If so, this is likely a bug with MNTP.
I believe you are correct, I'll try to restore my backup and retest it in the next couple days.
is working on a reply...