Forum Replies Created

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter j3d3s3

    (@j3d3s3)

    In our server the port 465 was blocked. The “Easy WP SMTP” plugin was configured to send the email through SMTP using that port (SSL – 465 – smtp.gmail.com). So when BPS was trying to send the email (successful admin login email) using “Easy WP SMTP” configuration it was stuck since the port 465 was blocked in our web server. It took almost 5 minutes to login (probably timeout on Admin login email process). So when I changed the settings from “BPS Security->Login Security->Login Security & Monitoring->Logging Options->Log All Account Logins” to “BPS Security->Login Security->Login Security & Monitoring->Logging Options->Log Only Account Lockouts“, it does not have to send email on successful Admin login, so it goes in immediately. When we opened up the port 465 in the server, BPS was able to send the email using “Easy WP SMTP” configuration and it goes in immediately even with the setting “BPS Security->Login Security->Login Security & Monitoring->Logging Options->Log All Account Logins“. Hope this helps. Thanks.

    Thread Starter j3d3s3

    (@j3d3s3)

    I disabled all the plugin and found out that the “easy smtp email plugin” was forcing the BPS to send email through smtp. But there was a port issue with the server in sending smtp emails. So the BPS is trying to send the email (when admin login happens) using smtp and the server was holding the process. As soon as we corrected the server issue for smtp, the BPS is working great as usual!

    Thank you so much for taking great effort in making the plugin a wonderful one! We have been using the plugin for few years now and never seem to have the issue with the plugin – always something else!

    Thread Starter j3d3s3

    (@j3d3s3)

    Found out that it works for “What to show? -> html5 options and does not work for flash”.

    Thread Starter j3d3s3

    (@j3d3s3)

    Thank you for the update. As it has been three months to resolve this issue, hope you are able to support the free version as well reasonably.

    j3d3s3

    (@j3d3s3)

    I have about 10 blogs. So buying one license would allow me install in all of these blogs? or would I need separate license for each of them? Thanks.

    ***SOLUTION***

    I have successfully converted my multisite from non-www to www using the following method. Please be cautious and backup your db before doing it. Also read all the following instructions completely before starting the process.

    1. edit wp-config.php and change
    from
    define(‘DOMAIN_CURRENT_SITE’, ‘mydomain.com’);
    to
    define(‘DOMAIN_CURRENT_SITE’, ‘www.mydomain.com’);

    2. get the search & replace script from https://github.com/interconnectit/Search-Replace-DB and read the instructions on the site on how to use it.
    It is straightforward as explained below. Put the downloaded script in your website home folder and go to http://mydomain.com/searchreplacedb21.php
    step1: select the pre-populate the db values option and clik submit
    step2: check your pre-populated db details and click submit
    step3: select the tables (select 10 at a time: If you select all of them, the script execution time might exceed and would fail. So either select few tables at a time or increase your script execution time in your php.ini). Do not select “Leave GUID column unchanged”, so leave this unselectecd. Because this is the reason (to update GUID) we are using this script to update the db.
    step4: search for “http://mydomain.com” and replace with “http://www.mydomain.com”. ***NOTE***: here make sure to put the http:// infront of your domain in your search terms, because you will have entries in the db for folders such /home/blahblah/public_html/mydomain.com and you do not want to replace these instances. So you have to search and replace for http://mydomain.com to http://www.mydomain.com
    step5: The results shown on how many are replaced on the selected tables. Now use browser’s back button to go back to step3 and select the next set of tables and continue the process until you finish all the tables.

    3. During the search & replace process, let us say you would start search and replace from http://mydomain.com/searchreplacedb21.php and in the middle it might say permission denied. Because for the main domain the path would have already changed to http://www.mydomain.com. So if this happens visit http://www.mydomain.com/searchreplacedb21.php and restart the process and complete the search and replace for all the tables.

    4. delete the file searchreplacedb21.php from your domain.

Viewing 6 replies - 1 through 6 (of 6 total)