You might put this in the update notes.
I am just now seeing your image count suggestion and that did the trick. Thanks again!
Morning, I just updated to the new version. This is resulting in different effects, but is still not working for the site. We are no longer seeing the hashtag error message. We are now seeing outlines of where the image should be. Links work to follow to Instagram. I cleared my cache just to see if it was a local issue and this error still occurs. Let me know if you need more information and thanks.
If you happen to have the same or similar issue you may try switching to PDT method in paypal as this resolved my issue at the moment.
can’t say this would work for you, but I was able to get things going last night. We are on paypal so keep that in mind as I could not tell you if they use the same terminologies or not. Orders placed were being updated via IPN(instant payment notification) prior. Post update we were still receiving the IPN and I could see that IPN in the order notes section. I am not technical, but looked around enough in the paypal options to see there was another option called PDT and decided to enable this option also. PDT is being received in the order notes section, Status is updating, inventory is decreasing, and order emails are flowing at the moment.
If you knew what you were looking for like @helgatheviking is stating possible use of $order->ID then you could just do a search in all files on your site using a plugin called String Locator. In the example below I search $order->id, but I only bring up code being called out in woocommerce files it looks like so I would almost want to say that maybe helgas example may not be what is up. I am not super technical, but you could search the field in your error, see if a file pops up in a plugin folder path that might be named with a suspect plugin to help limit things.
Could also click through your site, while pinging your log to see if you can replicate the log error. If you can determine a possible click the sends the error or page load that sends the error, then you could compare sourcecode on that page/previous page depending on if you are clicking something, versus what you find in string locator to better pinpoint things.
-
This reply was modified 9 years, 1 month ago by caseydoes.
do you have this corrected yet?
