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

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

editing imported html

sigei

Hi,

I imported my existing website as a test and notice that it doesn't allow me to edit html files inline. However if I create a new file in a web project and enable inline editing in the properties at the end of the wizard it seems to work fine.

How do I enable in-line html editing of a bulk-imported site? Is this disabled intentionally?

thanks
sig

Find more posts tagged with

Comments

paolo_bettini

I imported my existing website as a test and notice that it doesn't allow me to edit html files inline.
[…]
How do I enable in-line html editing of a bulk-imported site? Is this disabled intentionally?

Same same problem… I was looking around for the same answer!

Actually, when I create a "html" web content in a web project, I can write it by the inline html-editor, but when I try to edit it again, I have to download/upload… exactly as after a bulk import.

I've been able to enable inline editing only on contents in Spaces that are not under a web project.

Thanks in advance,
Paolo.

kvc

Guys:

Yes, you can't just use TinyMCE to edit imported HTML pages. TinyMCE is designed to create and edit HTML fragments. If you have an existing web page, if you attempt to open in TinyMCE, all your Javascript and such will get munged and corrupted by TinyMCE. That's why it's disabled. People were importing static sites and then instead of using the standard editor they used to create the page, tried using TinyMCE. Their pages were munged and unpreviewable. They'd have to Undo their changes and revert their sandboxes back to the latest version of Staging.

What to do?

Create one simple web form, article. Make it have two elements: a title (xs:normalizedString) and a body (xs:string). Then, take your HTML page, save as a *.ftl, and mark-up to make a Freemarker template (add a Freemarker decorator as your first line, declare your XML namespaces, and then delete all the body content and reference instead the body element in your XML. Create a new XML, generate your page, and then on an ongoing basis, users can edit HTML page - but the body only - using TinyMCE. And because it's a template, if you change your template, you can use our Regenerate wizard to re-build all your HTML pages.

It's a slight bit more work, but it'll make your static HTML pages based on XML and standard templates in a pretty quick, straightforward manner. That's part of the power of Freemarker, btw - any HTML page can serve as the basis of a Freemarker template.

We go through this exercise in our WCM Training course. I encourage you to sign up!

Kevin