az09az
Forum Replies Created
-
I did submit a PR that should solve this problem.
Hi Lap,
did you get my e-mail?
It seems to be a bug, I added more details in the github repo.Thanks,
Paul- This reply was modified 5 years ago by az09az.
We would also like to use the same product names in all languages. It sometimes doesn’t make sense to translate specific parts.
Hi Eva,
Maybe it would be a good idea to consider implementing a new general option under “Plugin setting” to have no whitespaces be added for the pre- and suffix.
The default setting would then be that there are whitespaces as it’s now. So this wouldn’t be a breaking change for current users. But would allow everyone to control this behaviour as they see fit for their feed.
And if a space is needed for a field it can manually be added.
I believe such an implementation would help more then case by case additions for specific fields.
Thanks,
PaulHi Eva,
do you have any idea what the problem might be?
Thanks,
PaulHi Eva,
Thanks for this update, that should potentially be a solution!
However after updating to 5.5.6 it doesn’t seem to work for me.Here are my settings:
https://pasteboard.co/IePoAqE.jpgAnd the output:
https://pasteboard.co/IePpmqe.jpgThe feed is a custom feed and the field a custom field. The SKU selected is the normal woocommerce SKU field, the second in the dropdown list.
Any clue what could be the problem on my end now?
Thanks,
PaulHi Eva,
Thanks for your answer to my question.
Unfortunately this won’t be a solution in our case as we would like to add a suffix behind the SKU field.
I only showed the wc_post_id_ field to show this didn’t work as expected as well.
Thanks,
Paul