Loading...
 

Inline Editing

Inline editing is currently only implemented in the ExperimentalBranches ckeditor4. However, a port to trunk should occur soon.
Inline editing has just been ported to trunk .
Test sites

Inline Editing in Tiki 

End-user Documentation 

End-user documentation is at: https://doc.tiki.org/Wiki+Inline+Editing


This is how it currently works..

)

The 3-second typo-fix is here! (if your system is responsive)

Former dev documentation 

[+]

Tracker-based list of Wishes 

Open 

RatingSubjectSubmitted byImportanceEasy to solve?PriorityCategoryVolunteered to solveLastModifComments
(0) Inline edit keeps creating new P elementsFernando Torres5630
  • Error
2016-06-022
fvtorres-04 Jun 16
(1) wiki (wysiwyg) inline editor transforms page alias links into standard wiki page link on save (alias lost)Xavier de Pedro5525
  • Error
  • Consistency
  • Conflict of two features (each works well independently)
2015-04-260
(0) Multiple problems with inline editing toolbar for HTML mode pagesArild Berg7321
  • Error
  • Usability
2013-10-281
Chealer9-08 Jan 18
(0) Prevent simultanous inline editArild Berg6318
  • Error
  • Feature request
2013-10-281
marclaporte-04 Oct 13
(0) Inline editing add unwanted title to some elementsArild Berg0
  • Usability
2014-07-230
(0) impossible to set a cell padding in a tableJean-Marc Libs60
  • Error
2016-08-020

Pending 

No records found

Closed 

RatingSubjectSubmitted byImportanceEasy to solve?PriorityCategoryVolunteered to solveLastModifComments
(0) Double clicking inside an inline edited area, brings up the full wysiwyg editorArild Berg80
  • Regression
2013-10-201
pascalstjean-20 Oct 13
(0) Enabling "wysiwyg inline editing enabled" causes modules to disappear jcarter50
  • Conflict of two features (each works well independently)
2014-01-081
jcarter-03 Jan 14
(0) Better Editor or at least better FADE function.ShowCaseSupport@projectashenfire.org0
  • Feature request
  • Support request
2019-12-092
ShowCaseSupport@projectashenfire.org-09 Dec 19

Wiki-based list of Open issues 

  • Inline editing "eats" plugins
    • As of r46852 elements containing plugins are no longer editable inline
  • The inline editor tags are saved along with the HTML content. This one has returned
  • Opening the regular wysiwyg-html editor, when the inline editor is open, will use a different toolbar
  • Fix up inline menu.
    • Should use max 2 rows.
    • Must not use any plugins (since plugins are not supported at the moment).
    • Help menu with the plugin selector should also be removed.
    • The ckeditor4 image dialog should be used (with the "Browse Server" button)
    • Possibly should be the ability to customise toolbars for inline editing for each type of object? Like you can for comments
      Would make it possible to solve most of the issues above i think (can be done when back in trunk)
    • Toolbar for the table element contains the paragraph format drop down (H1..6). Should be removed.
  • Inline editing a top-level table tag (not in a div or p) works, but no menu is displayed.
  • User is not warned, when leaving a page with uncommitted inline changes.
  • Before starting an inline edit sessions, it must be checked if another editor is active. Similarly, when the inline editor is active, it should not be possible to start another editor (except by override)
  • Possible performance issue with large pages. The Lorem Ipsum page can be used for testing
  • It is possible to have uncommitted content displayed on the page. It should be visually easy to spot these sections, e.g. a red border. The "page-data" itself should also show that it has "dirty data".
  • On the wysiwyg wiki test server inline editing does not work. OK on the HTML test site.
  • Inline Edit: False positives visible in wiki diff after edit. They are not false positives. Check the difference in length between the sections. The problem is that an extra image is being inserted when inline editing.
  • "Rich Text Editor, editwiki" tooltip should be removed / changed. Occurs when inline editor is active, with mouseover an editable area.
  • HTML syntax in wiki pages. See below for steps to reproduce.
  • When closing the inline editor unsaved changes are lost. The user should get a warning, like when trying to leave the page.

HTML syntax in wiki pages 

To reproduce..
0) set system in html mode (use wysiwyg-html as default)
1) create a new wiki page with very basic content, e.g. bla bla
save it (in html)
2) Reopen the editor and switch to wiki mode.
save the page (in wiki syntax)
3) now make some inline changes and save.
... wiki mode page has HTML tags

Tested in ckeditor4 exp branch. "Allow HTML" was not set.

Would be nice 

  • The admin wysiwyg panel should make the 3 editor choices clearer. One of ("wysiwyg-html" or "wysiwyg-wiki") and possibly "inline editing". Now that wysiwyg is a basic feature, the selections look fine in the "basic" view.
  • Auto save for inline editing / a way to recover unsaved content, due to a "lost" editor.
  • sections containing plugins are not editable, but the edit plugin button is showing an "edit frame". Clicking on it works fine, and the plugin dialog opens.
  • to be able to add an edit comment
  • Faster paste operation. Pasting works well, but is very slow
  • Any chance of getting jcapture to work with inline editing.

