maxguru

Hi Jan.

When you say “PDF creation fails”, what exactly do you mean?

The warning is there to let you know that the plugin version 1.3.2 is not verified to work with WPForms version 1.10.0.2. It might still work but there is a chance that the new WPForms version has major changes that break some features of PDF Forms Filler. I would recommend you downgrade WPForms (possibly using WP Rollback plugin) until a new version of PDF Forms Filler is released that has support for WPForms version 1.10+, which will happen soon.

Please let me know exactly what has been happening since mid January.

Thank you.

There is no concept of mapping “fields” in PDF Forms Filler for WooCommerce like there is in the other PDF Forms Filler plugin variants. There is only the concept of placeholders and the ability to map a text mixed with one or more placeholders to a PDF field. This means that all placeholder values have to be converted to strings and concatenated together into a single string (even if there is only one placeholder in your mapping).

Unfortunately, as of today, the documentation on the PDF Forms Filler website is still missing the WooCommerce section. I have plans to add it in the future.

If the plugin allowed multiple lines in value mappings, then you could have mapped text\nillustration value to “Yes” for both PDF fields, however, the plugin doesn’t allow multiple lines in value mappings, so, you can’t use this method.

What you can do is exactly what you are suggesting, split the checkboxes into separate meta data keys. So, you might have nsv_our_work_type_text and nsv_our_work_type_illustration meta data keys and map {order_item_meta:nsv_our_work_type_text} and {order_item_meta:nsv_our_work_type_illustration} placeholders to their respective PDF fields. For multiple choice PDF fields, you can map both placeholders separated by a new line character (in the mapping text area) to the multiple choice PDF field.

Let me get back to you regarding improving how the plugin handles placeholders with multiple values. I will think about your use case and see if I can come up with a redesign.

Your use of foreach seems incorrect.

In the current version of the PDF Forms Filler for WooCommerce plugin, placeholder output is turned into an array (for filling multiple choice PDF fields) by splitting on newline characters. However, your code is storing an array as the value of order item meta nsv_our_work_type, which gets turned into the string [Text, Illustration]. The reason why this happens is that the plugin needs a string representation of the array value to be inserted inside another string (text in the mapped text area). So, the string representation [Text, Illustration] is not going to get split correctly for the multi-select PDF field. What we need is to use implode( "\n", $array ) to store a string with multiple lines, each containing a multiple choice field value, instead of storing an array in order item metadata record.

Below is the code that will currently work for you.

function nsv_cpt_wc_order_line_item( $item, $cart_item_key, $values, $order ) {
    $array = [ 'Text', 'Illustration' ];
    $item->update_meta_data( 'nsv_our_work_type', implode( "\n", $array ) );
}

add_action(
    'woocommerce_checkout_create_order_line_item',
    'nsv_cpt_wc_order_line_item',
    10,
    4
);

Let me think about how to refactor array value handling in the plugin such that we can make it work with multiple choice PDF fields without having to use implode. Meanwhile, try the code above and let me know how it goes.

What kind of customization are looking to do?

There is a lot that can be done with CSS.

The download box code is in the js/frontend.js file (in the plugin directory). Perhaps it can be changed to do what you need, however, one issue is that any changes there will be overwritten by updates. You may be able to hide the original download box with CSS and add your custom version by making your own frontend.js file.

This seems to be an issue with the plugin. I think it can be fixed rather easily. Give me a little bit of time to release a new version with a fix.

The flattening option does exist. It is not enabled by default. So, it is possible to not flatten the PDF form. However, if you have an XFA form PDF file with no AcroForm fields then flattening is forced. This is happening because of limitations of the SDK being used.

Use the ‘flatten’ option.