Module missing after update!

I'm pretty sure that this is not caused by views itself but by your way of updating modules.

Just a wild guess would say you use the update module, but the problem of the update module is that
many people, for example you, don't make a backup before updating. Maybe you canceled the update process at some point so the old module got removed but the new one didn't get written. There is really no reason on earth why views should remove itself.

So next time do a proper way to update and don't use the drupal interface to do it.

Bob:
I feel your pain. The latest update of Views broke my site as well.

dereine:

I find your response somewhat condescending. I'm not flaming; just being objective.

I have updated hundreds of modules on tens of sites for years. I'm sure Bob and I both know the risks, and sometimes we do the full "backup your database... etc., etc. Sometimes I don't, though I know there is a risk involved. We are not asking someone to fix our sites. We are letting you know that there appears to be something wrong with the latest package, unless there are special instructions that needed to be followed (and should have been more clearly posted).

. . . "So next time do a proper way to update and don't use the drupal interface to do it."

Well, duh. But its a bit like saying, "Next time, look both ways before you cross," to a guy who's lying in the street with two broken legs. You only say it to drive home a point that should have been clear. You don't say it as a means of coming to someone's aid. Do you see the point I'm trying to make?

BTW: in my case, after updating Views, relationships stopped working. Though I had already run the update script, I foolishly attempted to roll back my Views version, which wreaked havoc. It was only a test site, so no serious damage, though I am now looking at a few hours of repair work.

. . . "I'm pretty sure that this is not caused by views itself but by your way of updating modules."

I'm pretty sure it was caused by Views.

I think in my case the answer is probably found here:

http://drupal.org/node/1345132

perhaps that will help someone else.

Eric: Unfortunately, as far as we can tell, the problem appears to be caused by update.module, not Views. Think about it -- how does a module *make itself* go missing during an upgrade?

You don't say it as a means of coming to someone's aid.

Please take a look at the amount of traffic this issue queue gets. There are hundreds of thousands of users of this module, but only a very small hand full of people who spend time actually trying to answer people's questions. If you're going to berate someone who's trying to help for not having the lightest touch, the most likely scenario is that volunteers will simply stop answering because getting abuse isn't really worth the trouble of helping someone.

It's very hard to tell exactly why a module might go missing during an upgrade. It is known that the core update.module is not only less than perfect, it can be actively harmful. However, as module maintainers, there is nothing we can do about update.module.

So please, keep the accusations to a minimum. Try to understand that the people helping here are volunteers.

I'm pretty sure it was caused by Views.

Bold statements like this need to be backed up with some kind of evidence. OH WAIT. You're posting about a completely different issue. So not only are you berating dereine, you're also hijacking an issue.

I take it the real problem here is that something isn't perfect, and you're angry about it, and you want to take it out on us. That is, IMHO, unacceptable behavior. Please find a better way to interact.

Actually the comment above is just to long to read :) Easy to solve problem.

The module was completely gone, but my databases weren't effected. I just had to reinstall Views, and it was all there.

That's just crazy. update.module-- for that even happening.

(FYI drush has a MUCH better updating package than update.module)

Merlinofchaos:

First let me just say that I totally respect your response, and I have the utmost respect for anyone who volunteers to help users like myself when we get ourselves into trouble. I really didn't intend to make any accusations of any kind (and I honestly don't think that I did). My only intention is to point out the fact that a comment such as, "You must have done something wrong," is not a helpful statement.

"... If you're going to berate someone who's trying to help for not having the lightest touch, the most likely scenario is that volunteers will simply stop answering because getting abuse isn't really worth the trouble of helping someone."

Seriously, though I fully understand the above statement you have made, and I agree with you, and I do in fact now have a better appreciation for the efforts of the volunteers you speak of, I must point out that

A) I have not berated anyone.
B) Your response is a mirror of my response, to which you were responding.

You didn't like my tone. Well, I just didn't really like dereine's tone, I guess. So we're in agreement, I think.

Again, I want to express my deep appreciation for the amazing modules which you have created. It is an amazing body of work, which, by the way, has allowed me to do some pretty amazing things with my websites. And by the way, my statement, "I'm pretty sure it was caused by Views," was meant purely as illustrative rhetoric, as I am obviously unqualified to make such an assertion.

Thanks,
-Eric