Home → General →

Publishing in multi level depth

• Edit

usmanehsan0613

07 Sep, 2015 05:44 AM

Hi,

 Can you please help me to publish cascade website in multilevel folder depth. Here is my site structure

  Base Folder
   - main
     -- about
     --- staff
     ---- admin
     ----- senior
     ------ president office staff
     ------- staff.html
     ------ vice president office staff
     ----- junior
     ---- work
     
From above structure you can see i have much in depth nested level of folders . If i select main folder , select all the folders and do publish. It will not publish the inner level page ie. staff.html that is nested inside 5 folders from the main folder. Rather i had to manually go and publish staff.html page.

Like this i have 170 of (main) folders and 40 - 50 sub folders within each main folder. Each sub folder will have other sub folders and lot of pages. So its very difficult to manually go and publish each page and folder.

Please let me know the best solution to publish all in less time.

Looking forward.

Thankyou

1. 1 Posted by Wing Ming Chan on 07 Sep, 2015 12:45 PM

   

   Hi Uthman,

   To selectively publish folders of any depth, you can use web services. But can you handle web services?

   Wing

   • Edit

2. 2 Posted by usmanehsan0613 on 08 Sep, 2015 04:47 AM

   

   Hi wing,

    I can use .net based webservices as my site is running on IIS .

   Thankyou

   Uthman

   • Edit

3. 3 Posted by Wing Ming Chan on 08 Sep, 2015 12:41 PM

   

   Hi Uthman,

   I built a web service library using PHP last year. Using this library, you can practically write a few lines of code to publish any folder you want. If you want to stick with .net, then you have to write your own library.

   This is what my library code can offer you: you can specify a folder, and the code can traverse that folder recursively, and publish any type(s) of assets you specify. If you want to publish pages, then all pages inside that folder will be published. If you specify to publish the base folder, then pages of the entire site will be published. Let me know if you are interested.

   Wing

   • Edit

4. 4 Posted by Ryan Griffith on 08 Sep, 2015 02:24 PM

   

   Hi Uthman,

   Curious, if you view the publish report for the top-level folder publish, do you see any skipped/failed publish jobs? If so, when the publisher encounters consecutive issues with a Destination it will register it as failed and skip the remaining jobs. This could very well be why those deeply nested assets are not publishing.

   Also, a few other items to check out:

   • Make sure ancestor folders in the asset's structure are configured to be publishable
   • Make sure the asset, and it's ancestor folders, has not hit it's expiration date, which will automatically make the asset unpublishable

   Please let me know if you have any questions.

   Thanks!

   • Edit

5. 5 Posted by usmanehsan0613 on 09 Sep, 2015 05:59 AM

   

   Thanks Wing and Ryan for your replies.

   @Wing : Yes I am very interested in the library you have coded in PHP. I will try to use that or write the same in C#. As by reading your code i will get much information about the use of webservices.

   @Ryan : I had check following

   • Yes ancestors folders are all configured to be publishable
   • Nothing gets failed during publishing.
   • I had not choose any expiration date for any asset .

   Please let me know your thoughts about this.

   Many Thanks,

   Uthman

   • Edit

6. 6 Posted by Ryan Griffith on 09 Sep, 2015 03:48 PM

   

   Hi Uthman,

   Definitely interesting that you are not seeing any errors in the publish report. What version of Cascade are you currently running?

   Thanks!

   • Edit

7. 7 Posted by usmanehsan0613 on 10 Sep, 2015 04:07 AM

   

   Hi Ryan,

   I am running v7.10.2 ..

   Thanks !

   • Edit

8. 8 Posted by Ryan Griffith on 10 Sep, 2015 03:50 PM

   

   Hi Uthman,

   I am not aware of any specific defects in that version that would be causing this behavior. When you have a moment, please attach the following so we can take a closer look:

   • your most recent cascade.log from around the time of the publish job, and an approximate time you performed the publish
   • a copy of the generated publish report

   Please let me know if you have any questions.

   Thanks!

   • Edit

9. 9 Posted by Ryan Griffith on 24 Sep, 2015 12:33 PM

   

   Hi Uthman,

   Just wanted to follow up to see if you had a chance to view my recent comment.

   Please let us know if you have any questions.

   Thanks!

   • Edit

10. Tim closed this discussion on 08 Oct, 2015 07:52 PM.