By timmeh on

we are using drupal 6.19 and ubercart 6x-2.4. when we make changes directly in the database on multiple nodes at once, like price changes and weights on the products through the database, there is no change in the item unless (through trial and error) i edit and resave the item without changing anything, just resaving the node. we've ran cron, php update..everything. is this a common problem? how can we have the site reflect changes immediately after making changes to the database??

Comments

jfarry’s picture

jfarry commented

Honestly, that sounds like a caching issue.

I know you said, 'we've ran cron, php update..everything' but does the 'everything' include dumping your cache? yoursite/admin/settings/performance "Clear Cached Data" at the bottom of the page is the quickest way :)

timmeh’s picture

timmeh commented

yes we've cleared cache by going to admin/settings/performance as well. its just not taking. is this common at all? anyone experience this?

timmeh’s picture

timmeh commented

my co-worker thinks that this is the issue on this guys blog

http://caritatis.wordpress.com/2010/06/18/fixing-paths-in-drupal-database/

any thoughts?

timmeh’s picture

timmeh commented

anyone have this problem?

timmeh’s picture

timmeh commented

bump

timmeh’s picture

timmeh commented

OK, we are still having this problem. maybe i should clarify with a specific example.

this is what's happening:
we are using ubercart and we changed all the product dimensions to 36x6x6 for all products in the database directly.
the database reverts back to "0x0x0" when looking directly at the database, but when we edit the product it shows "36x6x6". so what we've had to do is basically "edit > save" without making any changes at all.

this is just weird. the database reverts back to old values, but shows up when we try and edit the node.

anyone have any ideas?? anyone??

transformative’s picture

transformative commented

I have had similar issues when I have made changes in the database, and re-saving the node cleans everything up and fixes the problem.

In my most recent case, the View Bulk Operations (VBO) module enabled me to re-save many nodes in one go. This fixed my problem.

In case you're not familiar with it, VBO automatically creates a handy alternative view for administering your content. It can be found at admin/content/node2 (I generally go into this view and change its URL to admin/content/node, as I prefer it to the standard Drupal content view).

Once in the admin/content/node2 view, I:

  1. backed up my database
  2. filtered for the content type I wanted to change and clicked "Apply";
  3. (you may also want to filter for Published nodes, to make sure you don't accidentally publish nodes that are meant to remain Unpublished)
  4. clicked the checkbox to the left of "Title" in the header row of the view;
  5. clicked the "Select all ### rows in this view" button;
  6. selected "Publish post from the drop-down menu";
  7. and clicked "Execute".

(In my particular case, I ran out of memory and it wouldn't save all 1,000+ nodes at once, so I just changed the view to show me 400 nodes at a time, and executed the bulk operation on each page of the revised view.)