jongyc
Forum Replies Created
-
Thank you! I look forward to that update. 🙂
I don’t understand why we are going in circles and coming back to make sure all pages are assigned under Presentation » Store. I’ve clarified before that all pages are assigned under Presentation » Store pages. I’ve also clarified that I added shortcodes to each page to display the content that I wanted. If you’re telling me that defining all pages under Presentation » Store page options should fix it, then why is the checkout button on the shopping cart page not going to the checkout page? I reverted the plugin change that I proposed before and did a plugin conflict test like you requested and I’m still seeing the issue. If there are no further tests I can do to pinpoint the problem, then it must be the code I mentioned earlier and there needs to be a fix put in for that.
- This reply was modified 7 years, 11 months ago by jongyc.
I reverted the change to the plugin and ran a plugin conflict test. I deactivated one plugin at a time, flushing permalinks, and I’m still getting the same problem with the checkout page not redirecting to the correct page. Can you explain how the button with a link to /store/shopping-cart-2/ redirects to checkout correctly? Is it a redirect through the plugin? Is it a virtual page?
I would prefer to have things corrected with the plugin as-is in case the client updates the plugin again, which would remove the manual fix I applied.
I dug into the plugin code and found the following in /includes/common/class-mp-cart.php.
<a class="mp_button mp_button-checkout mp_button-widget-cart" href="' . mp_store_page_url( 'cart', false ) . '">' . __( 'Checkout', 'mp' ) . '</a>';The shopping cart link is being assigned to the checkout button. Is it supposed to be that way? When I change it to this:
<a class="mp_button mp_button-checkout mp_button-widget-cart" href="' . mp_store_page_url( 'checkout', false ) . '">' . __( 'Checkout', 'mp' ) . '</a>';…I get the desired results.
Sorry it took me so long to test this. I’m still experiencing the same issue with the checkout page. These are the steps I took.
- Create a checkout page and assign it to Checkout page under Store Settings » Presentation » Store Pages » Checkout.
- Add the shortode
[mp_checkout]to the Checkout page and save. - Starting from the store front page, go to products list.
- Add a new item to shopping cart.
- Navigate to shopping cart. Click “Checkout” button.
From the last step is where nothing happens. Clicking the “Checkout” button refreshes the page; I’m not taken anywhere else. Here are a couple of other findings though.
- “Empty Cart” button next to “Checkout” button works. I can confirm that it does clear the shopping cart.
- The checkout button takes me to “/store/shopping-cart-2/” instead of the page I created at “/store/checkout/”. There is no existing page for “/store/shopping-cart-2/”. Is this another virtual page?
- I can reach the checkout page by going directly to http://www.mydomain.com/store/checkout/. For some reason, it’s just not registering it to the Checkout button on the shopping cart page.
I’ve flushed my permalinks countless times throughout these steps.
I’m afraid I don’t know the version from which the plugin was updated. I wasn’t the one who performed the update so I can’t say. I do know that there was a database update required after the plugin was updated.
I did create a checkout page as you described, assigned it to the checkout page under presentation settings, and added the shortcode too. I can try again today. I will report back on my findings.
Hi marusic,
I checked the variable
$wp_scripts, and it looks like the handle for addthis_widget.js isaddthis_widget. If you enqueue the scripts, you can deregister the script like below.add_action( 'wp_print_scripts', function() { wp_dequeue_script( 'addthis_widget' ); }, 100 );Hope that helps.
I’m seeing the same notice too.
Having this same issue.
I too came across this issue after updating Yoast SEO plugin on my website. I did some checks and validation and the status of my website’s SEO is still good. Can this message be a mistake on the plugin’s behalf?