Hi there,

When I upgrade the module to alpha 14, I notice that after I run update.php I get an error that says:

The following queries were executed
advanced_forum module
Update #5004

* Failed:
* Failed:
* Failed:

That did not look reassuring at all, so I tried to update it again, and got the same message.

After that, I checked back to my forums, and it looked like a mess, with text outside of where it was meant to be, and previously integrated modules not integrated.

Fortunately, I was able to restore all the files and run update #5003, in order to get back to the older version I was using.

That said, I'm not sure what happened when I updated this module. Did I do something wrong, or is anyone else experiencing this problem? Maybe update.php should not have been run. I would really like to be able to use the newest version of this module.

Thanks for your assistance!

Comments

nath’s picture

nath commented

Update 5004 is just deleting of unused variables. I don't think that is a problem if that fails. It just means that you already didn't have those variables.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Priority: Critical » Minor
Status: Active » Postponed (maintainer needs more info)

Yes, it's just cleaning up variables that I changed the name of several releases ago. It doesn't hurt anything and is just a one off thing so I'm not going to worry about it.

As to your problems: The style issue sounds as if you didn't copy over a fresh copy of the style. For the contrib integration, you need to follow the instructions in #326460: Finalize contrib integration API

Michelle

transliteration’s picture

transliteration commented

I've got the same notification, and just ignored it, but the forum still looks OK.

michelle’s picture

michelle
she/her
Primary language English
Location Wisconsin, USA
commented
Status: Postponed (maintainer needs more info) » Fixed

Guessing that was it, then, since no more info.

Michelle

Status: Fixed » Closed (fixed)

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