When building a form in Drupal 5.x, you may just run into the following error:
What happened, is that you probably sent modulename_form() to the drupal_get_form function. The problem is that drupal_get_form is expecting the name of the form function, rather than calling the function.
I was banging my head against the wall trying to implement the following:
Spambots began attacking my newly founded blog about 4 weeks ago. I was deleting around 3 posts an hour, and installed the Drupal spam module to battle the spammers. It worked great, but still required a lot of maintenance - I was still deleting about 5 posts a day.
Raise your hand if you don't like comment spam. I see everyone has their hands up. We've all dealt with it, either as a site visitor or as a blog owner, and it's simply no fun. I haven't had this blog up long, maybe 6 weeks in all, yet somehow I've already made it into the blackjack spambot. Yes, each of the last 263 comments have all had something to do with blackjack. Who knew the card game was so popular? I sure didn't.
I ran into a problem the other day where one of my Drupal sites would not open up properly. Drupal is installed atop a MySQL database, and as it turns out, the /var partition had filled up. After removing some of the old log files that I didn't need, I restarted MySQL and found it was running fine for my non-Drupal sites. But, I was still having Drupal problems and noticed the following error in the Admin screen:
Problems with Drupal Caching? I'm more concerned with turning it off at times than turning it on. There are two primary places (that I know of) to check to determine how / where Drupal is being cached.
1. Admin > Performance
Within the Performance Administration screen, there is a fieldset titled Page Cache. Set the caching mode to Disabled to turn off overall site caching.
2. Content Caching in MySQL
There are 5 (depending on the modules you have installed) tables involved with content caching:
• cache
• cache_content
• cache_filter
• cache_menu
