Views integration not working

Scipr,

Views should be working fine with role_expire. See "Sample test instructions" at http://drupal.org/node/915334#comment-4868216.

If that URL helps and views is actually working for you, please change the status to "fixed".

If that URL doesn't help, please provide step-by-step process you used to generate the failure. Don't forget to include your list of enabled modules.

Thanks

Scipr, thanks for the painstaking report. If I hadn't seen the screenshot, I wouldn't have believed it. I've been able to duplicate the problem, and I don't like what I'm seeing. Turns out I was using a dev version of Views from over a month ago. I was using dev because the rc1 version of Views wasn't working.

The rc1 version of Views is *still* not working (it hasn't changed since 2011-06-17, so that's no surprise). But now the current dev version of Views (2011-09-26) is also not working. (BTW, the Views UI has changed a lot in the new dev version. It looks more like the 6.x version of Views.)

So now I'm in the same boat as you. I'll have to do some research and figure out why it isn't working any more and then see if there's something we can do in role_expire to fix the issue you've uncovered.

I'm changing this from 'support request' to 'bug report' because it's not a user issue or an education issue. Something's broken somewhere. Also, I'm escalating this from minor to major, because this is important functionality.

I've figured it out. The dev version of Views used to report that it is version 3.0. Now it reports that it's version 3.0-alpha1. The following patch will make role_expire work correctly with the current version of Views. If this patch gets tested and approved, we'll create a beta3 of role_expire. If you are unable to apply and test the patch here's a shortcut. Just edit the file role_expire.module. Around line 190, you have

return array('api' => '3.0');

Replace that with

return array('api' => '3.0-alpha1');

Role_expire should then work with both views-rc1 and views-dev.

Please report back here if this works for you.

@stewsnooze, the attached patch has some sophisticated smarts in role_expire_views_api(). Is it over the top? If you approve, I'll commit.

That's a good question. If my patch gets iimplemented, here's what will happen as Views gets updated:

1. If Views becomes version '3.0', it will work fine.
2. If Views becomes version '3.{anything}', it will work, but you'll have a warning message that this version of Views is untested. If you find that that version works fine, you could file an issue and we can update role_expire to say we're compatible with this new version of Views. FWIW, during the whole life of Views 2, the version number was always '2.0'. My suspicion is that will be the case with 3.0 as well.
3. If Views becomes version >3, it will not work, and you'll get an error message telling you to file an issue at the role_expire issue queue.

This stringent compatibility checking may be overkill. If there's a Views expert listening in on this issue and can advise that the level of integration we're doing with Views doesn't require such strict checking, then I'll gladly loosen the compatibility checks.

The patch at #1293846: Problem entering default expire time comment #10 addresses this, loosening the rule to 'any 3.x version' is OK.

You still need to add the views.inc to the info file so that the d7 registry can see it.
files[] = role_expire.views.inc
files[] = role_expire.rules.inc

I've committed those two lines to the info file. Could you give it a go and see if that fixes your issue?

This will be available in the next dev release

Has there been any progress on this since 2012? Is "expiration date" supposed to be working in views now?

Thanks.

Test most recent version. Look for the fields on attached screenshot. If you find any problem, open a new issue. Thanks!