Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By jdenniss on
I don't seem to be able to save any settings (or anything else) in Drupal at the moment. I'm suspecting a php issue, but don't really have a good basis for that suspicion.
basics: drupal 6.6 gentoo (Linux cms 2.6.25-gentoo-r7 #1 SMP ) apache 1.3.41 PHP/5.2.6 MySql 5.0.60
Site was initially developed w/ apache2 and was running well except for 'file' nodes (http://drupal.org/node/324758).
Couldn't find any solutions to problem with apache2 so I decided to replace it with apache 1.3.41. The site is 'up' under the new config (haven't tested every aspect), but doesn't seem to save anything new. No new settings, no updates to existing nodes, apparently no new backups either.
There are no errors logged by either apache (clearly shows 'POST' in access log), php or mysql. The 'submits' I've tested thus far simply return me to the same page (without any evidence of the update occurring). This is true on update.php (select page), site maintenance, node edit, theme list and enable and backup/migrate.
Links seem to work. Forms apparently do not.
Has anyone seen this sort of behavior before? Any ideas?
thx
Comments
I got the same problem. I
I got the same problem. I asked http://drupal.org/node/330038 before. I haven't tried yet an another version of drupal but I think this is a bug of the latest version(6.6).
looks like a php problem
I wrote a simple form html->php and discovered that the $_POST array is not being filled. I twiddled with registerglobals but saw no change in behavior.
Found some very old notations about bugs in php that did this but were resolved years ago.
I'm currently attempting build php and apache with the same module config on a FreeBSD box that I have - work is still in progress.
UPDATE -> just did test over again in FireFox. It worked fine - This begins to look like an IE problem.
IE is awful
I'm not sure what weird state IE got into, but it now appears there was no problem with the site - just the browser.
FireFox had no problem at all and IE figured itself out after I restarted it...
argghh!