hi
i am using Privatemsg 6.x-2.x-dev latest version.
& i got this error
user warning: Table 'vividbase.pm_disable' doesn't exist query: privatemsg_is_disabled /* dhaval : privatemsg_is_disabled */ SELECT 1 FROM pm_disable WHERE uid = 1 in C:\xampp\htdocs\vivid\sites\all\modules\privatemsg\privatemsg.module on line 308.

plz help me..

CommentFileSizeAuthor
#6 privatemsg_fix_update_functions.patch3.68 KBberdir
#4 Quieries.png16.28 KBimDhaval
#4 errors.png43.33 KBimDhaval

Comments

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Postponed (maintainer needs more info)

Did you run update.php?

imDhaval’s picture

imDhaval commented
Status: Postponed (maintainer needs more info) » Active

thnx for ans. me
yes Berdir i did run update.php
but problem still occurs
need help......

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

Oh crap, I see the problem :)

Try re-running the 6007 update function.

We have an overlap there...

imDhaval’s picture

imDhaval commented
StatusFileSize
new errors.png43.33 KB
new Quieries.png16.28 KB

ok!! i re-run the 6007 update function of Privatemsg module
& it works ..
wow...

user warning: Table 'vividbase.pm_disable' doesn't exist query: privatemsg_is_disabled /* dhaval : privatemsg_is_disabled */ SELECT 1 FROM pm_disable WHERE uid = 1 in C:\xampp\htdocs\vivid\sites\all\modules\privatemsg\privatemsg.module on line 308.
error solved.

but i got few new things & i attach them below, just look at them & tell me about them
thnx

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Title: user warning errors » Renumber update functions in 6.x-2.x to avoid overlapping with 6.x-1.x

Thats ok. These errors happened because the function 6008-6010 were run a second time.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Active » Needs review
StatusFileSize
new privatemsg_fix_update_functions.patch3.68 KB

Ok, here is a try at fixing this mess :)

Basically, all update functions that were added in 6.x-2.x are renamed to 620X and a a check is added for most of them so that they are not run twice for those that are already using 6.x-2.x.

I need some confirmation that this works correctly, bot upgrading for 6.x-1.x and 6.x-2.x. For 6.x-2.x, there shouldn't be any errors/messages at all and for 6.x-1.x it should run all update functions without errors and everything should work correctly on the site after that.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Status: Needs review » Fixed

Commited.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.