Oh, I want to clarify: the PHP Error messaging doesn’t go away, but at least in my client’s case, they are able to log in using their masked admin address once I allow access to Site1’s control panel.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
June 28, 2011 4:00pm
Subscribe [9]#16 / Jul 07, 2011 10:59pm
Oh, I want to clarify: the PHP Error messaging doesn’t go away, but at least in my client’s case, they are able to log in using their masked admin address once I allow access to Site1’s control panel.
#17 / Jul 08, 2011 2:25pm
Unfortunately, this thread hasn’t caught the attention of the right folks at the Lab yet. Sue’s doing her part here, but this type of issue is sitting too long in the queue.
I went ahead and made a bug report to see if that helps get this one resolved.
This is an issue that deals with site security and people’s access to their own site, and my clients will have been locked out of their own sites for 2 weeks, even if we get a working patch by Monday of next week.
Hopefully the bug report will draw someones attention.
#18 / Jul 08, 2011 5:17pm
Just adding an update of my own. Still having the issue.
I’ve noticed that if you select one of the radio boxes for the fields that just give a number (per my and Kurt’s screenshot) you’ll get an error that it’s an unknown field in the database (understandably).
Additionally, I had been trying to get masked CP access working, but was unable to via all the traditional methods (sounds like the same issue Kurt is having). The only thing that worked (for me) was the same procedure as lealea mentioned. As they both mentioned, even with that workaround, the PHP errors sill persist and, understandably, is not an ideal workaround.
Thanks.
#19 / Jul 11, 2011 6:24am
Kurt,
Unfortunately, this thread hasn’t caught the attention of the right folks at the Lab yet. Sue’s doing her part here, but this type of issue is sitting too long in the queue.
I went ahead and made a bug report to see if that helps get this one resolved.
The PHP errors is a bug that I reported previously. The devs have already confirmed it as a bug so are currently working on it.
#20 / Jul 11, 2011 3:34pm
Hi All,
So the issue that Kragit first posted has been fixed. Greg and Pascal got it taken care of late Friday and today, and Greg has a patch ready for anyone that needs it. It will be included in the next release, but since the scope of this bug doesn’t reach very many EE users, it won’t be released as an emergency hotfix. (That’s not to minimize just how much of a show-stopper the bug is for those that it does affect. Clearly it is!) If this issue is affecting you, please get the patch from Greg and apply it. We’ll keep this thread open for a little bit to make sure this issue is resolved.
#21 / Jul 12, 2011 2:52am
The PHP Errors are gone after the patch, but none of the member-groups or members created post version update can log into the CP yet.
See bug report for more details: https://support.ellislab.com/bugs/detail/16143/
#22 / Jul 12, 2011 5:43pm
Hi Kurt,
I’m going to have the devs take a first-hand look at this on your servers. Be on the lookout for an email from me.
#23 / Jul 17, 2011 2:22pm
Hi Kurt,
I think this is the one that you have taken over to the beta of private support, can you confirm? If so, then so long as everyone else in this thread is all set, then it’s time to close ‘er out.
Thanks!
#24 / Jul 20, 2011 11:51am
Since Kurt is now working on this issue with us in Private Support and everyone else seems to be taken care of, I’m going to close this thread up. When we find a resolution, we’ll post back here for all to see!
In the meantime, if you have anyone else has anything additional to add, please let us know!