We apologize for the instability of composr.app and appreciate your patience. We are working on the statistics addon and trying to find an optimal way to store and render data. Unfortunately, we have yet to find a solution that can handle the traffic (and therefore, tens of millions of statistical records) of composr.app. We're working hard on one.
Just to check if the parsing is working correctly, what was in the IP bans just before it wouldn't add any more? Please submit your response as a private note so as to not leak IP addresses.
For public record, they said:
"OK let me say this I am not doing a ban from selecting the IP I was entering them manually and saving the record. This is where it is not adding the added IP. It does add the IP if I go to view and click ban this IP. The record is then added."
Sounds like an issue with the text field on the module perhaps. I'll investigate. It may be a while before I do so as my current focus is getting v11 alpha1 out the door. This does seem like an issue that could impact multiple v10 users though so I'll try to get a hotfix out. It sounds like you have somewhat of a workaround for the time being. You could probably also type any IP in investigate user and then toggle banning on it if you need to manually ban an IP.
I unfortunately could not reproduce this issue. Are you sure the new IP addresses you are entering were not already entered? That's the only time I could get the form to erase entries is if the entries already existed.
For public record, they said:
"OK let me say this I am not doing a ban from selecting the IP I was entering them manually and saving the record. This is where it is not adding the added IP. It does add the IP if I go to view and click ban this IP. The record is then added."
Sounds like an issue with the text field on the module perhaps. I'll investigate. It may be a while before I do so as my current focus is getting v11 alpha1 out the door. This does seem like an issue that could impact multiple v10 users though so I'll try to get a hotfix out. It sounds like you have somewhat of a workaround for the time being. You could probably also type any IP in investigate user and then toggle banning on it if you need to manually ban an IP.