This forum is for questions about upgrading an existing Drupal site. Don't forget to read the UPGRADE.txt file that comes with every Drupal download.

Rss Problem

hello drupal community!

I'm experiencing a problem with the xml code generated by my installation of drupal.

Since i've upgraded from 4.5 the /feed page is no more readable and I get back an error message; I don't know yet how it comes out but i've noticed that -in the http[...]/feed generated code- there is a first blank line that -in my modest opinion- could be the cause of the error.

Can't add new custom block (common.inc & database.mysql.inc) errors

I can't ad more than 1 custom block and if I do the following 2 errors are displayed. I can still ad the default blocks supplied with modules.

user error: Duplicate entry '' for key 3
query: INSERT INTO boxes (title, body, info, format) VALUES ('Test block title', 'Test block body', '', 1) in /home/gossip/public_html/includes/database.mysql.inc on line 66.

warning: Cannot modify header information - headers already sent by (output started at /home/gossip/public_html/includes/common.inc:384) in /home/gossip/public_html/includes/common.inc on line 192.

HELP - Duplicat Entry errors and site crash after turning on the Blog module.

Hello,

I was changing some settings on a site I have recently taken over as web master (i've never touched drupal before this). I turned on the Blog module and the home page crashed. Anyway, after reading some similar forum topics I managed to atleast get the homepage working with out error messages by turning on the node module in the systems table, but half the content that was originally on the home page is now missing and the log registers duplicate entry errors every time i try to view the admin/modules section. I set the status of the Blog module to 0 in the systems table in hopes that it would fix something but it didnt do squat....any suggestion would be much appreciated : ) ...heres a list of the log errors.

php Feb 8 2006 - 8:20am Duplicate entry 'modules/image_import/image_import.module&# Admin
php Feb 8 2006 - 8:20am Duplicate entry 'modules/image/image.module' for key 1 Admin
php Feb 8 2006 - 8:20am Duplicate entry 'modules/help.module' for key 1 query: Admin
php Feb 8 2006 - 8:20am Duplicate entry 'modules/gsitemap/gsitemap.module' for Admin
php Feb 8 2006 - 8:20am Duplicate entry 'modules/gmap/gmap.module' for key 1 q Admin
php Feb 8 2006 - 8:20am Duplicate entry 'modules/forum.module' for key 1 query Admin
php Feb 8 2006 - 8:20am Duplicate entry 'modules/formupdater/formupdater.module Admin
php Feb 8 2006 - 8:20am Duplicate entry 'modules/flexinode/flexinode.module' f Admin

upgrade 4.6.5 to 4.7 beta 4

Warning: Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_swedish_ci,IMPLICIT) for operation 'like' query: SELECT * FROM access WHERE status = 1 AND type = 'host' AND LOWER('82.3.32.76') LIKE LOWER(mask) in /home/walkerst/public_html/includes/database.mysql.inc on line 124

Warning: Illegal mix of collations (utf8_general_ci,COERCIBLE) and (latin1_swedish_ci,IMPLICIT) for operation 'like' query: SELECT * FROM access WHERE status = 0 AND type = 'host' AND LOWER('82.3.32.76') LIKE LOWER(mask) in /home/walkerst/public_html/includes/database.mysql.inc on line 124

Warning: Unknown column 'referer' in 'field list' query: INSERT INTO watchdog (uid, type, message, severity, link, location, referer, hostname, timestamp) VALUES (0, 'php', 'Cannot modify header information - headers already sent by (output started at /home/walkerst/public_html/includes/database.mysql.inc:124) in /home/walkerst/public_html/includes/common.inc on line 143.', 2, '', '/update.php', '', '82.3.32.76', 1139392203) in /home/walkerst/public_html/includes/database.mysql.inc on line 124
Drupal database update

* warning: Cannot modify header information - headers already sent by (output started at /home/walkerst/public_html/includes/database.mysql.inc:124) in /home/walkerst/public_html/includes/common.inc on line 143.
* warning: Cannot modify header information - headers already sent by (output started at /home/walkerst/public_html/includes/database.mysql.inc:124) in /home/walkerst/public_html/includes/common.inc on line 143.

problems of upgrading from 4.6.5 to 4.7.-beta4

I got the following three errors when upgrading the database:

Character set problem - simple solution?

Hello, I'm experiencing the following difficulty moving my database from latin1 to utf8.

I began developing my first Drupal site (4.6.5) using Mysql 4.1, and knowing nothing about character sets The characters sets in use at that time were:

Client, connection, results, system: utf8
database, server: latin1

Accented characters showed up fine in Drupal, but scrambled in PHPMYADMIN. I now know that this is because I had utf8 data stored in a latin1 database. Instead of leaving well-enough alone (doh!), I wanted everything to show up properly in both Drupal and in PHPMYADMIN. Thinking I had the answer, I decided to move to a utf8 database.

Here's what I did:

1. Created a new (empty) database, with character set utf8.
2. Exported the data definition and data from my working database to a text file. Edited the file to change charset of the table definitions from latin1 to utf8, and changed the encoding of the file itself to be utf8.
3. Did an import to the new (empty) database using the "mysql" command.

Results:

I now have the following Character sets:

Client, connection, results, system, database: utf8
server: latin1

All the tables and columns have default character set utf8. In PHPMYADMIN, all the accented characters are displaying properly. Looks beautiful. So far so good.

The problem is that now when I connect the new database to Drupal, the special characters show up as garbage. It's a terrible mess, because not only to accented characters show up as garbage, it breaks the html and the page itself doesn't render properly.

Pages

Subscribe with RSS Subscribe to RSS - Upgrading Drupal