Colin

@spraveenitpro Thanks so much!

@mrfrent37 thank you. This is extremely helpful. I’ve alerted the woothemes support crew of your tests and I’ll let you know what they say.

Cheers!

P.S.

I’m sorry to do this, but until I hear a response from either, I am posting this issue to both the WooThemes support system AND this support thread, because I’m unsure of which one is recommended. Let me know for future reference.

Cheers!

UPDATE:

I have confirmed that this is related to the new “Payment Methods” endpoint (i.e. the output of woocommerce_account_payment_methods();).

1. I created a new staging site with WC 2.5.5 (the version prior to 2.6 release), and Stripe 3.0.2. This is what the My Account page looked like (you’ll notice 2 instances of the “Saved Cards” section, one is the default which the Stripe plugin hooks into the woocommerce_after_my_account hook, and the other is my own custom integration, in which I hooked WC_Gateway_Stripe_Saved_Cards::output into a custom action hook): [screencap]
2. Then I updated to WC 2.6 and where the default Stripe “Saved Cards” output was previously hooked (i.e. woocommerce_after_my_account) became empty.
   Additionally, the Saved Cards output function I was hooking into my tab container (i.e. WC_Gateway_Stripe_Saved_Cards::output) began throwing an error: [screencap]
3. So I removed my custom hook, and replaced it with the new WC 2.6 “Payment Methods” output function woocommerce_account_payment_methods();, and this is what I saw: [screencap]
4. Finally, I temporarily renamed my theme’s customized woocommerce/myaccount/myaccount.php template override, and allowed the default WC 2.6 core myaccount.php template file to be used instead. This is what I saw: [screencap]

As you can see, where there was once a saved credit card, there is now just a message saying “no saved methods found”. All the other my-account endpoints rendered their respective content properly (i.e. “Dashboard”, “Orders”, “Subscriptions”, “Addresses”, “Account Details”, etc.), but no saved cards were displayed in the “Payment Methods” endopint.

Has anyone else come across this?

It should also be noted that no WC or WP settings were changed during the above test. Here is a screen capture of my staging site’s WooCommerce > Settings > Checkout > Stripe: [screencap]

If need be I can provide Admin and FTP access to my staging site. You can feel free to contact me at colinsafranek (AT) gmail for access credentials.

Thanks in advance!

resolved-ish

Thank you!

Ok, I’m sorry, I guess I wasn’t clear in my original question.

Let’s just take one example:

Before the 2.6 update I used the following to display the “My Orders” section:

wc_get_template( 'myaccount/my-orders.php', array( 'order_count' => $order_count ) );

But now that the my-orders.php template is deprecated, I would like to use the orders.php template instead. But when I use the same function with the new orders.php template part, no orders are displayed. Instead it says “No order has been made yet.”

I tried the following:

wc_get_template(
    'myaccount/orders.php',
    array(
        'order_count' => $order_count,
        'user'        => $user,
    )
);

But I can’t get the orders to display.

So what parameters do I need to pass to the above function to get it working again?

That’s very disappointing ?? I was hoping you could at least point me in the right direction.

Not true, since we don’t load all the data at the same time as before.

Actually it is definitely true!

Scenario 1: load everything on the my account page at once – load time = 1 second

Scenario 2: load each section separately – load time = .5 seconds

If you have 5 sections on your my account page, scenario 2 will require 2.5 seconds of browser load time to view them all, versus 1 second in scenario 1.

Am I missing something?

Anyway, the best thing about WooCommerce is it customizability. If I switch to the new tabbed my account endpoints, I will be drastically changing my customers’ user experience, for the worse. It sucks that you aren’t at least telling me that what I want to do is possible, especially since it was possible in the previous version. I only want to continue doing what I’m currently doing, but you’re telling me that it isn’t possible?

C’mon man. Help me out.

I just need to know which parameters to pass to which my account template parts so that they render with the current user’s information (i.e. user object or user id). Can you help me with that?

Yes, I have already read that wiki, but it doesn’t give any information about how to render the endpoint content without using the endpoint system.

I would like to organize the myaccount page differently, and avoid having to reload the page for each section. Is there any documentation on that?

Is wc_get_template() a good method? Is there a better method?

In the 2.6 release announcement, they said the new tabbed my-account template was created to reduce load time for sites with many WC extensions, but if you only have a few WC extensions and the my account page loads fast already, this new tabbed system is actually slower than the old system, because the user has to wait for the page to load every time they switch between tabs. That’s not an improvement in my opinion.

Could you make any suggestions re: my original question?

It would be much appreciated.

@julien731 are you still planning to release an update with the patch for this?

Thanks!

colinsafranek AT gmail

Hi again Julien. Never heard anything back from you. Have you been able to troubleshoot this bug?

Let me know if you need anything.

Julien, do you mean you need access to an error log via ftp? Or do you just want us to copy/paste the errors we’re getting?

My error also only affects the WP Admin, preventing it from loading:

[31-May-2016 14:58:55 UTC] PHP Fatal error: Call to a member function is_main_query() on a non-object in /nas/content/staging/adaptify/wp-includes/query.php on line 744

If you need access to my staging site I’ll create a user for you. Would you need access to both the Admin as well as the server (ftp)?

Let me know what you need and which email to send credentials to.

Thanks!

+1

Same here. The error did not have a stack trace, so I don’t know where it’s originating from, but it occurred directly after updating to the latest Awesome Support version.

Please advise, thank you!