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.

"Your system folder path does not appear to be set correctly. Please open the following file and correct this"

September 20, 2011 9:26am

Subscribe [3]
  • #1 / Sep 20, 2011 9:26am

    ChiefAlchemist

    913 posts

    This was a 2 phase upgrade to 2.x.

    Phase 1 was install 1.x but also move EE out a sub-folder into the root. That seemed to go fine. But now that I’m trying to install 2.x I’m getting “Your system folder path does not appear to be set correctly. Please open the following file and correct this”

    I’ve tried /system/

    I’ve also tried /home/myaccnt/public_html/system/


    Each gives me a slight different error. It’s also as if the is_dir() in the root index.php is returning false when there is in fact a /system/ dir.

    Anybody?

    I’m also wondering if in the Phase 1 1.x install if I didn’t miss a spot or two where EE was/is looking for itself in a sub-folder instead of the root. Maybe I need to phpMyAdmin some of the settings in some of the tables? But…which tables?

    Please help. This has been going on since Sunday and I’m time sucked at least 5+ hours on getting this to work. Worst of all, the client’s site is down while this is getting resolved.

  • #2 / Sep 20, 2011 7:31pm

    Dan Decker

    7338 posts

    ChiefAlchemist,

    I’m sorry you are experiencing this, let’s see if we can get it sorted out. Is the error complaining about path.php? And you have EE 1 installed in your web-root is that correct? Open path.php and set $system_path=”./system/” tale note of the leading period. Let us know if that sets it straight.

    Cheers,

  • #3 / Sep 21, 2011 1:14pm

    ChiefAlchemist

    913 posts

    To make sure we’re on the same page, let me backup a bit.

    The original install was on a PHP 4.x box with EE in a subfolder (root/cms/{ee}). In order to use Wygwam, the install needed to be moved to a PHP 5.x box and upgraded to EE 2.x.

    Step 1 was get EE 1.x set up and out into the root (not the subfolder as it was.) That seemed to go well. I did the install, restored the DB, etc and things we working just fine. (Note: But maybe I missed removing a /cms/ somewhere in the CP when I was doing that clean up?)

    So I moved on to Step 2…Upgrade to 2.x. I ran the wizard and it said everything went fine. But then I clicked on the Here’s your CP and Here’s your site links it was immediately obvious things did not go as planned.

    btw, I also ran the ee_server_wizard and the environment passed.

    That’s where I’m now in limbo.

    I’ve tried changing the sys_path in the main (root) index.php and in path.php. I also tried in system/index.php. I have tried /system/ and since it’s a c-panel environment I’ve tried the absolute path of /home/mysite/public_html/system/

    I either get:

    “Your system folder path does not appear to be set correctly. Please open the following file and correct this.”

    Or I get:

    “Your config file does not appear to be formatted correctly.”

    I’d gladly PM you any credential you might need. Something is just slightly out of whack. And as hard as I’m trying to change just one parameter at a time I’m sensing that it’s something so obvious I might never see it.

    Thanks in advance for your help. I would LOVE to get this revolved already. This all start Sunday afternoon.

  • #4 / Sep 22, 2011 12:47am

    Dan Decker

    7338 posts

    CheifAlchemist,

    Indeed, we should go in and have a look at this. It seems as though you are in upgrade limbo. Please be looking for an email from me.

    Cheers,

  • #5 / Sep 23, 2011 7:03pm

    Kevin Smith

    4784 posts

    Hi Mark,

    The message your getting that says “Your config file does not appear to be formatted correctly” is spot on. Your config.php isn’t formatted correctly. While the version number reflects 2.2.2, it’s formatted like a 1.x config file.

    Was there anything about the upgrade process that failed for you? Anything you had to skip? Anything out of the ordinary? From the looks of it, the upgrade didn’t complete, so you are correct that your system is somewhere in limbo.

    Dan will be back on tomorrow, so he’ll be able to help you from there. In the meantime, is there any way you can try the upgrade again and let us know if anything fails in the process? Before doing so, please read up on troubleshooting upgrade errors, especially the portion on wiping your database.

    Thanks for your patience on this. We’ll do our best to get you back up to speed in no time!

  • #6 / Sep 23, 2011 8:04pm

    ChiefAlchemist

    913 posts

    Hey Kevin -

    Well the config starts blank correct? And then I thought there was a step where in the upgrade instructions where it said “Copy your 1.x config to the 2.x config.” Correct? Or did I misread? If I did that, then where/when is the config supposed to change? Can’t I just slap in a properly formatted config and then adjust that to my install?

    Anyway, from there I ran the update wizard (?) and got the success 2.x screen with the links to the site and the CP. Clicked on those and my heart broke. From there I tried to follow the messages, etc. but still nothing.

    Either later this evening or early tomorrow (I’m East Coast) I’ll follow that link and will try again. That being said, I did DROP the whole DB once already figuring something might not have gone right. That didn’t help. I also re-FTP’ed the whole 2.x thinking maybe there was a corrupted php file. That didn’t help either, obviously :(

    What else in the guts of the upgrade might do this? Maybe there’s something I need to massage in the DB tables prior to going from 1.x to 2.x?

    Please clarify on the copy the config step before I try again, else this is just going to be a repeat of before. I don’t need any more grey hairs :(

  • #7 / Sep 24, 2011 12:15am

    ChiefAlchemist

    913 posts

    Ok…I’m back to 1.x.

    I just noticed in the CP that this site is on 1.5.1. Yeah, that old. I don’t recall seeing anything on this but maybe this is too old to go to 2.2.2? At least in one shot? Could that be why I was getting the config.php message?

    I have to be honest, at this I’m fearful to going to 2.x on my own. Is there anyway ya all could give it a pop? Or at spoon feed on what to do next?

    This upgrade has sucked up more hours than the enhancements I did :( But considering the client was site-less for a week, at this point I’ll do just about anything to get this completed. Well, for the moment some of the pressure is off, but we still need to get to 2.x. Soon?

    Either the light I’m seeing is the end of the tunnel or the gates of heaven. If you know what I mean.


  • #8 / Sep 24, 2011 5:00pm

    Dan Decker

    7338 posts

    ChiefAlchemist,

    While it is not *required*, I would suggest updating to 1.7.1, making sure everything goes smoothly, and then upgrade to 2.2.2

    Cheers,

  • #9 / Sep 24, 2011 5:55pm

    ChiefAlchemist

    913 posts

    Thanks Dan

    Are there instruction anywhere for from 1.5.1 to 1.7x? Or is mostly just a matter if FTPing the newer files into place?

    Also, I have to be honest, my level of confidence with this whole process is about nil at this point. For example, this “while not required…” is confusing if not annoying. I honestly feel like I’ve been down this rabbit hole before and don’t want to get sucked down it again only to be left waiting for 24 hours to get some help and then once again notching back to 1.x from the botch 2.x

    Let me just say that it’s been a week and I don’t feel any closer to a successful. Should an upgrade take a week?

    I’d like to add that Einstein once said, “Insanity, doing the same thing over and over and expecting different results.” I feel like what I’m about to do is insane. While it’s not exactly what I’ve done before, you’re also not exactly saying it’s necessary. I feel like I’ve taken enough pop shots and this is just another one. I don’t see this is being a wise decision on anyone’s part. Can’t EL just look at it and sort it out?

    See?

  • #10 / Sep 24, 2011 6:17pm

    Dan Decker

    7338 posts

    ChiefAlchemist,

    I apologize for contributing to your frustration. That was not my intent. Updating to 1.7.1 is not required, but I was recommending it as a best-practice. I’m sorry if this caused any confusion. The update instructions you inquired about can be found here.

    I’m afraid that performing updates for users is beyond the scope of support and not a liability that EllisLab can take on. No one knows your site better than you. Of course, we will continue to work with you through this process and do everything we can to help.

    Cheers,

  • #11 / Sep 25, 2011 9:25am

    ChiefAlchemist

    913 posts

    Good morning Dan

    I certainly understand:

    “I’m afraid that performing updates for users is beyond the scope of support and not a liability that EllisLab can take on.”

    But the alternative of me wasting away more hours and breaking it *yet again* just so I can say, “I need help,” just doesn’t make any sense at all to me. What am I missing here?

    Ultimately, the client approved a moved to EE 2.x (on my recommendation). They were without a site for a week and 2.x has yet to happen. Pardon me for repeating myself but to go down a road we’ve already been down, best I can tell at this time, qualifies as insane. I don’t like being in that position.

    btw, you can add disappointed right after frustrated on the list of attributes I currently associate with EE. I feel like I’m using W*rdPress (i.e., no real support and dodgy documentation.) I feel like I’m getting responses but not resolution.

    None the less, wish me luck. What’s around couple hours sucked out of my life at this point :(

  • #12 / Sep 25, 2011 2:50pm

    ChiefAlchemist

    913 posts

    Hello again Dan

    1) I’ve done some looking around and it’s not clear to me how to get a copy of 1.7.x in order to pre-upgrade on my way to 2.x.

    2) I’m upgrading the site of a non-profit. In the age of a EE 1.x, I believe such licenses were free. Now that 2.x is ~ $150 I just kinda presumed there was no real upgrade path in terms of price.

    Long story short,  when this all started I purchased a non-commercial for the full price but My Downloads is now leading me to believe there’s a less expensive ($50.00 + $39.95 Renewal) way of doing so.

    Pardon me for being a pain and/or not seeing the obvious but I’m so paranoid at this point I’m just trying to stay focused. Maybe too focused? Call me stress but the more I run around in circles, the less I want to do so. Ya dig?

    Thanks -

    Mark

     

  • #13 / Sep 26, 2011 6:03pm

    Dan Decker

    7338 posts

    Hi Mark,

    ExpressionEngine used to have a free version called Core. I’m going to do a login and get a sense of what version you are on. If you are on Core, we may need to work out a way to move forward.

    Cheers,

  • #14 / Sep 26, 2011 6:32pm

    ChiefAlchemist

    913 posts

    I’m pretty sure it’s not on Core. I’m not sure because I was hired to do the EE dev for the outfit who designed the site for the end client.

    I was just trying to point out that maybe they’ve now overpaid for the 2.x upgrade. That’s really minor at this point. Just more dust in my air, see?

    The CP said 1.5.1. but if I need to do a 1.7.x prior to 2.x, then how do I get a copy of 1.7.x?

    I’ll be honest. I’m all but begging at this point. I just want to get this 2.x upgrade done, finish the enhancements and invoice it. I’ve got other work that’s waiting for my attention but without closure I don’t want to open up any new EE cans of worms.

    Thanks

  • #15 / Sep 28, 2011 3:02pm

    ChiefAlchemist

    913 posts

    Anything?

    Or are you waiting on me? I didn’t get the impression that was the case but maybe I missed something. My “vision” is so out of whack at this point that all I can think about is how to get closure on this one.

    Let me know what I need to do to get this wrapped up and 2.x’ed.

    Thanks -
    Mark

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

ExpressionEngine News!

#eecms, #events, #releases