VM4 and "special characters" [VM 4.0.6] [J 3.10.10]

[Rune Rasmussen]

VM4 seems to have several issues with "special characters" around in the system.

Found so fare is that customer comments including t.ex. Nordic characters like æøåäö is stored like html entities in the database.

For images containing such characters or other special characters, the system loses connection to those images as soon as they are opened up for editing, the system can't recognise them. And if new images are uploaded with such characters, they are being renamed to use html entities, and the system still can't recognise them ...

vmError: Could not find the file æøå.jpg

Anyone else facing the same issues?


Btw! And yeah, I know, don't use special characters in filenames. But try to get people follow that when Windows have learned them differently ....

[Rune Rasmussen]

And the search is killed, but that's already reported it seem...

[Rune Rasmussen]

FE issues confirmed in vmbeez3

[beny.rfg]

Yes, I found another issue - after placing order, VM replace special characters in customer name to HTML entities, see attachment.

[Mike J]

Hi guys,

I found that switching to mysql 5.7.39 fixed most of that ( If you're on a previous/different version ).

... But VM 4.0.2.10661 gets broken by J! 4.x.x & VM 4.0.4.10688 / 4.0.6.10690 have their own problems...

If you're running a live production site that needs to take orders, don't venture beyond J! 3.10.10 / VM 4.0.2 10661 and await VM 4.0.8 IMHO.

[Rune Rasmussen]

Hi Mike,

MySQL Version   8.0.29-cll-lve
(did you switch up or down?)

So you say that VM 4.0.2 actually is more stable than 4.0.4 and 4.0.6, now that's really interesting ...

[beny.rfg]

I have downgraded to 4.0.2 and it works... (at least the rewriting of characters and the search problem)

[Rune Rasmussen]

I have downgraded to 4.0.2 and it works... (at least the rewriting of characters and the search problem)

Indeed it works, everything mentioned above plus more, isn't a issue in VM 4.0.2 ... huh ...