Thread

Hi there,
I am trying to upgrade to 2.3 and have followed all the instructions including updating the admin.php and index.php system file path. However when I try to point my browser to http://www.mydomian/admin.php The page you requested was not found.

Worth saying that my system is above root.

Not really sure why this is happening… can you help.

Edd

A bit more info here… If I update the admin.php file so the system path is incorrect this is recognised, and I receive the appropriate message… therefore I assume that the admin.php file is being recognised when I direct my browser to it…

Can anyone help, really want to get this sorted in the next 24 hours.

Cheers,
Edd

Okay, really need some help here now. Please.

Downloaded 2.3.1 and tried to upgrade to this… had the same issue. So I decided to roll back to 2.2.2 which was working fine and now wishing I never tried to upgrade in the first place.

So the rollback has left me with a site that does not render correctly, looks like the CSS are not loading. I have logged back into the CP and all is there thank god. But still left with this issue. To be honest upgrading to 2.2.2 was bit of a pain when I did this a few months ago and now this is making me feel like I don’t want this anymore.

Please help. Or at least reply.

Edd

Okay managed to restore to my backup now. Used a fresh version of the index.php file from my 2.2.2 download and updated the system path accordingly.

However. I am still keen to upgrade to 2.3.1. Can you explain why the admin.php file was not being recognised. Before I attempt this…

Some help would be much appreciated. I know I am sounding desperate here, but basically I am.

Cheers,
Edd

Hi Edd,

are you using a full system path in your admin.php and index.php in your root to point at your system folder below your root?

Hi John,
Thanks for getting back to me.

‘../renamedsystem’

Edd

Hi John,
Any more advice?
The main reason that I want to upgrade to 2.3.1 is because the HTTP access enabled pages with 2.2.2 is not recognising usernames and password details, even superadmin…. I am hoping that this is just a 2.2.2 issue and will be resolved by the upgrade.

Cheers,
Edd

Some more info. I am running MSM. But am experiencing the login issue across all sites?

Cheers,
Edd

Hi, EWDC -

Is your site running PHP as CGI by any chance?  If so, HTTP auth won’t work.

We can tackle the update issue separately as it is recommended (and a security update) but I just want to get to the bottom of the primary issue you’re having.

Hi Lisa,
Thanks for getting back to me. A little out of my knowledge level I am afraid… Server API is CGI/CGIfast is this what you need?
Was working fine before I upgraded to 2.2.2 a while back…

Cheers,
Edd

Hi Ed,

Regarding Lisa’s question, could you ask your host if they’re running PHP as CGI? They’ll know the answer to that. If yes, then like Lisa mentioned, HTTP Auth is incompatible with PHP running as CGI. I suspect it’s not, though, since you mentioned that HTTP Auth was working fine before EE 2.2.2.

Regarding the problems you’re having upgrading, could you go into more detail about how your files and directories are structured for your EE installation? Then go into more detail about how you went about upgrading your system. Are you skipping or altering any steps in the User Guide’s article on upgrading?

EE 2.2.2 included admin.php in the web root, so was accessing your CP through http://example.com/admin.php working correctly then? If so, are you using the same system folder path in the new admin.php file as you were in the old one?

Hi Kevin,
Okay so turns out that I am running PHP as CGI, have the option to switch to FCGId i? Will this resolve the issue without causing others? Pretty certain that it worked before, but I have been creating .htaccess files as a workaround so perhaps this what I am recalling.

I think the main issues that I am experiencing are all to do with login related stuff. All front end… (logging into the CP works fine – running one admin.php file for ‘site 1’ as I want one point of access to manage all the sites… the admin file has been renamed, which is something I think is the issue with my latest upgrade attempt as I restored the old config.php file which is no doubt referring to this renamed admin.php file as opposed the latest version provided with the upgrade…)

I am planning to have another crack at upgrading over the weekend so will let you know how it goes and detail the steps taken… I have been following the guidelines provided and have done upgrades a few times before.

Here is a short list

1. HTTP access not working (mentioned above)
2. Super Admins not being recognised for viewing off line sites other than ‘site 1’ I am running 5 sites at the moment and it is growing at about 1 site month.
3. Once logged in at the front end, login status not recognised when moving from one site to another even though the user is either a super admin or of a member group that has access to both.

Hope this helps.

Edd

Kevin,
Can you advise on the first question above…

... have the option to switch to FCGId i? Will this resolve the issue without causing others?

Regards,
Edd

Hi Edd,

I’m not a server admin, so I would recommend working with your host to determine the best setup for your account. From what I understand, however, running PHP as CGI or FastCGI either one is incompatible with HTTP Auth for access to particular templates within EE.

Now hang on; this next part can get confusing…

Numbers 2 and 3 in your list behave that way for the similar reasons: unless you enable Multi Site Login on your MSM sites’ front-end login, you will only be logged-in to the site for which you submit the login form. For example, if you have a login form on site 1, that’s the site you’ll be logged-in to. Note that Multi Site Login is only available for logins on the front-end.

Now with that in mind, does it make sense why EE behaves like it does with question 3?

Further, even if you enable Multi Site Login, since it only applies to login forms on the front-end, if you login to the CP, you will only be logged-in to the front-end and the backend of the site that hosts the admin.php file for the CP. It won’t log you into other sites on your MSM installation. (Even though you can edit them through the CP, you technically aren’t logged into that particular site.) This is even Super Admins aren’t able to see your other MSM sites when they’re offline. In order to see site 2, they would need to be logged-in to site 2’s CP (through an admin.php file at site 2). I understand that’s not how you wanted to set your site up, and that’s totally fine.

While we’re aware that this is functionality that our users would love to have—and it’s indeed something we would like to provide—I’m not able to give any details for when that sort of a thing might be a reality.

Does that help clear things up for the login behavior confusion?

HI Kevin,
Apologies for the delayed response, had to leave things as they were for a while focus on delivery. I am still keen to sort all this out.
really useful and detailed reply so thank you for that.

The main one left to sort is the whole HTTP access thing. I am keen to get to a point where I can utilise this across various sites using the EE functionality. This is how I would like to use it.

<a >

I am not sure the issue can be a server side thing as I am running all sites of the same server and have discovered that site 1, site 2 and site 3 all work with HTTP access set up, but site 4, site 5 and site 6 do not… therefore I am wondering if it could be something to do with additional sites added to MSM?

Hope this makes sense.

Regards,
Edd