By Passionate_Lass on

Hello.

The site I am working with is a live site. I was doing some routine theme modification and adding a video archive when things went... weird.

I took it upon myself to provide the client with an update. I updated the modules he had that were out of date. I completed the work and everything seemed fine.

Next day, there's a problem with the theme modification I provided and it took restoring the old modules and modifications to the css theme file to fix the problem.

Now, I cannot access admin/build/views or any of the views the site uses.

When I view the home page this error is created in the log. Homepage does not use any views.

include_once() [function.include]: Failed opening '/views_cache.inc' for inclusion (include_path='.:/usr/local/php5.2.6/lib/php') in /usr/home/cust25/www/htdocs/sites/all/modules/views_filterblock/views_filterblock.module on line 9.

include_once(/views_cache.inc) [function.include-once]: failed to open stream: No such file or directory in /usr/home/cust25/www/htdocs/sites/all/modules/views_filterblock/views_filterblock.module on line 9.

When I view the video archive I created which is a view, it comes up as page not found.

I do not understand what is going on and I need to fix this by tonight.

Feel free to ask me any questions needed to resolve the problem.

My MSN is me@kristinahall.ca

Ciao

⋅ Categories: Drupal 5.x

Comments

dadderley’s picture

dadderley commented

Just to be clear, you updated some modules (including views) then you had some theme problems. So you got rid of the new modules and put the older ones back in. Now you have the problem with views. Is this correct?

First off, when you encountered the problem and went back to the older modules, did you restore the site from a back up?
I am guessing not.
This being the case, all of the newer modules that you installed all have been updated in the DB. You can get rid of the actual module but Drupal is still running the modules with all of the DB modifications that happened when you ran the updates. This is most certainly what is happening with the views module. You are stuck with that.

You should back up your DB before you do anything else. Then you could try removing the older views module from the modules directory. After doing this, go to your site in the browser, then reload the page. Your error message should have disappeared. Now install the new views module (the version that you installed earlier), you probably will not need to run the updater as you have already done that. At this point your site will probably work.

If you have reverted to older versions of modules (after updating) the same will apply.
Good luck with it.

Passionate_Lass’s picture

Passionate_Lass commented

Hi.

I didn't have a database backup. Client failed to provide one and did not give me access to the database. I'm asking him if he happens to have one from before me working on the site.

I updated the modules, reverted the module files back, and now put back the updated module files. I'm still experiencing the issue however I'll give it another shot.

Passionate_Lass’s picture

Passionate_Lass commented

Hi.

I tried this locally and no go.

I still cannot access views administration (no link) and when I do go to admin/build/views/

This is all I get:

Site building
This screen shows all of the views that are currently defined in your system. The default views are provided by Views and other modules and are automatically available. If a customized view of the same name exists, it will be used in place of a default view.
[more help...]

* There is a security update available for your version of Drupal. To ensure the security of your server, you should update immediately! See the available updates page for more information.
* There are security updates available for one or more of your modules. To ensure the security of your server, you should update immediately! See the available updates page for more information.

I get something similar if I go to admin/logs/updates (I added the d5.x updates module).

Is it possible this is caused by another module being out of update when the database is updated?

dadderley’s picture

dadderley commented

OK, it is becoming a little clearer.

As far as I know, Drupal 5 does not check for available updates and does not advise you to update. Drupal 6 in the other hand does.

You are running a version of Drupal 5 correct?
Check the the version of the views module to make sure that you have a Drupal 5 version of the views module.

A mismatch between Drupal 5 and a Drupal 6 module could be what you are experiencing.