Copied to clipboard

Flag this post as spam?

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


  • Fergus Davidson 309 posts 588 karma points
    Jan 29, 2013 @ 16:28
    Fergus Davidson
    0

    Path is incorrect in moved nodes

    i am using Umbraco v4.11.3 with CMDP v1.2

    when i move nodes from one place to another within the site, the path in the umbracoNode table is not correct. that is to say the path is not full with some nodes skipped out.

    Is this by design?

    The problem i have is that i have deep links such as: /umbraco/actions/editContent.aspx?id=1332

    These links work perfectly with a full path, but without the full path, the tree will not open to the required position. in a site with lots of nodes and a deep structure, this is a problem.

    thanks

     

    fergus

  • Richard Soeteman 3968 posts 12470 karma points MVP
    Jan 29, 2013 @ 16:39
    Richard Soeteman
    1

    Hi Fergus,

    Have to dive into this. Just did a quick check and I'm using the normal Umbraco API. Will have to come back on this one. Sorry.

    Cheers,

    Richard

  • Fergus Davidson 309 posts 588 karma points
    Jan 29, 2013 @ 16:45
    Fergus Davidson
    0

    ok, thanks

    i have done some tests here, but i will have a futher dig around in the meantime to make sure it is not related to something else.

  • Fergus Davidson 309 posts 588 karma points
    Jan 29, 2013 @ 17:05
    Fergus Davidson
    0

    Hi Richard

    thanks again for the quick response. I must apologise - seems i was a bit hasty. it seems to be a problem with Umbraco as when i move things around using the context menu, it appears the same tings happens.

    it seems that when an item is moved, it's path is changed, but the paths of any nested items is not correctly updated, keeping the previous parent node id in their path.

    fergus

  • Fergus Davidson 309 posts 588 karma points
    Jan 29, 2013 @ 17:10
    Fergus Davidson
    0

    FYI - found a couple of issues raised:

    http://issues.umbraco.org/issue/U4-1579 ;

  • Richard Soeteman 3968 posts 12470 karma points MVP
    Jan 30, 2013 @ 08:05
    Richard Soeteman
    0

    Hi Fergus,

    That explains a lot. great that the issue is fixed for 4.11.4 which should ne out soon

  • Sean 10 posts 30 karma points
    Jan 31, 2013 @ 20:22
    Sean
    0

    Hi,

    I'm having the same problem, and I'm using 4.11.1. When I move content, the path is not always updating. I can't change to another umbraco install as myself and other developers are already working on this and have imported a lot of content. Is there a way to fix this? FYI, I'm also using the same version of Content Maintenance.

    Thanks,

    Sean

  • Fergus Davidson 309 posts 588 karma points
    Jan 31, 2013 @ 21:39
    Fergus Davidson
    0

    Sean,

    as richard says above, this is not a problem with the package, but with Umbraco. it will be fixed in the 4.11.4 release when that arrives. might be able to use something from the nightlies[?]

    i dont have a fix, but i managed to get around the issue of broken paths by moving everything up to a node in level 1 chunk by chunk and then moving them back to where they should be. the paths were all then as they should be. it was fairly easy for me as i only had a few hundred nodes in half a dozen parent nodes [if that makes sense] but it would take a while if you needed to do a whole site.

    lets hope 4.11.4 is coming soon.

  • Sean 10 posts 30 karma points
    Feb 01, 2013 @ 02:57
    Sean
    0

    Thanks for the prompt reply Fergus! I'm not sure if I'll be able to wait for 4.11.4 though, so I might have to attempt downgrading or looking into the source code directly. Hopefully I can get this sorted out quickly as two large projects at my company are based on 4.11.1.

  • Richard Soeteman 3968 posts 12470 karma points MVP
    Feb 01, 2013 @ 07:41
    Richard Soeteman
    0

    Don't know if it help guys, but the core team created a project that will fix the path issue

    http://our.umbraco.org/projects/developer-tools/path-fixup

    Cheers,

    Richard

  • Claushingebjerg 916 posts 2496 karma points
    Mar 20, 2013 @ 11:09
    Claushingebjerg
    0

    I just installed the package on 4.7.2 and cautiously moved a single subnode to another parent node as a test.

    It is visually moved in the tree, but not physically. It apparently still resides in its old location.

    I've tried editing the node, and changes appear in tis old location frontend...

    I get a 404 when visiting the new location /gamle-nyheder/nycke-groot-pokalfighter/

    What to do? 

  • Richard Soeteman 3968 posts 12470 karma points MVP
    Mar 20, 2013 @ 11:24
    Richard Soeteman
    0

    I assume physically you mean front-end Try a republish?  I know there is a bug in 4.10+ in Umbraco showing weird paths but 4.7.2 should work fine.

  • Claushingebjerg 916 posts 2496 karma points
    Mar 20, 2013 @ 11:33
    Claushingebjerg
    0

    Hmmm, a bit funny behavior.
    Moving it doesnt update the path.
    Publishing the node after moving it doesnt either.
    But "Republish entire site" does... 

    Thanks for the heads up

  • Eric Schrepel 155 posts 210 karma points
    Apr 18, 2013 @ 19:15
    Eric Schrepel
    0

    In Umbraco 6.0.3, I also have issues moving nodes from one parent to another, the path/parent connections don't match and URLs don't get updated correctly, also breaking my breadcrumb macros. Frustrated by that situation, downloaded and ran PathFixup per suggestion.

    Backed up db, ran Path Fixup but I sense something's more wrong yet, as the UmbracoTraceLog shows the same nodes getting processed repeatedly as PathFixup runs, and it never finishes (i.e., the line "PathFixer - Fixing paths for children of 15576" shows up every few minutes, and the UI screen also shows the same nodes getting looped through and it never completes.

    Also, in lieu of the endless loop situation with PathFixup, it'd be rad if instead of the UI showing "Fixing node ___", it would show an overall progress bar. As it is, I don't know whether to just stop this now or let it run (minutes? hours?). We have about 1,500 nodes, if that's useful information, and I'm happy to attached some of the tracelog if anyone can help.

     

  • Richard Soeteman 3968 posts 12470 karma points MVP
    Apr 18, 2013 @ 23:05
    Richard Soeteman
    0

    I Think this is related to a move bug in the core then. Maybe add a bug to the Umbraco issue tracker? This package only uses a move method of the supported API if a bug in the core mess up the path. Then it should be fixed in the core. Sorry about the issue.

Please Sign in or register to post replies

Write your reply to:

Draft