I upgraded from biblio version 6.x-1.2 to 6.x-1.4. The status report informed that it is necessary to run the database update script. When trying to do that, I get the error: warning: Cannot modify header information - headers already sent by (output started at [...]/sites/all/modules/biblio/biblio.views.inc:199) in [...]/includes/common.inc on line 141. Previous uses of the database update script with other modules worked fine. I did take a look at the two files mentioned in the warning. They do not have any characters in front of <?php. Now I am lost.

CommentFileSizeAuthor
#2 database-update.png12.36 KBulrich

Comments

rjerome’s picture

rjerome commented

Unfortunately, I don't see that error when I update from 1.2 -> 1.4. Do you get this message before doing any updates or after?
The biblio.views.inc file is not included by any of the biblio code, so it would have to be the views module that is doing that. What version of Views are you using?

ulrich’s picture

ulrich commented
StatusFileSize
new database-update.png12.36 KB

I did upload the biblio 1.4 files to my server (linux). Next when I go to status report, I get the message: Database updates: Out of date. Some modules have database schema updates to install. You should run the database update script immediately. Clicking on the database update script link starts

rjerome’s picture

rjerome commented

what happens if you disable the views module and then run the update script?

ulrich’s picture

ulrich commented

Disabling the views module did solve the problem! The database update script proceeded without a warning. I will now enable the views module again. Thanks so much so far. Anything else that should be done? Fantastic response time!

rjerome’s picture

rjerome commented

Strange, I really can't explain why that happened. I ran the update with Views enabled and it worked fine.

You should be good to go now.

Ron.

ulrich’s picture

ulrich commented

Thanks so much! Ulrich

rjerome’s picture

rjerome commented
Status: Active » Fixed

Status: Fixed » Closed (fixed)

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