nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Livesite Templating

robertl

I'm using Livesite 2.1. I've created several templates, and they seem to work fine when creating new pages. However, the following happens when changes are made to either the templates or the created pages:

1) if template components were added or deleted, the pages that use the templates which have not been customized or have been customized will not show the changes when updated using the "get latest components/update all" option. Only overwrite seems to work which defeats the purpose of templating. What do I need to do to preserve at least my content customization ?

2) permissions such as layout and content set on the template components do not seem to work when editing pages created using the template. I'm trying to lock down the components. I like authors to only be able to add/customize content.

Find more posts tagged with

Comments

wscott

For 1), there are a couple of factors at work here...

If you delete and re-add a component to a template that counts as a whole new component for purpose of Get Latest Components. Your old component (and any customizations) gets discarded and the fresh new one added.

However, if you do Get Latest Components and select "Update All," it won't actually delete any components that were removed from templates (so that you don't accidentally lose those customizations) but it will add new components. This can sometimes result in components overlapping one another. You might be seeing an old component covering up a new component.

If you do "Manually select which components/templates to update," then it will remove the components. (We're changing this in the next version to always remove the components since the way it works now seems to confuse people more than help them.)

For 2), what version of LiveSite are you using? In earlier versions, the page owner always had full permission to the page and everything on it. I think we changed that in the latest version though so that even if you own a page you are restricted by the permissions.

robertl

Thx Will. On #2, your answer was correct -- unfortunately. We're on ver. # 2.1.0.1. Which version has the correct implementation of access permissions ?

As for #1, when I "update all", it actually deleted the old component, but did not add the new component. Let's approach this differently. Here's the scenario. I've created and customized several pages that use 1 template. At a future date, if I choose to change the template by merely rearranging the left navigation and header and footer info, but keeping the body content in the middle of the page. What's the best way to do this, but still maintain my customized body content ?

Thx.

shanon

Here's the scenario. I've created and customized several pages that use 1 template. At a future date, if I choose to change the template by merely rearranging the left navigation and header and footer info, but keeping the body content in the middle of the page. What's the best way to do this, but still maintain my customized body content ?

Hi --

I would not have the body content inside the template. Instead, leave the body content section blank and lock the layout of the template. Then, page authors may add in the custom body component(s) themselves. That way, you're just rearranging the body "wrapper" in the template and the actual content body belongs to the page. When you run Get Latest Components after updating the template, only the wrapper will be updated and you should be good to go.

Shanon

wscott

I think version 2.2 is when we started enforcing permissions upon the page owners, but it may have been 2.2.1. If you are going to upgrade, go all the way to 2.2.1 anyway, since it fixes some minor issues from 2.2. (Although you will need to upgrade to 2.2 first and then to 2.2.1 to migrate the data correctly.)

robertl

Thx Shannon on the input on the tempating. However, to enforce a strict UI, I need to lock-down everything including the body. Ideally, we'd also like take away the "add component" functionality for authors.

Is there any way to do this? Otherwise, frankly, the templating is worthless.

shanon

Thx Shannon on the input on the tempating. However, to enforce a strict UI, I need to lock-down everything including the body. Ideally, we'd also like take away the "add component" functionality for authors.

Is there any way to do this? Otherwise, frankly, the templating is worthless.

The GLC update preserving changes should keep all of the changes in the components on the page. ( your #1 point ) above. There were some bugs with GLC in the beginning but we think that most have been worked out.

You should be able to do what you're describing and run GLC and have all your customizations maintained.

Shanon

robertl

Thx again for the prompt response. Is it safe to assume that the GLC bugs were fixed as of Ver. 2.2.1 ? We're still on Ver. 2.1.0.1.

wscott

All the GLC bugs that we know of have been fixed in 2.2.1. Smiley Wink

However, it can still be confusing, particularly the behavior with adding and removing components from templates. We going to spiff up the UI a bit in a future release, but for now, my advice is to use the "manually compare" option (rather than "update all" or "overwrite all") so that you can compare the new and old templates and see which pages and components will be modified.

niske

maybe for you it would be a good idea to create two separate templates, one for the 'curtain' and one for the body content. Even if there is only one component on the body template, it still allows you to secure it.

Frederik

FYI you have resurrected a thread that was 1y and 1m old ;-)