New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The logout functionality is very inconsistent and buggy... cannot figure out why. #28493
Comments
Hi @simplicity17, Thank you for submitting the issue. However, I can’t reproduce it using the steps you provided. Everything is working as expected on my end. I tested with Twenty Twenty and Storefront themes which are the default themes that we usually test against. Twenty Twenty: Storefront: The Woostify theme + Elementor combination you are using could the cause of the issue. Please test your site for theme and plugins conflict. To do that, you’d need to deactivate all plugins except for WooCommerce and switch the default theme such as Storefront. Then test again. If the issue is resolved with the default theme and all plugins deactivated, it means that one of your plugins or a theme is causing the issue. You will then need to enable it one by one and test every time you do that in order to figure out which plugin is causing the issue. You can also open the browser console as you are trying to log out and see what errors will be listed in the console (if any) when you can reproduce the issue. It often leads to an understanding of what could be going on. If you are on a Mac computer and use Chrome browser, you can open the console by using the |
Hi @simplicity17, As a part of this repository’s maintenance, I am closing this issue due to inactivity. Please feel free to comment on it in case we missed something. We’d be happy to take another look. |
Reopening to add feedback from #28619
Hi @simplicity17, Thank you for including more information on the linked issue. However, I also can’t reproduce it using the steps you provided. Everything is working as expected on my end, I tired with both the default My Account page and an additional page using the My Account shortcode Your video shows The Woostify theme + Elementor combination you mentioned. Can you provide a video or screenshots of your attempt with Wordpress 2020 theme and WooCommerce default barebones My Account widget/shortcode? Finally, it will be great if you could share your current System Status Report. You can get it by navigating to the WooCommerce / Status section of your site. Once there, click on the Get system report button and then copy it by clicking on the Copy for support button. Then paste it here in a comment. |
Thank you for reopening the ticket and for your help, has been very busy here and wanted Woostify to get back to me with their take on the bug. So this video is with Woostify theme and their WooCommerce Account widget and other widgets on the page, built with Elementor: https://www.youtube.com/watch?v=jNaXdRMM3wo&feature=youtu.be This last video is with 2019 Theme installed, haven't updated Wordpress yet, (it still appears styled because I have the header and footer templates set in Elementor) and the WooCommerce shortcode inserted on the My Account page with other widgets on that same page buit with Elementor: https://www.youtube.com/watch?v=mBuNQadeI4Q&feature=youtu.be Here is a video of it happening with Wordpress 5.6, 2020 theme, page built in Wordpress without Elementor with the barebones WooCommcerce My Account shortcode: https://youtu.be/AinsxSmqS94 It is some sort of redirect issue with WooCommerce, just don't know what is causing it. Site status below. NOTE: Before getting the site status data I switched the site back to Woostify theme since it doesn't appear to be causing the issue. I did not touch the My Account page from my last test (no Elementor, just the shortcode on the page) but the status says that it does not see the shortcode on the page... but the page does work, shows the login screen and then dashboard, just doesn't logout properly. Not sure if this is related. That data is what is attached. ` WordPress EnvironmentWordPress address (URL): https://tikumi.simplicitydesign.business Server EnvironmentServer Info: Apache SUHOSIN Installed: – DatabaseWC Database Version: 4.8.0 Post Type Countsacf-field: 31 SecuritySecure connection (HTTPS): ✔ Active Plugins (29)a3 Lazy Load: by a3rev Software – 2.4.2 Ajax add to cart for WooCommerce: by QuadLayers – 1.1.4 Inactive Plugins (0)SettingsAPI Enabled: – Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) Connected to WooCommerce.com: ✔ WC PagesShop base: #13 - /shop/ ThemeName: Woostify TemplatesOverrides: – Action SchedulerCanceled: 1 Complete: 17 ` |
PowerPack plugin was the culprit! Even if you don't use their login/register widgets, if you do not set the Login and My Account pages in their plugin settings, everything breaks. Going to report it now but just wanted to put this information here for anyone else having this issue! |
Thanks @simplicity17 for the update! |
When logging in, everything works perfeclty. When logging out, there are a number of outcomes.
There is a strange URL and a blank white page. URL reads https://tikumi.simplicitydesign.business/wp-login.php?action=logout&redirect_to=https%3A%2F%2Ftikumi.simplicitydesign.business%2Fmy-account%2F&_wpnonce=39b6cbd1fe
You are able to logout, but when you log back in, there is a notification on the My Account page that says "Are you sure you want to logout?". From here...
a) If you click the original Log Out button, you are logged out successfully.
b) If you click the "I'm sure I want to logout" button, you get the strange URL above and a blank white screen.
Even if you manage to logout successfully, the "Are you sure you want to logout" message appears. This is driving me crazy, I have no clue what is happening. This is my only website this is happening on. I am using the Woostify theme (my account page is built using their template system in conjunction with Elementor).
Thank you in advance for your help!!
View screen recording of what is happening here: https://youtu.be/jNaXdRMM3wo
The text was updated successfully, but these errors were encountered: