I have been toying with installing some modules, removing those that didn't fit the bill. Somewhere along the way, I've lost a couple of columns in the admin area.
Specifically, weight is missing from the blocks area. The column is present but blank. In ePublish, the topic is missing. Same deal.
If I look at source code, I get something like this:
My hosting company (where I have several Drupal sites) have just advised me that next week they are going to upgrade Mysql (from 4.0.26 to 4.1.15) and Php (to 4.4.1).
Can anyone point me to any problems these upgrades may cause me with Drupal 4.6.3?
I would love to find out ahead of time so I can prepare.
I was able to do this because I just took note of the files to be patched in the patch files found in the upgrade instructions of 4.6.4 -- http://drupal.org/drupal-4.6.4.
However, there are no equivalent patches in the instructions of 4.6.5. -- http://drupal.org/drupal-4.6.5. Only these less precise instructions:
Bugs fixed
The most important bug fixes since Drupal 4.6.4 include:
Patch #29133, #39566, #39670: fixed problem with URL filtering that caused table sorting and pagination to be broken.
Patch #22200: fixed problem with aggregator that resulted in content being filtering twice.
Patch #38889: fixed problem with using multiple database connections.
Upgrading from 4.64 to 4.6.5 cause the following error.
I get the following error and cannot access my site after the 4.6.4 to 4.6.5 update:
Warning: mysql_connect(): Access denied for user: 'username@localhost' (Using password: YES) in /home/xlecom/public_html/includes/database.mysql.inc on line 31
Access denied for user: 'username@localhost' (Using password: YES)
I think this just started showing up with an upgrade to 4.6.4. My log file seems to be getting full of errors: "Page not found" errors are generated by images not being found. Almost the images are specified in the style.css files, are actually visible (therefore definitely found), and are being looked for in the root directory of the installation rather than in the theme directory.
I'm thinking it might have to do with a search cron job but the times don't match. Or with clean_urls (which I've just turned on just before the errors started appearing).