I've noticed flaky results with the "break" tag in Drupal content posts: sometimes the summary is broken at the break tag, sometimes not.
I'd never put a lot of effort into figuring it out.
Until today.
Set up a dev site for a client yesterday and was pleasantly surprised that the break tag split the summary from the body of the content as expected.
Today, reviewing the front page, I noticed content that was not split as expected.
After spending too much time diagnosing, I realized it was the Filtered HTML vs the Full HTML Text format setting.
Searching with that new-found knowledge, I came upon a bug report, which indicates it is a regression bug and has existed for 5 years!
I'm shocked by that, and rather disgusted frankly.
Seems the solutions, such that they are, consist of:
Granting Full HTML to all users
Apply one of the questionable patches to every update of Drupal
Have users copy & paste the desired summary from the body content each and every time they modify the body.
This is pathetic that some solution hasn't yet made it into the main branch.
Blah, I have a love-hate relationship with Drupal and it tends towards hatred lately.
Comments
Ron
Wed, 2015/03/18 - 18:28
Permalink
And, another thing...
When adding a Tag for this post, the following error got thrown up by JavaScript:
An AJAX HTTP error occurred.
HTTP Result Code: 200
Debugging information follows.
Path: http://critters.maow.net/taxonomy/autocomplete/taxonomy_vocabulary_2
StatusText: OK
ResponseText: {"Drupal, accountability":"accountability","Drupal, back country":"back country","Drupal, Barnes":"Barnes","Drupal, BC forestry camp sites":"BC forestry camp sites","Drupal, Betty":"Betty","Drupal, CBC":"CBC","Drupal, exobiology":"exobiology","Drupal, fail2ban":"fail2ban"��wupal, Queen Elizabeth":"Queen Elizabeth","Drupal, Samba":"Samba"}
All I'd entered in the tag field was "Drupal," and possibly "b".
Not sure why "Drupal" is pre-pended onto all shown tags.
R o n
- - -
Vancouver
Ron
Sun, 2015/03/22 - 11:39
Permalink
Work-around found
herzbube posted a work-around for the <!--break--> tag being broken in response to my post.
It should persist through Drupal updates, but would need to be applied to each instance of a Drupal multi-site installation.
An admin needs to allow "<!-->" to the list of allowed HTML tags for Filtered HTML.
This can be accomplished by going to /admin/config/content/formats/1 (Configuration > Content Authoring > Text Formats > Filtered HTML configure) and selecting Limit Allowed HTML Tags.
Add " <!-->" to the end of the list of tags under the label Allowed HTML tags.
I have not yet tested this though. Stay tuned.
R o n
- - -
Vancouver
Ron
Sun, 2015/03/22 - 11:55
Permalink
Tested - works
This method does indeed work.
Not pretty, but ... acceptable.
R o n
- - -
Vancouver
Add new comment