The easiest would modify the post_author in wp_posts table in the database.
Do not know if this will break anything, have done it like this several times, has worked for me.
What has changed in 2.6 RC6 ?
Just noticed this is available to download, cannot find any info about it.
Postmeta size should not be that big.
I have 2.6m+ posts and it is way smaller.
Can you make a query and list, how many distinct meta_keys you have in your DB.
This is what i have found out taking the whole of GDPR into account.
The biggest issue actually is logging IP addresses. (sensitive data)
IP address is data which you can use to find out a persons location (in collaboration with ISP).
But since this is a forum, comments itself are not personal data, but IP addresses are.
In Terms and conditions it should be clear that IP addresses are collected, they are visible to the persons with the following rights.
If a person requests removal of IP addresses related to them, then you should not do that right away. It needs to be clear what is the time legally when somebody can file a complaint legally against a comment.
Then you as a service providor need to keep that data available and not delete them right away due to legal regulations.
The same thing comes into play if a person requests to delete their account.
No idea if this was the most optimal way to do it, but did it like this :
<?php
$val2=bbp_get_user_id();
$val3=get_current_user_id( );
if ( current_user_can( 'moderate' ) OR $val2 == $val3 ) :
?>
Anything you want the moderator or logged in user to see.
<?php endif; ?>
Modified all the user-*****.php files like this.
Also in other template files I modified the code so usernames are not linkable to their profile.
Is there anything that could be done do get the 2.6 release out sooner ?
Have a large site + a test site (where i can play around in with newer releases) with 2m replies and about 200k topics.
Is RC5 safe to use on a live site ?
Have a huge site and willing to experiment 🙂
Threaded replies is disabled.
The problem is that pagination is showing, but the filter above does not affect pagination of single forum view. Single forum view topic pagination count can only be edited by changing the global value in settings, but i do not want to change it from there inorder to give different posts per page value to mobile users.
I Have a site with about 2 million posts (topic+replies total), have seen errors like theese before.
Your problem is not with bbpress, but with wordpress in general.
Turn on your mysql-slow log and see what query is causing the problem.
Probably you’ll see SELECT SQL_CALC_FOUND_ROWS listed there.
So the post appears in “Activity”, but not in other views ? (general forum view etc.)
This is probably not a bbPress problem, but it is caused by a plugin you use for cacheing.
You could always turn-off whatever plugins you are using (not neeed for forum to lose functionality) and then see if everything is OK.
Conversion is done.
On the last one i used 10000 rows, 0.1 sec delay.
Did a total of 3 conversions, the third one succeeded.
The first two conversion failed because i started getting ———– lines.
Split the conversion into two, 1.5m and 1.5m. Topics that haven’t been replied to since 2012 will get imported at a later date.
Took about 9-10 hours.
The custom importer is already tested and everything is working properly.
The odd thing is that after 2 million rows the converter slows down noticeably.
Doing a stop/start for the conveter only helps for 10 minutes or so to get the speed up again.
Also i can see, that memory/cpu usage went down noticably after 2m, so a lack of resources is not a problem here.
No problems.
Just experimenting anyway in a test environment.
Managed to speed up the process a little.
Currently converting at the speed of 130 000 rows an hour vs previous 95 000 rows/hour.
Do not know exactly but the slow speed might have to do with the fact that in the old DB post/reply content is stored in the DB in a serialized array and i added a function to unserialize all the data during the import.
For some reason at 2 million post rows a big drop in speed, statistics show that MySQL command ratio dropped by three times compared to normal.
Had to stop/start the converter to get back to the normal speed.
