davidtrebacz

I’m also getting a similar error (not using Gutenberg editor). That error is preventing my Ship Easy integration from functioning (can’t pick up orders from our site). Enable publicize “fixes” it?

2018-12-01T17:32:00+00:00 CRITICAL Uncaught Error: Call to a member function current_user_can_access_publicize_data() on null in */wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-fields/post-fields-publicize-connections.php:118
Stack trace:
#0 */wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-fields/post-fields-publicize-connections.php(136): WPCOM_REST_API_V2_Post_Publicize_Connections_Field->permission_check(18798)
#1 */wp-content/plugins/jetpack/_inc/lib/core-api/class-wpcom-rest-field-controller.php(116): WPCOM_REST_API_V2_Post_Publicize_Connections_Field->get_permission_check(Array, Object(WP_REST_Request))
#2 */wp-includes/rest-api/endpoints/class-wp-rest-controller.php(394): WPCOM_REST_API_V2_Field_Controller->get_for_response(Array, 'jetpack_publici...', Object(WP_REST_Request), 'product')
#3 */wp-content/plugins/woocommerce/includes/api/v2/class-wc-rest-products-v2-c in */wp-content/plugins/jetpack/_inc/lib/core-api/wpcom-fields/post-fields-publicize-connections.php on line 118

I cannot tell you how happy I was to find this. I was trying to figure out why my state was changing when Angeleye’s (excellent) Paypal Express plugin was changing the state when passed back from Paypal. It was fine on all my local environments, but breaking on the production dreamhost VPS. I had been troubleshooting this on and off for 2 weeks. THANK YOU!

I went ahead and tested in rollback, using WP Rollback. It went fine in my staging environment, so I also did the same in production.

Same conflict with Mailpoet 3 here. Exact message in the dashboard is: MailPoet Error: MailPoet has detected a dependency conflict (\csstidy) with another plugin (/var/www/XXX.com/wp-content/plugins/fast-velocity-minify/libs/CSSTidy/class.csstidy.php), which may cause unexpected behavior. Please disable the offending plugin to fix this issue.

Mailpoet fails to run when the latest version of FVM is loaded. Mailpoet has a potential fix here:

https://beta.docs.mailpoet.com/article/204-resolving-conflicts-with-other-plugins

Right now I have disabled FVM, but may consider a rollback, if this goes long.

Host is Dreamhost VPS (AWS cache solution also). I’ll put a ticket into Dreamhost to ask.

After clearing opcache, Fast Velocity Minify cache and WP Super Cache the site seems to be operating fine. Not sure which one cleared the issue, but in my case it seemed cache related. Hope this helps. Cache clearing is not a normal procedure for us when taking upgrades.

This did start 3 days ago.

I have logging turned on. Here is the log for the test transaction above. I cannot replicate on our staging server:

====End Log====

01-23-2018 @ 21:49:22 – ====Start Log====
sources/{\”id\”:\”src_1BnfGFGbqsC9YjTbDg1iWdu7\”,\”card\”:{\”exp_month\”:5,\”exp_year\”:2020,\”address_line1_check\”:\”unchecked\”,\”address_zip_check\”:\”unchecked\”,\”brand\”:\”Visa\”,\”card_automatically_updated\”:false,\”country\”:\”US\”,\”cvc_check\”:\”unchecked\”,\”funding\”:\”credit\”,\”last4\”:\”4242\”,\”three_d_secure\”:\”optional\”,\”tokenization_method\”:null,\”dynamic_last4\”:null},\”bitcoin\”:\”\”,\”flow\”:\”none\”,\”object\”:\”source\”,\”status\”:\”chargeable\”,\”type\”:\”card\”,\”usage\”:\”reusable\”}
====End Log====

