Forum Replies Created

Viewing 15 replies - 1 through 15 (of 63 total)
  • Just two more pages and you would have found this: https://www.ads-software.com/support/topic/terms-and-conditions-not-showing/

    But, you are right, it appears quiet and totally different from the last time I posted a question.

    You know the old saying? “You get what you pay for”, maybe this is the threshold moment when “support” is equal for everyone, but more equal for paying customers…

    And I love WC, for all its foibles. ??

    tomaszmak

    If you paste the code you use to create the variable product and the code that you use to create the data/params passed to that, I would be happy to take a look and see how it compares to my code.

    @caleb My bad. From your profile I thought you were more ’embedded’.

    Thread Starter DRHughes00

    (@drhughes00)

    Update.

    First, thanks to both of you for indulging me on this.

    If there are no variations shown on the product page, there are no ‘prices’, and thus no price range is needed or shown.

    I have spent the last few weeks monitoring when this occurred and, as you correctly said, it is a zero stock issue – which resolves itself automatically (no pun intended, although I thought about it) when the item regains stock.

    So, resolved. With thanks.

    Dennis

    Is it permissible for other members to try and resolve? I have just been through this process with my own code and there are a few little anomalies not documented that take a bit of trial & error to resolve… imho.

    And @caleb – Would it be possible for people like yourself, who (I think) are part of automattic to be flagged as such? Claudio & Mike come up as “Plugin Authors” while you come up as a “Member”.

    Just a thought…

    Thread Starter DRHughes00

    (@drhughes00)

    @claudio

    @drhughes00 I just checked the code and is intentional.

    I have to say I am a little surprised at your answer, so please clarify.

    What is ‘intentional’ – I am sure that you do not mean that it is ‘intentional’ that (apparently) random products stop showing prices?

    If you do, then please educate me in the precise set of circumstances/product settings that result in this behavior – so that I can make sure that my product settings never fall foul of this again.

    I would also be extremely interested in your reasons for making such a “[bug]feature”.

    We are making progress however, as you now seem to know why the phantom ‘ – ‘ appears. That’s good, as soon as you tell me I can try and make it go away (hopefully). ??

    Dennis

    Thread Starter DRHughes00

    (@drhughes00)

    Hi Claudio.

    Did you watch the video? That was done on a bare site, no other plugins except query monitor running, and running storefront theme. I subsequently re-tested with an empty functions.php with the same result.

    You are correct in that the issue first came to light when I was loading the product base via the API – they are all loaded now and this is an issue with already loaded products.

    The video shows that the issue arises by merely changing the ‘Hide out of stock’ setting. No changes are made to the product either directly or indirectly via the API. To summarise, the product data stays the same – the only change is the “hide” setting.

    I am more than happy to accept that this is a problem with my installation, but having replicated the problem with no custom code or plugins running I really don’t know where to look next.

    Thread Starter DRHughes00

    (@drhughes00)

    Had a thought that the bbloomer snippet I was using to show the price as “From £0.10” instead of showing “From £0.10 – £23.00 might be the culprit for the phantom ‘-‘ – sadly it was not.

    Same result with an empty functions.php.

    I’ll keep looking (after all, it might be my setup of the products that is causing this) and checking and fixing all my products each day ?? until the answer….

    Did you guys have a chance to look at the video yet?

    Thread Starter DRHughes00

    (@drhughes00)

    Hi Claudio, I think it has nothing to do with my code: I can replicate the effect without changing anything – either directly or indirectly through the API, and, I have finally found a product that can demonstrate this effect at will. No changes to the product are required (which I hope eliminates my code as the cause) and simply hiding out of stock items from the catalog will cause this issue.

    Rather than try and explain, I have done a small movie for you – no admission fee (or, sadly, popcorn).

    If you could find a few minutes of your time to view I think that it demonstrates the issue more eloquently than I ever could.

    I ran this on a stripped down local copy with virtually nothing other than woocommerce running and using the storefront theme. The video is actually from the production site (the local copy runs painfully slow and I did not want you to get bored) but the result is the same on both.

    Versions: WC 2.6.2 WP 4.5.3

    Video here: Video

    As you can see, with no editing, either directly through the backend or indirectly through the API, the price displayed changes which follows through to the frontend where no prices are shown.

    Maybe there is something I am missing here that you will spot – I hope so as it will save me time each day….

    Thread Starter DRHughes00

    (@drhughes00)

    Thanks Mike & Claudio.

    I take all your comments to heart.

    Nevertheless, this issue is still extant.

    I have tonight tested the update to 2.6.2 on a local copy which seemed to work well. I will therefore be updating my production site tomorrow (after our nightly backup) and will then monitor the situation closely.

    Slightly frustrating, actually very frustrating, is that there appears to be no common feature to those products who suddenly display no prices.

    Anyhoo, will do the update and see what occurs.

    Thanks for all you guys do. Much appreciated.

    Dennis

    Thread Starter DRHughes00

    (@drhughes00)

    Thank you Mike.

    Looking at the 2.6.2 code, it looks as if the ‘fix’ did not make it to the release.

    However, it also looks as if the overall code has changed quite a bit so maybe the ‘fix’ was no longer needed…

    Should I go for 2.6.2 and hope that everything is fixed? Or stay with 2.5.5 and waste an hour each day checking that prices are not broken?

    I would appreciate a definitive response to how I should proceed – this is a real-life income problem to me and I cannot afford to have my income stream go down for any great length of time.

    Thread Starter DRHughes00

    (@drhughes00)

    Thanks for your reply Caleb. PHP BTW.

    I had already read the updated API docs which seemed to imply that all I needed to do was to include the settings posted above in my $options parameter when instantiating a new Client object.

    Is this the case, or not?

    Thread Starter DRHughes00

    (@drhughes00)

    Thanks for the reply, but I’ve fixed it.

    For anyone else with the same problem, the answer is to pass the fourth parameter ‘$options’ to the wrapper:

    $options[‘query_string_auth’] = true;

    $this->wc_api = new Client( $store_url, $consumer_key, $consumer_secret, $options );

    Details here:

    https://github.com/woothemes/wc-api-php/blob/master/README.md#client-options

    Dennis

    Thread Starter DRHughes00

    (@drhughes00)

    Hi Mike,

    If I decide to try it I will update you.

    Will probably just do my core stock (without variations) for now so the WC microdata already included should suffice.

    Thread Starter DRHughes00

    (@drhughes00)

    Thread Starter DRHughes00

    (@drhughes00)

    Thanks Mike.

Viewing 15 replies - 1 through 15 (of 63 total)