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.

2 errors after upgrading to 2.2

June 23, 2011 5:06pm

Subscribe [3]
  • #1 / Jun 23, 2011 5:06pm

    stevemckinney

    12 posts

    Hello, I’m hoping this turns out to be really simple. As the title says I’m getting 2 errors after updating, followed instructions to the point. I’m seeing the following error when going to the admin page:

    An Error Was Encountered
    Unable to load the requested file: _shared/menu/item_parent.php

    I can view my index.php file, but when I go to my blog which is what EE controls mainly, I get this:

    A PHP Error was encountered

    Severity: Notice

    Message: Undefined property: EE_Loader::$_ci_view_path

    Filename: api/Api_channel_fields.php

    Line Number: 340

    A PHP Error was encountered

    Severity: Warning

    Message: Cannot modify header information - headers already sent by (output started at path/to/system/codeigniter/system/core/Exceptions.php:170)

    Filename: core/Common.php

    Line Number: 405


    Fatal error: ob_start() [ref.outcontrol]: Cannot use output buffering in output buffering display handlers in path/to/system/codeigniter/system/core/Exceptions.php on line 166

    (note I’ve changed the path at the start just for caution). I hope I’ve explained well enough, thanks for your help in advance.

  • #2 / Jun 24, 2011 6:12am

    John Henry Donovan

    12339 posts

    stevemckinney,

    Are you using any add-ons?

    Can you confirm that you have the system/expressionengine/views folder?

    Are you using the default EE control panel theme or Corporate?

  • #3 / Jun 24, 2011 6:23am

    stevemckinney

    12 posts

    I am using add ons I removed them all and reloaded no luck. The views folder is there only has an index.html file that’s obviously wrong as I type this I’m uploading the views stuff. It seems some things have gone missing in my update process. I was using the default cp theme. Uploading the views folder solved it but my blog page is still showing the error.

    Edit: I also get this error when going to create a new entry:

    A PHP Error was encountered
    Severity: Notice
    Message: Undefined index: field_visibility
    Filename: content/publish.php
    Line Number: 71
    closed_eye.png" alt="Delete" width="15" height="15" >
  • #4 / Jun 27, 2011 3:17pm

    Robin Sowell

    13255 posts

    I’m worried something may have gone very wrong with the FTP’ing of the files.  The view folder being effectively empty is a red flag, and checking the api/API_channel_fields.php file, the line throwing the blog error is just some comment code in the current version.  In other words- it should be impossible for that file to throw that error.

    I think the best thing for us to do right now is upload a fresh copy of the files.  Quick question- when you updated, did you replace the files in the system folder, or did you upload the contents to a brand new ‘holding’ folder and then just switch out the folder name, like the ‘Tip’ section in part 2 of the update docs describes?  Uploading to a new folder rather than overwriting can help avoid ftp issues.  That said- the views foldering being effectively empty shouldn’t have happened regardless.  Did you notice anything weird when uploading the latest release?

    In any case- I would upload a fresh copy of the system folder- I’d upload it to as a folder named system_new or something, copy over the config, template and third party files as described in that ‘Tip’ section, and then swap out the current system folder to system_old and the new from system_new to system.

    That SHOULD get rid of any FTP oddness.  If it doesn’t, we’ll want to take a closer look as the errors are very odd.

    Does that make sense and are you comfortable with how to put up a fresh copy of the files?

  • #5 / Jun 27, 2011 3:56pm

    stevemckinney

    12 posts

    I think a lot of files went missing in the process I’ve tried to replace them best I can. I’ve probably missed some, unfortunately I didn’t follow the tip (it’s my first time updating and as I’d began uploading the files I’d just noticed the tip). I checked my backup which I did and the views folder was completely empty. I’m going to give uploading all the files a go again, following the tip.

    Thank you I’ve uploaded the files, it’s worked. Checked the problem areas and none appear to be there, my blog page works fine, lesson learnt.

  • #6 / Jun 27, 2011 4:19pm

    Robin Sowell

    13255 posts

    WOOT!  Your lesson learned was much easier than many of mine have been.  ‘What does ‘Truncate’ do?’  Sigh.

    Glad all is well on your end!  And the next upgrade will be a piece of cake.

    If you run into any more issues, just start a new thread and we’ll make sure you get squared away.

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

ExpressionEngine News!

#eecms, #events, #releases