I recently installed Drupal and set up a site with it for the first time. I installed Views from http://drupal.org/project/views . In my admin module section under Views it lists Views 6.x-2.6, Views experter 6.x-2.6, and Views UI 6.x-2.6. All are enabled. I've also installed the advanced help. I my problem is, no matter where I look or what I do, I apparently am stuck using the Views 1 interface.

How do I switch to the Views 2 interface? It is driving me crazy!

Comments

merlinofchaos’s picture

merlinofchaos CreditAttribution: merlinofchaos commented

The Views 1 interface doesn't exist on Views 2. What you say cannot be correct.

Webbstre’s picture

Webbstre CreditAttribution: Webbstre commented

In the advanced help it shows a picture of the Views 1 interface and the Views 2 interface, but all I get when I use views is the list-style interface shown in the pictures of Views 1. I downloaded it from the place I linked to... And those are the version numbers showing up when I check the Modules as an admin.

I'm not lying... :(

Edit: If it helps, I can show you. E-mail me at webbstre@runicgamesfansite.com and I'll send you the URL and a username and password you can use to access my test subdomain.

merlinofchaos’s picture

merlinofchaos CreditAttribution: merlinofchaos commented

Okay, you're not lying. But the Views 1 UI does not exist under Drupal 6, in any form. So I don't know *how* you're getting the Views 1 UI, without some very, very strange things going on.

Webbstre’s picture

Webbstre CreditAttribution: Webbstre commented

Are there any other modules that affect the Views UI? Themes? I checked the views folder and the readme says it is the right version, as does everything else. Is there even a Views 1 for Drupal 6?

merlinofchaos’s picture

merlinofchaos CreditAttribution: merlinofchaos commented

There isn't, which is what makes this very strange. Without actually seeing what's going on, I have no reference point with which to offer help. :/

Webbstre’s picture

Webbstre CreditAttribution: Webbstre commented

Is there a way I can contact you with the site and login information so you can see yourself? I'm still kind of new to Drupal and I can't find an e-mail or PM option for your name anywhere.

merlinofchaos’s picture

merlinofchaos CreditAttribution: merlinofchaos commented

Are you able to connect to IRC? YOu can find me in #drupal on freenode (though be patient it can take me awhile to respond)

Webbstre’s picture

Webbstre CreditAttribution: Webbstre commented
Status: Active » Fixed

Ok, for anyone who might repeat this in the future, this is what happened:

I wasn't installing my themes and modules in the sites/all/themes and sites/all/modules folders. Instead, I was trying to install things to the area belonging to the core, which my Theme didn't like. It was disabling things by the core, and disabled the CSS file that should have been used by the Views module (and who knows what else). The broken CSS is what made everything appear as if it was Views 1. I moved everything to the correct folders, and the problem is fixed.

Thanks to merlinofchaos for the help!

merlinofchaos’s picture

merlinofchaos CreditAttribution: merlinofchaos commented
Project: Views (for Drupal 7) » Beach
Version: 6.x-2.6 » 6.x-1.0-beta1
Component: User interface » Code
Assigned: Webbstre » Unassigned
Category: support » bug
Status: Fixed » Active

Note: I consider this a bug in Beach. It is using a very lazy method to determine if a CSS file belongs to core, which caused a serious WTF when a user mistake comes into the equation.

Beach should probably compile a list of core CSS files (this is easy with find) and specifically remove only those.

Sungsit’s picture

Sungsit CreditAttribution: Sungsit commented

Thanks for bug forwarding. We'll find out another smarter method to fix this. At the moment, I just added WARNING into Beach project page. Hope, that's not another lazy warning method.

kong’s picture

kong CreditAttribution: kong commented

Of course we programmers are very lazy, that's the reason we write codes and let the computer work for us, isn't it? :)

However, I modified the code in CVS to remove Drupal core CSS files using the less *lazy* method. This should prevent this kind of WTF to happen again.

domesticat’s picture

domesticat CreditAttribution: domesticat commented

@kong: Please reroll a new beta release with this fix.

itapplication’s picture

itapplication CreditAttribution: itapplication commented
Status: Active » Closed (won't fix)