/admin/build/views is blank.

It was ok in alpha5, and the one view I created using alpha5 still works but the views listing is totally blank.

However,

/admin/build/views/add
/admin/build/views/import
/admin/build/views/tools

all appear fine.

I first saw this problem when I switched to beta1 and still see it now with beta2.

Comments

merlinofchaos’s picture

Do you get an error in your php/httpd error log?

Drupalr’s picture

No, I don't see an error in the apache2 error.log.

FYI, I'm running php5 and the memory_limit in php.ini is 128M.

merlinofchaos’s picture

Wow. Without some kind of error message, I don't have much to go on. Have you hit update.php? It might be possible that the theme registry cache needs to be cleared to see the new theme function that got added?

merlinofchaos’s picture

Status: Active » Postponed (maintainer needs more info)
Drupalr’s picture

I have drupal running with the cache off, but just in case, I hit the "clear cached data" button again. Also I hit the update.php button. Still the same blank page on /admin/build/views with no errors in the logs.

Quite mysterious. Sorry I can't provide more info.

merlinofchaos’s picture

Just to be absolutely safe, go into your database command line and type 'truncate cache' (or phpmyadmin equivalent) and make sure the theme registry is clear.

Second, make sure the file theme/views-ui-list-views.tpl.php exists in your theme directory.

Drupalr’s picture

I truncated the cache

and

confirmed the presence of theme/views-ui-list-views.tpl.php.

still blank admin/build/views

merlinofchaos’s picture

Wow. I'm not sure what to do next; without being able to get into the account and personally debug this, I'm out of ideas on what to try.

Drupalr’s picture

I'll make an effort to debug this problem myself and report back when I learn something. I thought for sure someone else has reported the same problem but apparently it is just me. It's probably some quirky combination of modules installed that is causing this.

Pedro Lozano’s picture

A blank screen is often due to the request getting out of memory, which may be related to http://drupal.org/node/252698

foot-2’s picture

Version: 6.x-2.0-beta2 » 6.x-2.2

I had blank admin/build/views when module Views installed after Token and Pathauto.
Fix for me: Disable and uninstall Views, Token and Pathauto, then install Views first.

caravinci’s picture

Had the same problem until I disabled CCK and Views, then re-enabled Views first, then CCK.

reikiman’s picture

I'm having the same problem ... http://drupal.org/node/446762

Just tried turning off views & CCK modules, uninstall views, then enable views. Still get a blank screen. Haven't enabled CCK yet.

esmerel’s picture

Status: Postponed (maintainer needs more info) » Closed (fixed)

Issue referred to is closed, unable to replicate. No updates for more than 30 days.

lupus78’s picture

Version: 6.x-2.2 » 5.x-1.6

i get the same error, and non of the above helps!

I'm running Drupal 5.20 with Views 5.x-1.6! I've recently updated from 5.4 and earlier version of Views. Since that update the Views page is blank! It dosen't even show up under admin/build !

Tried disable, reenable the Views module, and CCK! Runned update.php again. No result!
No error message, jut a plaing page with "Site building" header text!

lupus78’s picture

Status: Closed (fixed) » Active

Fro me even these page result in a blank page:
/admin/build/views/add
/admin/build/views/import
/admin/build/views/tools

merlinofchaos’s picture

Version: 5.x-1.6 » 6.x-2.2
Status: Active » Closed (fixed)

Please don't take over old issues. Views 2 is a completely different piece of software than Views 1, so bugs in one cannot be the same bugs in the other. Please read the submission guidelines fully, and understand them, before posting here again.

Budrick’s picture

I had the same problem.
The cause was calling path_to_theme() from a custom module.
The side effect of this was admin theme change.
After deleting path_to_theme() call, works OK.

greg.harvey’s picture

Hmm, experiencing this too. Will check for path_to_theme() instances now.

Edit: sadly this wasn't our problem, though symptoms are the same... =(