Hi Folks,

I'm having this error saving a commenting the Blog entries, and just comment the Blog entries. Not even at the preview comment. Just saving. Any thoughts? I've check the forum for old messages and I saw that is a very annoying and mysterious bug. I'm right? Any tip for solving this?

Thanks in advance!

Comments

edalcin’s picture

Updating. The same at the Forum reply. Just Stories are ok...

drupalnesia’s picture

Try to re-download Drupal package then re-install to your computer and see if the error still occurs.

edalcin’s picture

Thanks. But, doesn't work. I'm not really "reinstall". I replaced the 6.8 Drupal installation files.

Looking at the previous messages related with this, I notice that this is a pretty common bug, very "generic", which came from different situations, versions and site maturity. I'm amazed that no one, at this point, had came with a reasonable explanation about this, or even a generic but assertive solution, since this is a pretty wide spread annoying bug.

Is it a module "bad behavior"? Is it a core problem? Is it a PHP or MySQL bug? Those simple, but basic questions, have no a agreed answer at all?

drupalnesia’s picture

As you explain that this error only happen on node saving. In my experience I found these actions can solve the problem:
1. try disable any antivirus and firewall
2. try another browser, i.e: if u use FF then try IE
3. since blog is core module then you can try disable any additional/contribution modules, also sometimes change to Garland theme is a good test

The bad situation may need:
1. try to reinstall your WAMP/LAMP, even change to another package, i.e: if you use appserv then try to use xampp
2. install on a clean system (with new installed os)

Since limited information and complex environment then hard to find a quick solution. HTH.

dave reid’s picture

Take a look at the new Troubleshooting FAQ page on this error for information on how to debug and fix this problem.

Leonth’s picture

I got this error when using comment notify module. In my case it is because the node author did not upgrade to drupal 6 properly (specifically, the author still uses the old definition of url() function which is different from the latest one).

Try to disable modules to see which contrib modules are really the culprit and file an issue for that module.