In DC 2.3, after saving a cloned or new view, I get a page not found error page. After checking the dblog, I found the following log entry:

Unknown column 'view_php' in 'field list' query: INSERT INTO views_view (name, description, tag, view_php, base_table, is_cacheable) VALUES ('video_latest_comments', 'The latest comments on all videos', '', '', 'comments', 0) in /path/to/site/profiles/drupal_commons/modules/contrib/views/includes/view.inc on line 1723.

I found this Views issue at http://drupal.org/node/1127872 although since Views is distributed by Commons, then it should be addressed in the distribution.

Comments

ezra-g’s picture

Status: Active » Postponed (maintainer needs more info)

Thanks for reporting this.

If you visit update.php, does Views have any updates available?

If not, manually select update #6012 for Views, run the update, and try saving a View again.

Let us know if that resolves the problem!

ezra-g’s picture

Also, can you confirm whether your're running Views 2.x or 3.x?

frifoles’s picture

I'm using the same version provided by Commons 2.3, which is Views 2.x. Does Views 3.x work flawlessly with Commons 2.x?

The "views module" on update.php only goes up to 6009 on the select list. Do I run 6012 for the "system module"?

ezra-g’s picture

My mistake. No, don't manually run 6012 for system unless it is unapplied.

I would try running the Views update 6010().

Commons 2.3 ships with a somewhat patched version of Views which makes it difficult to troubleshoot. If running the Views 6010 update doesn't resolve the issue, I suggest downloading a nightly development snapshot of Commons and upgrading in a test environment to see if this resolves your issue.

We're working on update documentation, to test the dev snapshot you'll want to:

- Run update.php

- Revert all Commons features

- Visit admin/rules/trigger - For any action where status isn't
default, revert the action. If you have customized rules messages,
make a note of those messages to re-enter after the upgrade. It should
not be necessary to revert your customized messages in future
releases.

- At admin/settings/activity_log - Clear message caches

- At admin/settings/activity_log/regenerate - Regenerate activity

Views 3.x should work with Commons, but the Views will need to be re-exported in #1270348: Upgrade to Views 3.

frifoles’s picture

Views update has 6009 and not 6010.

ezra-g’s picture

Do you have any custom modules on your site?

If not, I suggest updating to the night dev snapshot of Commons to see if this problem persists.

frifoles’s picture

I do not. I only have other contrib modules installed.

I will test on development and see if the nightlies resolve it.

lsolesen’s picture

Version: » 6.x-2.x-dev
Issue summary: View changes

Closing old issues for inactivity. Please reopen if the problem still persists.