Hi,

I was trying to import the attached file (change the .txt extension to .xml) to a new and clean drupal 7.4. The import works great and I can see all the posts and comments. The problem occurred when I click on the "CREATE NODES FROM PROCESSED ENTRIES" button.

Blogger import has encountered an error.
Please continue to the error page

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /?q=batch&id=14&op=do StatusText: Service unavailable (with message) ResponseText: PDOException: in field_sql_storage_field_storage_write() (line 424 of /home3/lincl/public_html/gardnerhamilton.lin.cl/modules/field/modules/field_sql_storage/field_sql_storage.module).

When I click on the "error page" I get the attached error.txt

Don't know how to continue the debugging but I will be happy to help if I can.

Thanks in advance.
Linus Casassa

CommentFileSizeAuthor
#1 error.txt106.31 KBParisLiakos
blog-07-16-2011.txt153.8 KBlcasassa

Comments

ParisLiakos’s picture

Issue summary: View changes

moving the error to a txt file

ParisLiakos’s picture

StatusFileSize
new106.31 KB

Yes i am able to reproduce it.I will check it now..
Also attached the error in a .txt

ParisLiakos’s picture

ok i fixed it..it is because you had non utf8 characters in your posts...i will commit the changes soon and release 7x-1.0-alpha4 version...when it is out,update your module and retry the import..if you still have same problem re-open this issue..
if you face other issues non-related to this then open a new issue.

Cheers!

ParisLiakos’s picture

Status: Active » Fixed

alpha4 is out, just now:)

lcasassa’s picture

Title: Error when creating a node » feeds
Version: 7.x-1.0-alpha3 » 7.x-1.0-alpha4

I had a similar error doing the same thing but it was related with the module feeds. I disabled it and it works great! Thank you very much for the fix and fast respond!

ParisLiakos’s picture

Title: feeds » Import dies when xml contains non-utf8 characters

No problem:)

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

made error easier to read