# Hoe betrek je Discourse het beste voor een groter WordPress magazine? **URL:** https://meta.discourse.org/t/how-best-to-engage-discourse-for-a-larger-wordpress-magazine/284394 **Category:** WordPress **Created:** [4 november 2023 om 09:51 UTC](https://meta.discourse.org/t/how-best-to-engage-discourse-for-a-larger-wordpress-magazine/284394 "2023-11-04T09:51:53Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![simon](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/simon/32/339122_2.png) [@simon](https://meta.discourse.org/u/simon) #### Post date: [4 november 2023 om 13:51 UTC](https://meta.discourse.org/t/how-best-to-engage-discourse-for-a-larger-wordpress-magazine/284394/2 "2023-11-04T13:51:31Z")
> [@Petr\_Mišák](#): > > But we’ve been running the magazine for about 13 years, and in that time we’ve had hundreds of thousands of comments and tens of thousands of registered users. > [@Petr\_Mišák](#): > > I’ll set up the [DiscourseConnect](https://meta.discourse.org/t/13045) Client The [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) client functionality works in a similar way to how other forms of social login work. For example, it’s similar to logging into WordPress through Facebook, but with your Discourse site as the authentication provider instead of Facebook. That means that before users can login to your WordPress site with [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true), they will need to create an account on your Discourse site. Not creating a Discourse account won’t prevent any users from logging into your WordPress site though. When the WordPress site is the [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) client, the normal username/password login on WordPress is still available. Since you have a lot of users who are used to logging into your WordPress site, it might be worth considering using your WordPress site as the [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) _provider_ for your Discourse site. If you set things up that way, all of your existing users will be able to easily login to your new Discourse site. All they will have to do is click a link on your WordPress site. Details about how to construct a link to do that are here: [Create a DiscourseConnect login link](https://meta.discourse.org/t/create-a-discourseconnect-login-link/109290). It sounds like you want to completely move the social aspect of your site from WordPress to Discourse, so possibly that would be a reason to not use your WordPress site as the [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) provider. My concern is that requiring users to create new accounts on Discourse, instead of just logging into their WordPress account and clicking a link to access the forum, might prevent some users from joining the new site. The main thing to be aware of if you use WordPress as the [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) _provider_ is that when things are configured that way, it becomes the only login method for Discourse. That means that you can’t have some users logging into Discourse through WordPress and other users logging into Discourse by registering accounts with a username/password on the Discourse site. All users will have to have accounts on WordPress to access the Discourse site. Let me know if the distinction between using WordPress as the [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) client and [DiscourseConnect](https://meta.discourse.org/t/13045?silent=true) provider is not clear to you. > [@Petr\_Mišák](#): > > I haven’t found any elegant way to transfer our users’ comments that are already published in WordPress to the newly launched Discourse. It’s technically possible, but I don’t think there is a well tested method of doing it. There might be some other members of this community who have ideas about how to approach it. > [@Petr\_Mišák](#): > > that a WordPress article will not be transferred to Discourse as hidden after publishing, but a Discourse thread will be created only when someone clicks on the link below the WordPress article and adds a comment? It might be possible. My sense is that it could lead to problems. On your Discourse site, you can filter out unlisted topics by adding the following query string to a URL: `?status=listed`. For example [https://meta.discourse.org/latest?status=listed](https://meta.discourse.org/latest?status=listed). There is an existing theme component that can be used to toggle between viewing “open” and “closed” topics: [Topic Status Filter](https://meta.discourse.org/t/topic-status-filter/111307). If it doesn’t already exist, it would be fairly easy for someone to add “listed” and “unlisted” status’s to that filter. But I guess for that case you would only want the filter to be seen by staff users. > [@Petr\_Mišák](#): > > And if it were to be absolutely perfect, then via a “magic link” from WordPress, the Discourse thread would only be created temporarily, and if by chance a comment wasn’t added and the user changed their mind/left, the thread would be deleted after some time. This could be accomplished from WordPress with an API request that was handled by a cron job. --- _[View the full topic](https://meta.discourse.org/t/how-best-to-engage-discourse-for-a-larger-wordpress-magazine/284394)._