forum.excito.org

Gordon wrote:You might want to try enabling the "register globals" setting in php.ini and see if that fixes your issue.

For any sane php application that doesn't make any difference. You can see what moves between your browser and webserver with something like firebug (net tab).

Check to where and what your browser sends the login information to.

Is it the correct script? Also you may have to check php and apache logs. (access and error)

Does this say anything?
[error] [client 192.168.xxxxx] PHP Warning: Unknown: POST Content-Length of 138 bytes exceeds the limit of 2 bytes in Unknown on line 0, referer: http://b3.local/

In the WP login: POST wp-login.php gets 200 OK to my EasyFind domain. Wp-admin.css, and colors-fresh.css both get: 304 Not Modified.

I don't know what the "correct script" should be.

I get this information about the content:
Content-Length148
Content-Type application/x-www-form-urlencoded

The problem is that with login the passwords and usernames get wiped off the login-window when i press enter and there is no login. It is the same for WP and for ownCloud. I tried to install a new ownCloud, but it is the same problem. Whatever I try to enter in, passwords, users, etc. gets just wiped off and no login happens.

toukie wrote:Does this say anything?
[error] [client 192.168.xxxxx] PHP Warning: Unknown: POST Content-Length of 138 bytes exceeds the limit of 2 bytes in Unknown on line 0, referer: http://b3.local/

What is post_max_size in php ini on your B3? Maybe there's a missing "M" in it?

Also you can get everything between requests with firebug by clicking persist button in it.

Thanks a lot Nrde!

You solved the problem!

I can log into WP now!

The problem was that I followed bad advice at another forum (ownCloud). Somebody told to augment the max_whatever_size by writing 2GB into the php ini. Now I know that it is written as 2048M and nothing else.
Well, there is advice and advice, and you don't know the difference before you know it.

Firebug seems to be an interesting tool for learning.

The partial re-install works. Now I'll put back all the stuff I had before the crash, but I'll try to be a bit more careful.

Nrde wrote:

Gordon wrote:You might want to try enabling the "register globals" setting in php.ini and see if that fixes your issue.

For any sane php application that doesn't make any difference.

Now that depends on your definition of "sane", doesn't it? I agree that the mentioned applications are current projects, so you would expect them to be up to date with the current PHP installs but I've learned there's never any guarantee.

Anyway, good to see that the problem was finally solved. Would have been nice to know that there had been previous changes to php.ini, but that's the wonderful world of IT support

Gordon wrote:

Nrde wrote:

Gordon wrote:You might want to try enabling the "register globals" setting in php.ini and see if that fixes your issue.

For any sane php application that doesn't make any difference.

Now that depends on your definition of "sane", doesn't it?

I hope my definition of sane is sane Anyway register_globals was deprecated as of php 5.3.0 (3 years ago) and already before that I can't even remember when it wasn't always stressed that you should not use it. php 5.4.0 doesn't even have it anymore.

But anyway it's good that the problem got solved.

please please please do not recommend on fora that people turn on register_globals. It is the spawn of hell.

thank you

nobody wrote:please please please do not recommend on fora that people turn on register_globals. It is the spawn of hell.

thank you

Actually, the reason for disallowing globals (and then adding a setting to re-enable them) is that most people using PHP for creating web-pages use uninitialized variables, which is bad programming practice. Combined with easy to guess internal variable names this can enable someone ("a hacker") to pass an initial value themselves, either by GET, POST or COOKIE, and do stuff that he shouldn't be able to.

So yes there is a risk with enabling register_globals, but only if your code is bad.

I know, but the thing is that other people read these fora too, get things out of context and just enable register_globals because it may just help. If it does nothing they leave the setting enabled and wonder why their site gets all these weird errors a few weeks later.