Johann Heyne
Forum Replies Created
-
I would also like to add that it would be helpful to have information about the product variant as well in the /update API response. If you have mixed products with and without variants, then it is not possible to compile a meaningful product name with a description without the variant data.
File: lemon-squeezy/src/class-lsq-rest-controller.php
Line 683, add:'order_item' => $order_item ? $order_item->attributes : null,return new \WP_REST_Response(
array(
'success' => true,
'error' => '',
'error_code' => '',
'update' => array(
'version' => $latest_file->attributes->version,
'tested' => null,
'requires' => null,
'author' => $store ? $store->attributes->name : null,
'author_profile' => $store ? $store->attributes->url : null,
'download_link' => $latest_file->attributes->download_url,
'trunk' => $latest_file->attributes->download_url,
'requires_php' => null,
'last_updated' => null,
'sections' => array(
'product_name' => $product ? $product->attributes->name : null, // New
'order_item' => $order_item ? $order_item->attributes : null, // New
'description' => $product ? $product->attributes->description : null,
'changelog' => $latest_file->attributes->version,
),
),
),
200
);Thanks a lot again,
JohannForum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] Open Link in new tabHi,
The new plugin version v1.3.34 now allows the
target="_blank"attribute by default in table cell content HTML links and automatically ensures that therel="noopener"attribute is set.
I hope, that helps.
Cheers,
JohannForum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] Open Link in new tabHi,
The
target="_blank"attribute is sanitized by a script called DOMPurify. By default of DOMPurify, the target attribute is not allowed. But if you know what you are doing usingrel="noopener", you can allow it by configuring DOMPurify; see the following link.https://wordpress.org/plugins/advanced-custom-fields-table-field/#ui%20sanitizing%20options
I will try to find a solution that allows
target="_blank"by automatically addingrel="noopener". That would make this strict setting for the DOMPurify target attribute unnecessary.
Thanks,
JohannHi, the issue seems to be solved. I was able to reconnect to my Lemon Squeezy account.
The issue seems to recur from time to time. Could you please do something to prevent this?
Thanks in advanced,
JohannForum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] Translation with PolylangHi,
Support for Polylang will be included with the next update. I’m currently trying to implement the Polylang DeepL translation functionality.
Meanwhile you could add the following code in your functions.php to add the basic Polylang support:
if ( class_exists( 'Polylang' ) && function_exists( 'acf_render_field_setting' ) ) {
add_action( 'acf/render_field_settings/type=table', function( $field ) {
$choices = array(
'ignore' => __( 'Ignore', 'polylang-pro' ),
'copy_once' => __( 'Copy once', 'polylang-pro' ),
'translate' => __( 'Translate', 'polylang-pro' ),
'translate_once' => __( 'Translate once', 'polylang-pro' ),
'sync' => __( 'Synchronize', 'polylang-pro' ),
);
$default = 'translate';
acf_render_field_setting(
$field,
array(
'label' => __( 'Translations', 'polylang-pro' ),
'instructions' => '',
'name' => 'translations',
'type' => 'select',
'choices' => $choices,
'default_value' => $default,
),
false
);
});
}
Thanks for pointing that out.
JohannForum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] Bug in readme markdown for 1.3.19Thanks, i fixed it.
Forum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] update_field does not work with usersThe new version 1.3.30 with the fix is released. I hope that works for you.
Cheers,
JohannForum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] update_field does not work with usersHi, thanks for the great issue report. I will fix this in the next release. But it will take up to two weeks before I can release the fix in the next release.
Cheers,
JohannForum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] Won’t updateHi, Sorry, I made a mistake. The minimum PHP requirement is version 7.4. I’ve corrected that. Please reinstall the plugin to correct the PHP version.
Sorry for the inconvenience.
Johann- This reply was modified 11 months, 2 weeks ago by Johann Heyne.
Forum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] PHP 7.5?Hi, Sorry, my mistake. PHP 7.4 is the minimum PHP version. I’ve changed that. Please download and install the plugin again.
Thanks for the important note.
JohannThanks, that helped. I’ve looked into it and taken a few things into consideration.
Regarding the trademark issue, I wrote to ACF and asked for their position and instructions.OK, I’ll take care of it. It’ll be integrated in the next release.
Thanks, again!Cheers, Johann
Forum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] Error loading translationsHi, the text domain name in the plugin did not meet the requirements. Thanks a lot for the feedback. I corrected it, and in my tests, the Russian translation loaded now correctly. I am now waiting for wordpress.org to approve plugin version 1.3.28.
Cheers, JohannForum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] Incorrect links to Secure Custom FieldsHi, thanks a lot! I’ve fixed it.
Cheers, JohannForum: Plugins
In reply to: [Table Field Add-on for ACF and SCF] Image in table headHi,
The HTML image tags in your website’s table source code are being escaped. The table plugin itself does not do this. I suspect that another tool is filtering the output, possibly using
esc_html()or a similar function. Does this help you?
Cheers, Johann