By blueblade on

Hi,

Blocks on my site has been unmovable for weeks now. I tried switching back to the original theme that Drupal is shipped with but that problem didnt go away. I also tried changing the weight numbers in my database (block table) but the numbers always go back to 128 (many of them have this number i am not sure if this is a bad thing)
Do I need to change the block weight number else where? I am not sure if this is caused by some modules. I have tried disabling some but that didnt help..

BB

⋅ Categories: Drupal 6.x

Comments

matt_harrold’s picture

matt_harrold commented

You can reorder your blocks on the admin/build/block page. You certainly don't need to hack the DB to do something fundamental like that.

blueblade’s picture

blueblade commented

the blocks keep moving back to their current locations after I save the changes...

ludo1960’s picture

ludo1960 commented

...you any custom modules? Seems very strange to me! This is not normal behaviour, problem must be hidden in a custom or modified module.

blueblade’s picture

blueblade commented

I have been trying to enable/disable modules for the past 6 hours. The strange thing is that sometimes I can move the blocks again after disabling a module but sometimes it doesnt change anything even after enabling/disabling the SAME EXACT modules (Adsense, UR, Rules etc) I am starting to wonder if this has something to do with server memory or php.ini...do you have any idea?

ludo1960’s picture

ludo1960 commented

..think it's a module issue.

PS I feel your pain, been there, seen it, done it and got the T shirt! Has to be a module!

blueblade’s picture

blueblade commented

I did try to change the weight numbers in block table (database) but ALL block weight numbers go back to the SAME EXACT NUMBERS after I save the changes...very weird...
Do you know if I should change something in 'variables' table also? what are stored in the table anyway, do you know?

ludo1960’s picture

ludo1960 commented

Not that I know of. maybe use phpmyadmin to check for corrupt tables. Then back to disabling modules!

blueblade’s picture

blueblade commented

how do you do that?

blueblade’s picture

blueblade commented

is there anything you can suggest me doing?

ludo1960’s picture

ludo1960 commented

Fire up phpmyadmin

Select your database

Scroll down to the bottom

Select check all

From the drop down menu that says "With Selected" select "Check Table"

Then repair any damaged tables

blueblade’s picture

blueblade commented

I have no idea how to fix these....can you tell what should be removed?

Problems with indexes of table `node_limitnumber_rules`
The indexes PRIMARY and limit_id seem to be equal and one of them could possibly be removed.

Problems with indexes of table `sessions`
The indexes PRIMARY and sessions_sid_idx seem to be equal and one of them could possibly be removed.

Problems with indexes of table `users`
The indexes PRIMARY and uid_2 seem to be equal and one of them could possibly be removed.

The indexes PRIMARY and uid seem to be equal and one of them could possibly be removed.

ludo1960’s picture

ludo1960 commented

Just select each damaged table by ticking the select box then click repair from the drop down, then buy me a beer next time you are in Scotland!

blueblade’s picture

blueblade commented

beer is good but clicking repair didnt fix the problem...

ludo1960’s picture

ludo1960 commented

Tables again. are they repaired?

blueblade’s picture

blueblade commented

problem still there. but i dont even understand what the problems really are...

ludo1960’s picture

ludo1960 commented

Now that you know how to check and repair tables, disable modules and repeat table operations unitil you find the culprit.

blueblade’s picture

blueblade commented

Do you know what are 'the indexes PRIMARY' and where to find 'limit_id'?

Problems with indexes of table `node_limitnumber_rules`
The indexes PRIMARY and limit_id seem to be equal and one of them could possibly be removed.
ludo1960’s picture

ludo1960 commented

of your modules uses this table, I dont have this table in my installation, so I dont know what module it is. But I am 99.9% sure that whatever module it is, that is the culprit! Some sort of rules module the table name suggests.

blueblade’s picture

blueblade commented

"indexes"?

blueblade’s picture

blueblade commented

what is "PRIMARY"? I have no idea what they mean and where to find them...and so I dont know which should be removed...

ludo1960’s picture

ludo1960 commented

Primary Indexes are properties of database referential tables, that allow for optimizing searching and joining, They are nothing to do with your problem. Explaining the workings of every type of database would take an eternity. All you need to know is that a module that uses the damaged table has to be dealt with.

blueblade’s picture

blueblade commented

I have just removed a table but the problem is still there, please read: Update: http://drupal.org/node/678850#comment-2455134

alan d.’s picture

alan d. commented

Do you have heaps of blocks? #293370: Block sort / reorder fails if more than 20 items may be related. Is the order saved when you save the blocks page with JScript turned off? Forget the database indexes - these will be unrelated.

It also could be a server issue - http://drupal.org/node/189292#comment-2302536

[The easiest way for testing these errors is to use FF + Web developer extension - you can toggle the JScript very easily from the Web developer toolbar.]

Alan Davison
blueblade’s picture

blueblade commented

Thanks for helping. I wont touch the database indexes anymore.

I am not quite sure what you mean by "Is the order saved when you save the blocks page with JScript turned off"? but I am pretty sure that I have tried moving/saving the blocks while having the JScript both on and off. I did contact my hosting company and show them http://drupal.org/node/189292#comment-2302536. Unfortunately I was told that nothing was wrong on their end.

Last night, I decided to turn off all modules in order to move the blocks - right now they are at the positions where I want them to be. However, I am not able to move them as soon as the modules were turned back on again. While doing what I did last night, I found that there is no one module that decides if I can or can not move the blocks - sometimes the blocks are movable when UR module is turned off, sometimes Adsense module, and last night I had to turn them and almost all other modules off before I could do anything to the block positions... I remember I had similar problem months before and was able to find out which exact module was causing them but certainly not this time.

I did try to change the block weight numbers on phpmyadimin a couple of weeks ago. The strange thing is that the weight numbers always get reverted to the original numbers afterward. I am just curious... does that mean the block weight numbers are saved in multiple places in the database?

gpashis’s picture

gpashis commented

I have the same problem here dont know what to do. Its keep on changing even after db edits.
Any help would be better.

Exom’s picture

Exom commented

I figured out including jquery.js between body tags causes this problem. After deleting this line i can change block weight on the page of building blocks.