Hi all
I am a bit confused, 
I thought it was possible to apply a new or any design from the global site, downwards to the other assets. But this proved to be incorrect in 3.12.2.
I tried it but the changes didn't take effect at all, therefore I had to do it by parent and the child of any assets, then only the changes took effect.
I didn't come across any issues when using 3.10.3. :blink:
Cheers :lol:
Its not incorrect – a design applied to the site will be inherited by any assets that do not have a more specific design applied at a lower level. If you set an "Override" design, it only applies to that asset, and is not inherited.
You need to make sure that the assets underneath the site do not have a specific design applied so that the design assigned to the site takes affect.
[quote]Hi all
I am a bit confused, I thought it was possible to apply a new or any design from the global site, downwards to the other assets. But this proved to be incorrect in 3.12.2.
I tried it but the changes didn't take effect at all, therefore I had to do it by parent and the child of any assets, then only the changes took effect.
I didn't come across any issues when using 3.10.3. :blink:
Cheers :lol:[/quote]
We have the same problem. Did you find that the page gets sent off when you attached the new design, but the hippo never starts?
Richard
Your problem is that the HIPO cannot begin because you have too many assets to apply the design to and the DB query is taking too long on your system. Your workaround until we redesign the update lookups HIPO is to apply the designs in chucks, or to do it through the DB.
[quote]We have the same problem. Did you find that the page gets sent off when you attached the new design, but the hippo never starts?
Richard[/quote]
Well Richard, I have not come across that problem yet. So how pages does it take for this thing to occur in a site???
Cheers :lol:
It is impossible to say -- it depends on your database server and how long it takes to process the query. On Oracle systems that I work with, we are able to start HIPO processes for designs that will be applied to over 50,000 assets.
This is a good point… we have had design changes (change an entire site to a customization for example) were we have had similar experiences as Yogi. This has been due to some of our publishers having specifically applied the designs as 'New' on child page assets… this causes the new customization to not cascade to those assets when assigned at the parent (as you would expect really).
So training for better practices has been our outcome. To apply the most commonly used design from the parent, and only override it where needed. Therefore the 'New' section is only really used at the sites root (or departments / schools subsites root)… to this end the best practice when child assets have a specific 'New' design - try to just 'clear' the design from the child - it will assume the parents set 'New' cascading design - future proofing for design changes.
[quote]Well Richard, I have not come across that problem yet. So how pages does it take for this thing to occur in a site???
Cheers :lol:[/quote]
Many, many assets - I think our system has more than 40,000. I stopped counting after I ran out of fingers and toes…
R
The Oracle system I'm working on at the moment probably has around 75,000 assets, though not all under the same Site. I reckon our largest site has 20,000 odd assets in it.
Avi, can you please clarify for me how you determine the number of assets under a site (do you simple determine at the database level from tables liek sq_ast?)
A
The easiest way is to lock the Permissions screen of the site asset. The cascade message at the bottom will tell you how many assets are going to be altered if you press commit. That is how many assets there are under the site.
Many Thanks Greg....Given this technique our partially migrated Internet Site has around 8,500 assets under it. I would suggest that we are less than 1/2 way through our migration......fun fun fun... :)
Also the Workflow screen displays the total number of assets, sadly the setting screen doesn't have this. Why is that????
This could greatly help the users in telling them the number of assets which could be effected with a particular design???
cheers :lol:
[quote]sadly the setting screen doesn't have this. Why is that???
This could greatly help the users in telling them the number of assets which could be effected with a particular design???[/quote]
Designs are different, though – because you set different designs at different levels, there is no way to determine how many assets will actually be affected by setting the Design at the site level. And unfortunately, Matrix will run the entire HIPO even though it may not actually be changing any assets.
Ouch.
After reading these numbers I am starting to realise how big our site is. We have just over 22.5k (and growing) assets under the site asset of our main site, and ~55k in Matrix all up. I guess I can expect a few issues when it is time to go live and I need to start playing around at a site level.
You just need to be aware of the site size and act accordingly. :) We have a few sites with over 100,000 assets.
Our asset numbering just hit 7 digits....but we don't have that many assets.
Richard