davidtrebacz

No idea why. I can confirm that either pass Google Structured Data Testing tool.

Thanks @larsbuur. The only thing I’d add to the hack is to make the schema.org URL https:

'availability'  => 'https://schema.org/' . $stock = ( $product->is_in_stock() ? 'InStock' : 'OutOfStock' ),
<strong>'itemCondition' => 'https://schema.org/NewCondition',</strong>
sku'           => $product->get_sku(),

• This reply was modified 7 years, 6 months ago by davidtrebacz.

Thank you for the great response. I may have never noticed the issue since we didn’t have multi-country checkout.

I did try “Skip minification on JS files”. It didn’t change anuthing.

I am not using “Enable defer parsing of JS files globally”.

I ran https://www.glasshousestore.com/wp-content/plugins/woocommerce/assets/js/select2/select2.min.js

through the closure-compiler in the advanced mode. It showed no errors and 168 warnings… Not being a JS guy it really didn’t mean much to me, but I didn’t see anything really nasty…

Loading in the develop branch also solved it for me. Thanks for the quick response.

Here is a screenshot of the address in checkout:
https://cloud.trebacz.com/index.php/s/mhECpQhfkUdoUZv

Here is the paypal interface after logging in:
https://cloud.trebacz.com/index.php/s/3v4nB7qhzsYGKdQ

The sandboxed site is publically available at https://protodotglasshousestoredotcom -replace the dot with .

I can confirm that refund functionality is working correctly after applying 1.4.1 update.

To be more specific. I’m using the WC checkout page (with either a manually put in shipping address or my default same as billing address), choosing “PayPal Express” as my payment method (Stripe is my other choice).

After providing the login credentials to Paypal window, Paypal just shows the default shipping address in my Paypal account. Not the address I had in the WC checkout page.

My apache error log gives this when the error is produced:
`[Tue May 02 07:47:03.616226 2017] [:error] [pid 8395] [client 192.168.0.180:51867] The The “woocommerce_add_order_item_meta” hook uses out of date data structures and function is deprecated since version 3.0.5. Replace with woocommerce_new_order_item., referer: https://proto.glasshousestore.com/wp-admin/post.php?post=12525&action=edit
[Tue May 02 07:47:04.068989 2017] [:error] [pid 8395] [client 192.168.0.180:51867] The The “woocommerce_add_order_item_meta” hook uses out of date data structures and function is deprecated since version 3.0.5. Replace with woocommerce_new_order_item., referer: https://proto.glasshousestore.com/wp-admin/post.php?post=12525&action=edit’

Not to hijack, I did also get a refund error from my staging server when testing 1.4.0 on Woocommerce 3.0.5 in sandbox mode. This was an upgrade of our production setup in a staging environment.

It gives the error “An error occurred while attempting to create the refund using the payment gateway API.” in a popup in the browser. This happens on each order I try.

Arefund with the stripe gateway processes fine.

Thanks. The version 1.5.0 works great!

Thanks. Look forward to the debugging file.

I did change the php timezone on the shared server that I use, but GUI is still UTC. It looks like the localized time function for WordPress is: https://codex.www.ads-software.com/Function_Reference/current_time

It would be helpful if the GUI worked on blog time (localized time) vs having to adjust… ?? Right now what seems to be happening is I schedule the updates to run at midnight, 00 UTC in WordPress and they actually run at ~5pm (or 17) Pacific time.

I swapped out the wppfm-cron.php file with your changes. I let the automatic jobs run overnight (they run fine). Unfortunately the URLS’s are still not properly permalinked when created using the cron function.

Here is another feed file as an example:
https://www.glasshousestore.com/wp-content/uploads/wppfm-feeds/GlassBevels.xml

Cron generated links look like this:
https://www.glasshousestore.com/?product=quilt-star-bevel-cluster&utm_medium=cpc&utm_source=googlepla&utm_campaign=goolge_pla

Instead of the canonical version:
https://www.glasshousestore.com/product/quilt-star-bevel-cluster/?utm_medium=cpc&utm_source=googlepla&utm_campaign=goolge_pla

I added the supplied patch to the production site and have scheduled a cron update of one feed in the next hour.

I also noticed that the feed manager screen uses UTC time (vs local time in WordPress). I assume that also applies to the feed generation, so I set the schedule using UTC time. I would suggest to have all the settings in local time in the plugin.

Yes version 1.4.3. I’ll try the supplied patch today and let you know…

All the issues seem to be resolved in the latest update. Thanks…