1. There is a custom post type and a field with multiple values (for example, wpcf-file)
2. There is a Toolset Form that creates a post and that includes the wpcf-file field.
3. Everything goes well, until the file with Japanese letters is saved in the wpcf-file field. The field value itself is stored correctly and contains Japanese characters. The problem lies in the attachment, which is created from the value of the custom field. Its title no longer contains Japanese characters. Why did I point out that this is a bug? Because the problem does not occur when uploading a file directly to the media library from the admin panel.
I no longer have access to this site, I just want to help the client solve this problem if possible. The client wants to search in media files, and for this the file name must be complete and contain special characters.
Thank you
Hi,
Thank you for contacting us and I'd be happy to assist.
I've performed some tests on my website with file and image type custom fields in Toolset Forms, but couldn't reproduce this behavior. The Japanese characters in the file names remained intact.
It seems it could be something specific to that website, but, to investigate that we'll need access to the website's admin area.
Alternatively, you can create a test website and if the issue is reproducible, you're welcome to share its admin access along with the exact steps to see the issue.
Note: Your next reply will be private and it is recommended to make a complete backup copy, before sharing the access details.
regards,
Waqar
Is someone looking into this issue?
The login info works, thank you.
We had a busy forum queue over the weekend, but, I'll be resuming this troubleshooting today.
Thank you for your patience.
Thank you for waiting.
During testing on a couple of different servers, I couldn't reproduce this behavior and the Japanese characters stayed intact in the attachment title.
( example screenshot: enlace oculto )
Do I have your permission to download a clone/snapshot of your website? This will help us in troubleshooting this on a different server, without affecting the actual website.
@waqar:
Please go ahead and download a clone/snapshot of the site.
I came across this ticket while looking into my follow-up list.
The ticket's status never changed because the user who started the ticket never replied.
As we have no way of knowing that the two accounts are related, can you please use the "Max" user account for permission to proceed with the clone/snapshot?
Waqar, Duong
I apologize for not taking part in the discussion. I want to explain everything. I was following this forum thread and didn't participate as I saw Duong taking part in the discussion. Duong is my client and he has full control over his site.
And yes, I give you permission to proceed with the clone/snapshot.
Thank you
Thank you for the permission and I'm on it.
Will keep you updated on the progress.
Thank you for waiting, while I performed tests on your website's clone.
Even while testing your website's clone on a couple of different servers, I couldn't reproduce this issue with the attachment titles. The Japanese characters are not removed from the attachment titles when uploaded through Toolset's file field in the form.
( example screenshot: enlace oculto )
I'll recommend turning on WordPress debugging ( ref: https://wordpress.org/support/article/debugging-in-wordpress/ ) and then testing the file upload process again and seeing if any errors or warnings are logged in the error log.
It would also be interesting to deploy a test website on this same server with only Toolset plugins and a default theme like Twenty Twenty-One and see if the issue is reproducible. This will help in confirming whether it is specific to a server environment.
Hi Waqar,
Thanks for looking into this issue. I retested this feature by uploading a file with japanese and korean characters in the filename.
Good news! It's working and I was unable to replicate the issue.
I didn't have to debug anything.
Thanks!
-Duong
Hi Duong,
Thanks for the update and glad that this is working now.
I'm going to mark this ticket as resolved, but you're welcome to start a new one for each new question or concern.
If you need to share any update on this same matter, just include this ticket's link in a new ticket and we'll know the background.
regards,
Waqar
