I'm not sure if I should report this here or on the single theme projects, but since this is happenning to me with almost all the themes I'm suspecting it's a Views issue and filing it here--please feel free to move it if it's the wrong place.
I'm running latest Drupal head and Views module directly from cvs, this is a fresh installation of Drupal. The only theme that seems to be able to display the Views admin pages is friendselectric, all the other themes (bluemarine included) show up a blank page. The themes are checked out from cvs as well. If it were a theme-related issue, I think bluemarine at least would show Views, but it doesn't. I have other contributed modules enabled and those show up fine. I've tried resubmitting the modules page, but nothing. I also tried disabling all other contributed modules and leaving only Views as contributed module, thinking it was a conflict problem, but nothing changed.
I have no idea why this is occurring--if more info is needed, I'm willing to provide.
Comments
Comment #1
e-kipa commentedI have exactly the same problem and could not find the way to fix it. I am surprised how it is possible that nobody else hasn't found this issue before. Does it mean that it has to do with the local environment configuration: php, permissions?
Comment #2
Permanently Undecided commentedI'm running php 5 with MySQL 4.1.12 on MacOS X Tiger Client, if it helps. This is a clean installation with no kind of access control modules and I haven't encountered any other problems of this kind apart from Views, which still strikes me as weird. Could it be a Drupal head problem? Maybe this could be the reason why nobody reported this before, if everybody else is running 4.7.2.
Comment #3
merlinofchaos commentedViews is not currently compatible with Drupal HEAD due to the way the CVS/project system works.
There is a patch that'll fix this (search the views issue queue for 'postponed' and you'll find it), and there's something else I can do that'll at least temporarily work but I'm not updating Views for HEAD since that will basically force development for 4.7 to stop.
Comment #4
Permanently Undecided commentedThanks very much for the info, merlin!
Comment #5
catchComment #6
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.