Hey,

I just got a shiney new pair of Dell servers (sweet!) and am running into some very strange trouble with $_POST data.

A bit of background:

  • Server is running Debian Testing
  • Apache 2.0.55-4 and PHP 5.1.4-0.1
  • Mysql 5.0.22-3
  • I am running a test version of www.projectopus.com on the server
  • My other servers include 2 Debian testing boxes, and an Ubuntu Dapper box. None of those are using Mysql 5 .... but that "shouldn't matter"

Please flag me right away if that LAMP version combo seems like a bad move.

NOTE: This problem may seem similar to the thread "Problem with login (doesn't seem to 'take')" however I assure you this matter is differnt. That thread is about problems with: certian browsers, cookies, and session caching. My problem is that on certian forms (on every browser, from any location) the post data doesn't get passed all the way through PHP.

I can confirm this by putting a drupal_set_message('POST: ' . var_export($_POST)) in a menu hook of a loaded module (menu hook gets hit always and at least once). On some forms I can see my post data show up. On the "broken" forms I see one or possibly two lines showing POST: array().

Specifically the problem affects the following forms:

  • Quick Login (user/login works correctly though)
  • Create Node
  • Edit Profile
  • Save the admin/settings page
  • ... many more ...

Has anyone ever seen anything like this happen before?

PS: Yes, I tried logging a var_export of the $_POST data right inside the index.php to see if it was at least getting into PHP at all. It appears that the POST data is not even reaching PHP.

Comments

James Andres’s picture

Sorry about the spelling. Just mentally change:

  • certian => certain
  • differnt => different

James Andres

Lead Developer on Project Opus
www.projectopus.com

James Andres’s picture

This might help somebody else so I'll post it here.

I'm still not quite sure what the problem is but I formatted the computer and installed ubuntu dapper (server) amd64-xeon, moved my configs back in, and the problem disappeared.

My best guess is the debian testing php5 packages have a bug that was causing this behaviour on my machine.

Cheers!

James Andres

Lead Developer on Project Opus
www.projectopus.com