Compatibility with WYSIWYG Filter for Domain Validation [#2100027]

Having issues using the https://drupal.org/project/wysiwyg_filter module with BOA.

We have enabled Whitelist - Add rel="nofollow" to all links except those leading to domain names specified in the list below.

And aded both the www.domain.com and domain.com. to the white list.

Have tested both with and without the "Domain Validation"
Have cleared caches after each and every time make a change.

issue

Within BOA we have enabled redirect from the www. to main alias 'domain.com'

There is a related issues #744970: Domain validation is way too strict and have tested the patch but still unable to get to work with BOA.

Comment	File	Size	Author
	2013-09-28 11.08.57 am.png	52.5 KB	HyperGlide

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

omega8cc CreditAttribution: omega8cc commented 30 September 2013 at 13:05

Project:	Barracuda	» Octopus
Component:	Documentation	» Miscellaneous
Status:	Active	» Postponed (maintainer needs more info)

What is the problem or error exactly and why do you think it has anything to do with BOA?

By the way, you should separate domains with just a comma, not a new line.

Comment #2

HyperGlide CreditAttribution: HyperGlide commented 30 September 2013 at 14:36

Status:

Postponed (maintainer needs more info)

» Active

The problem is that the "whitelited' domain are having the rel="nofollow" added when it should not be added.

There is an issue in the WYSIWYG Filter queue about the domain validation being to strict but I have applied the patch from the issue noted and still did not resolve the problem. Only way to resolve is to "disable" the check.

Retested by changing entry to
domain.com,www.domain.com

After saving the page and reloading the domains are listed 1 per line in the "Domain List" form box.

Cleared all caches but the issue persists.

Comment #3

omega8cc CreditAttribution: omega8cc commented 30 September 2013 at 14:41

Status:

Active

» Closed (won't fix)

Still, I fail to see how it could be related to BOA. Feel free to re-open the issue if you will have a *proof* that it is a bug or problem caused by BOA.