"Page not found" error after saving a view

In general the drop is moving very fast at the moment.

So better try to get the latest version(next day dev version) again, and see whether it's still happening

If you don't have the human_name column, you must run update.php

Hello, I had the same issue here. I have been having an unrelated problem with views_slideshow and am trying out views_slideshow 3.x which requires views 3. I upgraded both on my dev machine and ran drush updb, but it did not find any updates to apply. However, couldn't get any view edits to save. I found this issue and checked my views_view table and sure enough, no human_name column. Tried updb again, but nothing. I ended up "drush pm-uninstalling views" and then enabling again and the fields were added... Not sure why the table updates didn't happen with the drush updb. It's my understanding that that is the same as running /update.php.

Here is the reason for this problem: 6012 is missed in 6.x-2.x

I see. That's not so cool. I abandoned the particular tangent I was on so this isn't a bigissue for me at the moment. I'll keep it in mind for the next time I need to upgrade views from 2 to 3.

I ran into this problem, too. If it helps anyone else, you can run update.php the old-fashioned way, but select the Views 6012 update manually.

Can someone please describe how to run update.php "the old-fashioned way"?

My site seemed fine after upgrade though, surprisingly, the views upgrade didn't cause any (or a significant number of?) database updates. After trying to edit a view and trying to save, the site is hose:

PHP Fatal error: Call to a member function access() on a non-object in .../modules/views-7.x-3.0-rc1/includes/view.inc on line 317

No backup, because I don't usually backup my database before editing a view... :-(

Time to try hacking the database by hand...

OK, back in business after installing the current dev version instead of rc1 and heading to .../update.php

I cannot save new, duplicated or imported views anymore. Views sais it is saved, but the page is not found afterwards, neither does the newly created view appear in the list.

On this perticular site I'm working with Views 6.x-2.13. I updated to a more recent version of views before, but rolled back because certain views I built did not work anymore: the ones involving the signup module. Signup links/buttons did not show up anymore so I had to downgrade to 2.13. It is a pretty complex website so I am very anxious about upgrading again. Maybe something went wrong in the process of upgrading and downgrading...

What can I do to fix this so I can add views again?

Found a way to fix the views. Now they also work for 6.x-2.16. Had to uncheck "Do not rewrite when empty" on certain fields, which is a new setting in 2.16.
Must have had something to do with upgrading and rolling back again. Sorry for the confusion.

(D7 #fail) Somewhere along the line a hook_update_N() was missed; I had this as well (on a site that had a long, pre-D7 release history). There are no updates remainting to be applied, but I have this problem.

I had to do this to fix it

ALTER TABLE `views_view` ADD COLUMN `human_name` VARCHAR(255) NULL  default '';
ALTER TABLE `views_view` ADD COLUMN `core` INT(11) DEFAULT 0;

I also replaced Views 2.x with Views 3.x and found after updating to 3.x, no views were being saved. After a running update.php with 6012 views are now being saved. Thanks, all for posting the fix. (I'm running Drupal 6.x)

Hello,

I am having the same issue. Out of nowhere my views started to not save, only new ones. I have 2.16 installed on D6.

Though I am not getting a table error, only Page Not Found when I go to save a new view. I am not moving to Views 3.x though.

I see people mentioning to run update with 6012 but I am not sure how to do that specifically. I can drush run updates but how do I specify 6012?

nvm got it. Using Drush to update doesn't give you an easy option to select versions. Im sure it does, but i couldn't find it.

So i ran site.com/update.php and selected 6013 since 6012 wasn't available on the list and it worked.

There is also no 6012 for me. I am on 6010, and 6011 and 6013 are available. Should I choose 6011 or 6013?

Hello Seijun,

Same as #19, I didn't see it either and just grabbed 6013 and it worked fine

The issue was also solved for me by running update 6013. It seems like this has worked for everyone who has tried it, so that's good news.

It appears you must manually select Views 6013 each time you run update.php, or the problem reoccurs.

I can confirm that manually selecting 6013 from update.php does indeed solve the problem for me.

RTBC means that there is a patch, I can't find one of those here :)

Running update.php and selecting views version 6013 manually worked for our site as well.

Hi all, this is an old post but I have this problem too. But where can I select 6013 manually ? Do I need to install something first ? Don't know how to update manually :-( And I can't find it. Please help because I can't save changes in the views. I sarted from drupal 6, upgraded it to drupal 7.44 and fixed a few problems, but this issue is hard for me. thank you

Hi, I was working on a D6 site with the same issue and #24 or #26 works fine for me.
Lot of thanks!!! :-)

The Drupal 6 branch is no longer supported, please check with the D6LTS project if you need further support. For more information as to why this issue was closed, please see issue #3030347: Plan to clean process issue queue