Update fails passing from 6.x-1.3 to 6.x-1.11

The reported query is not explicitly executed by the installation file. May you report which update function causes the error?

I changed the code, and added an update function to verify that the fields not correctly defined are added to the table. The changes have been committed in CVS.

Thanks for your report, and for the time took to find the cause of the problem.

So what is the recommended strategy? I'm in the same situation as the OP, going from 6-1.3-beta3 to 6.11. What versions should I upgrade to along the way?

6.1.3-beta3 >> ? >> ? >> 6.11

I'm not sure I want to use the -dev version...

See #6

Uh, hi. Maybe my comment was missed, so I'll repeat it. What is the recommended upgrade strategy? I'm in the same situation as the OP, going from 6-1.3-beta3 to 6.11. What versions should I upgrade to along the way?

6.1.3-beta3 >> ? >> ? >> 6.11

I'm not sure I understand what is "fixed"...

The status of this report refers to the issue reported from the OP.

When updating, it is always a better solution to not directly update, but to proceed with intermediate updates.

Yes, I understand what the status of this report is about. And I'd like to avoid the same problems that the OP had.

So your recommendation is seriously for me to go through TEN updates, one by one? If you have any recommendations about how to update in a more reasonable manner, it would really help... There are lots of people who have been stranded on one of the 15 or so various updates in the last 3 months, and expecting them all to update 15 times to get to 6.12 is asking a lot...

Quite simply, I don't understand what the fix is for this issue, and I'm asking for clarification.

@WildBill: Please don't set the status of an issue to active if you don't have any prove that this issue is still present; as you report you don't understand what the fix for this issue is, then it is probable you don't understand what this report is about (see what reported by the OP).

About the updates, nobody said you have to update 15 times; if you think that updating once could not cause any problems, then you are free to do so.

Jesus Christ. I just want to avoid the problem the OP had. Wouldn't it have been easier to explain how to do that, rather than spend multiple comments arguing with me about it?

From your non-answering of the question, I'm going to have to assume that you have no idea how to upgrade safely from 6.1.3 to 6.11. So that leaves me with no other option than to upgrade multiple, multiple times.

Forget this, I give up.

I just want to avoid the problem the OP had.

Simply don't install version 6.x-1.11, which is the version with the issue reported by the OP. The answer is not specific for Nodewords, as that is always valid for every version with an issue of every project.

From your non-answering of the question, I'm going to have to assume that you have no idea how to upgrade safely from 6.1.3 to 6.11.

The answer to how safely upgrade from version 6.x-1.3 to version 6.x-1.11 is the same answer that is valid for any other project. There is not anything in Nodewords that is different from other projects.

It's not needed to switch the status of an issue report to active, if you have any questions about the issue; changing the status to active makes other users think the issue has not been fixed, which is not true.

[quote]The answer to how safely upgrade from version 6.x-1.3 to version 6.x-1.11 is the same answer that is valid for any other project. There is not anything in Nodewords that is different from other projects.[/quote]

No, there is something different with Nodewords, and the answer is not the same as for other projects. In other projects you can skip versions when upgrading (you can jump from 6x-1.4 to 6x-1.9 for example), but you're telling me that for Nodewords I must upgrade one by one, every single version, until I finally reach the most recent version. Actually, you're NOT telling me that, I have to guess from your strange replies.

The only question I've ever asked in this thread, and the only one I care(d) about was: what intermediate releases are recommended between 6.1.3-beta3 and 6.11? But apparently you don't know, or you don't want to tell me. So forget it, I don't care anymore. You win.

what intermediate releases are recommended between 6.1.3-beta3 and 6.11?

Do other projects have recommended intermediate releases? For what I know, they don't.

If you want to update directly from version 6.x-1.3 to version 6.x-1.11, you are free to do it; I don't suggest to do that, especially if there are 3 − 4 update functions that update the content of 400 − 500 database rows, which could then block the update process because of timeouts, or other problems (including problems with the browser currently used). I have never said to execute the single updates, but I will never say from which version to which version update because that is irrelevant, as far as updating from version 6.x-1.3 to 6.x-1.11 is not done in a single step.

If then you still want to update in a single step, feel free to do it.