Well currently it just returns sql errors. I am running the query on the whole database should I click into the table before running it?

No – you run it at database level.

I am sorry if it is returning errors but that can only be because it has not been entered properly. The query itself is sound and checked. (with the exception of the stray quote at the end which was a typo)

You DO need to enter those angle brackets in manually and you DO need to check the table prefix is correct for your database. ‘wp_’ is just the default.

I agree this is a major problem for you but please do understand that this is a totally unique report after large numbers of users have upgraded PM with no issue. This makes it remarkably difficult to try and analyse and diagnose and reach any conclusion as to why it is happening. Hence trying to take this one small step at a time. The first step being to discover how much data is found to be a part of the upgrade process.

You know what. I might be wrong about that query. Let’s turn it around at try it this way:

SELECT DISTINCT title, message_slug FROM wp_sfmessages WHERE to_id != from_id ORDER BY message_id

Might have been another copy and paste error for which I deeply apoligise.

I have updated the table name to match the table being used. I also typed the whole thing by hand without pasting.

I will try again this evening. When I first upgraded it deleted the old table but didn’t populate the new tables with the old PM’s. I also tried replacing the old table and performing the un-install and reactivate as you instructed me to do and it doesn’t delete the old table and re populate the new ones.

Okay thanks I will let you know how it goes.

Hi,

I ran the query and it returned all of the data.

And how many rows in total?

48, which is the correct number of rows in the db.

That’s very disappointing. I was kind of hoping for a really big number so that at least we could perhaps feel that a timeout was the issue and that we could probably deal with. But 48 is such a very small number…

I have to admit to having no idea whatsoever. Steve (Mr Papa) – anything you can come up with?

I believe that the only way I can progress this is to actually have a copy of the database so I can monitor the activity during the upgrade process. I assurer you I have no interest in the content whatsoever but it is going to be the only way to catch this issue.

Hi can you provide me with a way of sending the sql file to you?

Sure – you can zip it up and email it to me – support at simple-press dot com – and we can try an upgrade here to see what happens.

You would also need to send me (either in the email or a PM here) login credentials of an SP admin so I can actually get into the site to run the upgrade from the admin.

All material will be removed as soon as the problem is diagnosed.

Email sent

I included the whole DB file so it may take a while to get to you.

Sorry busy day ill zip it and send it.

Oh this is one of those so, so stupid errors but there agauin totally forgiveable. Well I think so anyway!

Tell me – do you know how to add a new column to a database table? Or – perhaps easiest – run this small script to do it for you (below)

You will need to perform all of this on the database BEFORE trying to activate PM. In other words – your original database with SImple:Press updated but PM not yet activated. Run this script:

ALTER TABLE ironpalmprodsmemberssfmessages ADD (attachment_id BIGINT(20))

And then activate PM and let;s see where we are after thatr.