hecttech08
Forum Replies Created
-
Forum: Plugins
In reply to: [Advanced Ads –?Ad Manager & AdSense] Rolled Back to Version 1.35Hello,
I can confirm the same happened on my Website. I already rolled back the changes since I saved them before updating.
I even tried to go back to ad placement settings to make sure it is still centered. But the issue remained.
@azizulraju Hello, Im still having issues with this. On my test website, it creates a WordPress subscriber, but not the free tier Memberpress subscriber.
Also, on the signup page it makes it look like you did not sign up. The Memberpress registration page just sits there, even though you do get an email to verify.
Have you tested it on my website?
Are you able to create an account and use all my webpages, or are you blocked?
@azizulraju it creates a normal WordPress subscriber but not a memberpress subscriber.
You are able to access the full website? No pages say access denied?
To confirm, you are testing all on my staging 9 site and ad not my main website? The main website does not have this plugin since it was not working.
Hello @elenachavdarova ,
To confirm, I won’t need to change anything on my page? It should work after the next plugin release?
Also, how long before the next plugin release. This way I prevent my main site form updating until then.
Hello Elena,
Thank you for your response.
To confirm, I won’t need to change anything on my page? It should work after the next plugin release?
Hopefully, this will help others with custom login URLs as well.
Hello Pavel,
I do have the paid version of Elementor, and it did not work before in the other post. This is the reason I had to have my developer look into fixing this issue in order to make it work with SiteGround Security. After this recent update, it no longer works. I went back before the update on my main page to get it to work again.
On the Staging page I linked above, after you enter your login credentials, it is supposed to bring you to the page to enter your 2FA if you are any role instead of Subscriber. If you are a Subscriber, it will bring you to a page inside the website that only logged-in users can see. It works like normal for Subscribers. For admin or any other role, it takes you to a blank white screen. Please see link for screenshots.
https://drive.google.com/file/d/1WD2PYWM-XUCq9GJlLnKTQKftMrM9znd2/view?usp=sharing
https://drive.google.com/file/d/1N98cfr151sLfvBw2oQPgX3mXUvOfoi8l/view?usp=sharing
https://drive.google.com/file/d/1mqjntcrK28DfXyTg0qzIh15ntQ8kpt3Q/view?usp=sharingThis is what he stated would be the solution.
“right now the function they are using ‘setcookie’ will update the cookie when page got reload, but in the code we need cookie in the same script so they need to update $_COOKIE global variable instantly so the value in the Cookie and value updating in Database match and it will detect the is_wp_login correctly”
However, it is not best practice to fix your core coding.
Can you see what we are talking about now?
Also, please let me know if there is a way to attach an image here.
We can show you the line of code that has this issue.
Hello,
I was just curious if there has been any progress on a solution for the issues I have with 2fa on a custom Login page?
Ok great.
Thank you for all of your help.
I will be waiting for a response.
If you need me to try something new, just let me know.
Yes, Siteground is my host.
https://www.staging2.collectahobby.com/login-page/
That is the staging site Url. Please let me know if you would like me to create an account for you to test as well.
Thanks again.
Hello,
Thank you for responding.
I just tested this. I cleared local and server cache.
Tried again on multiple browsers, same issue.
Also, weird thing is, I had no errors on Chrome debug browser. However, the Firefox browser showed warning/errors. I will post it below. Keep in mind, there are characters missing, looks like it’s a unique identifier for my username. So I won’t add that part.But should be enough for what is going on, or what is expected.
Cookie “buddyboss_user_sw_has been rejected because it is already expired. admin-ajax.php Cookie “buddyboss_user_sw_secure_ has been rejected because it is already expired. admin-ajax.php Cookie “buddyboss_user_sw_olduser_ has been rejected because it is already expired. admin-ajax.php Cookie “wordpress_ has been rejected because it is already expired. admin-ajax.php Cookie “wordpress_sec_ has been rejected because it is already expired. admin-ajax.php Cookie “wordpress_ has been rejected because it is already expired. admin-ajax.php Cookie “wordpress_sec_has been rejected because it is already expired. admin-ajax.php Cookie “wordpress_logged_in_ has been rejected because it is already expired. admin-ajax.php Cookie “wordpress_logged_in_ has been rejected because it is already expired. admin-ajax.php Cookie “wp-settings-0” has been rejected because it is already expired. admin-ajax.php Cookie “wp-settings-time-0” has been rejected because it is already expired. admin-ajax.php Cookie “wordpress has been rejected because it is already expired. admin-ajax.php Cookie “wordpress has been rejected because it is already expired. admin-ajax.php Cookie “wordpress_sec has been rejected because it is already expired. admin-ajax.php Cookie “wordpress_sec has been rejected because it is already expired. admin-ajax.php Cookie “wordpressuser has been rejected because it is already expired. admin-ajax.php Cookie “wordpresspass has been rejected because it is already expired. admin-ajax.php Cookie “wordpressuser has been rejected because it is already expired. admin-ajax.php Cookie “wordpresspass” has been rejected because it is already expired. admin-ajax.php Cookie “wp-postpass has been rejected because it is already expired.