Support Forum
sounds like jquery conflict... see: http://codex.simple-press.com/.....-conflict/
do yo have link to site so we can check for obvious conflicts?
Visit Cruise Talk Central and Mr Papa's World
When you say 'are not visible' can you give some details? Is anything visible? Do you see the PM framework?
And are you able to look into the database tables? If so do you have a table named (wp-prefix)'sfmessages'? And if so does it have any data in it?
Oh yes - and remembering you had that annoying problem upgrading from V4 - when you reset all the permissions do your members still have permission to use and see PMs?
YELLOW
SWORDFISH
|
Hi,
I can see the plugin frame work and after looking in the database and sfpmmessges and sfpmrecipients both have no data.
This is all in a local environment not our live site but I used the same database to create the local site before beginning the upgrades. I am not sure where the messages have gone.
Ash
then you dont have the private message plugin installed... is pm plugin the latest version? that indicates you did upgrade the pm db since the table Andy asked about is removed in favor of the new ones... but there has never been an upgrade of pm that went south like that...
do you have a db backup from before the upgrade and could look for its tables?
when you upgraded to 5.x, did you do it with no plugins active until after the upgrade?
Visit Cruise Talk Central and Mr Papa's World
I am not quite sure what Steve (Mr Papa) was getting at there either... But he is right about a couple of things. We have had no reports of problems upgrading PMs - and a very large number of users have done that now. And there is clearly something going on that has caused the problem for you. Sadly - you have not had much luck so far upgrading and I am sorry to learn of that.
The only thing I can suggest - and Steve may have other and better suggestions when he visits later on - would be for us to take a look at the 'sfmessages' table from the backup DB simply to see if we can run the upgrade here under test conditions to see if there is a failure point. That has to be your call of course.
as to your other question - I am unsure of what to say to be honest. The problem you had with the upgrade from V4 to V5 is one that a few users have had but one we have been unable to locate a cause for. It has been the case where a user has had the problem - reverted to a backup and then retried with no issues. We have also been given whole databases that had shown the problem to see about recreating it here and again - we have never been able to replicate it. It has, to be honest, been a very trying and very hidden issue although thankfully seems to effect few even if apparently random.
Your solution to the problem - while a nuisance - is the best way to resolve it and 'clean' up the data.
YELLOW
SWORDFISH
|
1 Guest(s)