I have a suggestion
-
Thank you for your great forum plugin and add-ons.
I have a suggestion.
Could you please just use member table as a default WordPress user table instead of creating Wpforo profiles DB itself?
I know Wpforo has a lot of community features, however, in case of me, I just need a forum feature itself. I don’t need community feature at all. Wpforo has an option to make it a community, so if an admin wants, then create a member DB for Wpforo community. In addition, the table ‘wp_wpforo_profiles’, the member profile has not been removed after I delete user on backend at the same time, so the member’s profile is left. It is against the GDPR clause.PLEASE do not create member profile table apart from WordPress’ user and usermeta table on DB.
Second, Please do not create too much data if an admin does not want. DB became so dirty due to unused data such as
Array ( [ID] => [user_login] => [user_pass] => [user_nicename] => [user_email] => [user_url] => [user_registered] => [user_activation_key] => [user_status] => [display_name] => [userid] => [title] => [username] [groupid] => [posts] => [questions] => [answers] => [comments] => [site] => [icq] => [aim] => [yahoo] => [msn] => [facebook] => [twitter] => [gtalk] => [skype] => [avatar] => [signature] => [about] => [occupation] => [location] => [last_login] => [online_time] => [rank] => [like] => [status] => [timezone] => [is_email_confirmed] => [secondary_groups] => [fields] => [name] => [cans] => {s:2:" [description] => [utitle] => [role] => [access] => [color] => [visible] => [secondary] => [groupname] => [profile_url] => [stat] => Array ( [points] => [rating] => [rating_procent] => [color] => [badge] => [posts] => [topics] => [questions] => [answers] => [question_comments] => [likes] => [liked] => [title] => [rank] => ) )Last login and other db are useless and it burdens DB a lot. Please concentrate on the forum itself, and add community features only who want as an option.
Thank you for your great work again. Have a nice day.
Best regards,
Jen
-
Hi @stokim.
Thank you for the suggestion. wpForo Profile system is not against to GDPR. It’s a simple profile system. wpForo is has lots of option for GDPR. You can find all information in the documentation: https://wpforo.com/docs/root/gdpr/Wpforo has an option to make it a community,
Please let me know what option do you mean? wpForo always creates a community. There is no way to have forum without forum profile. The forum profile provides usergeoup and other forum specific information that is required for forum accesses and permissions.
@stokim,
The_wpf_member_objis a cache object. This is not a duplicated thing. This makes wpForo very fast, it doesn’t collect Users and profile information for each user on each page load because of_wpf_member_objcache object. This object is a collection of all user information in a one field. wpForo has built-in cache for users and for all other forum parts.wpForo only uses the cached user object, nothing else. The cached object = WP User + wpForo Profile Fields. wpForo profile table stores all necessary information in a one row which is much faster to get, than store all those fields as one separate row in bloated WP usermeta table. In any case
_wpf_member_objcache object makes all those easy to access and very fast to use without using hosting service resources for each user on each page load.Disabling wpForo Profile will lead many issues. wpForo forum accesses are based on Usergroup and Secondary Usergroups. All these come from profile system. The antispam system also depends on number of post, which also comes from profile system. I’m not talking about avatars, signatures, online status and reputation information.
About 1/3 of the current core have to be changed if we disable the profile system. So we should have strong advantages and reason. Having some more fields in user data is not a strong reason. Again, those data are being cached and doesn’t affect your performance much.
- The topic ‘I have a suggestion’ is closed to new replies.
