Do you see any errors at indexing time? It might be useful for you verify that the documents in question are getting indexed by uploading one of the problem documents a second time and watching error.log for any issues. Have you established that the documents in question are getting indexed? So in y...

As to the question around caching and invalidation Dispatcher really doesn't support the user case in question out of the box. In order to arrive a solution you'll have to gather a few requirements around your solution:How are you structuring the URLs of your servlets. If you are using a query strin...

Adding new meta-data fields is a developer activity. See http://dev.day.com/docs/en/cq/current/dam/how_to_edit_metadata.html#Creating%20New%20Metadata%20Property%20for%20Assets for details on how to add new fields.

Depending on how active your users are and how granular your tracking is you might want more directories below the month node (you probably don't want more than a couple hundred child nodes of any one directory. You will also want to make sure you account unique node names across publish instances -...

The widgets do wrap by default so if you aren't seeing widgets you have configured to be there my guess is you are experiencing some sort of javascript error, or browser compatibility issue. When you open the dialog if you expand the size of the dialog do the widgets you expect to see show up? What ...

That isn't possible in AEM/CQ. In the current version there is support for an undo feature, but there is now way to do save at the page level.

To my knowledge there is no auto-save behavior anywhere is AEM/CQ. In design mode if you open a dialog for a individual component you get save buttons at the individual component level. Are looking for the ability to edit the design of multiple components and then hit a single save button for all th...

Looks like a bug to me - I'd report it to Daycare. I see the same thing on my local. 

It sounds like you need to enable sticky sessions. I don't know what your infrastructure set up looks like so you may only need to do this for the load balancers in front of your web servers, or you may also need to implement them between the web servers and the publish servers. 

In screenshot you provided you set the run mode of the trigger to Publish. When you set the run mode to Publish that means that workflow will on be kicked off on a server that includes the Publish run mode. Since you author server has a run mode of Author that workflow trigger will never start a wor...