Default Input not being applied

It would be good to see the selector for formats in the node creation screen.

Are any of the settings being applied?

The general issues to check are:
-- Ensure you are checking with a user that has one of the affect roles. Like if you are testing with your User 1 make sure it has the Admin role.
-- Make sure you are looking at the node body or a CCK text field. BF 6.x does not work with custom created fields by other modules.

I have same problem. Doesnt work on any of my Drupal various instalations.

I've tested on my systems and all is fine.

Beyond what I mentioned above, I can only ask if you have any other format modules installed or custom format code that could be conflicting.

Closing because of no activity.

Another item to check that several people have reported is themes based on Tao or any other themes that make aggressive format theming changes.

For what it's worth, I'm seeing the same issue. It seems to be happening only for the core php filter (just like the screenshots in #1 and #2).

I'm using 6.x-1.2. However, I do have a custom theme and other input filter modules (eg., customfilter), and haven't debugged it to see if something else is causing the problem. I'll try to see if I can isolate the issue.

Would you guys recommend trying 6.x-2.x-dev?

I guess I have the same problem - even though it relates to some other posts here.
Unfortunately only addressed to version 7.x..
So - let me describe what I try to achieve:
There are different text inputs: The main body input and some cck text fields.
The main content must have the input format "full text" which is done with tinyMCE and some other modules that complement its functionality (for e.g. insert and WYSIWYG ImageField).
And a "Teaser Text" - not the classic teaser shortened input - but an editorial text - that will also be shown on the nodes full page. This text input should only have some basic text editing - "simple text" - but also done with tinyMCE. - I have attached a picture to illustrate this (the site's in German; nevertheless I hope it's showing what I mean ).
But - I can not set the default input format for the different inputs.
It's always set back to the nodes default. The user should not be able to choose between the input formats - they have to be set by the admin. Unfortunately I cannot get this to work.
When I set it in the Nodes ContentType section - it simply will not stick.
I can set it all to one type - but this is not working for me.
Is there a work around? Probably someone is working already on a patch for the 7.x branch:
#1275266: Add field level default format with full Better Format options
I hope I could make me understood - as you may have figured out already - English is not my native language.

After researching on this for ages finally I found the the solution...
It has been around for ages - but I could not relate it to my need...
So - after setting up the 6.x-1.2 version of Better Formats - you need to apply a patch - found here:
better_formats-350696.patch
After applying - you need to enable it as explained here:
How to use the patch

I don't this this fixes anything. This module is so needed as various users should not have to think about Input Format (what geek speek)

The issue is that no matter what patch you apply. Or even if you use DEV or try to figure this out for 6 hours once the node is saved this module 100% of the time reverts back to the system Default Input Format.

I am pretty module implementation savy but I can't make this module retain the original used input format. When you create a new node everything works as expected. Which is great as long as you never need to edit it with anything other than the system default Input Format.

I will admit I have lots of other modules (60+) and if I have time tomorrow I might try a fresh install to see if this is a module conflict.

I am using Core 6.24 and WYSIWYG API with TinyMCE for the Editor. I have MCE bridge installed and the WYSIWYG Spellchecker.

I would sure like to make this work but I am stumped.

The 6.x-1.2 version of this module works fine as indicated by the thousands of sites using it. The most likely cause of your issues are from a collision with another module or theme, contrib or custom.

The module only works on node create not node edit and that is as designed.

Well it works fine for me also on Node Create. If you have a site were you don't edit nodes then it is the best thing since sliced bread since it removes all the clutter or lets you rename the clutter. In my case the nodes are repeatedly edited and it reverts to the default input format.

I guess I don't understand why everyone would not want it to work on Edit? I read the note that say it would only work on new but I figured that meant from all nodes created going forward I did not read that to mean that a node that was created after this module was created would also revert to the default input format.

Is there a hack that would allow it to work on Edit? That would be very appreciated.

The reason it does not operate on edit is so that your choice of format is preserved without having to re-select your format every time you edit. So if you choose a different format than the default then that format is preserved. It goes to the very core of what it means to have a "default", default is only for when there is no other value yet chosen hence only at node creation.

What you say makes sense but for me it does not remember the input format I picked it always goes back to the System Default not the user picked default. So here is what I do I default role 1 to be input format A but the system default input format is B. I also default format B to for role 2. I log in as a role 1 user and it does default to Input Format A and I create content and save it. I then edit that same node will as role 1 and every time it comes up in Input Format B instead of Input Format.

The word default I think can get misconstrued in this context so I hope that clears up my issue.

If this is a module conflict do you have some suggestions for modules I might turn off to see if I can get it working. Based on your response I now am back to thinking it does not work as expected on EDIT. It seem clear you are saying that it should retain the format picked by role 1 user regardless of which input format that users picked. In my case I do not want users to be able to pick the format I want specific roles to get specific formats each time. But even when I hide the selection the Role 1 users still sees the system default input format B anytime they edit content that was created using Input Format A.

Thanks for all the quick responses. I really want to get this working so my users dont have to wonder what an input format is.

What you describe is definitely not normal behavior so you have a conflict somewhere. Look for any module or theme that you may be using that does anything else with input formats and start there. Themes like TAO make major changes that some have reported incompatible because the break the internal form format core creates. Look though the BF issue queue, anything that is has been reported incompatible and not fixed is there.

Thanks. I will see if I can nail this conflict down and report on what I do find. I saw one other post that was similar to mine but the patch was already in the version I was using. I will start disabling some modules.

I am using a custom version of Adaptive theme.

Even the way it is it will be better than not using it at all. These features should be core. Most users of real sites do not pick and input format or have once clue what that is and it needs to be supressed. At least I can supress it for the majority of my users who use the system default format, and if I can't figure out the conflict then the site admin will just have to change back to a broader format each time they edit.

I found the culprit. I had installed and older version of "Node and Comments Form Settings" to try and suppress all this unwanted text associated with the "editor". I disabled that module and Better Formats module retains the input format that the user picks or was assigned via the default. I did try a newer version of Node and Comments Form Settings and it works fine with Better Formats. Well, at least the issue I was having was no longer there.

With Better Formats module I don't really need Node and Comments Form Settings module so I uninstalled it. The only thing it was really doing was suppressing the silly Split Summary check box....what the heck is that anyway...LOL

Since I did not want a whole module just to do that I suppressed the Split Summary noise with a little css

.teaser-checkbox .form-item {display:none;}

Thanks for you patience and help. Better Formats is the way to go for setting your Input defaults and suppressing all the unwanted text surrounding the "editor" . A good add would be to turn off the Split Summary check box in the settings where you decided if you want to apply the defaults at the Content Type level.

I can now force each Role to use one Input Format and remove all the unwanted text that surrounds the Editor fields.

Perfect!