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.

EE 2.1.2 PHP Errors in Publish page "Undefined index"

December 15, 2010 4:25pm

Subscribe [24]
  • #16 / Dec 19, 2010 6:01pm

    PhilBrienesse

    187 posts

    Similar issue and wouldn’t let me save layouts till i reset them all.  Not an issue on this site but I have another one that uses custom layouts extensively.  I have already had to reset them before because of other issues.

    Much like Kurt i can’t see resetting and redoing layouts on every site after an upgrade. Also often a problem after installing a module which creates tabs on the publish page such as seoLite.

  • #17 / Dec 20, 2010 1:09am

    Blair L

    110 posts

    Same here.  Would be helpful if this one went away.

  • #18 / Dec 20, 2010 8:39am

    Me too. No Forums tab, only Pages, seems to occur with all five channels, all of which have their own publish layouts.

  • #19 / Dec 20, 2010 9:28am

    carvingCode

    380 posts

    Pages. No Forum.  Same problem.

  • #20 / Dec 20, 2010 5:32pm

    ROCKET MEDIA

    153 posts

    Same problem with all of my custom layout channels. (2.1.2)

  • #21 / Dec 21, 2010 10:24am

    Sue Crocker

    26054 posts

    It appears the issues are fixed with 2.1.3 - Kurt, did you give it a try yet?

  • #22 / Dec 22, 2010 7:37am

    joemo

    26 posts

    I have just had this when installing latest update 2.1.3

    All my custom publish menus have had to be reset.

    Not happy.
    The Publish windows seem very flakey , my experience with them so far has not been good.
    I now have to redo a bunch of channels again.

  • #23 / Dec 22, 2010 1:42pm

    PhilBrienesse

    187 posts

    Just upgraded from 2.1.2 to 2.1.3 and didn’t have to reset my custom publish layouts this time.  This site makes minimal use of them and i did reset them when i went from 2.1.1 to 2.1.2 I am trying it on a much larger site that makes much more extensive use of custom publish layouts tonight.  I will let you know how that goes.

  • #24 / Dec 23, 2010 12:15am

    John Henry Donovan

    12339 posts

    joemo,

    What version did you update from?


    PhilBrienesse,

    I am trying it on a much larger site that makes much more extensive use of custom publish layouts tonight.  I will let you know how that goes.

    Excellent. Thanks for letting us know

  • #25 / Dec 23, 2010 2:01am

    davidrussell

    102 posts

    I can confirm this problem exists when upgrading from 2.1.1 to 2.1.3. I believe I have seen this once before, coming out of the beta product to final release. Didn’t expect to see it again. :( Can someone tell me if there is any other way to do this without destroying and re-building custom publish layouts?

  • #26 / Dec 23, 2010 3:34pm

    PhilBrienesse

    187 posts

    Upgraded the site i mentioned above.  No issues.  Did not need to reset custom publish layouts and can change them around and save them.

    Does not fix the other bug where if you alter a custom field it reappears on all layouts. There is already a bug submitted in the tracker for this though.

    Also like someone else mentioned, even though the layout is displaying correctly all of the eye icons are open for hidden fields.

  • #27 / Dec 23, 2010 3:35pm

    PhilBrienesse

    187 posts

    Should mention this upgrade was from 2.1.1 to 2.1.3 so I am not sure what is different from the poster above me who did have to reset all his layouts

  • #28 / Dec 23, 2010 4:01pm

    joemo

    26 posts

    Hi I updated from 2.1.0 build 20100810.

  • #29 / Dec 27, 2010 1:24pm

    Brandon Jones

    5500 posts

    Thank you, PhilBrienesse. I will look into the eye icons being incorrect and try to reproduce. Glad it is working otherwise for you.

    joemo,

    Is the Discussion Forum module installed by any chance? Can you also confirm that you aren’t seeing errors after resetting the layouts?

  • #30 / Mar 10, 2011 2:39am

    Kaepora

    8 posts

    Having the same issue. This is absolutely ridiculous - my experience with EE so far has been flaky code and a support staff that actually expects you to fix the issue by manually resetting your website’s entire custom fields - ignoring the fact that your website might actually be huge and employ quite an amount of fields that need resetting. You’ve had the opportunity to roll out a new version of EE to fix this bug for months, but still haven’t - no wonder everyone’s leaving you for Wordpress.

    EE is the scraped bottom of the CMS barrel, and the support staff are nothing short of haggling for cash.

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

ExpressionEngine News!

#eecms, #events, #releases