Through the web html_not_likey

[David Bain]

I propose that we consider providing a through the web interface for listing the ids and classes that should not show up in a newsletter.

Some of you are familiar with:
plone_html_strip_not_likey, located in
http://svn.plone.org/svn/collective/collective.dancing/trunk/collective/dancing/composer.py
It provides a list of classes and ids that should not show up in a newsletter.

For two reasons I propose that this should be configurable via the web.
1. Convenience
2. The "sensible defaults" may not fit use cases where persons actually want to show some of the filtered items.

This is the list that I currently use in my plone_html_strip_not_likey. Being lazy I just 'hack' the dancing egg after it is installed.

note the use of content-history, this accomodates plone 3.3 which has changed the id from review-history to content-history.

plone_html_strip_not_likey = [
    {'id': 'review-history'},
    {'id': 'content-history'},
    {'class':'documentActions'},
    {'class':'portalMessage'},
    {'id':'plone-document-byline'},
    {'id':'portlets-below'},
    {'id':'portlets-above'},
    {'class': 'newsletterExclude'},
    ]

BTW, with a name like "plone_html_strip_not_likey" it's difficult to write this email with a straight face.
--
SplashStart - Professional Websites. Starting Now.
http://www.splashstart.com

[Daniel Nouri]

On Sat, Jun 27, 2009 at 8:34 PM, David Bain<david...@alteroo.com> wrote:
> I propose that we consider providing a through the web interface for listing
> the ids and classes that should not show up in a newsletter.
>
> Some of you are familiar with:
> plone_html_strip_not_likey, located in
> http://svn.plone.org/svn/collective/collective.dancing/trunk/collective/dancing/composer.py
> It provides a list of classes and ids that should not show up in a
> newsletter.
>
> For two reasons I propose that this should be configurable via the web.
> 1. Convenience
> 2. The "sensible defaults" may not fit use cases where persons actually want
> to show some of the filtered items.

+1 Sounds like a good idea to me!

> This is the list that I currently use in my plone_html_strip_not_likey.
> Being lazy I just 'hack' the dancing egg after it is installed.
>
> note the use of content-history, this accomodates plone 3.3 which has
> changed the id from review-history to content-history.
>
> plone_html_strip_not_likey = [
>     {'id': 'review-history'},
>     {'id': 'content-history'},
>     {'class':'documentActions'},
>     {'class':'portalMessage'},
>     {'id':'plone-document-byline'},
>     {'id':'portlets-below'},
>     {'id':'portlets-above'},
>     {'class': 'newsletterExclude'},
>     ]
>
> BTW, with a name like "plone_html_strip_not_likey" it's difficult to write
> this email with a straight face.

:-)

--
http://danielnouri.org

[David Bain]

To extend my proposal, I think this could be implemented under Channel > "edit channel" > composers