Open Questions 

Saving inline changes 

Should saving inline edits be a regular save, or a minor save? For regular saves, an email may be sent to users monitoring the page. This may not be wanted for a tool that is "ideal" to fix typo's.

There is currently no way to select the type of save. A regular save is always done. Thus monitors can receive an email for every typo fixed.

All saves create a new version of the page. Each version keeps a full copy of the page data. Having 10 new versions, due to 10 typo fixes, is far from ideal. This would be the case if the user chooses save in the inline toolbar.

If the user left the changes uncommitted and did a final commit by turning the inline editing off, only one commit would be done. Thus only 1 new version of the page.

An excessive number of page versions can become an issue, depending on the use pattern.

Maybe inline saving should work more like auto save, i.e. write to a draft version until a commit/save is done. The commit can be when the inline editor is closed. If no commit is done, and the page is reloaded, the draft is still there and can be worked on even more before a commit is done.
This would limit the number of page versions.


Based on jonnyb's comment in Chat
"one main issue i think with getting plugins working is that it's not using the auto_save plugin, and most of the parsing etc for plugins is done by that ".

Sounds like we should re-introduce the auto-save function, somehow.

As a user I find it good to be able to save the content immediately after fixing (e.g. a typo).
This "save" could update the draft version.
A "commit" (a save of a new page version) should also have an explicit button, which the user can trigger. I assume the draft can be loaded by the standard editor and saved there.

Maybe the scheduled auto-save should be disabled. So, saving inline draft is only user triggered.

When a page is loaded and a draft exists for that page, the inline editor should then load the draft instead of the saved page.

Toolbar layout 

Page in html syntax 

[+]

Page in wiki format 

[+]

Notes etc 

[+]

Keywords

The following is a list of keywords that should serve as hubs for navigation within the Tiki development and should correspond to documentation keywords.

Each feature in Tiki has a wiki page which regroups all the bugs, requests for enhancements, etc. It is somewhat a form of wiki-based project management. You can also express your interest in a feature by adding it to your profile. You can also try out the Dynamic filter.

Accessibility (WAI & 508)
Accounting
Administration
Ajax
Articles & Submissions
Backlinks
Banner
Batch
BigBlueButton audio/video/chat/screensharing
Blog
Bookmark
Browser Compatibility
Calendar
Category
Chat
Comment
Communication Center
Consistency
Contacts Address book
Contact us
Content template
Contribution
Cookie
Copyright
Credits
Custom Home (and Group Home Page)
Database MySQL - MyISAM
Database MySQL - InnoDB
Date and Time
Debugger Console
Directory (of hyperlinks)
Documentation link from Tiki to doc.tiki.org (Help System)
Docs
DogFood
Draw
Dynamic Content
Preferences
Dynamic Variable
External Authentication
FAQ
Featured links
Feeds (RSS)
File Gallery
Forum
Friendship Network (Community)
Gantt
Group
Groupmail
Help
History
Hotword
HTML Page
i18n (Multilingual, l10n, Babelfish)
Image Gallery
Import-Export
Install
Integrator
Interoperability
Inter-User Messages
InterTiki
jQuery
Kaltura video management
Karma
Live Support
Logs (system & action)
Lost edit protection
Mail-in
Map
Menu
Meta Tag
Missing features
Visual Mapping
Mobile
Mods
Modules
MultiTiki
MyTiki
Newsletter
Notepad
OS independence (Non-Linux, Windows/IIS, Mac, BSD)
Organic Groups (Self-managed Teams)
Packages
Payment
PDF
Performance Speed / Load / Compression / Cache
Permission
Poll
Profiles
Quiz
Rating
Realname
Report
Revision Approval
Scheduler
Score
Search engine optimization (SEO)
Search
Security
Semantic links
Share
Shopping Cart
Shoutbox
Site Identity
Slideshow
Smarty Template
Social Networking
Spam protection (Anti-bot CATPCHA)
Spellcheck
Spreadsheet
Staging and Approval
Stats
Survey
Syntax Highlighter (Codemirror)
Tablesorter
Tags
Task
Tell a Friend, alert + Social Bookmarking
Terms and Conditions
Theme
TikiTests
Timesheet
Token Access
Toolbar (Quicktags)
Tours
Trackers
TRIM
User Administration
User Files
User Menu
Watch
Webmail and Groupmail
WebServices
Wiki History, page rename, etc
Wiki plugins extends basic syntax
Wiki syntax text area, parser, etc
Wiki structure (book and table of content)
Workspace and perspectives
WYSIWTSN
WYSIWYCA
WYSIWYG
XMLRPC
XMPP




Useful Tools