Skip to main content
A
Arkwright22111
Participant
March 23, 2017
Answered

Checking Out Files With Dependent Files That Have Dependent Files

  • March 23, 2017
  • 1 reply
  • 780 views

I'm trying to get my head around the integrity of the check-in/check out process on a large web site (700 pages) that uses lots of library items in each page and whose library items appear in many pages.

I get the simple outline in user help, the page you check out looks for all dependent files like library items and images and checks them out too, so controlling only one person can edit content at the same time.

After checking out and editing content you check them back in and if a library item has been edited then that in turn updates all other pages with that librray item, checking them out too.

What I think happens also, but I'm not 100% certain is that in addition to updating the individual library item in another page, it also updates the other library items within that page

To keep integrity, I presume a  check needs to be performed that more current library items are not available on the web server rather than available  locally.

This would trigger a cascade of similar check-outs of which I see no evidence happening.

I guess what I'm looking for is an explanation of what actual processes the check-out process completes beyond simply checking out the page, making it read.write and doing the same for any file whether it be library or images linked within the html of that page.

I can't get my head around dependent files that are checked out and made editable, dependant files that get updated but remain read-only (like a simple get command) and related files where no update check is perforned at all.

Thanks

This topic has been closed for replies.
Correct answer Nancy OShea

You don't need a CMS to use Server-side Includes.  SSIs are far less painful to work with than proprietary Library Items that only work in DW & on locally managedl files.  

With LI's you must upload every page containing the Library Item whenever you make changes.  LI usage is restricted to the <body> tag of your documents.  And then there is the visual inspection required to ensure the LI is populating correctly to all your local site pages.   All too often, this breaks down.  With File check-in/check-out this process has even more margin for error.    I would not use this approach.

In contrast, SSI's can be used anywhere in a document.  They are not dependent upon DW.  SSI's perform their magic on the server.  You simply Edit, Save & Upload the SSI file.  You're done.   The parent pages are automatically populated with new content by the web server.  A huge time saver even for small sites.

Nancy

1 reply

Rob Hecker2
Rob Hecker2
Legend
March 23, 2017

I don't have the answer to your question because I would never manage content the way you appear to be doing it.

If you use a content management system, then this whole problem goes away.

A
Arkwright22111Author
Participant
March 23, 2017

For mainly SEO reasons a CMS system is not appropiate for us and not an option.

(Sorry we've been through this many times with consultants where the initial response was like yours, but after looking at the SEO implications for migrating to CMS it becomes a non-starter and we continue with static html)

Rob Hecker2
Rob Hecker2
Legend
March 23, 2017

I would like to hear your reasons for rejecting a CMS on the grounds that it hurts your SEO.

GOOGLE knows that in the 21st C no major website is built from static pages.

I can't think of any ways a static website would be superior regarding SEO. I can think of some ways CMS websites are superior, such as the ability to automatically maintain time-relevance by removing dated content and keep a sitemap up-to-date. Also, a CMS allow a site to follow a tight logical structure that helps search engines comprehend the content.

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