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.

Cannot edit HTML content in WYSIWIG editor

tvars

Hi,

I'm trialling the Alfresco community edition 2.1 + WCM and I have a problem when editing html content for a Web Project. I can create the content in the WSYWIG editor fine. However, when I try to edit it by clicking on the edit icon next to it, I get the message "
To edit the file 'test.html', click the link below and if asked select Save." instead of the WSYWIG editor. I can't edit the content on the web browser. It's as though Alfresco can't work out that I can edit the content type in the browser.

When I create HTML content outside of a web project (e.g. in a normal Space) I works fine.

Any clues? Thanks for your help.

Find more posts tagged with

Comments

tvars

Ok, it seems from this thread that this is a feature not a bug.

http://forums.alfresco.com/viewtopic.php?t=8209

Is there a way to enable inline editing? For my purpose I really need it to be enabled.

kvc

Tvars:

Two options:

1. Create and edit your HTML fragments in a normal Alfresco space, and
     use a content rule to auto-promote to a Web Project (using the pre-built
     action or creating your own custom action using the Javascript API)

2. Create a very simple web form that has one defined element,
     a rich-text field (using whatever appearance annotation you want
     to customize what functions and plug-ins you want to enable). You
     can associate that form with a simple Freemarker template to strip
     out the HTML from the generated XML and write as a standalone
     HTML fragment. Your end-users would then be able to click edit
     on that HTML fragment and re-load upu the form for editing.

The goal of our authoring services is to make content re-usable,
repurposable, and well-structured. Obviously, you don't always
need that. In the simple case, just use a very simple form. Starting
with this model, though, means that you can extend over time to
increasingly structured data entry (extend your XSD to start capturing
titles and abstracts) or content reuse (associate more templates to
generate increasingly different output).

A separate feature enhancement to simply load up the WYSIWYG editor for an HTML fragment without an associated template is noted. However, to get started today, I'd recommend either one of the two above. Ultimately, if we were to address the feature improvements, under the covers we'd likely make the out of the box use of the WYSIWYG editor works exactly as noted in #2 above.

Cheers. Hope that helps.

Kevin

rscheele

Hi kevin,

do you have any plans for the second options to incorporate in the upcoming releases? I would be a nice way for simple editing of static HTML files when migrating from a 'web 1.0' website.