It appears that on one of my sites the Leech module drops line feeds and carriage returns in leeched body text making the material difficult to read.

Comments

alex_b’s picture

alex_b commented

did you try to adjust input filters? i. e. set the input filter for your feed items to full html.

let me know if this helps.

Clemens’s picture

Clemens commented

Setting filter to 'Full HTML' does not appear to make any difference... Even after removing all items and leeching new items.

matt_harrold’s picture

matt_harrold commented

I had the same problem but the solution DID work for me.

Full HTML input filter fixes the carriage return (and other markup) problem for me.

It's not all gloom, just for some.

Leeteq’s picture

Leeteq commented

This could be caused by a conflict between two filters or depending on which order the filters are applied. Quick test: Does it make a difference if you ensure that only the HTML filter is allowed for leech items?

Leeteq’s picture

Leeteq commented
Category: bug » support

As it works on other sites, this seems like a support request and not a bug.

alex.cunha’s picture

alex.cunha commented
Version: 5.x-1.x-dev » 5.x-1.9

I also have the same problem.

I have set input filter to 'Full HTML' and doest notice any difference.
Have removed all items and leeched the items again.

alex.cunha’s picture

alex.cunha commented

to DanielTheViking

How can I ensure that only the HTML filter is allowed for leech items?

I have edited the imported item and noticed the input format is set to 'filtered html'. Switching to 'full html' solves the problem and then carriage return and images are OK.

So, I rechecked the input format on the Content Feed and is set to 'full html'. So I no understand why the imported itens are with 'filtered html'.

thanks for your help

alex_b’s picture

alex_b commented
Status: Active » Closed (fixed)

If you change filter settings be sure to clear the cache before you check for changes. The devel module offers a convenient "clear cache" link in a block, but you can also go to the DB and wipe cache_filter. This issue is closed, right?