Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Jeroen Breuer 9904 karma points admin mvp c-trib
    Sep 01, 2010 @ 11:04
    Jeroen Breuer
    0

    The given key was not present in the dictionary after creating blogpost

    Hello,

    I upgraded from Umbraco 4.5.1 to 4.5.2 and now I get the following exception when I try to create a new blogpost in Blog 4 Umbraco:


    The given key was not present in the dictionary. 
    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

    Exception Details: System.Collections.Generic.KeyNotFoundException: The given key was not present in the dictionary.

    Source Error: 

    An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

    Stack Trace: 
    [KeyNotFoundException: The given key was not present in the dictionary.]
    System.Collections.Generic.Dictionary`2.get_Item(TKey key) +9489373
    umbraco.library.niceUrlDo(Int32 nodeID, Int32 startNodeDepth) +277
    umbraco.library.NiceUrlFullPath(Int32 nodeID) +41
    Umlaut.Umb.Blog.EventHandlers.Autoping.Document_AfterPublish(Document sender, PublishEventArgs e) in d:\TeamCity\buildAgent\work\6c8a1edaa924eb51\Umlaut.Umb.Blog\EventHandlers\Autoping.cs:43
    umbraco.cms.businesslogic.web.Document.FireAfterPublish(PublishEventArgs e) +75
    umbraco.cms.businesslogic.web.Document.PublishWithResult(User u) +2528
    umbraco.cms.presentation.editContent.Publish(Object sender, EventArgs e) +308
    System.EventHandler.Invoke(Object sender, EventArgs e) +0
    umbraco.controls.ContentControl.savePublish(Object Sender, ImageClickEventArgs e) +96
    System.Web.UI.WebControls.ImageButton.OnClick(ImageClickEventArgs e) +115
    System.Web.UI.WebControls.ImageButton.RaisePostBackEvent(String eventArgument) +120
    System.Web.UI.WebControls.ImageButton.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +10
    System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +13
    System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +36
    System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5563

    Could this have happend from upgrading?

    I've already added a codeplex item for this: http://blog4umbraco.codeplex.com/workitem/5526.

    Jeroen

  • Frej Raahede Nielsen59 karma points
    Sep 06, 2010 @ 21:12
    Frej Raahede Nielsen
    0

    I get a similar error with Umbraco 4.5.2. "By accident" I installed Blog4Umbraco via the package repository in Umbraco, which I uninstalled and then installed the 4.5 version.

  • Duncan Gunn30 karma points
    Sep 07, 2010 @ 17:08
    Duncan Gunn
    1

    This doesn't happen straight away on creating the blog post for me, but I do get the same error when I enter some content and publish.

    However it sorts itself out and seems to work when I refresh the nodes.

    Another thing that could be related is that the blog post initially is created directly under the Blog node, not under the 2010/9/7 structure.

    Publishing, ignoring the error and refreshing fixes this.

  • Shaun416 karma points
    Sep 07, 2010 @ 19:21
    Shaun
    0

    I'm seeing the same behavior as Duncan. I have googled and according to this chap...http://twitter.com/theplastictoy, blog4umbraco can be made to work "smoothly" by using this changeset - http://blog4umbraco.codeplex.com/SourceControl/changeset/changes/54177

    Unfortunately I have no idea what to do with the changeset now I've downloaded it. Anyone else got any ideas?

     

     

  • Frej Raahede Nielsen59 karma points
    Sep 13, 2010 @ 17:54
    Frej Raahede Nielsen
    0

    I get a rather strange error that might have something to do with the .NET error on publish: The blog creates a dublicate of the datefolders and blog post - with the same id! 

    I will try updating the package and see if it fixes it.

  • Rick Ratayczak21 karma points
    Sep 15, 2010 @ 08:55
    Rick Ratayczak
    0

    I am getting this error, and I also don't know what to do with the changeset either.

    When I try to set the blog skin I also get this error:

    Error installing skin:
    System.IO.FileLoadException: Could not load file or assembly 'ICSharpCode.SharpZipLib, Version=0.85.4.369, 
    Culture=neutral, PublicKeyToken=1b03e6acf1164f73' or one of its dependencies. The located assembly's 
    manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) File 
    name: 'ICSharpCode.SharpZipLib, Version=0.85.4.369, Culture=neutral, PublicKeyToken=1b03e6acf1164f73' 
    at Umlaut.Umb.Blog.DataTypes.SkinBrowser.ExtractPackage(String zipPath) at Umlaut.Umb.Blog.DataTypes.
    SkinBrowserDatatype.DataEditorControl_OnSave(EventArgs e) in d:\TeamCity\buildAgent\work\
    6c8a1edaa924eb51\Umlaut.Umb.Blog\DataTypes\SkinBrowserDatatype.cs:line 71 WRN: Assembly binding
    logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
  • Lee2679 karma points
    Sep 23, 2010 @ 21:02
    Lee
    0

    I am having this problem, however I think its an actual problem with an event that triggers after the post is published I'm going to download the code from codeplex and see if I can figure it.

    @Shaun - That changeset will not fix this bug, if you look at the comments its from Ben (CodeGecko) and all he has done is changed the XSLT files not the core. If I make any progress I'll post back here

     

  • Duncan Gunn30 karma points
    Sep 23, 2010 @ 22:55
    Duncan Gunn
    0

    Thanks Lee, look forward to seeing how you get on.

  • Lee2679 karma points
    Sep 24, 2010 @ 07:48
    Lee
    0

    I have narrowed down the problem, and it is a problem with blog4umbraco package - If you install and leave the root blog node in its default location it works fine 

    Home
    Blog

    But as soon as you move the blog under a different node, this is what I have done

    Home
    -- Blog
    -- Other Page

    when you try and PUBLISH the node it fails and cannot generate the URL - I have some client work to get completed this morning, but will download and try to submit a patch on Codeplex this afternoon.

  • Lee2679 karma points
    Sep 24, 2010 @ 08:00
    Lee
    0

    In fact even moving it back to its original position still keeps the bug!  Annoying...

  • Lee2679 karma points
    Sep 24, 2010 @ 11:02
    Lee
    0

    Ok I think have found the problem and fixed the 'The given key was not present in the dictionary' message appearing, its to do with the Autoping class and it not getting the fullpathURL to the blog.

    I'm going to need to check with Tim as it just doesn't seem to be able to get the Nice URL of the node from the NodeID even though the event is triggered after publish? Even though my fix stops the error, it still means the autoping won't work and will ping with an invalid URL.

    I'll spend another half an hour playing, and if I'm still stumped I'll email Tim :)  I'll post up the DLL's in a bit for you to use, to stop this message

  • Bo Petersen61 karma points
    Sep 30, 2010 @ 17:17
    Bo Petersen
    1

    I have found a workaround but it's a small hack though.

    If you remove the "Ping" property from the Blog document type, now it doesnt throw an error. But you still cant use the dashboard for creating posts.

  • Robert Foster790 karma points admin c-trib
    Oct 01, 2010 @ 01:06
    Robert Foster
    0

    Hey Lee,

    Just wondering if you made any progress on this?  If not I'll take a bash at it over the weekend...

  • Lee2679 karma points
    Oct 01, 2010 @ 07:16
    Lee
    0

    I have sorted the problem in the blog4umbraco package, but its not different really to removing the ping property above as at the moment you can't use the ping property because there is actually what seems to be an underlying bug in the umbraco core.

    I started to try and debug the core, well NiceURL() to be precise but I struggled to get the solution to compile in .NET 4 as that's what my site is running - this is as far as I got

    http://our.umbraco.org/forum/developers/api-questions/12996-Document_AfterPublish-Bug

    As you can see there is a bug in the after publish event which stops umbraco being able to get the URL of the currently published node.

  • Anders Stentebjerg234 karma points
    Oct 04, 2010 @ 18:05
    Anders Stentebjerg
    0

    I have found a workaround, please let me know if it works for you.

    http://screenr.com/vz4

    / Anders

  • Lee2679 karma points
    Oct 04, 2010 @ 18:11
    Lee
    0

    Thats not a work around, if you create another new post you will still get the error... It only trys to ping (I think) on the first publish so you can re-publish after without the error..

    The work around is as posted by Bo above, which is basically remove the 'ping' feature

  • Jeff Grine189 karma points
    Oct 04, 2010 @ 21:01
    Jeff Grine
    0

    NiceUrl uses the xml cache and a new node won't be in there the first time afterPublish fires. Normally I'd check sender.Published before using it, but in this case that would mean you'd always have to publish twice the first time to get pinging to work. I wonder if there's an easy way to pull the Url from the database instead?

  • Jeff Grine189 karma points
    Oct 04, 2010 @ 21:06
    Jeff Grine
    0

    Sounds like the cache just needs to be updated first according to this - http://our.umbraco.org/forum/developers/api-questions/3135-Afterpublish-get-document-url? Kind of wasteful to do it every time though.

  • Jeff Grine189 karma points
    Oct 04, 2010 @ 21:12
    Jeff Grine
    2

    That does the trick. I added this line

    umbraco.library.UpdateDocumentCache(sender.Id);

    before the call the NiceUrlFullPath and it publishes ok. Not really that wasteful since it only updates the node being published.

  • Lee2679 karma points
    Oct 04, 2010 @ 21:56
    Lee
    0

    Top man!  Completely and utterly missed that!  Have you submitted it to codeplex for Tim to add to the project?

  • Jeff Grine189 karma points
    Oct 04, 2010 @ 22:03
  • Bernhard König28 karma points
    Oct 08, 2010 @ 15:58
    Bernhard König
    0

    Hi,

    I applied this fix and it works now to publish new blog posts, thank you Jeff :) ... unfortunately, the post is now always placed directly under the blog root instead of the date folder hierarchy (2010/10/08). 

    All I did was adding the UpdateDocumentCache-line in the b4u code and recompiled, then replaced the Umlaut.Umb.Blog.dll on the server with the new one.

    Hmmm ... any additional ideas?

    cheers,
    b.

  • Jeff Grine189 karma points
    Oct 08, 2010 @ 16:45
    Jeff Grine
    0

    Looks like that runs in BeforePublish, so shouldn't be affected by the change you made. See EventHandlers/BlogDateFolder.cs You should also have some entries in umbracoLog telling you what happened with the date folder.

  • Bernhard König28 karma points
    Oct 08, 2010 @ 17:40
    Bernhard König
    0
    Thanks for your reply!
    Hm ... the item is placed under the root immediately after creation. In the log I just see a New and Open event for this new blog post node, but no info to folders, no errors ... think I will have to investigate further. Maybe the code i downloaded from Codeplex is not current. I got the code from changeset 40819 (2.0.26 release) IIRC ... 
    Just for verification ... i placed your fix code line into the class Umlaut.Umb.Blog.EventHandlers.AutoPing, void Document_AfterPublish ... this is the right place, isn't it?
    Thanks again!
  • Jeff Grine189 karma points
    Oct 08, 2010 @ 18:03
    Jeff Grine
    0

    I was working with 54177. Looks like there was no EventHandlers\BlogDateFolder.cs in the release you're using? Not sure how the date folder was being created in that case. 

  • Bernhard König28 karma points
    Oct 08, 2010 @ 18:31
    Bernhard König
    0

    I wanted to use the last stable release as the codebase for the fix ... but now I tried with 54177 too and same thing ... post gets created directly under the root. If I roll back to the old assembly, it works fine again (of course, with the new bug that I can't publish then).

    That's frustrating. :(

    Can you upload your assembly somewhere so I can try this one? Maybe I'm just doing something wrong. Would really appreciate that :)

  • Jeff Grine189 karma points
    Oct 08, 2010 @ 20:13
    Jeff Grine
    0

    Can you debug and see if the handler in BlogDateFolder.cs is getting hit when you publish the post? If you're not seeing anything in the log, sounds like the handler is not being called, but I've no idea what would cause that.

  • Bernhard König28 karma points
    Oct 08, 2010 @ 22:51
    Bernhard König
    0

    I think I found the problem. I freshly installed a 4.5.2 Umbraco instance on my dev machine and installed the blog package. The behaviour of the blog package is different than on my production machine. In Prod, a new post gets directly created under the date folders (which are created, if needed). On my local dev machine, the blog post gets firstly created on top level and is then moved to the date folder on publish/save.

    The behaviour on the dev machine fits to the code, and there I found a property on the BlogPost doctype which is called "PostDate" ... in the code, this property is checked and if it does not exist, the date folder creation is skipped.

    In prod, the Document Type does not have this property.

    So, it seems I have a old Blog4Umbraco version in prod ... but the package manager says Blog4Umbraco 2.0.26 ... as does my new and freshly installed local dev instance.

    Does this package gets updated with new code while the version number is not raised?

    Next intresting thing is ... the thread-starting issue ("the given key was not present ...") also just does not appear ... i can use Blog4Umbraco without any errors in 4.5.2 ... 

    Consider me confused :)

    Anyhow, I'll try to upgrade my blog package in prod now ... 

  • Jeroen Breuer9904 karma points admin mvp c-trib
    Oct 18, 2010 @ 16:19
    Jeroen Breuer
    0

    Is it safe to use the latest changeset of Blog4Umbraco? Does this error still occur and is this workitem already fixed?

    Jeroen

  • Greyhound124 karma points
    Oct 18, 2010 @ 16:43
    Greyhound
    0

    No I dont think it is.

    I've spent the day doing the following:

    1. Upgrade of Umbraco from 4 - 4.5 (latest release)
    2. Upgraded Blog4Umbraco to Blog4Umbraco_2.0.26_for_4.5.zip
    3. Error when publishing still exists

    Also tried:

    1. Fresh vanilla install of 4.5
    2. Fresh vanilla install of Blog4Umbraco
    3. Got a cannot load control error and some xslt errors

    I'm in a right mess now!

    I think Blog4Umbraco is a fantastic offering given that it is free but it'd be great to a solid blog componant for Umbraco that worked out of the box.
    Could we not have a "donation" drive to fund this. I for one wouldn't mind paying towards getting a solid blog platform for Umbraco up and running I'd also be happy to contribute time-wise.

    Cheers,

  • Jeroen Breuer9904 karma points admin mvp c-trib
    Oct 18, 2010 @ 16:46
    Jeroen Breuer
    0

    Hi Greyhound,

    Did you try all of this with the latest changeset from codeplex or the download on the project page?

    Jeroen

  • Greyhound124 karma points
    Oct 18, 2010 @ 16:49
    Greyhound
    0

    Hi,

    Missed out another step above - when trying the vanilla installs I did it with both versions.

    Comments also seem to be nacked as well.

    Cheers,

    Ben

  • Lee2679 karma points
    Oct 18, 2010 @ 16:55
    Lee
    0

    If you are using .NET 4 I have a working blog4umbraco DLL which has been updated and can post a link to if anyone needs it?

  • Greyhound124 karma points
    Oct 18, 2010 @ 16:57
    Greyhound
    0

    Hi Lee - most helpful, I'll take one off your hands please. :)

  • Jeroen Breuer9904 karma points admin mvp c-trib
    Oct 18, 2010 @ 17:06
    Jeroen Breuer
    0

    Hi Lee,

    That would be great! I'm using Umbraco 4.5.2 with .NET 4 so I would love to have a working DLL. Is that the only updated file so does it work with all the XSLT files from the latest changeset?

    Jeroen

  • Greyhound124 karma points
    Oct 18, 2010 @ 17:14
    Greyhound
    0

    Correction. I have just done another vanilla install of :

    1. Umbraco_4_5_2_for_NET_4.zip
    2. Blog4Umbraco_2.0.26_for_4.5.zip

    This works ok - although comments can still not be posted.

    I think my original Umbraco upgrade hasnt worked. I should be getting lots of xslt errors surely? I cant find a way of forcing the upgrade to use the latest schema.

  • Lee2679 karma points
    Oct 18, 2010 @ 17:18
    Lee
    0
  • Jeroen Breuer9904 karma points admin mvp c-trib
    Oct 18, 2010 @ 17:30
    Jeroen Breuer
    0

    @lee Thanks will give it a try.

    @Greyhoud If you download the latest changeset (http://blog4umbraco.codeplex.com/SourceControl/changeset/changes/54177) the XSLT files in this download should work (not tested yet).

    Jeroen

  • Greyhound124 karma points
    Oct 18, 2010 @ 17:37
    Greyhound
    0

    @Lee - thanks. This dll doesnt create date folders - is this the intended behaviour?

    @Jeroen - thanks, I'll give them a try,

  • Lee2679 karma points
    Oct 18, 2010 @ 19:06
    Lee
    1

    @Greyhound - It's working fine for me, firstly make sure you definitely have the 'postDate' propety on your blogpost doctype (See below) as this is what is used for the Date Folder in the latest one ALSO without trying to sound funny you do know it only creates the DateFolder AFTER you have published the post for the first time.  

    So if you create a new blog post, it won't show in a date folder straight away - It will just show under the blog node as unpublished, once you 'Save & Publish' it will then create the date folder and move the post.

  • Greyhound124 karma points
    Oct 18, 2010 @ 19:54
    Greyhound
    0

    Thanks Lee - I added the postDate property and this has sorted it out. I've got bigger problems though which is making B4U a show stopper.

    Something is defintely not happy since my upgrade to 4.5.2 which I am now cursing ever having attempted.

    I'm getting errors like "Error parsing XSLT file: \xslt\Blogpages.xslt" now and am unable to save any of the XSLT files in the admin (invalid data at the root level etc)

    Giving it another 2 hours then giving in, I was in love with Umbraco until it came to upgrading and this blog business!!

  • Jeff Grine189 karma points
    Oct 18, 2010 @ 20:00
    Jeff Grine
    1

    You might check in a text editor if there is an extra character at the end of the xslt file when you get the root level error. That was the problem with BlogTagCloud in the version I downloaded.

  • Greyhound124 karma points
    Oct 18, 2010 @ 20:05
    Greyhound
    0

    Thank you, that got it - now I'm searching for an answer to :

    "Value was either too large or too small for an Int32" - its defintely one of those days.

     

  • Jeff Grine189 karma points
    Oct 18, 2010 @ 20:07
    Jeff Grine
    0

    That's usually a call to niceUrl or GetMedia that has a bad value being passed in, but I have seen that in 4.5.2 when saving xslt in the admin when the xslt is actually fine. If you check the box to ignore errors, does the xslt actually work on your site?

  • Greyhound124 karma points
    Oct 18, 2010 @ 20:18
    Greyhound
    0

    Weirdly enough that looks to be the case although ignoring the errors still doesnt render the XSLT.

    In BlogTagCloud I changed:

    <

     

     

    a href="{umbraco.library:NiceUrl($currentPage/ancestor-or-self::Blog/@id)}?filterby={.}">

    to

    <

     

     

    a href="{umbraco.library:NiceUrl(1509)}?filterby={.}">

    This works ok but I'm not sure where to start looking now in order to fix the ID problem. I'm assuming that due to the site upgrade there is an old value somewhere that is still be used?

    Your help is very much appreciated.

  • Jeff Grine189 karma points
    Oct 18, 2010 @ 21:07
    Jeff Grine
    0

    If it's just the xpath not working, then first spot to check is umbraco.config. If it's not obvious there, then you might have to hit the debugger. 

  • Greyhound124 karma points
    Oct 18, 2010 @ 21:47
    Greyhound
    0

    I've replaced the the entire contents of the config folder with the vanilla install (which is working) but to no avail. Something has obviously gone very wrong with the initial upgrade although everything is fine apart from the blog.

    12 hours straight and feeling very dispondent - throwing the towel in. It just shouldnt be this hard to upgrade a CMS and blog.

    Thanks for your help anyway.

  • Greyhound124 karma points
    Oct 19, 2010 @ 12:26
    Greyhound
    0

    After a reboot and a nice cup of coffee everything is playing nicely. I can only assume that this would due to some cacheing problem.

    The modified DLL is working so thanks Jeff and Lee.

    @Jeff - as you have probably guessed I'm more of a creative than a developer but if I can ever help you out with some graphics or css in return for the dll then do let me know.

  • Aming43 karma points
    Oct 19, 2010 @ 13:44
    Aming
    0

    "Give this a try

    http://www.n3o.co.uk/b4u.zip"

    Hi Lee, my computer has .Net 2.0, 3.5 and 4.0 framework, and I installed Umbraco 4.52 by web installer. When I replaced the b4u DLL, I got the following errors. Do you know the reasons? thanks.

    Could not load file or assembly 'Umlaut.Umb.Blog' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

    Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. 

    Exception Details: System.BadImageFormatException: Could not load file or assembly 'Umlaut.Umb.Blog' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.

     

  • Greyhound124 karma points
    Oct 19, 2010 @ 14:00
    Greyhound
    0

    May be worth checking in IIS that the website is running in framework version 4.

    I think that error message means that the website is running in a version lower than 4 and the dll requires framework 4.

  • Aming43 karma points
    Oct 19, 2010 @ 14:56
    Aming
    0

    Thanks for your reply, but when I changed to the framework version 4, then I got the following error. Do you know the reasons? thanks.

     

    HTTP Error 500.19 - Internal Server Error

    The requested page cannot be accessed because the related configuration data for the page is invalid.

     

     

    8: <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"> 9: <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication" /> 10: <sectionGroup name="webServices" type="System.Web.Configuration.ScriptingWebServicesSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">

  • Aming43 karma points
    Oct 19, 2010 @ 15:01
    Aming
    0

    Config Error  There is a duplicate 'system.web.extensions/scripting/scriptResourceHandler' section defined

  • Lee2679 karma points
    Oct 19, 2010 @ 15:01
    Lee
    0

    You can't just change the site to run on v4 without changing all the other files to reflect this - Obviously one of them will be the web.config.  

    You are currently running the site as v3.5, so if you want to change to v4 you need to update ALL the other DLL's from the ASP.NET v4 version of umbraco from CodePlex and then update the web.config to reflect this too.

  • Aming43 karma points
    Oct 19, 2010 @ 15:16
    Aming
    0

    Thanks for your reply! I might need to re-install the umbraco. The current problem is that I have already built part of the website. Do you have any suggestion how to export it before uninstall the umbraco, and how to import it back after re-installation ? Thanks.

  • Lee2679 karma points
    Oct 19, 2010 @ 15:19
    Lee
    0

    Yep you can create a package from your site and install the package into your new install  - I suggest you get a subscription to umbraco.tv as I think that has some videos on creating a package.  Its very simple to do - You might be able to find out more from just googling around or searching the forums.

  • Aming43 karma points
    Oct 19, 2010 @ 15:34
    Aming
    0

    I have subscribed to umbraco.tv. I will check it out.

  • Lee2679 karma points
    Oct 19, 2010 @ 15:42
    Lee
    0

    Good stuff - Hope the HQ reads this and I get some extra karma for selling umbraco.tv subscriptions :P ..lol

  • Aming43 karma points
    Oct 19, 2010 @ 15:55
    Aming
    0

    Yeah, you deserve some extra karma. :)

    I just checked the videos and didn't find the topic about creating a package. Could you give me a link? 

  • Tim Finucane60 karma points
    Oct 19, 2010 @ 21:49
    Tim Finucane
    0

    The link to that updated DLL seems to no longer work. I am having this problem; does anyone know where I can get that updated DLL?

    Thanks,

    Tim

  • Lee2679 karma points
    Oct 19, 2010 @ 21:55
    Lee
    0

    I deleted it from the server - I'll re-upload in a minute

  • Lee2679 karma points
    Oct 19, 2010 @ 22:00
    Lee
    0

    Its back... I'll leave it there for a few days

  • Lee2679 karma points
    Oct 19, 2010 @ 22:01
    Lee
    1

    *Cough* feel free to apply some high fives if this helps anyone ;)  Nothing like a bit of karma to show your appreciation :P

  • Tim Finucane60 karma points
    Oct 19, 2010 @ 22:18
    Tim Finucane
    0

    Thanks Lee, much appreciated. I'd high five ya if I had enough karma to do so.

  • Duncan Gunn30 karma points
    Oct 19, 2010 @ 22:47
    Duncan Gunn
    0

    Just curious if there's a .NET 2.0 version that anyone has compiled from the source?

  • Aming43 karma points
    Oct 20, 2010 @ 04:13
    Aming
    0

    *Cough* feel free to apply some high fives if this helps anyone ;)  Nothing like a bit of karma to show your appreciation :P”

    I tried to vote but was rejected because I don't have 70 Karmas. I will come back to vote when I collect enough Karmas.:)

  • Lee2679 karma points
    Oct 20, 2010 @ 07:54
    Lee
    2

    I didn't have enough time to get compile the project in 2.0 but I have updated the zip to contain both 4.0 and 3.5 versions now

    http://www.n3o.co.uk/b4u.zip

  • Jeroen Breuer9904 karma points admin mvp c-trib
    Oct 20, 2010 @ 09:27
    Jeroen Breuer
    0

    Hi Lee,

    What exactly is different from this dll compared to the latest changeset (54177) on codeplex?

    Jeroen

  • Jeroen Breuer9904 karma points admin mvp c-trib
    Oct 20, 2010 @ 12:50
    Jeroen Breuer
    0

    I just tested you dll Lee and the bug I started this topic for is now solved! Guess that's what your dll does :). Thanks.

    Jeroen

  • Lee2679 karma points
    Oct 20, 2010 @ 13:01
    Lee
    0

    Great stuff - Don't forget to mark the thread as solved to help other people looking for the same issue.

  • Jeroen Breuer9904 karma points admin mvp c-trib
    Oct 20, 2010 @ 13:09
    Jeroen Breuer
    0

    Which post should I mark as the answer? The one where people can download your dll seems the best post, but if you remove the dll I should mark another post as the answer.

    Jeroen

  • Lee2679 karma points
    Oct 20, 2010 @ 14:02
    Lee
    0

    Yeah mark that one, I'll leave them up until the source is changed on Codeplex

  • Jeroen Breuer9904 karma points admin mvp c-trib
    Oct 20, 2010 @ 17:02
    Jeroen Breuer
    0

    Hi Lee,

    Publishing now works, but is really slow. Is this because of your dll and is it related to ping? I've added 4 external links to ping.

    Jeroen

  • Aming43 karma points
    Oct 20, 2010 @ 17:28
    Aming
    0

    The .Net 3.5 DLL works for me. Many thanks!

  • Lee2679 karma points
    Oct 20, 2010 @ 17:59
    Lee
    1

    @Jeroen - Yep pinging multiple sites can be slow, I stupidly added 20 odd sites when I first started using it and it constantly timed out. Try using ping-o-matic or similar that does the multiple pinging for you (rpc.pingomatic.com)

  • AntonioMX57 karma points
    Oct 22, 2010 @ 22:45
    AntonioMX
    0

    the dll is working great, I had the same problem as the OP. I have also created the postDate property in the blogpost content type but when I "save and publish" the blog post it remains at the root of the blog, any thoughts?

  • AntonioMX57 karma points
    Oct 22, 2010 @ 23:35
    AntonioMX
    0

    Another thing I just realised, upon changing the name from "Blog" to "News" to have the path MySite/News the error is thrown, the Lee solution worked (with the postDate property included) but the post remains at the root.

  • AntonioMX57 karma points
    Oct 23, 2010 @ 01:15
    AntonioMX
    0

    Ok, third post about this. I have figured out a way to avoid this error.

    Keeping the original instalation, no dll mod or changing the datatype. Try first to save without publishing, then preview the post, then save and publish.

    This worked using the content folder to create the blog. Haven't tried using the example blog that you create after installing the package then renaming and/or moving it around.

  • Tim Finucane60 karma points
    Oct 29, 2010 @ 19:10
    Tim Finucane
    0

    I see others mention a similar problem here, but I just noticed it: when creating a blog post it no longer uses the date folders; it just puts it in the root.

  • Duncan Gunn30 karma points
    Nov 01, 2010 @ 22:50
    Duncan Gunn
    0

    Yes I get the same as Tim but on Saving and Publishing it does put it under the correct date structure.

    Is this by design?  I can see it as a useful(ish) feature!

  • Jeff Grine189 karma points
    Nov 02, 2010 @ 13:32
    Jeff Grine
    0

    Yes, that's by design. I'm assuming it's because the date folder should really match the date the post is published, not the date it was created.

  • Tim Finucane60 karma points
    Nov 02, 2010 @ 14:57
    Tim Finucane
    0

    Hmmmm... That is not matching the behaviour I get. For me it does not go into the date folders upon publishing; it remains in the root of the blog.

  • AntonioMX57 karma points
    Nov 02, 2010 @ 15:15
    AntonioMX
    0

    I tried this and worked like a charm.  Just make sure the PostDate property has leading caps.

     

  • Tim Finucane60 karma points
    Nov 02, 2010 @ 15:54
    Tim Finucane
    0

    I have one little problem trying to follow this, my Umbraco install won't let me have the leading caps; it changes it on me automatically. Is this a setting in the config?

  • AntonioMX57 karma points
    Nov 02, 2010 @ 16:09
    AntonioMX
    0

    Yeah, this is also something I experienced, I guess this is by design in version 4.5. What I did was to modify the Blog Post doc type in a 4.0.2 version and then imported it to the current one.

  • Tim Finucane60 karma points
    Nov 02, 2010 @ 16:52
    Tim Finucane
    0

    ok, I managed to change the postDate to PostDate in the database, but it still won't publish to the date folders on publish.

  • AntonioMX57 karma points
    Nov 02, 2010 @ 17:53
    AntonioMX
    0

    You still have the modified Umlaut.Umb.Blog.dll and Umlaut.Umb.Blog.pdb in the bin folder? If so, I would suggest to change them back to originals and try again.

  • Tim Finucane60 karma points
    Nov 03, 2010 @ 19:58
    Tim Finucane
    0

    Yeah, putting back the original DLLs just gives me the original error this post started out with. This is exceptionally frustrating.

  • Tim Finucane60 karma points
    Nov 03, 2010 @ 20:12
    Tim Finucane
    0

    Ok, I figured it out! I needed to enable the Date Folder as a document type that could be created under the blog. It was not on by default. When I turned it on, posts now create the date folder that matches the PostDate.

    Yea!

    Thank you to all who tried to help me.

  • Duncan Gunn30 karma points
    Nov 06, 2010 @ 11:48
    Duncan Gunn
    0

    I can't find any way to moderate comments on this version; apparently they should be listed in the Content dashboard but I see nothing.

    Anyone else have the same issue?

Please Sign in or register to post replies

Write your reply to:

Draft
Our.umbraco.org is the community mothership for Umbraco, the open source asp.net cms. With a friendly forum for all your questions, a comprehensive documentation and a ton of packages from the community.