Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
I just installed from 4.7.5 to 4.7.6. I had a number nodes with files attached, but now when I attach a file to node, it doesn't point to the right file. The file is uploaded, but for some reason it points to an older file that I uploaded. Any ideas? Do I have to uninstall attachment and re-upload everything on the site (will be painful given the number of files).
I upgraded my drupal from an earlier version of 4.7 to the current 4.7 version. All seemed to go ok. After following the upgrade instructions and copying over the modules I had uploaded previously I could log in and click around ok. The only error I noticed was that the "recent blogs" menu block was not showing.
I logged in as admin and noticed a lot of these errors in the admin logs
"Message mysql_query() [function.mysql-query]: Unable to save result set in /var/www/web1/web/includes/database.mysql.inc on line 102."
Upgraded site from Drupal 4.7.4 to 5.1 ... and post-upgrade all content from roughly the past 8 months that anonymous visitors and registered users could see before the upgrade is no longer visible to them. Admin user still sees everything.
Tried using Admin > Content management > Post settings > Node access status ... but that throws a HTTP 500 error before accomplishing whatever it's supposed to do.
I'm trying to upgrade from 4.7.4 to 5.1 and find that some contributed modules uploaded to the sites/all/modules folder on the upgraded site do not appear on the admin/build/modules list, while others do.
For example Event Views does appear, but Event does not, even though they both live in the sites/all/modules/event folder.
I added about 25 folders with contributed modules to the sites/all/modules folder in a single batch, and am wondering if that exceeded some Drupal limit for handling module additions.
I Recently upgraded to 5.1 from 4.7 and the site performance has gone downhill to the extent that hosting provider took it offline on account of the wider effect on this shared machine.
The immediate cause of the problem is trackback spam. The httpd log file regularly records up to 10 minutes at a time continuous 1 post per second of the following format:-