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.
Following the info on the main page about upgrading, I downloaded the 4.6.4 build and installed it by uploading and replacing all files in
includes/
modules/
index.php
cron.php
(settings.php are not different than 4.6.3)
Up until then I had 4.6.3, I have custom theme, running phptemplate. Non-core modules: flexinode, poormanscron, gsitemap. I did not execute update.php, as the security notice said there was no update to database or API. Should I have launched it?
I just updated from 4.5.5 to 4.5.6 and now all my comment area are not even a letter wide. So commenting is effectively broken. Is there a fix or do I have to forego the security for functionality?
As per title! Nothing is affected by it, only xstatistics which gets its data for the summary page from there. I can say for certain that nothing else is affected as I upgraded this site from 4.5 to 4.6 about 5 months ago and it's been working fine all this time!
...I don't even know which Drupal component to look at which uses this table? VERY confusing :o(
Well, I'm trying to get CVS HEAD working (checked out at 2005-11-25 00:35 GMT+08:00), and noticed that many contributed modules haven't been updated to the new API yet. I also noticed that legacy.inc (happily enough!) seems to contain at least some of the functions that those old modules need. Rather than try to submit patches for all the modules in CVS (which I don't understand how to do in most cases yet), I figure I should just include legacy.inc somewhere for now. Is there a correct way to do it? Grepping for "legacy.inc" in all the files brought up no hits, so I just slapped a
After upgrading to Drupal 4.7 I can't login anymore as administrator. I managed to stop SQL errors but that is all. I had problem with upgrade script and manually add missing rows in database - but with no lack.