01-23-2018 @ 21:49:22 – ====Start Log====
Error: stdClass Object
(
[error] => stdClass Object
(
[type] => invalid_request_error
[message] => No such source: {\”id\”:\”src_1BnfGFGbqsC9YjTbDg1iWdu7\”,\”card\”:{\”exp_month\”:5,\”exp_year\”:2020,\”address_line1_check\”:\”unchecked\”,\”address_zip_check\”:\”unchecked\”,\”brand\”:\”Visa\”,\”card_automatically_updated\”:false,\”country\”:\”US\”,\”cvc_check\”:\”unchecked\”,\”funding\”:\”credit\”,\”last4\”:\”4242\”,\”three_d_secure\”:\”optional\”,\”tokenization_method\”:null,\”dynamic_last4\”:null},\”bitcoin\”:\”\”,\”flow\”:\”none\”,\”object\”:\”source\”,\”status\”:\”chargeable\”,\”type\”:\”card\”,\”usage\”:\”reusable\”}
[param] =>
)

)

====End Log====

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

I’m also getting a similar error. We have intermittent orders failing with Stripe (last 2 days). I placed the production server in test mode and got this error: No such source: {\”id\”:\”src_1BnfGFGbqsC9YjTbDg1iWdu7\”,\”card\”:{\”exp_month\”:5,\”exp_year\”:2020,\”address_line1_check\”:\”unchecked\”,\”address_zip_check\”:\”unchecked\”,\”brand\”:\”Visa\”,\”card_automatically_updated\”:false,\”country\”:\”US\”,\”cvc_check\”:\”unchecked\”,\”funding\”:\”credit\”,\”last4\”:\”4242\”,\”three_d_secure\”:\”optional\”,\”tokenization_method\”:null,\”dynamic_last4\”:null},\”bitcoin\”:\”\”,\”flow\”:\”none\”,\”object\”:\”source\”,\”status\”:\”chargeable\”,\”type\”:\”card\”,\”usage\”:\”reusable\”}

Thanks for the quick fix (and an awesome plugin)! Applied the update on my sites – and all is good. Especially since it wasn’t raised in all setups. In my case it showed publically in all three of my environments.

I turned off php 7.0 strict error reporting and the error still surfaced on pages.

I experienced corruption twice since the update. Site is stable then all of a sudden wp-cache-config.php becomes corrupt and breaks the entire site. In my case the corruption is the first few characters are replaced “<?php /*” are replaced with garbage characters.

There is no active changes to site configuration when this occurs.

+1

In my case all our products are new. I “solved” the item condition issue using the following code in functions.php in a child theme.

add_filter('woocommerce_structured_data_product_offer','trebacz_add_offer_meta');

function trebacz_add_offer_meta($markup_offer_trebacz) {
                if ( ! isset( $product ) ) {
                        global $product;
                }
                if ( ! is_a( $product, 'WC_Product' ) ) {
                        return;
                }
                if ( '' !== $product->get_price() ) {
                        $markup_offer_trebacz['itemCondition'] = 'https://schema.org/NewCondition';
                        $markup_offer_trebacz['description'] = $product->get_short_description().' '.$product->get_description();
                }
                return $markup_offer_trebacz;
}

This also concatenates the description meta data. The full question and solution are documented here:

https://github.com/woocommerce/woocommerce/issues/15045

It’s much more complicated if you have a mixture of new and old items. If you have a more complicated solution, there is a very full featured charge plug-in here:

https://www.schemaapp.com/product/schema-woocommerce-plugin/

It seems to address the full challenges of good product meta data in WooCommerce, but I have not tried it yet. My situation is just not that complicated yet.

There is a bug in the initial release of WC 3.1 that turned off most micodata. That bug was reported by me here:

https://github.com/woocommerce/woocommerce/issues/15873

The fix is:
1. Wait for 3.1.1 to be released that will revert the change. The fix has been tested and committed, but no release date has been set.

or

2. Change your includes/class-wc-structured-data.php to add the line that was accidently removed in the last release. Line 235$markup['offers'] = array( apply_filters( 'woocommerce_structured_data_product_offer', $markup_offer, $product ) );

I did #2 and the microdata that was showing on the page before 3.1 is appearing again.

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

I’m getting the same error after the last update (intermittently), but it seemed to be masked from my other caching plugins…. Had some weird behaviour in WooCommerce that was difficult to explain also.

Made the change you suggested and things seem to be behaving.

Thank you. I thought I was going crazy.