If you use invisimail filter and Views and see what's happening you'll probably know to disable the Invisimail filter in your input format, but it would be nice if we didn't have to.
Here's what happens:
- use invisimail filter on an input filter (e.g. filtered html)
- set the filter weight for invisimail so it runs last, in order for email adresses to be encoded
- create a View that shows a 'Live preview' of a post that contains an e-mail adress.
- When saving the view, you will see a blank screen with just the email adress contained in the post. You can go back, but you can't save it, will hang at this screen.

I guess this is some javascript thing going on.

Comments

eabrand’s picture

eabrand commented
Assigned: Unassigned » eabrand
Status: Active » Needs work

This will require someone to implement views_hook and such. Whoever wants to give it a try, go for it.

sdboyer’s picture

sdboyer commented

I don't think it's a question of any views hook implementations - more a problem of javascript interaction.

It SHOULD work fine if you set invisimail to just use non-JS encoding, at least while you're setting up your views. I'm not enough of a js wizard to know what it would take to wrap the js output in such a way that it would play nicely with Views' live preview embedding.

Crell’s picture

Crell commented
Status: Needs work » Closed (duplicate)

Actually, I suspect this was caused by the document.write(), which was replaced in #874120: document.write breaks ajax. So marking as a duplicate. Yay, clean issue queue!