JJ

Hi Chris,

Thanks for the update, it works perfectly!

Hi symisz,

I don’t develop or work for Gutenberg but I can tell you that Gutenberg IS part of the WordPress core. This plug-in makes sure you’re on the latest version of Gutenberg.
The WordPress core is technically using an outdated but stable version if you don’t use (and update) this plug-in.

So in short, this plug-in has got the latest features, but may be unstable compared to the WordPress core version. (So without this plug-in you can still use Gutenberg but an older version.)

As for your error, my best guess is that you’ve got another plug-in which might add Gutenberg blocks to the editor, so now you’ve got 2 blocks trying to use the same name.

Kind regards.

Hi clubkert,

Thanks for letting me know! I’ll update the plug-in now and let you know if it’s still broken for me or if there’s anything else.

Kind regards,
Jan

I guess this plug-in is abandoned?

Quick update, problem is resolved.
I went to the WooCommerce dashboard and saw the Connect Jetpack button there, once clicked and verified the JetPack pages were working again!

Hi @k4m1k4dz3 (and others who might find this like me),

I’m not associated with this Plug-in, but I did just stumble upon -probably- the same error. And I know how to atleast prevent it from breaking the whole plug-in.

It does require modifying the plug-in, so updating it would remove the fix.

Steps how to fix it:

1. Navigate to: /wp-content/plugins/premmerce-woocommerce-product-filter/src/Admin/Tabs/
2. Open: Taxonomy.php
3. Go to functions “switchToDefaultLanguage()” & “switchToCurrentLanguage()” (They’re below each other)

Change the first “if” statement in both these functions from:
if (defined('ICL_LANGUAGE_CODE'))
to:
if (defined('ICL_LANGUAGE_CODE') && isset($sitepress))

Hope this helps!

Hi all,

Just to keep everyone up-to-date here, the PolyLang update (1.5.1) did not fix the problem for me.

If the update fixed it for other people here, please let me know! ??
(Then it might be another conflicting plug-in.)

Kind regards,
Jan

Hi again @alexmigf ,

Just wanted to update you and help others that may find this thread in the future, I’ve just implemented your snippet and added the meta field to the output successfully!

For people who find this in the future, after adding alexmigf’s snippet above you can add this code as a plug-in (or snippet) to add it to the Orders Rest API:

<?php
/*
Plugin Name: WooCommerce Invoices REST API
Plugin URI: https://janjacobs.nl/
Description: Adds invoices to the WooCommerce Orders REST API
Version: 1.0.0
Author: alexmigf + Jan Jacobs
Author URI: https://janjacobs.nl/
License: GPL2
Text Domain: woocommerce-invoices-rest-api
WC requires at least: 4.0.0
WC tested up to: 4.6.1

*/

//  Add PDFs to order output
add_action( 'wpo_wcpdf_before_document', function( $document_type, $order ) {
	if( !empty($order) && $document_type == 'invoice' ) {
		$debug_settings = get_option('wpo_wcpdf_settings_debug', array());
		if( isset($debug_settings['guest_access']) ) {
			$pdf_url = admin_url( 'admin-ajax.php?action=generate_wpo_wcpdf&template_type='.$document_type.'&order_ids=' . $order->get_id() . '&order_key=' . $order->get_order_key() );
			update_post_meta( $order->get_id(), '_wcpdf_document_link', esc_attr($pdf_url) );
		}
	}
}, 10, 2 );

// Add PDFs URL to order output to meta_data
function add_invoices_to_rest_api( $response, $object, $request ) {

    // Check if response has data
    if(empty($response->data)) {
        return $response;
    }

    // Get the Order ID
    $order_id = $response->data['id'];

    // Get _wcpdf_document_link value
    $product_meta__wcpdf_document_link = get_post_meta($order_id, '_wcpdf_document_link', true);

    // Catch empty fields
    if($product_meta__wcpdf_document_link == "" || $product_meta__wcpdf_document_link == false  || $product_meta__wcpdf_document_link == NULL) {
        $product_meta__wcpdf_document_link = "";
    }

    // Add _wcpdf_document_link value to response
    $response->data['_wcpdf_document_link'] = $product_meta__wcpdf_document_link;
 
    return $response;
} 
add_filter( 'woocommerce_rest_prepare_shop_order_object', 'add_invoices_to_rest_api', 10, 3 );

*Edit: This code was originally intended for product meta, I’ll optimize it soon.
*Edit 2: I wrapped alexmigf’s and my code in 1 big plug-in snippet as seen above.

And again, thanks @alexmigf !

Kind regards,
Jan

• This reply was modified 4 years ago by JJ.
• This reply was modified 4 years ago by JJ.

Hi @alexmigf ,

Thanks for the quick reply!
I looked into using custom filters/actions for this functionality but I thought I’d ask here first just be sure. And it looks like it paid off, this is more than I could ask for!

Thank you very much for your help and taking the time to write that snippet. I really appreciate it. I’m going to try and implement it straight away.

Kind regards,
Jan

Hi @hitec4ever ,

The last update on the ticket was on 07.10.20 12:46 with the message: “Your request status has changed to In Progress.”

(FYI; I’m the ticket creator.)

Kind regards,
Jan

Just updated & checked. Seems to be working perfectly. Thanks again for the quick updates!

• This reply was modified 4 years, 1 month ago by JJ.

Hi @wordpressslider ,

Yes, that’d be perfect! Thanks for the quick follow-up. ??

Kind regards,
Jan

Hi @wordpressslider ,

Good to know the arrow bug is fixed. I’ll update to the new version soon to test.

As for my second point, I’ve actually already bought the ‘Pro Lifetime edition’ because I’m so impressed with the plug-in I plan on using it for a long time!

The thing is that the slide duration is changeable but it’s limited to a maximum of 10 seconds (so yeah, I can change the setting but not as much as I’d like). I’d like to set a specific slider to 30 seconds but I can’t because of this limit.

Kind regards,
Jan

Hi @aweissinpsyde ,

Great to hear! I’ll be waiting patiently then. Would you mind updating us here once this update is released? (Right now I’ve disabled auto-updates for the Mollie plug-in as to not break my site again.)

Kind regards,
Jan

Hi @aweissinpsyde ,

As I’ve mentioned before on your support site, the problem is that version 5.8.3 of your plug-in broke compatibility with PolyLang. I’m aware that without PolyLang the plug-in does work (I also mentioned this on your support form). So, yes, this behaviour only happens when another plug-in is active. But it worked perfectly fine before the 5.8.3 update.

The changelog of the 5.8.3 update:

5.8.3 – 09-09-2020
Fix – Apple Pay button is disabled if Apple Pay gateways is disabled
Fix – Breaks Urls of translations plugins
Fix – Translations update endless loop

So to me it seems logically that this second fix (Breaks Urls of translations plugins) actually broke the PolyLang translation plug-in. (I guess this was for WPML or another translation plug-in?). So if the changes for that update could be toggled with a checkbox (Check this box if using PolyLang) or a check in the code which checks if PolyLang is active, or something in that sense, that’d solve it, it seems to me.

Kind Regards,
Jan