Limited Support
Our team is currently on holiday, so support will be limited during this period. Response times may be slower than usual, and some inquiries may be delayed.
We appreciate your patience and understanding, and we’ll resume our usual support by the end of August.
Hi,
I am hosted at wordpress.com, WordPress + wpForo
After restoring my site and forum with Jetpack Backup (A service from Wordpress.com ), my front end shows an empty forum, like when I started: 
It seems data are still here because I saw them on the admin panel: 
,
and I see also members in wpforo>members
On the other hand, there is nothing in "Category and Forums" 
, and I lost all my settings (Customize CSS, SPAM settings, etc.)
In wpforum>Tools, I see an error message on the "Database Tables" tab 
, but when I click "Solve database problem" it doesn't solve the issue.
When I try to do it by using phpMyAdmin Database Manager > WordPress Database > SQL Tab I get also another error message
#1062 - Duplicata du champ 'community' pour la clef 'unique_slug'
I don't know if my issue with the data stored, and the empty front is linked to this message error in DB, but I need support to fix my issue.
I need to be sure I can back up and restore mywpForo at any time.
Thanks
After more analysis with Phpmyadmin :
I see my forums on wp_wpforo_forums and vp_backup_wp_wpforo_forum
but my frontend show forums from wp_wpforo_6-forum
And I can see all the information in tables on the DB (Posts, tags, etc...). So my data are not lost but not well linked.
Please advise.
Reagrds
It seems wpForo show data from wp_wpforo_6_xxx tables when in fact they are all in wp_wpforo_xxx
The number 6 is coming from the board ID
Please advise.
Regards
Please edit the board in wpForo > Boards admin page, and change the Board Slug to forum-tmp.
Then go to wpForo > Tools > Database tables tab and click the [Solve Problems] or execute the SQL again, it should work now.
It'll create a new board with boardid=0. Once the board with boardid=0 is created, you can delete other boards.
Hi Robert,
it's fixed. Thanks for your quick support. 👍
