By ckidow on

Drupal 5.7 - OG 6.0rc4 - rc6

I added two new text-fields to the node-type "groups" and createt two groups. After a few days I deleted these two fields. Now when I want to create a new group, the error comes up: "You must use the default input format when authoring a group node." after pushing the "submit" button.

Don't know exactly what I did wrong. Already deinstalled og and droped the directory and reinstalled but always the same error. Created new og-node-type with different name: "langauge-groups" instead of "groups" but no effect. I Think it's not a "og"-problem. Already checked the "input format"-settings and saved but also no effect.

Anybody with the same problem and a solution?

greetings

CKIDOW

⋅ Categories: Drupal 5.x

Comments

Mike Wacker’s picture

Mike Wacker commented

I'm not directly familiar with the module, but I can tell you what is happening.

Only certain users have permission to use certain input formats. Thus, within a group, some users may able to use a certain input format, and others may not. However, if all members of a group can edit a group node, then they all must have permission to use the input format the node has. The only input format all users can use is the one which has been specified as the default.

If you allowed a different input format to be used, then any users who did not have permission to use that input format could not edit that particular node. Thus, whenever you create a group node, the input format selected under the "Input Format" fieldset must be your default input format. This ensure that everyone in the group can edit the node.

Mike Wacker
Assistant Web Editor, The Cornell Daily Sun
mwacker@cornellsun.com

droople’s picture

droople commented

I am having the same problem

I have installed a lot og groups before and never had this problem.

It must be an OG issue

let me check the OG isssue page

ckidow’s picture

ckidow
he/his
Primary language German
commented

The only input formats I use are the three default which come with drupal core: Filtered HTML, PHP Code and Full HTML. I didn't added or deleted any Input formats. But I also can't find any access controll for input formats. :(

MfG

CKIDOW

droople’s picture

droople commented

I have filed an issue on the project page.

Keep an eye on that.

cheers

ckidow’s picture

ckidow
he/his
Primary language German
commented

Thx a lot... *thumbsup*

'edit: I set up a new Drupal 5.7 with OG 6-rc6 and a minimum of modules but there is the same error when creating a group' :(

MfG

CKIDOW

najibx’s picture

najibx commented

I experience the same error when trying to update group information.
I do have CCK field attached to the group field.

never had this problem earlier ...

ckidow’s picture

ckidow
he/his
Primary language German
commented

Problem is fixed and new 'Organic Group' Version is released.

Big thanks to Mr. Weitzman

MfG

CKIDOW

najibx’s picture

najibx commented

Thank you ...how can I live without all of you ...

jimezam’s picture

jimezam commented

I still have the same problem. I am using Drupal 5.7 with OG 5.x-7.2 and I don't use CCK.

If I try to change the input format from a OG page I always get this error: "You must use the default input format when authoring a group".

What could I do ?

Thanks,

jimezam.

vinoth.3v’s picture

vinoth.3v commented

I am also having the same Issue in OG latest og-6.x-1.0-rc3.tar

வினோத்

Vinoth - வினோத்

mydllurth’s picture

mydllurth commented

My difficulties started with the News and Wyrld Report security upgrade from Drupal 5.8

Everything was working last night, prior to the upgrade. My groups' home pages require PHP code for features which are dependent on user role and other characteristics of the group purpose. I wanted to modify the label on one button, and was denied while uid 1 "must use the default input format when authoring a group node." Other content types quietly modify with not default input formats.

The failure can be mitigated by temporarily changing the site default for input format to an appropriate PHP filter, but I find that unacceptable after malicious server-side script discoveries in previously utilized feeds to our news site. Placing the news site off-line while editing group home pages reduces risk with insecure content but inconveniences our readers while I administrate changes at a blistering 5 wpm rate.

That said:
I can only suppose changes in the Drupal 5.9 core from our previous (5.8) core, addressed the bugs/features that our site exploited. The stated problem is a feature; carefully read #258913: Problem with input filters in group nodes and the solution becomes apparent. In my case, creating a new field for my features in my groups' home pages with a user-selected filter type made life much more pleasant.