Comment 25 for bug 1867502

Revision history for this message
City of Oz (ozinfotech) wrote :

Not sure what happened, but it seems to be working now even with that error message.