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

SitePublisher Page Editor

catownsley

What is the SitePublisher Page Editor? The Teamsite/Sitepublisher Developer's guide mentions the "live production page for the SitePublisher Page Editor environment" in the documentation for the Edit this Page and In Context Edit components. I'm beginning to work with these components and I can't find any documentation that explains if this is a tool or otherwise.

Find more posts tagged with

Comments

Faizi

What is the SitePublisher Page Editor? The Teamsite/Sitepublisher Developer's guide mentions the "live production page for the SitePublisher Page Editor environment" in the documentation for the Edit this Page and In Context Edit components. I'm beginning to work with these components and I can't find any documentation that explains if this is a tool or otherwise.

Whenever you click on Edit to edit a .page file it will open with an user interface that is called SitePublisher Page Editor.
SitePublisher's files (.page or .component) does support to any other external IDE / editor to creating or editing. You have to use it's own interface for creating or editing a file.

vpatel

Generally speaking SP Page Editor refers to the drag-n-drop canvas type of interface -- where you can create content by dropping components (drag-n-drop).

catownsley

I've used this editor for building pages and previewing in the SitePulisher environment, but not for the livesite runtime environment. When attempting to use the link for the Edit_this_Page.component, a 404 error comes up. Because the Edit_this_Page.component only works for the Livesite runtime, it seemed possible that there was another tool. Perhaps changes need to be made to the component code.

liv2luv

I've used this editor for building pages and previewing in the SitePulisher environment, but not for the livesite runtime environment. When attempting to use the link for the Edit_this_Page.component, a 404 error comes up. Because the Edit_this_Page.component only works for the Livesite runtime, it seemed possible that there was another tool. Perhaps changes need to be made to the component code.

I could not understand what you are trying to say. However, you need to be running the LiveSite Runtime to make use of this feature.

catownsley

I am running this component on the livesite runtime. It puts a link on the page. When I click the link I get a 404 error. I expected an editor to open.

tec_iwov

take a look at the html source what is the url being generated?

catownsley

It seems that issue is a configuration file on our server uses 'localhost' instead of the IP. This causes the component to look for the sitepublisher page editor on the local machine.

Thank you for your responses. Otherwise, I would have spent time looking for some sort of LiveSite specific page editor.

catownsley

I have new information after further research into this issue:

The 'localhost' setting comes from the value in the default.site xml. You can edit this value, but only by directly accessing the raw XML and NOT through the Edit dialogue.

The value is set when the site is created. This value (whether localhost, IP address, server name, etc) is pulled from the iwwebd section in iw.cfg. If you are going to use either the edit_this_page.component or the in_context_edit.component, I highly recommend that you do not use localhost in the iwwebd section of iw.cfg

Right now, both edit_this_page.component and in_context_edit.component are hardcoded to use http:// and NOT https://. If your network configuration requires SSL for traffic between LiveSite and SitePublisher, then the components will not work.

There is a patch release planned for around the end of June for TeamSite 6.7.2 SP1 that Interwoven hopes will allow for https://

I hope this was clear. Please let me know if you have questions about this post.

ccprofessional

Interesting issue.
It is my understanding that $URL_PREFIX should take care of the prefix to the url all the way upto 'sites'/;

I am not sure what your component is doing for building the link, but couldn't you have used this instead?

catownsley

Both of the components are OOB components. They call a class.method() that are part of the Interwoven java libraries. These class.method() returns the url to the component. I believe that the 'http://' value is hardcoded in the java class.