[#MDL-8773] Ability to disable HTML editor for specified database fields

Issue Details (XML | Word | Printable)

Key:	MDL-8773
Type:	New Feature
Status:	Open
Priority:	Major
Assignee:	Mathieu Petit-Clair
Reporter:	Ray Lawrence
Votes:	10
Watchers:	0

Operations

Add/Edit UI Mockup to this issue

If you were logged in you would be able to see more operations.

Moodle

Ability to disable HTML editor for specified database fields

Created: 06/Mar/07 05:32 PM Updated: 26/Nov/07 03:43 PM

Return to search

Component/s:

Database activity module

Affects Version/s:

1.7.1

Fix Version/s:

2.0

Environment:

Any that support HTML editor

Database:	Any
Participants:	Martin Dougiamas, Martin Huntley, Mathieu Petit-Clair and Ray Lawrence
Security Level:	None
Affected Branches:	MOODLE_17_STABLE
Fixed Branches:	MOODLE_20_STABLE

Description

« Hide

The HTML editor is overkill for some text areas which are small or where simple unformatted text is the required input.

It would be most useful if there was an option to disable the editor as required (in a similar way to the option for templates).

All

Comments

Change History

Version Control

Sort Order:

[ Permalink | « Hide ]

Martin Huntley added a comment - 06/Mar/07 10:28 PM

I agree. Very important to making more useable interfaces for simple data collection tools. Ideally, there would be a general way to selectively disable HTML editor that works across modules, because the database module is not the only one where this is overkill.

[ Permalink | « Hide ]

Martin Dougiamas added a comment - 07/Mar/07 08:59 AM

This is a tricky to do due to how the editor works, but we should tackle it sometime soon.

I'd like to see a little switch next to the editor to toggle it on and off. The trouble is that this will need to reload the page, and so you'd have to lose any/all unsaved changes made to the form. I guess we can live with that.

I'd like to see this toggle be "sticky" for every page too, which means storing a flag in user prefs for every page that a user hits the switch on (that overrides site+user settings for that page only).

[ Permalink | « Hide ]

Ray Lawrence added a comment - 07/Mar/07 05:23 PM

Cheers.

Sounds great. Just in case my initial post was not clear on this point, I'd like the capability to disable the editor when creating the activity but also for the status of the editor for specified text areas to be the status for each participant who subsequently accesses the acivity .

All content on this web site is made available under the GNU General Public License, unless otherwise stated.