Hannon Hill Community What's New

"How "smart" is "smart publishing" in not...

jkreuzig

"How "smart" is "smart publishing" in noticing/mitigating race conditions?"

Andrew,

I sure I will be corrected on this if I'm wrong, but I believe "smart publishing" only has an effect on file assets. File assets (such as images) are not managed the same way in cascade, so cascade checks to see if the asset on ...

Multiple queue's would not be necessary i...

kevin

Multiple queue's would not be necessary if the publisher published multiple files simultaneously. Why now allow 10 items to publish at the same time? If you are concerned about the same file being in the publish queue more than once, keep track of the time entered and force those to publish in order, otherwise publish simultaneously. If you want to place more weight on certain folders/file that i...

I posted a request on another tangent for...

wabaus

I posted a request on another tangent for speeding up publishing of small jobs here:

http://success.hannonhill.com/cascade-server-ideas/publish-job-should-trigger-next-job-queue

Publish Job should trigger next Job in Queue

wabaus

When a publish job completes, it should trigger the server to check the queue again.

Polling the queue every 30 seconds causes a delay of many minutes when the queue is stacked with many jobs.

Example: if there are 12 jobs in the queue that take 8 seconds each, polling would require just over 6 min...

As I recall, there is a "snapshot" effect...

wabaus

As I recall, there is a "snapshot" effect applied to an asset when it is published. Not sure how far down the dependency chain it goes. It could be complete, as Cascade knows the timestamp of the publish job – but I don't know if it is.

Re-ordering the queue is "at your own risk" and c...

The workflow will lock the asset while it...

plower

The workflow will lock the asset while it is in progress. You could add an action to any step that would allow editing by either the initiating user or a user that is re-assigned to the workflow. I've done this in our system by copying and modifying one of default workflow defenitions. I think I looked at "General -> 4 Step" and maybe "Legal -> Standard Review". It...

Is there a best practice for unpublishing...

welched57

Is there a best practice for unpublishing an asset? Recently, one of our managers was removing old employees from the online directory, yet the pages still appear on the production server. Why would a page still appear online after being unpublished, and what are the proper steps to ensure that items get removed? Also, what is the best way to check an asset for linked pages before it is removed?<...

Removing old assets - unpublish?

welched57

I also vote for multiple queues. We get...

amcmilli

I also vote for multiple queues. We get very few complaints from our user community about Cascade but waiting on publishing is one thing that they have complained about.

Are you only concerned with the editor? ...

plower

Are you only concerned with the editor? I would imagine you could do some xslt formatting of urls to strip off the page durring publishing.

you could also use external links, but I don't recommend that since moving folders or changing the names would begin to break links.

As far as I've seen, that is correct. T...

plower

As far as I've seen, that is correct. The systems sees folder and files both as assets. It doesn't necessarily know that a page asset will be output as html, xml, asp, or anything else(folder if possible).

Publishing has been an issue for us as we...

jkreuzig

Publishing has been an issue for us as well. I think the idea of having a site-specific publishing queue may work. Of course, once you have assets linked across sites you end up with some of the same issues (asset locking, race conditions, etc.) as the current publishing model.

I'm thinking out loud here, so YMMV. If there was a way to "snapshot" all component...

I vote for multiple queues.

cbarry

I vote for multiple queues.

I agree with tgatkins. It would be nice a...

TonyDunn

I agree with tgatkins. It would be nice as well, to tie publishing sets to specific queues, so that priority jobs could automatically go to the top of the queue when triggered by a workflow (for example).

Allowing users to create new content

tim.reilly

@definition-path attribute in structured data

ross.williams

Using Internal and External Code Sections

tim.reilly

Mail-to button in the WYSIWYG

bradley.wagner

When implemented at an enterprise level a...

tgatkins

When implemented at an enterprise level across a large institution, multiple publishing queues is essential. This should include at least one "priority" queue, available for use to only a small group of specific users, reserved solely for mission-critical jobs.

Metadata inheritance

jraller

Even moving up to two queues where large ...

jraller

Even moving up to two queues where large jobs go into the large queue and single pages go into the small queue would be an improvement because it would automatically sort the single page jobs so they could go through faster.

I'd also like to see Hannon Hill offer a separate publishing server. That would allow us to separate out publishing from editing so that when Queue ...

Customize system labels

allie

System File Name Settings

schroeder

Include file extension in Index Blocks

jraller

This is a bit lengthy, so I apologize. F...

plower

This is a bit lengthy, so I apologize. First I'll briefly describe our issue:

Cascade server was set up and in use before I got to work for NOVA. I noticed that the compare with current feature never worked, even after several updates. I put in a ticket, and Hannon Hill discovered that we have no default region in our templates(required for compare, and in the document...