[
http://www.jahia.net/jira/browse/JAHIA-3739?page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#action_25675
]
Sergiy Shyrkov logged work on JAHIA-3739:
-----------------------------------------
Author: Sergiy Shyrkov
Created on: 10/Dec/08 11:53
Start Date: 10/Dec/08 11:53
Worklog Time Spent: 2 hours
Issue Time Tracking
-------------------
Remaining Estimate: 0 minutes
Time Spent: 2 hours
> HTML Checks and Validation: fully remove it from Server Settings
> ----------------------------------------------------------------
>
> Key: JAHIA-3739
> URL: http://www.jahia.net/jira/browse/JAHIA-3739
> Project: Jahia Web Content Management Server (WCMS)
> Issue Type: Bug
> Components: Administration Center
> Affects Versions: WCM 6.0 (Andromeda)
> Environment: 23153
> Reporter: Stephane Croisier
> Assignee: Sergiy Shyrkov
> Fix For: WCM 6.0 (Andromeda)
>
> Attachments: screenshot-1.jpg, screenshot-2.jpg
>
> Time Spent: 2 hours
> Remaining Estimate: 0 minutes
>
> Would it be possible to fully remove the "HTML Checks and Validation" menu
> from the Server Settings and to only keep one of it on a per site basis?
> Currently the "Manage Site settings" sub-menu is duplicated on the server and
> site levels.
> I think the Display HTML Editors List is useless. We do not package Andromeda
> with any thrid party editor any more. Customers who really want to install
> another WYSIWYG editors could perfectly modify manually some config file. Do
> we really need a "reload from disk" option in the admin center (that nobody
> will never test and which will be probably broekn quite soon)?
> So it rests the Manage Markups filterings in order to customize the parsing
> and clean-up of big texts. This one should ideally be also customizable at a
> site level. I do not understand the "apply to all sites" paradigm as I can
> not select a group of sites for instance. Ideally speaking this should also
> be combined with some other jtidy or Necko HTML parsing parameters in order
> to let the webmaster decides which are the default parsing paramaters for the
> big text of his current site. First of all I even do not remember if we are
> using jTidy or NeckoHTML in order to parse bigtexts right now. Some releases
> of Jahia were using one parser and omse other another one. jTidy looks like
> quite a dead library. So do we still want to keep it? The only interesting
> things was about automatic correction of broken HTML (e.g. a end-user makes a
> bad copy/paste of HTML and forget some closing brackets which are then
> corrupting the whole page). But I think Necko (or other lib) can today also
> perfeclty make it. Finally such a menu would be bit by bit upgraded in order
> to better support distinct FCK configuration with some roles. Lots of
> customers are asking to be abyl to dynamically load different FCK toolbars
> for different group of users. I think this is only a FCK JSP to dynamically
> load. So such an option would be really appreciated by a lot of customers.
> So without breaking everything, could we firt see how to move such options at
> a virtual site level?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://www.jahia.net/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
jira_list mailing list
jira_list@jahia.org
http://lists.jahia.org/cgi-bin/mailman/listinfo/jira_list
