Search
Close
AI Search
Classic Search
 Search Phrase:
 Search Type:
Advanced search options
 Search in Forums:
 Search in date period:

 Sort Search Results by:

AI Assistant
Notifications
Clear all

Issues with private messages : wpforo 1.4.3

10 Posts
3 Users
0 Reactions
8,408 Views
Posts: 4238
 Tom
Admin
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@tomson)
Famed Member
Joined: 11 years ago

Addon doesn't delete any data in database without calling delete action by user. This is something impossible. This is a hosting service problem or database tables have been damaged. Also you may clicked on delete button accidentally. There is no way to delete messages on plugin update or activate/deactivate process.

In any case if you have database backup, you can restore the two PM tables.


Reply
Posts: 18
 Eric
Customer
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@veganostomy)
Member
Joined: 9 years ago

With so many of my users having this issue, what do you suggest I do to prevent it in the future?

As a sidenote, I updated from wpforo 1.3.1 to 1.4.3 around the time these problems began. I also updated to the private messages v.1.0.3 to 1.0.5 after updating wpforo. 


Reply
Posts: 4238
 Tom
Admin
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@tomson)
Famed Member
Joined: 11 years ago

The update doesn't matter. If you don't see the messages in database, it means they are deleted, that's it. if you're sure that messages don't exist in _wpforo_pms table you should follow to my suggestion above. Just restore the two table of PM addon from old backup files. There is no other suggestion here. Data are deleted in your database and the reason is not the addon. Ive already mentioned reasons above.


Reply
Posts: 18
 Eric
Customer
Topic starter
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@veganostomy)
Member
Joined: 9 years ago

But what about the "last pm date" in the wpforo dashboard? For me, it shows that my last message was 9 months ago when I know that's not true. Other users, who are actively posting private messages show 2 months or 9 months (and in between) as their last PM date when I know that messages are being sent recently (confirmed by looking at the database). 

Something must be off somewhere for these inconsistencies. 

Would uninstalling/reinstalling the private messages addon help?


Reply
Astghik
Posts: 6645
Admin
Translate
English
Spanish
French
German
Italian
Portuguese
Russian
Chinese
Japanese
Korean
Arabic
Hindi
Dutch
Polish
Turkish
Vietnamese
Thai
Swedish
Danish
Finnish
Norwegian
Czech
Hungarian
Romanian
Greek
Hebrew
Indonesian
Malay
Ukrainian
Bulgarian
Croatian
Slovak
Slovenian
Serbian
Lithuanian
Latvian
Estonian
(@astgh)
Illustrious Member
Joined: 8 years ago

Hi Eric,

We are sure that You deleted Your message, because wpForo couldn't delete messages, as Tom mentioned.

For "last pm date" please overwrite "wpforopm_stat_widget()" function

in function.php file, which is in " /wp-content/plugins/wpforo-private-messages/includes/ " direction.

We already fixed this issue and it will appear during the next update.


Reply
Page 2 / 2
Share:
Scroll to top