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.

Getting PHP errors on custom Publish layout!

August 27, 2010 5:38pm

Subscribe [12]
  • #1 / Aug 27, 2010 5:38pm

    LarryMiller

    11 posts

    This question may be related to a resolved thread.

    All I am trying to do is collapse some fields. I created 69 fields. 38 of the fields collapsed and saved without any issues. I added 60 more fields that I want to collapse as well. They will not collapse without causing PHP errors when I go to publish.

    I tried clearing the cache and the publish.js patch. No luck.

    Is there a limit to the number of fields that are customizable?

    Build:  20100810

    Not an upgrade.

    Thanks

  • #2 / Aug 29, 2010 2:42pm

    Lisa Wess

    20502 posts

    Hi, Larry,

    Can you please post the PHP errors that are receiving now?  What types of custom fields are you making?

  • #3 / Aug 30, 2010 11:07am

    LarryMiller

    11 posts

    I am using text, textarea, and multiple select fields.

    The errors I am receiving are:

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1574

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1577

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1574

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1577

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1574

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1577

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1574

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1577

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1552

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1566

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1574

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1577

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

    A PHP Error was encountered
    Severity: Notice
    Message: Uninitialized string offset: 0
    Filename: cp/content_publish.php
    Line Number: 1544

  • #4 / Aug 30, 2010 12:42pm

    hd 

    156 posts

    Sometimes you can get errors like this if there was an add-on with publish tabs that has been unistalled/removed, or if something has gone funky with the publish layout do to some other add-on mischief.

    When this happens to me I have to do the following:
    Backup my exp_layout_publish MySQL table, and remove the line/s for that particular channel (& for each member group affected). Doing this will reset the layout, and it can be re-done without the errors. This may be worth a shot in your case, and if it doesn’t work, restore the backup of that table.

    P.S. you wouldn’t have to do it this way if the “Remove Layout” button works for you, but I’d still suggest backing up the table.

  • #5 / Aug 31, 2010 3:42am

    John Henry Donovan

    12339 posts

    LarryMiller,

    Which patch in particular are you referring to?
    Are you using Publish Layouts?
    If so can you try removing it via the button and refreshing the page please as HD suggests. Don’t do anything to the database at this stage please.

  • #6 / Sep 01, 2010 5:41pm

    LarryMiller

    11 posts

    Derek Jones provided the patch file. http://ellislab.com/forums/viewthread/163520/

    I can remove the layout (via the button) and the PHP errors go away however; I back to a long list of fields I would like to collapse.

    I also followed HD’s advice concerning add-ons and removed the Forums module just to make sure that wasn’t the problem. I am still creating the site so forums are not needed yet. Removing the forums did not change anything.

  • #7 / Sep 02, 2010 3:14am

    John Henry Donovan

    12339 posts

    LarryMiller,

    I can remove the layout (via the button) and the PHP errors go away however; I back to a long list of fields I would like to collapse.

    To confirm. Have you tried to save the layout again after this and errors appear again?

    I have tried to recreate a similar set-up to yourself but have no errors.

    Have you split the fields between tabs or are they all under one tab?

     

    How much PHP memory do you have?

    Tools -> Utilities -> PHP Info

    Look for memory_limit

     

    Do you have any add-ons installed?

     

    Note that you can also change the Show this field by default? setting in each individual field to collapse them

  • #8 / Sep 07, 2010 3:35pm

    LarryMiller

    11 posts

    LarryMiller,

    I can remove the layout (via the button) and the PHP errors go away however; I back to a long list of fields I would like to collapse.

    To confirm. Have you tried to save the layout again after this and errors appear again?

    I have tried to recreate a similar set-up to yourself but have no errors.

    Have you split the fields between tabs or are they all under one tab?

     

    How much PHP memory do you have?

    Tools -> Utilities -> PHP Info

    Look for memory_limit

     

    Do you have any add-ons installed?

     

    Note that you can also change the Show this field by default? setting in each individual field to collapse them


    Yes, I have tried to change the layout multiple times and the errors appeared again. When I remove the layout (via button) they go away.

    All the fields are under one tab.

    There is no memory_limit on the PHP info page. Zend Memory Manager is enabled so nothing else about allocated memory is available.

    I have no add-ins installed.

  • #9 / Sep 08, 2010 2:32am

    John Henry Donovan

    12339 posts

    LarryMiller,

    38 of the fields collapsed and saved without any issues.

    If you remove the layout you have and just add 39 fields and save layout does this trigger the errors?
    What is the maximum you can add here before it happens

    Can you check with your host and see what the memory limit is please?

  • #10 / Sep 08, 2010 4:01pm

    LarryMiller

    11 posts

    Yes, I can collapse number 39 and it will produce the errors. Also, I can skip 39 and collapse field number 50 and the errors return.

    The memory_limit is 64M

    I was able to collapse some fields by editing each custom field without generating the errors.

    Very odd.

  • #11 / Sep 09, 2010 2:38am

    John Henry Donovan

    12339 posts

    Please check your email

  • #12 / Sep 20, 2010 10:35am

    stubear

    114 posts

    What was the resolution to this issue?  I’m having the exact same problem, however, mine is with a much simpler publish layout.  I’m just trying to get rid of useless tabs like pings and pages.

  • #13 / Sep 20, 2010 1:34pm

    LarryMiller

    11 posts

    I haven’t had time to investigate further.

    I will revisit this in a couple of weeks and set up an account for support.

  • #14 / Sep 20, 2010 5:48pm

    Wolfram

    115 posts

    Same php errors here on latest built. Just trying to remove the Ping Tab is causing the errors. Is there another way of “blocking” the Ping Tab? I have to launch two sites soon and instruct clients so a fast fix would be appreciated very much.

  • #15 / Sep 21, 2010 4:10am

    John Henry Donovan

    12339 posts

    stubear & Wolfram,

    What versions and builds of EE are you using?
    Are you using any third-party add-ons?
    Are you sites fresh installs or an upgrade from a previous version?
    If an upgrade did you update your themes folder in the process

    Did you have the same number of fields? What is your individual set-up?
    What were your PHP errors if different?

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

ExpressionEngine News!

#eecms, #events, #releases