Closed (fixed)
Project:
Views (for Drupal 7)
Version:
4.7.x-1.x-dev
Component:
Miscellaneous
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
21 May 2006 at 18:57 UTC
Updated:
22 Jul 2006 at 17:15 UTC
I am installing the latest version of Views (as of 21/5/6) into a completely fresh install of 4.7.0 .
'administer' > 'modules' > tick 'views' and 'views_ui' > hit submit > site vanishes. Nothing on resulting page at all. Source blank.
Running 'DELETE FROM system WHERE name LIKE 'views%';' sorts the lack of site, but same issue when I re-activate the views and views_ui modules.
Other modules installed (marked * if activated):
gsitemap *
image *
image_pub
image_assist *
masquerade *
og *
og_basic *
og_block *
og_book
og_views *
taxonomy_access
views
views_ui
Have tried enabling views without views_ui - same result...
Am I missing something really obvious?
Comments
Comment #1
merlinofchaos commentedLook in your httpd error log and see if there is some kind of PHP error being generated?
Comment #2
arcticflea commentedAfter a little more digging, I've discovered that there must be a conflict with Organic Groups module - disabling this and enabling views works. Turn og back on, and pow.
Comment #3
merlinofchaos commentedThere's been a lot of work on og to give it views compatibility lately, tho I suppose there could be some version mismatching. Are you using cvs tarballs, 4.7 tarballs or direct from CVS?
Comment #4
arcticflea commentedI'm using fresh downloads from the 4.7 module listings... to answer your earlier question I can't see anything out of the ordinary in the httpd log... I could post a sample if that would help?
Comment #5
merlinofchaos commentedOG's probably been more recently updated in 4.7 branch than Views and there is probably a disconnect there. I know the CVS versions work nicely together. I think I'll do a preliminary 4.7 tagging today.
Comment #6
ajk commentedIf the site vanishes completely then there's usually something in the error_log (php error of somekind).
When you say "httpd log" are which are you looking in, the access_log or the error_log ? The former won't give you much at all, the latter should.
regards
--AjK
Comment #7
jo1ene commentedI have experienced this also. I get this:
Fatal error: Cannot redeclare og_views_default_views() (previously declared in W:\www\modules\og\contrib\og_views\og_views.module:226) in W:\www\modules\og\og_views.inc on line 412
...when using views CVS and og CVS versions AND vews CVS with og 4.7 versions. What's the status on this?
Comment #8
ajk commentedLooking at CVS HEAD it appears we have a function name clash that needs fixing by the maintainer(s):-
function og_views_default_views()
Line xxx in contributions/modules/og_views/og_views.module
Line xxx in contributions/modules/og/og_views.inc
Both files were last worked on by cvs user "weitzman"
This can be explained by last CVS commit message in the og_views.inc 8 days ago:-
So it seems og_views.module, as a standalone, is retiring? SO it seems teh solution is to disable og_views.module and use og.module to create / recreate your views
regards
--AjK
Comment #9
laura s commentedI can confirm that removing og_views.module did it for me. Everything is back.
Comment #10
merlinofchaos commentedAs I understand it, the og_views.module is deprecated and should NOT be used.
Comment #11
jo1ene commentedThis just happened to me today with today's most recent 4.7 versions of Views and OG. Is the problem back?
Comment #12
pulpzebra commentedIt happens to me AND I have no OG installed on a brand new 4.7.2.
In the error_log I spotted this entry:
PHP Fatal error: Allowed memory size of 8388608 bytes exhausted (tried to allocate 11520 bytes) in [DOMAIN]database/updates.inc on line 1783, referer: http://[MY DRUPAL SITE]?q=admin/modules
Allowed memory size of 8388608 bytes exhausted (tried to allocate 153 bytes)
Comment #13
pulpzebra commentedAs a further info, I have to say that I run this site on mysql 3.23. In the error_log file, just above the Fatal Error, there's PHP notice:
PHP Notice: Undefined index: pass in [SCRIPTROOT]includes/database.mysql.inc on line 37, referer: [MY DRUPAL SITE]?q=admin/modules
Comment #14
merlinofchaos commentedLook at http://drupal.org/node/31819 for info on the allowed memory size issue.
Comment #15
(not verified) commented