views - i18n views conflict

That's nothing to do with i18nviews in special

I've heard some others have similar issues with views and D7.2.
I have tested the setup and it works cleanly. This seems to be a (yet) unknown special case bug of drupal.

Try a few times to disable, reenable and cache clears and provide some more report if we can clearly reproduce this.

I just had the same problem. I installed i18nviews, looked around a bit, then desactivate, uninstall and remove files from modules folder. When I was back to my structure, the Views link wasn't there anymore and trying to go "by hand", it give me the "You are not authorized to access this page." message.

Is there by any chance a possibility that i18nviews remove that link or authorization in a hard-coded way or something happening during desactivation or uninstall?

I put to active, since I think I have found a reproduce method.

1. With views installed, install i18nviews.
2. Check out in the settings of Views for the "Localization - Translation method" setting in the advanced panel. While it was set for "Core" by default, i18nviews add and change it to "Internationalization Views"
3. Desactivate i18nviews. Views should be removed from the structure links.
4. Reactivate i18nviews; Views should be back.
5. Change the "Localization - Translation method" back to "Core".
6. Desactivate i18nviews. Views should be there in the structure links.

So, I've got the feeling that i18nviews alter the settings of "Localization - Translation method" for "Internationalization Views" at install, but doesn't change it back to "Core" when being desactivated, hence Drupal prevent us to access Views because it has a non-valid setting.

I don't know the why behind though. Having a setting value in database that doesn't exist anymore and was created by another module that is not activated?

Anyhow, I guess an "easy" way to correct this would be to set Views setting back to "Core" in "Internationalization Views".

Clear the cache some times, and it will be ok. I have this issue several times, and the flush of the cache always fixed it.

And - of course -, use the latest ctools and views -dev versions.

This has been fixed with recent versions.