ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

PHP errors for members when editing an entry

October 20, 2011 6:23am

Subscribe [5]
  • #1 / Oct 20, 2011 6:23am

    Seashore Media

    7 posts

    When a member wants to edit an entry on the EE control panel on a site we recently constructed, he gets these warnings (however, he is able to make adjustments):

    1.
    A PHP Error was encountered
    Severity: Notice
    Message: Undefined variable: assigned_channels
    Filename: cp/content_publish.php
    Line Number: 2122
    2.
    A PHP Error was encountered
    Severity: Warning
    Message: in_array() [function.in-array]: Wrong datatype for second argument
    Filename: cp/content_publish.php
    Line Number: 2122
    3.
    A PHP Error was encountered
    Severity: Notice
    Message: Undefined variable: assigned_channels
    Filename: cp/content_publish.php
    Line Number: 2122
    4.
    A PHP Error was encountered
    Severity: Warning
    Message: in_array() [function.in-array]: Wrong datatype for second argument
    Filename: cp/content_publish.php
    Line Number: 2122
    5.
    A PHP Error was encountered
    Severity: Warning
    Message: Cannot modify header information - headers already sent by (output started at /home/mevenr93/public_html/venfot/codeigniter/system/core/Exceptions.php:170)
    Filename: core/Common.php
    Line Number: 409

    Oddly, we copied this site from another EE site we constructed a few months earlier, but there are no PHP warnings there.

    What have I done wrong, or did I forget to do?

  • #2 / Oct 21, 2011 9:10am

    Sue Crocker

    26054 posts

    Hi, Seashore Media.

    Which version of EE are you experiencing this with? You can see your version info at the bottom of any control panel page.

    We’ve seen this happen with earlier versions.

  • #3 / Oct 21, 2011 9:33am

    Seashore Media

    7 posts

    We use EE version 2.1.3.

    We run this site on PHP 5.2.4.

    The site we used to copy this site from, and that does not show PHP warnings, runs on an older PHP version: 5.1.6.

  • #4 / Oct 24, 2011 10:16pm

    Dan Decker

    7338 posts

    Seashore Media,

    First, I must strongly recommend that you update the latest version of ExpressionEngine (2.3.1) as there have been numerous feature enhancements, bug fixes and security enhancements since 2.1.3

    If that isn’t an option for you, are you using any custom publish layouts for this channel? Is this happening on one channel or all channels?

    Cheers,

  • #5 / Oct 25, 2011 5:58am

    Seashore Media

    7 posts

    Hello Dan,

    We will update, but since this site and license is just a few months old, I never expected to update it so soon.

    To answer your question: we experience this on all channels.

  • #6 / Oct 25, 2011 10:53pm

    Dan Decker

    7338 posts

    Hi Seashore Media,

    We try to release a new version of ExpressionEngine on a 12 - 14 week cycle. In general, we will always encourage updating to latest version as is feasible for you, but 2.1.3 in particular was a rather buggy release which is why I went with “strongly recommend” 😉 So given this schedule, you can expect the next release to be sometime in January or thereabouts.

    With that out of the way, can you tell us if you are using any third-party add-ons or field types? Are you using any Publish layouts?

    Cheers,

  • #7 / Nov 07, 2011 3:45am

    Jo

    5 posts

    Hi,

    The same php error is displaying my client when he logged into the CP. When I logged in as superadmin, I don’t see the error.

    EE v 2.2.2

    This is only happening when he adds or edits an entry for 1 particular channel.

    The modules/plugins I have are:
    Simple registration, taxonomy, better pages, protected links, wyvern, custom system messages, playa

    Help please.

  • #8 / Nov 08, 2011 6:56pm

    Robin Sowell

    13255 posts

    It is pretty strongly advised to go ahead and update to 2.3.1.  That said- take a look at this bug report- I believe the fix should take care of the issue for you.  And while it should have been squashed for 2.3.1, seems I need to take a closer look, as this report suggests otherwise.

    I’ll poke that mystery.  You folks let me know if the fix in the report gets you squared away for now.  And… sounds like it may need to be carried over to 2.3.1 when you upgrade.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases