Pablo BJB

Hello @Pablo BJB,
1. Kindly take a look at this link:
https://www.conquer-your-risk.com/2022/11/30/4-websites-to-check-if-your-password-is-in-the-darkweb/
https://haveibeenpwned.com/
The above website (have i been pwned) should be helpful in exploring the possibility that your user's accounts were breached as part of various data breaches at various companies and compounded by potential password sharing. 
The above website (have i been pwned) allows you to enter the email address and it will show all the breaches for that particular email address (you might have to scroll down a bit to see the detailed breach history). 
As part of troubleshooting and diagnosis, kindly consider checking various email addresses of the users you suspect are posting spam (perhaps involuntarily due to things going wrong somewhere and them being a trusted user) in the above website (have i been pwned). If their credentials were breached, you will probably see their email addresses as part of multiple breaches. 
 
2. As part of further troubleshooting and diagnosis effort, you could perhaps contact the user (assuming you have their phone number - sms / call as you deem appropriate, or send a personal email to their registered email - different from the usual forum notification which they might not read) and perhaps convince them to change their password and add in a 2FA and see if the problem goes away. This way you might be able to mitigate the issue. Part of the problem in handling data breaches is that people don't know that their credentials have been breached. And as a friendly suggestion, you might want to word it in a way that doesn't set off panic in the contacted user : (hey, I need your help in troubleshooting an issue with the forum, something along the lines of that, describe the issue and long term trusted users should be more than willing to help you out). And (assuming) that if indeed the user's creds have been breached, your user would need to change the passwords on all affected services. 
 
Good luck with your troubleshooting and do keep us posted. 
 
Regards,
TwinTurbo. 
 
 

Glad to hear you've found the information you've needed here 🙂 .

What are your Posting settings here?

Larger original attachments are actually discarded and not saved. 

Hi, 
Is there an option to force which currency is being displayed by default, in a multi-currency setup?
I have a system with two currencies, the first one is a local currency (RSD) for items I am selling (forum merch etc.), but the second one is for community members and their adverts (EUR). However, the first currency is being shown by default in the Classifieds homepage. 

Ideally, I would like to specify which currency should be used for adverts and only that currency would show up to my members as a price (to specify a price and view a price as part of an advert). Or, in case of a multi-currency advert, if a person specifies just one price and leaves 0 for the second currency, then for that advert the specified price would always be shown. 
Thanks,
Ivan
 
 

Hello fellow forum owners, 
I want to share details of my experience with the upgrade process, so that it can help others who might face same problems as I had. My forum has about 90k topics and 1.9M posts, dating from March 2005. till now (https://forum.bjbikers.com). 
About 10 days ago I ran the upgrade process (it took about 9 hrs to finish) and even though I have followed the instructions precisely, I had to rerun it because charser wasn't converted properly. Second time I have ran the db convert utility from the command line and then it worked. Here is that screen and the cli command is the one at the bottom:

Mind you though that this DB conversion utility did not look the same as in the screen above, IPS should update their Running the upgrade instruction page.
After the upgrade process finished for the second time, my community was up, but the problems have just emerged in the form of background rebuilding stuff tasks. It was running those tasks very slowly even though I have used cron tasks. My community runs on a dedicated server with decent hardware (Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 16GB RAM, 2x2TB SATA HDD in RAID-1). However, cron tasks were doing very little dent to the background tasks progress, while at the same time my community was extremely unresponsive, with load times over 20 seconds. Progress for rebuilding posts was like 2 hours for just 1%. My sys admin has convered all tables to InnoDB, switched to the latest version of MariaDB, upgraded PHP to v7.0 etc, but very little improvement happened. It seems that Rebuilding Posts task is using disk extensively, which on my server was completelly stalling other db operations. Then we found the mysql setting which improved things significantly. 
The param which improved the background task progress is the innodb_flush_log_at_trx_commit, in conjuction with the update of innodb-log-file-size param from 1G to 256M. We changed the innodb_flush_log_at_trx_commit from default value of 1, to 2. It improved write speed significantly, changing the progress from 2hrs for just 1% to 20% done in just 1hr. It did cause one db crash, but overall it was a life saver. Here is the info about that parameter from MySQL documentation.
Now the community is running smoothly, but there are some issues with several users not being able to log in. Hopefully I will resolve this with IPS Support. 
Just one final note. I am quite disappointed with IPS Support during this upgrade process. I have asked for their help in terms of advices, but all I was getting as their response were some generic replies like íts not us, its your server etc'. I understand that it was my server setting, but I was hoping that IPS support engineers could point me in the right direction when it comes to server configuration, especially db server. If I didn't spent like 2-3 days constantly trying to figure out why that db was performing so poorly, while having my community offline, my community would take a significant hit and I would have probably given up on IPS software by now. I think that it is reasonable to expect that IPS support is able and willing to share advices on what are the common settings which can significantly affect the server performance since from what I can see, IPS4.X requires significantly more hardware resources than IP.Board 3.4.x. 
In any case, I hope that my experience can help someone still holding on to the v3.4 and planning to upgrade to v4.x.
 
 
 
 
 

Hello fellow forum owners, 
I want to share details of my experience with the upgrade process, so that it can help others who might face same problems as I had. My forum has about 90k topics and 1.9M posts, dating from March 2005. till now (https://forum.bjbikers.com). 
About 10 days ago I ran the upgrade process (it took about 9 hrs to finish) and even though I have followed the instructions precisely, I had to rerun it because charser wasn't converted properly. Second time I have ran the db convert utility from the command line and then it worked. Here is that screen and the cli command is the one at the bottom:

Mind you though that this DB conversion utility did not look the same as in the screen above, IPS should update their Running the upgrade instruction page.
After the upgrade process finished for the second time, my community was up, but the problems have just emerged in the form of background rebuilding stuff tasks. It was running those tasks very slowly even though I have used cron tasks. My community runs on a dedicated server with decent hardware (Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 16GB RAM, 2x2TB SATA HDD in RAID-1). However, cron tasks were doing very little dent to the background tasks progress, while at the same time my community was extremely unresponsive, with load times over 20 seconds. Progress for rebuilding posts was like 2 hours for just 1%. My sys admin has convered all tables to InnoDB, switched to the latest version of MariaDB, upgraded PHP to v7.0 etc, but very little improvement happened. It seems that Rebuilding Posts task is using disk extensively, which on my server was completelly stalling other db operations. Then we found the mysql setting which improved things significantly. 
The param which improved the background task progress is the innodb_flush_log_at_trx_commit, in conjuction with the update of innodb-log-file-size param from 1G to 256M. We changed the innodb_flush_log_at_trx_commit from default value of 1, to 2. It improved write speed significantly, changing the progress from 2hrs for just 1% to 20% done in just 1hr. It did cause one db crash, but overall it was a life saver. Here is the info about that parameter from MySQL documentation.
Now the community is running smoothly, but there are some issues with several users not being able to log in. Hopefully I will resolve this with IPS Support. 
Just one final note. I am quite disappointed with IPS Support during this upgrade process. I have asked for their help in terms of advices, but all I was getting as their response were some generic replies like íts not us, its your server etc'. I understand that it was my server setting, but I was hoping that IPS support engineers could point me in the right direction when it comes to server configuration, especially db server. If I didn't spent like 2-3 days constantly trying to figure out why that db was performing so poorly, while having my community offline, my community would take a significant hit and I would have probably given up on IPS software by now. I think that it is reasonable to expect that IPS support is able and willing to share advices on what are the common settings which can significantly affect the server performance since from what I can see, IPS4.X requires significantly more hardware resources than IP.Board 3.4.x. 
In any case, I hope that my experience can help someone still holding on to the v3.4 and planning to upgrade to v4.x.
 
 
 
 
 

Hello fellow forum owners, 
I want to share details of my experience with the upgrade process, so that it can help others who might face same problems as I had. My forum has about 90k topics and 1.9M posts, dating from March 2005. till now (https://forum.bjbikers.com). 
About 10 days ago I ran the upgrade process (it took about 9 hrs to finish) and even though I have followed the instructions precisely, I had to rerun it because charser wasn't converted properly. Second time I have ran the db convert utility from the command line and then it worked. Here is that screen and the cli command is the one at the bottom:

Mind you though that this DB conversion utility did not look the same as in the screen above, IPS should update their Running the upgrade instruction page.
After the upgrade process finished for the second time, my community was up, but the problems have just emerged in the form of background rebuilding stuff tasks. It was running those tasks very slowly even though I have used cron tasks. My community runs on a dedicated server with decent hardware (Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz, 16GB RAM, 2x2TB SATA HDD in RAID-1). However, cron tasks were doing very little dent to the background tasks progress, while at the same time my community was extremely unresponsive, with load times over 20 seconds. Progress for rebuilding posts was like 2 hours for just 1%. My sys admin has convered all tables to InnoDB, switched to the latest version of MariaDB, upgraded PHP to v7.0 etc, but very little improvement happened. It seems that Rebuilding Posts task is using disk extensively, which on my server was completelly stalling other db operations. Then we found the mysql setting which improved things significantly. 
The param which improved the background task progress is the innodb_flush_log_at_trx_commit, in conjuction with the update of innodb-log-file-size param from 1G to 256M. We changed the innodb_flush_log_at_trx_commit from default value of 1, to 2. It improved write speed significantly, changing the progress from 2hrs for just 1% to 20% done in just 1hr. It did cause one db crash, but overall it was a life saver. Here is the info about that parameter from MySQL documentation.
Now the community is running smoothly, but there are some issues with several users not being able to log in. Hopefully I will resolve this with IPS Support. 
Just one final note. I am quite disappointed with IPS Support during this upgrade process. I have asked for their help in terms of advices, but all I was getting as their response were some generic replies like íts not us, its your server etc'. I understand that it was my server setting, but I was hoping that IPS support engineers could point me in the right direction when it comes to server configuration, especially db server. If I didn't spent like 2-3 days constantly trying to figure out why that db was performing so poorly, while having my community offline, my community would take a significant hit and I would have probably given up on IPS software by now. I think that it is reasonable to expect that IPS support is able and willing to share advices on what are the common settings which can significantly affect the server performance since from what I can see, IPS4.X requires significantly more hardware resources than IP.Board 3.4.x. 
In any case, I hope that my experience can help someone still holding on to the v3.4 and planning to upgrade to v4.x.
 
 
 
 
 

There is a guide for that and I can confirm that it worked for me: