I'd love to be able to use this module, but the unalterable blacking listing of client side image maps (map and area tags) makes this impossible.

Just curious, why blacklist image maps?

Comments

markus_petrux’s picture

Status: Active » Fixed

Because the complexity of the HTML involved in image maps.

This filter should not only allow you to use a particular HTML element, but it also needs to make sure you're using its syntax correctly, which is necessary for security reasons.

Image maps involve the use of elements IMG, MAP and AREA. Too complex to parse and validate, we didn't need that feature, and also it is not too common to see this kind of features in WYSIWYG editors.

WorldFallz’s picture

Thanks for the info.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

egon.ojamaa’s picture

Version: 6.x-1.x-dev » 6.x-1.5
Priority: Normal » Critical
Status: Closed (fixed) » Active

I'm a site admin and i need to add image maps into content that is made with WYSIWYG filter.
I cannot change to "Full HTML", because then this content is no more editable by moderators, but admins only.
I also do not see any security risks by allowing image maps.

I suggest to remove this mandatory restriction:

" Forbidden elements: < applet> < area> < base> < basefont> < body>... "

And let the site admins choose via the "element attributes filter" what they allow.
Admins usually know best what is secure enough for who " via role permissions ".

At the moment if anyone wants it right now
then quick fix is to open " wysiwyg_filter.inc " file.
search for " wysiwyg_filter_get_elements_blacklist() "
Delete the array content.

Leave it as:

function wysiwyg_filter_get_elements_blacklist() {
return array( );
}

I hope to see this fixed.

markus_petrux’s picture

Version: 6.x-1.5 » 6.x-1.x-dev
Priority: Critical » Normal
Status: Active » Closed (fixed)

Please, refer to handbook for proper usage of issue attributes.

This issue was just a support request, and fixed in #1.

It could be turned into a feature request, yes. But then it would require someone to provide a patch to parse image map tags properly. Please, see #1 for reasons. Thanks. With no patch, this is better closed. The original reason why this was not implemented still applies: lack of time.

rahultripathi’s picture

Title: why blacklist client side image maps? » client side menu add to the configuraction.
Version: 6.x-1.x-dev » 7.x-1.x-dev
Assigned: Unassigned » rahultripathi
Category: support » task
Status: Closed (fixed) » Active

function servicereminder_menu(){
$items = array();
items['admin/config/servicereminder'] = array(
'title' => 'Service Reminder Admin Settings',
'description' => 'Adjusts Service Reminder Management Operations.',
'position' => 'right',
'weight' => -5,
'page callback' => 'system_admin_menu_block_page',
'access arguments' => array('administer site configuration'),
'file' => 'system.admin.inc',
'file path' => drupal_get_path('module', 'system'),
);

$items['admin/config/servicereminder/servicemangement'] = array(
'title' => 'Service Mangement',
'description' => 'Shows Customers Listing.',
'page callback' => 'customer_listing_admin',
'access arguments' => array('administer site configuration'),
'type' => MENU_NORMAL_ITEM,
);
return $items;
}

WorldFallz’s picture

Title: client side menu add to the configuraction. » why blacklist client side image maps?
Version: 7.x-1.x-dev » 6.x-1.x-dev
Assigned: rahultripathi » Unassigned
Category: task » support
Status: Active » Closed (fixed)

@rahultripathi - please don't play around in the issue queues if you don't know what you're doing.

mherchel’s picture

Feature Request for this functionality is created at http://drupal.org/node/1508346