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; } } }

multiple skins in sitepublisher

liv2luv

I am reading the data from a DCR and rendering it as HTML, which is the default skin. Also, the requirement is to generate an XML file in a specified format. Let's say I will make another skin and generate the XML file.

My question now is, will this XML skin create an XML file every time an action is triggered in the HTML page (contains form fields including submit button)? I am a little confused understanding this.

Thanks

Find more posts tagged with

Comments

AlexC

Currently the skins are selected at design time (during page edit) and there is no way to dynamically select a skin.

Stokes

How do you need to get the XML version? If you do it as skins, you'd have to create two pages, an HTML one and an XML one.

But you might also use the $AJAX_URL for the component to get an XML document directly from your component. However, that doesn't make it easy to apply a stylesheet if you need to transform the DCR structure to a new format.

Stokes.

liv2luv

How do you need to get the XML version? If you do it as skins, you'd have to create two pages, an HTML one and an XML one.

But you might also use the $AJAX_URL for the component to get an XML document directly from your component. However, that doesn't make it easy to apply a stylesheet if you need to transform the DCR structure to a new format.

Stokes.

I am getting the XML version by creating another skin. When I choose the xml skin and generate HTML, it obviously shows up HTML format but not the XML format document. the HTML skin is working fine.

can you elaborate more on this $AJAX_URL for the component to get an XML document directly from the component?

Thanks

Stokes

can you elaborate more on this $AJAX_URL for the component to get an XML document directly from the component?

Well, it's meant for a rendered component to communicate with itself, so to speak. So a component might render itself, usually HTML, which includes Javascript for communicating back to the server, which is done using a new request (XHR) to the $AJAX_URL. That URL calls the component's external and returns its result as XML. (For a specific example, the OOTB Polling Component renders a multiple choice poll. When the user casts a vote, their vote is sent via AJAX and the results-so-far are returned as XML to display--without refreshing the whole page.)

In your case, this is probably shoehorning it a bit too much. It's definitely more straightforward to create an alternate .page that outputs XML. Sorry if my thinking aloud confused things.

Stokes.