Thread

I tried to delete a field group (custom channel fields) and got the following errors:

A PHP Error was encountered

Severity: Notice

Message: Undefined index: field_content_type

Filename: fieldtypes/ft.text.php

Line Number: 143
A PHP Error was encountered

Severity: Notice

Message: Undefined index: field_content_type

Filename: fieldtypes/ft.text.php

Line Number: 143
A PHP Error was encountered

Severity: Warning

Message: Cannot modify header information - headers already sent by (output started at /home/netc/public_html/ter/ee/codeigniter/system/core/Exceptions.php:170)

Filename: libraries/Functions.php

Line Number: 749
A PHP Error was encountered

Severity: Warning

Message: Cannot modify header information - headers already sent by (output started at /home/netc/public_html/ter/ee/codeigniter/system/core/Exceptions.php:170)

Filename: libraries/Functions.php

Line Number: 387

Thank you very much,
MISC

Version 2.1.3 Build 20101220

Hi, MISC. Was this the only custom field group? Are there any third party custom fields in that group?

Yes, it was the only one (without third party fields).

misc,

Were the errors appearing on the page directly after the deletion of the field group or on another page?

Was this afresh install or an upgrade from an older version or build?

Can you remember what fields were in it so we can try and replicate?

Hi John

I can replicate it. There were no special fields in it, just text input and text area fields. Two field input fiels were special related the content type: one time “integer”, one time “number”.

But the job was done (the field group as well as the field were deleted).

Kind regards,
MISC

I can replicate it as well. I created a bug report on your behalf.

Thanks for reporting this, hopefully it will be fixed soon.

Any news on this bug? its still doing the same on the beta version…

Hi, Etheya -

Unfortunately, no updates on the bug at this time.  You can always comment on the bug and tick the “subscribe to comments” box so that you receive any comment updates.

I’d keep an eye on it, for right now, it may be best to simply leave the field group until the bug is fixed in a released version.  You can rename the short names of he fields if you need to use those elsewhere.