petertely
Forum Replies Created
-
Hi @superlemon1998 ,
The documentation you shared indicates that additional images can be comma-separated for text feeds. But for XML feeds, it shows that each image must have its own “g:additional_image_link” tag.
@door360 Personally, I map 10 “additional_image_link” fields to “additional image 1”, “additional image 2”, … “additional image 10”.Hi!
Do you have any updates regarding the possibility of including the value of a custom field/ACF field? (For reference: https://ww.wp.xz.cn/support/topic/add-shipment-tracking-information-to-email/#post-18184056)Thank you.
Hi Sultan,
My need is similar.
For each WooCommerce order, my logistics partners sends back (via API Rest) a parcel tracking number in a custom field.With MailMint, is it possible to include the value of a custom field in a transactional email template?
The aim is to be able to automate the sending of the tracking number by including this type of sentence in the completed/shipped order template:
‘Your order has been dispatched, you can track the progress of your parcel using the following link:
https://parcelsapp.com/tracking/{{my-custom-field-value}}
Thank you.
Hi Jessie,
It’s excellent if you’ve managed to fix all the errors mentioned in this post.
I’ve just installed ParcelPanel 4.4.1 and will monitor over the next few days to see if the errors have indeed disappeared.Thank you for your excellent work.
PeterForum: Plugins
In reply to: [Judge.me Product Reviews for WooCommerce] Judge.me debug.log errorsHi,
Thank you for your attention to these errors.
They have been removed since November 5.Hello Jessie,
Thank you for your response.
It’s good to hear that you were able to reproduce the errors related to WC_Order_Data_Store_CPT. It’s unfortunate that you couldn’t reproduce those related to HPOS. The debug.log for the shops in HPOS mode where I use ParcelPanel shows the following error about ten times a day:
PHP Notice: Function WP_User_Query::query was called incorrectly. User queries should not be run before the plugins_loaded hook. Please see Debugging in WordPress for more information. (This message was added in version 6.1.1.) in /wp-includes/functions.php on line 6085
and the following error 1 to 3 times a day:
PHP Notice: The wpdb::prepare function was called incorrectly. The wpdb::prepare() query argument must have a placeholder. Please see Debugging in WordPress for more information. (This message was added in version 3.9.0.) in /wp-includes/functions.php on line 6085
On these various shops, disabling ParcelPanel prevents new occurrences of these errors from appearing in the debug.log.
Environment:
WordPress 6.6.2
WooCommerce 9.3.3
PHP 8.2.24
Parcel Panel 4.4.0
LiteSpeed Cache 6.5.2 (preset “Advanced (recommended)”)Hi Val Meow,
Thanks for your response and for explaining the difference between the two options.
Even if the PHP warning isn’t critical, will it be fixed in an upcoming update? I like to keep my debug.log clean 😉
As for the mass regeneration block, I thought it was due to a low “max_execution_time”. I increased it to 14400, but it didn’t change anything. My host (O2Switch) is known to be reliable in France. During the attempts, I don’t see any errors other than the ones already mentioned.
Thanks
Hi Jordy,
Problem solved! (media library popup + visual WYSIWYG)
Many thanks for your responsiveness and efficiency!Hi Jordy,
I’m experiencing the same issue.
In all WooCommerce product pages, whether published or saved as drafts, it’s impossible to:
- Replace the main image
- Add images to the gallery
- Assign images to any variants
The media library popup doesn’t open when clicking the button.
Deactivating “Media File Renamer” resolves the issue.
To reproduce the problem:
When the product hasn’t been saved yet (creating a new product), the media library popup opens fine. But once the product is saved (as a draft or published) and the page is refreshed, it no longer works.My environment:
- WordPress 6.6.1
- WooCommerce 9.1.4
- PHP 8.1.29
- Media File Renamer 5.9.5
- Shoptimizer theme 2.7.9
PS: “Media File Renamer” also causes another issue with invisible text in WYSIWYG fields (short product description, product description, ACF text areas, etc.).
In the “text” version of the WYSIWYG editor, the text is visible, but in the “visual” version, the text is not visible. This seems related to the problem mentioned in this other post.Forum: Plugins
In reply to: [YayMail - WooCommerce Email Customizer] Accent Bug with HelveticaHi Mia,
Thank you for your reply.
The problem is visible in the Yaymail editor as well as in Gmail for real commands, but only on a Microsoft Windows computer. On a Mac, Helvetica displays accented characters correctly.Maybe the problem doesn’t come from Yaymail but is specific to the Helvetica font.
To solve the problem, I changed Helvetica to Arial.
Forum: Plugins
In reply to: [Adminimize] Can’t get “Edit Page”Hi,
I’m also looking to remove “Edit with Elementor” from the admin bar on front-end.
I don’t see Elementor listed in “admin_bar_frontend_options” to be able to disable it.
Thanks for this excellent plugin!Hi,
Thank you for this information.
Is it the same for your WPB Form Popup plugin?
https://ww.wp.xz.cn/plugins/wpb-form-popup/Best regards
Small clarification after conducting some tests.
✅ If I integrate the Contact Form directly into the body of a page (without using “Request a Quote”), its translations display perfectly on the front-end for each language.
❌ The same form integrated via the popup of the Request a Quote plugin only displays in the main language.
I did follow the procedure mentioned by WPML for Contact Form: https://wpml.org/compatibility/2019/02/announcing-contact-form-7-ml/
Environment:
WordPress: 6.4.2
WooCommerce 8.5.2
DIVI 4.24.0
Get a Quote Button for WooCommerce 1.3.6
Contact Form 7 5.8.6
Contact Form 7 Multilingual 1.2.2
WPML Multilingual CMS 4.6.9This is my review 😉
https://ww.wp.xz.cn/support/topic/excellent-plugin-8995/Hi Martin,
I was about to give you access to a clone of the site so you could try it out, but you were quick ; )
I confirm that the problem has been corrected in version 1.29.
Thank you very much!
Pierre