Hi,
The namekey of the custom field will be used directly in the name of the override file where the modifications are stored.
We use Joomla's JFile::makeSafe function so it should strip special characters and work fine.
I did try on my end with a comma in the namekey and I didn't have a problem either. I used the order status namekey "Test , with , commas" and the modification of the HTML section worked fine in the "per status override" popup:
i.imgur.com/HPVvjQ2.png
And I got the file media\com_hikashop\mail\order_status_notification.testwithcommas.html.php created on my test website. As you can see, the makeSafe function stripped the commas and spaces and force the lowercase.
If you change the namekey in the database via PHPMyAdmin, you will have two problems:
- the order_status of the orders with that status won't match anymore. So you should also run a query to update the order_status in the hikashop_order table so that they are still linked
- the enable state in the different columns of the System>Order statuses menu will be lost for that order status. So you'll have to reset them there.
But as I said above, I didn't have the problem with a comma on my end so it's likely coming from something else.
Also, the last issue we fixed with the per status override dates from HikaShop 4.0.1 (
www.hikashop.com/forum/orders-management...ing-sent.html#304024
) so if you have the 4.4.2, you already have all the fixes on that end.
You also said "latest Joomla". On your screenshot, it looks like Joomla 3.x, not Joomla 4.0 so I suppose that you meant the latest Joomla 3.x. Otherwise, I would recommend updating HikaShop as the 4.4.2 has many bugs on Joomla 4 that we already fixed in later versions of HikaShop.
Finally, I guess we'll need a backend access and a FTP access to directly check on the issue since we can't reproduce it on our end.
Please provide these via our contact form along with a link to this thread for reference:
www.hikashop.com/support/contact-us.html