Notifications
Clear all

Move (/migrate) of wpForo from WordPress multisite/network subsite to mainsite

5 Posts
2 Users
0 Reactions
169 Views
Posts: 44
Topic starter
(@golabs)
Trusted Member
Joined: 4 years ago

My current setup is a WordPress multisite/network where I've split the different sections of my website over subsites:

  • main (located at "/", blog_id 1, publicly available)
  • shop (located at "/shop/", blog_id 2, logged in users only)
  • forum (located at "/forum/", blog_id 3, logged in users only)
  • other (located at "/other/", blog_id 4, logged in users only)

 

Although I do like to have it seperated I like to make maintenance of the overall design of the pages a bit easier as well as not having to duplicate the menu's after updates to the menu's. (The shop and other subsites have their own set of menu's with only the high level menu items of main and forum and these will not change over time.)

 

Also wpForo seems not fully WordPress network compatible when running it on a subsite as the 'is standalone' feature for Boards doesn't seem to function correctly 100% of the time with regards to rewrites (still have to figure out why this happens on my test environment). And e.g. v3.0.10 of wpForo Embeds shows "This plugin cannot be activated because required plugins are missing or inactive." when on "/wp-admin/network/plugins.php". But these things are all of less importance than my motivation mentioned above.

So moving (/migrating) the forum to the main-site is the logical step for me at this point as I'm preparing the new version of the website (build with Blocksy Pro theme + Greenshift Pro). Blocking access to the forum so only logged in users can access it is not a problem for me, I have that covered.

When I read the different posts about migrations then it's usually between servers or domains, not within a network setup so I want to validate my thought process.

 

My idea of the process to move wpForo between 2 sites within the same network is:

I'll use the default wp_ as prefix in the steps below. And I'll move wpForo from blog_id 3 to blog_id 1. Adjust the prefix and blog_id's to suit your situation.

 

  • Copy all wp_3_wpforo_* tables to wp_wpforo_* tables.
    I rather use a copy action here instead of a rename prefix so I leave the original situation as is as backup.

  • The wp_users and wp_usermeta tables are shared within the WordPress network setup so I don't have to do anything with them... is that correct?

    For the wp_users table I'm pretty sure nothing has to be done, with regards to the wp_usermeta table I'm close to 100% sure as well as I don't see anything like blog_id or paths in them...
    I see "wpf" references in meta_key's:

    wpf-acp-toggle
    wpf_read_topics
    wpf_read_forums
    wpf_all_read
    wpforo_read_topics
    wpforo_read_forums
    wpforo_all_read
    _wpf_member_obj


    Btw - is one set (e.g. wpf_read_* and wpf_all_read) perhaps legacy/remnants from wpForo v1, and if so - can they be safely removed from the usermeta table?
    When reading topics and forums I see the content of wpforo_read_* being updated and not that of wpf_read_*.

  • Enable wpForo plugin on the target main site (blog_id 1).
  • Copy the contents of /wp-content/uploads/3/wpforo/ to /wp-content/uploads/1/wpforo/.

    Then correct the paths in the column body of the wp_wpforo_posts table.

    Looking in the wp_wpforo_posts.body content I see e.g. <div id="wpfa-421" where in this example 421 reflects to the post_id of the media entry in the wp_3_posts table so perhaps I want to import those media posts also to the wp_posts table but then I need to update all those wpfa-x ID's to stay really in sync... mmm... that might not be worth the effort and I can life without the media attachments visible in the Media Library.

Are there any steps that I'm now overlooking and which should be added to the process?
Any paths or blog_id reference that need updating, or something like that?
And perhaps a better approach on moving the media for the Media Library?

4 Replies
Posts: 44
Topic starter
(@golabs)
Trusted Member
Joined: 4 years ago

Btw - is one set (e.g. wpf_read_* and wpf_all_read) perhaps legacy/remnants from wpForo v1, and if so - can they be safely removed from the usermeta table?
When reading topics and forums I see the content of wpforo_read_* being updated and not that of wpf_read_*.

In this thread I see that wpf_read_* and wpf_all_read meta_keys are from v1 and are no longer used by v2, I'll remove them from my usermeta table.

 

My other questions from the opening post still stand.

Reply
Posts: 44
Topic starter
(@golabs)
Trusted Member
Joined: 4 years ago

Additional question: via Settings > Export Settings I have all the data that is stored in the %wpf% records in wp_options, right? Is that including the setttings of the wpForo plugins?

Reply
Sofy
Posts: 5373
 Sofy
Admin
(@sofy)
Support Team
Joined: 7 years ago

Hi,

As far as we can see, everything appears to be correct now. However, we cannot guarantee that there won’t be any minor issues. You should complete the migration and thoroughly check to ensure everything is working as expected.

Additional question: via Settings > Export Settings I have all the data that is stored in the %wpf% records in wp_options, right? Is that including the setttings of the wpForo plugins?

Please note that wpForo options can be migrated using this tool. There are several checkboxes you can check to select, but these do not include the addon settings.

Reply
1 Reply
(@golabs)
Joined: 4 years ago

Trusted Member
Posts: 44

@sofy thanks. The settings of the add-ons are the easiest to manually set again so I don't overly worry about those. Knowing that the core settings can be migrated this way is very nice.

 

Are the usermeta keys wpf_read_topics, wpf_read_forums and wpf_all_read indeed legacy ones which can be removed safely?

Reply