Simone Economo

I've been struggling with this problem too. Apparently, it's not the WinRM session that determines the DC, but rather every invocation of `powershell.exe` has a chance of connecting to a...

> Having some set values will always come back to a situation that requires something unique, which would require changing of the extension code. There are many other ways to...

An idea could be an input field for numeric values plus a selectbox with the following options: "minutes / hours / days / etc." This should ensure the same flexibility...

Any news on this? While I know it's too late for Members 1.0 I'd like to discuss different approaches (like mine) for Members 1.1.

Just to clarify: there's no downgrade in functionality as the flexibility remains the same. The only differences between the current approach (taglist-like) and the one I proposed (input field +...

Then we need a better alternative because mine didn't take mixes into account. The underlying problem still remains, though.

> The underlying problem still remains, though. As an example, I accidentally wrote "24 hours 1 hour 45 minutes" (I thought I typed "24 days") and no errors were thrown....

Thanks for your replies. > we look at the actual purpose of the field. We're talking about activation expiry time. In my opinion, the most common range should fall between...

Brendan, if you are too busy I can submit a pull request with the mentioned changes. Just let me know.

Yikes, I don't think I have enough time today. If there's time to include this change in Members 1.0, then I think it's better if you make these changes yourself....