Skip to main content
R
rosenh
Known Participant
February 10, 2017
Answered

Library item won't update on pages

  • February 10, 2017
  • 1 reply
  • 675 views

I have a subsite (a 2nd website we're building) in a folder within the root folder.

My partner created this subsite and the libraries on her computer, with Dreamweaver 5.  I have Dreamweaver CC (Mac).

I downloaded her subsite, but the libraries didn't work for me (I tried to open them, and dreamweaver said it could not find them).  When I re-link them, they show up, but the pages won't update when I change the library.

On her computer, the library path was simply /Library/nav.lbi  (even though it was in the same subsite folder setup as I have it on my system)

When I pull them onto my computer, the library in my subsite folder ends up with the path: subsite/Library/nav.lbi

When I drag the new library into a page, it shows up, but if I edit the library it does not update on the page.

I've re-done the cache and the preferences, no change.

Do I have to put these subsite libraries in the root library, mixed in with the other website? even though all the pages are in the subsite folder?

    This topic has been closed for replies.
    Correct answer BenPleysier
    Is this a new "feature" with Dreamweaver CC?  Seems like libraries used to work, even if they were in a subfolder, as long as the pages were there... ie, the problem of relative vs absolute paths strikes again?

    This "feature" has not changed since the days of Macromedia. You just need to ensure that the Dreamweaver site has been set up properly.

    From what you describe, you did not place the new site as a subfolder of the old site. Hence you created a new root folder making the new site independent of the old site.

    Merely a matter of knowing how sites in Dreamweaver work.

    1 reply

    R
    rosenhAuthor
    Known Participant
    February 10, 2017

    I tested this... and if I put the library in the root folder, even though the pages are in a folder within the root, the updating works. 

    Is this a new "feature" with Dreamweaver CC?  Seems like libraries used to work, even if they were in a subfolder, as long as the pages were there... ie, the problem of relative vs absolute paths strikes again?

    BenPleysier
    Community Expert
    BenPleysierCommunity ExpertCorrect answer
    Community Expert
    February 10, 2017
    Is this a new "feature" with Dreamweaver CC?  Seems like libraries used to work, even if they were in a subfolder, as long as the pages were there... ie, the problem of relative vs absolute paths strikes again?

    This "feature" has not changed since the days of Macromedia. You just need to ensure that the Dreamweaver site has been set up properly.

    From what you describe, you did not place the new site as a subfolder of the old site. Hence you created a new root folder making the new site independent of the old site.

    Merely a matter of knowing how sites in Dreamweaver work.

    Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
    Firefly Community Gallery
    Adobe Firefly

    Remix with Firefly Community Gallery

    Thousands of free creations to fall in love with and remix in Firefly.

    Explore now
    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices