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.

Question about the Alfresco Wiki

partain

Hi,

I've been playing around with the wiki a bit and have a few questions that'll help me understand better how much of a "true" wiki it is.

1. Does it support markup or do I have to use the WYSIWYG editor?
2. Does it support editing individual sections (think mediawiki)?
3. Does it support auto-generation of a table of contents based on sections?

There are more things I'd expect from a wiki, but this is a good start 🙂

Thanks much!

David

Find more posts tagged with

Comments

cloudcontrol

I think you are being charitable about the wiki- it's a start, but not very good.

I'm using v3.2 community edition to manage project sites for work I do with my clients. There are two threads which purport to allow overrides of the strict html stripping that occurs with Share's implementation of tinyMCE and also manually edit which tags are allowed. Has not made a difference for me. Standard html syntax in the wiki is stripped. I stick with Alfresco because it's grounded in granular ACLs which I need more than anything else, but the wiki is embarrassing.

If anyone has had any success with suggestions in these threads I would love to hear it:

http://forums.alfresco.com/en/viewtopic.php?f=47&t=20323&start=0&hilit=blog+video

http://forums.alfresco.com/en/viewtopic.php?f=29&t=18741&p=61585&hilit=tinymce+strip#p61585

mikeh

The original thinking behind the wiki was to make it very simple, as there's really no point in us trying to compete with MediaWiki. I agree the current implementation is somewhat lacking, but works better in v3.4. It's still not a regular "wiki" though…

Thanks,
Mike

stevericker

We see tons of things happening on the WCM and other sides of Alfresco. Our little world is centered on the using Alfresco Share as a collaboration portal (as an alternative to Sharepoint). From our corner, functionality like the wiki, webDAV, file upload and downloading, etc., are the basic bread and butter of what we need. We've been an enterprise customer for years now and have watched the product develop.

The last thing we want to do is complain esp. given how hard Alfresco tries to encourage a robust open source community. It'd be really great though if problems like these in the wiki could be solved once and for all. A simple approach (as Mike H mentioned to be the original strategy) sounds good to us. So much software out there has bells and whistles that're never used and really detract from the basic power of an application. But we've seen a really buggy wiki now for several releases. I've lost track of the JIRA entries and threads quite honestly.

Is there a way to increase the focus on fixing the basic functionality on some of these collaboration-focused applications (e.g., the wiki in this thread). It's a shame, but we're really scared to use something like the data lists because we're worried that we'll come across bugs that, like the wiki, seems to persist.

Just our thoughts. Thanks very much.