KT Walrus

I'm starting a new community shortly and I just don't want my users to use deprecated features. Not a big deal, but if a feature is deprecated, I don't want to have someone use it and then react negatively when it goes away. Users don't like change (especially feature removals), in my experience.

I'm starting a new community shortly and I just don't want my users to use deprecated features. Not a big deal, but if a feature is deprecated, I don't want to have someone use it and then react negatively when it goes away. Users don't like change (especially feature removals), in my experience.

I'm starting a new community shortly and I just don't want my users to use deprecated features. Not a big deal, but if a feature is deprecated, I don't want to have someone use it and then react negatively when it goes away. Users don't like change (especially feature removals), in my experience.

I'm starting a new community shortly and I just don't want my users to use deprecated features. Not a big deal, but if a feature is deprecated, I don't want to have someone use it and then react negatively when it goes away. Users don't like change (especially feature removals), in my experience.

Simply allow us as admins to set an attribute on each installed theme that designates the modes the theme supports, either light, dark, or both. Next, have the ACP Themes section support setting a default theme for light mode users and a default theme for dark mode users. Admins can then choose a third party theme for users in dark mode and the default IPS theme for users in light mode. IPS could even provide a separate dark default theme to be used by those of us that don't use third party themes.
Finally, when a theme is loaded, it should be very simple to have a JS check for current mode and load the appropriate theme (as set in the theme attributes - light/dark/both).
I think this would be pretty easy to implement and not put any burden for third party themes since the dark mode theme would be a separate theme from the light mode theme. No big changes required to the existing IPS theming system either.

Simply allow us as admins to set an attribute on each installed theme that designates the modes the theme supports, either light, dark, or both. Next, have the ACP Themes section support setting a default theme for light mode users and a default theme for dark mode users. Admins can then choose a third party theme for users in dark mode and the default IPS theme for users in light mode. IPS could even provide a separate dark default theme to be used by those of us that don't use third party themes.
Finally, when a theme is loaded, it should be very simple to have a JS check for current mode and load the appropriate theme (as set in the theme attributes - light/dark/both).
I think this would be pretty easy to implement and not put any burden for third party themes since the dark mode theme would be a separate theme from the light mode theme. No big changes required to the existing IPS theming system either.

Simply allow us as admins to set an attribute on each installed theme that designates the modes the theme supports, either light, dark, or both. Next, have the ACP Themes section support setting a default theme for light mode users and a default theme for dark mode users. Admins can then choose a third party theme for users in dark mode and the default IPS theme for users in light mode. IPS could even provide a separate dark default theme to be used by those of us that don't use third party themes.
Finally, when a theme is loaded, it should be very simple to have a JS check for current mode and load the appropriate theme (as set in the theme attributes - light/dark/both).
I think this would be pretty easy to implement and not put any burden for third party themes since the dark mode theme would be a separate theme from the light mode theme. No big changes required to the existing IPS theming system either.

Simply allow us as admins to set an attribute on each installed theme that designates the modes the theme supports, either light, dark, or both. Next, have the ACP Themes section support setting a default theme for light mode users and a default theme for dark mode users. Admins can then choose a third party theme for users in dark mode and the default IPS theme for users in light mode. IPS could even provide a separate dark default theme to be used by those of us that don't use third party themes.
Finally, when a theme is loaded, it should be very simple to have a JS check for current mode and load the appropriate theme (as set in the theme attributes - light/dark/both).
I think this would be pretty easy to implement and not put any burden for third party themes since the dark mode theme would be a separate theme from the light mode theme. No big changes required to the existing IPS theming system either.

Has 4.1.18 been tested with PHP 7.1?

I see you are still using ReCaptcha v1 on the sign up form. Google has moved on to ReCaptcha V2 and Invisible ReCaptcha.
Is Invisible ReCaptcha supported in 4.2?
I think Invisible ReCaptcha should be the default to make sign up even easier for new users.

Are you going to provide more Custom Profile field types in 4.2?
I need a good Places field that allows entering the following:
City (w/ region and country) School (w/ school type and city) Place of Worship (w/ church type and city) Workplace (w/ workplace type and full address) Home (w/ full address) Neighborhood (w/ postal code from home address) Region Postal Code Country Basically, IPS4 would maintain a Places table that would be used for autocompletion on the Place Name input field. If a Place Name is submitted that hasn't previously been seen, the input text would be sent to Google Places to retrieve a list of possible matches and the user would be presented with a form to pick the correct place or change the input text and try again.
The Places table would include the Google Place Id and lat/long with each Place and use that for showing Maps for the Place when the field is displayed in the Profile.
Yes. I knew this too. I was just asking about whether 4.2 supports Invisible ReCaptcha. By your answer, I take it that it does not, but you are considering it.

I see you are still using ReCaptcha v1 on the sign up form. Google has moved on to ReCaptcha V2 and Invisible ReCaptcha.
Is Invisible ReCaptcha supported in 4.2?
I think Invisible ReCaptcha should be the default to make sign up even easier for new users.

Has 4.1.18 been tested with PHP 7.1?

I'd like to see support for 2-factor authentication (via text message) with the ability to enable this option for specific groups (e.g., admins and moderators must authenticate via text message while members may choose to enable/disable on their own accounts).

I'd like to see support for 2-factor authentication (via text message) with the ability to enable this option for specific groups (e.g., admins and moderators must authenticate via text message while members may choose to enable/disable on their own accounts).

I'd like to see support for 2-factor authentication (via text message) with the ability to enable this option for specific groups (e.g., admins and moderators must authenticate via text message while members may choose to enable/disable on their own accounts).

SMS 2FA is certainly better than just simple password authentication and most large sites offer this an option to its users. It certainly isn't the ultimate security feature, especially if you are the federal government, but I sign up for 2FA authentication for any site that has my credit card on file or has access to my bank accounts.
Besides, offering 2FA authentication to users gives the impression that the site is worried about security and privacy and is taking the usual measures to prevent unauthorized access to your account and personal information.

SMS 2FA is certainly better than just simple password authentication and most large sites offer this an option to its users. It certainly isn't the ultimate security feature, especially if you are the federal government, but I sign up for 2FA authentication for any site that has my credit card on file or has access to my bank accounts.
Besides, offering 2FA authentication to users gives the impression that the site is worried about security and privacy and is taking the usual measures to prevent unauthorized access to your account and personal information.

I'd like to see support for 2-factor authentication (via text message) with the ability to enable this option for specific groups (e.g., admins and moderators must authenticate via text message while members may choose to enable/disable on their own accounts).