I'm using this module and it works for Blog body, but not for Page body. I save the body field to default to "Full HTML", but after I save, I go back, the field edit form reverts to "filtered HTML." This causes new add new content to continue to default to "Filtered HTML."

I am using user #1, cleared cache, etc.

Comments

dragonwize’s picture

Status: Active » Postponed (maintainer needs more info)

I am unable to replicate this. All the content types and fields I have tested with all work fine. If you can figure out more exact steps to replicate I can look into this more.

johnv’s picture

This happens when you clear the field.
Possibly because when the field is cleared, it's corresponding record of e.g. table field_body is removed. So all settings are removed with it.

johnv’s picture

Status: Postponed (maintainer needs more info) » Active

IMO initial post is not clear enough about the context of his issue.

It appears he means when changing the body in the node edit form. Hence my comment #2 (and probably #1)
However, the error occurs on the Edit-tab of the content type's field
/admin/structure/types/manage//fields/

The feature is referenced in #1275266: Add field level default format with full Better Format options

A simple field level default that piggy backs on D7 Fields' default value is already committed. This allows the admin to set the default format of a field without having to also enter a value into the field if they wish. ...

johnv’s picture

Title: Setting default filter for Page body does not stick » Setting default filter in 'field settings-edit tab' does not stick
dragonwize’s picture

Status: Active » Closed (cannot reproduce)

Read the readme for full instructions.

You have to turn that feature on in the settings for it to take effect.

johnv’s picture

Status: Closed (cannot reproduce) » Active

I've read a setting should exist, but cannot find it.
Source contains a hook_menu for $items['admin/config/content/formats/settings'] , but visiting that page returns an error:
"The requested page "/admin/config/content/formats/settings" could not be found."

dragonwize’s picture

Status: Active » Postponed (maintainer needs more info)

Works for me and from experience in the issue queue for others as well. I would suggest checking that the module is enabled and caches are cleared. You can try disabling and re-enabling the module as well.

johnv’s picture

Status: Postponed (maintainer needs more info) » Closed (works as designed)

Indeed, I had an old copy of dev-version. Sorry to have bothered you..

jesbrown66’s picture

You really have amazing articles and reviews. Many thanks for sharing with us your webpage. I simply want to say I am new to blogging and seriously enjoyed your blog site.


Dublin daily deals