How to keep all assets from publishing to all destinations?
I am working on a mobile device web site, to be able to easily use event information that is already in the current public site i was testing using the destination pointing in the content types to populate my mobile site. Works fine except that all non html assets (jpgs, folders, pdfs, etc) get published even if they are not associated with the configuration that is supposed to go to that particular destination. is there some way to only publish the assets needed for the mobile pages?
Discussions are closed to public comments.
If you need help with Cascade CMS please
start a new discussion.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by Michael McGinni... on 11 Aug, 2011 10:24 PM
Are you publishing the mobile page itself, or a folder? It seems like just publishing the page would only publish the assets on that page.
2 Posted by Charlie Holder on 12 Aug, 2011 12:14 AM
What version of Cascade are you using?
If you're using > 6.8:
Are you publishing every Configuration for the Page? From what I understand, the supplemental assets (image, scripts, stylesheets) are published when they are referenced by the Template being used.
If you're using < 6.8:
There's no way to publish just a single Configuration. Every Configuration for a Page is being published, whereby calling on the Template, whereby accessing the associated image, scripts, stylehsheets, etc.
That being said, there should be a option for Smart Publishing in your Content Preferences that might help guard against the publishing of assets that haven't been modified since the last publish to a specific Destination.
3 Posted by jcp on 12 Aug, 2011 02:47 PM
my issue isn't with the html pages... it is with the images, folders and pdfs (basically all site content besides html pages)
Here is an example: currently i have one page on the site that has a configuration that publishes using the mobile destination. (assigned in the Content type for that page, i am using 3.8x in sites) So when i publish the mobile destination, it publishes that html file, and all jpgs, gifs, pdfs and folders on the site, even those not associated with the one html page that is supposed to publish. I tried using smart publishing... that has never worked for me, i have it checked but the system always publishes all files regardless of whether it changed or not. If i publish just that page then yes it just publishes the page i want and the associated files, but trying to automate publishing to capture changes to events pages.
4 Posted by Charlie Holder on 12 Aug, 2011 04:00 PM
Am I understanding your description correctly?
You have one, single Page in your entire Site that, on the Content Type for that Page, has a Mobile Configuration mapped to use a Mobile Destination. And when you try to publish from the Destination level, your entire Site is publishing -- files, folders, and other pages?
5 Posted by jcp on 12 Aug, 2011 05:48 PM
Ok, i am testing a new mobile configuration, so right now that is correct i only have one page that has the content type with a mobile configuration mapped to the mobile destination. When i publish the mobile destination that one html page publishes and all the non html files and folders. So only the one html page but the entire site's worth of folders and supporting files.
6 Posted by Charlie Holder on 12 Aug, 2011 06:30 PM
Publishing from the Destination level is the same as publishing the entire Site. It will process from the scope of the Base Folder for whatever Site your Destination has been created in -- it will process through every asset in the tree starting at the Base Folder.
If you're looking to publish just a single Page asset and have only the files, scripts, stylesheets, etc that are dependancies be caught then you'll want to publish from the Page itself.
To catch any Page dependencies, you can use a Publish Set.
I hope this helps. Let me know!
7 Posted by jcp on 12 Aug, 2011 07:19 PM
i am just used to setting nightly publish schedule at the destination level. Hopefully that will work. Not ideal either because as pages are added to the mobile config i will have to manually add them to the publish set. oh well better than the alternative. Just wish there was a way to block folders from publishing to a specific destination, any time someone publishes any site asset and doesn't un-check mobile it will put it on the public site and the mobile site... so there will soon be a ton of misc junk on the site.
thanks
8 Posted by jcp on 15 Aug, 2011 02:00 PM
Basically here is another way to look at my problem. I have a legacy system built way before "sites" and "content types" so any asset that doesn't have a content type, whether it be jpg, pdf or html, will publish to all destinations. So for example, i have an existing Publish Set that publishes all pages related to events every 6 hours. Most of the pages involved with that publish set don't have a content type so they publish to all destinations, including my new mobile destination. And if i set the scheduled publishing to do a destination, ie just the mobile destination, it also publishes all jpgs, pdfs, gifs, folders and htmls. (the htmls it publishes are all that don't have a content type, which in the case of my site it is 90% of the pages on the site.
Obviously the longterm plan is to implement content types for all pages... BUT in the mean time, is there anything you can suggest so that my mobile site doesn't include 1GB of files it doesn't need?
9 Posted by jcp on 15 Aug, 2011 02:06 PM
One more comment regarding "smart publishing", as i mentioned earlier, i have version 6.8.2 and i have "smart publishing" enabled and i have never seen it work. Besides activating it in the Content preferences is there something else i need to do? Any time i have a scheduled publish or if i click on a html and select publish it always publishes all assets associated with that publish regardless of if it is newer than the existing file or not.
10 Posted by Charlie Holder on 17 Feb, 2012 04:49 PM
Going back over some older threads. Were you able to create a manageable system or are there still any outstanding things that we might be able to provide information about?
As far as Smart Publishing goes, depending on how you've setup your asset references and links, using the
system-assettag basically overrides the Smart Publishing setting. For example, if you're using those tags for every image in a CSS file, the system will grab all of the images every time because thesystem-assetis a hardcoded way of dynamically managing. There's no in depth tracking of both the managed asset and the last time the link was managed. Hopefully that makes sense.11 Posted by jcp on 17 Feb, 2012 05:14 PM
i am gradually modifying all my pages to be content types so in that way i am managing the publishing destination. As far as the images go, I have some with system asset tags, but the majority of the images are using this format: src="/render/file.act?path=imagenamehere.jpg
why doesn't smart publishing work for those images (the system asset was only used for wrapper design... not a ton of images...
12 Posted by Charlie Holder on 17 Feb, 2012 06:14 PM
How are you sending the publish requests? If the job is for a folder, any images will be published. But if the job is for a page, the "smart publishing" should take over.
13 Posted by jcp on 17 Feb, 2012 06:34 PM
when it publishes from the destination it publishes everything every time
is there another way to schedule the publishing and have smart publishing actually work?
14 Posted by Charlie Holder on 20 Mar, 2012 02:24 PM
Hey jcp -- Following up with you again.
Smart publishing should work for both tracked images and linked images.
How are you determining that the images are publishing each time? Is that based on what you see in the publish message or by what you see when actually monitoring the time stamps of those files on the web server?
15 Posted by Charlie Holder on 17 Apr, 2012 11:37 PM
Hey jcp --
Did you see my above comment?
How are you determining that the images are publishing each time? Is that based on what you see in the publish message or by what you see when actually monitoring the time stamps of those files on the web server?
Thanks!
16 Posted by jcp on 18 Apr, 2012 01:43 PM
sorry missed your post... i was determining it by the message where it listed all the image files published and by the bandwidth/time it takes to do the publish.
17 Posted by Ryan Griffith on 18 Jun, 2012 07:24 PM
Hi jcp,
Apologies for the late response.
As Charlie mentioned, there really is no way of picking and choosing what images/files to publish other than the smart publishing (i.e. publishing assets that are linked to a specific page configuration). If you are publishing an entire folder, this is especially true.
What you could do is create a scheduled Publish Set that targets the pages you would like to publish specifically (or a folder of pages), this should publish any linked assets along with the pages.
Please let us know if you have any questions.
Thanks.
Ryan Griffith closed this discussion on 25 Jun, 2012 06:00 PM.