Sash

Its about the Oxygen Builder Addon again the third time in the line, sorry but that makes your Plugin unusable for a bigger Site.
The new update 2.3 cant be updated and always display it. Here its only the Problem about your updater. After some debug and test on a clean install. We only cant Update to 2.3. No other problem dedected.
No other Plugins, only Oxygen Builder 3.9 and your Plugins are installed.

Server: Nginx / php 7.4

• This reply was modified 2 years, 12 months ago by Sash.
• This reply was modified 2 years, 12 months ago by Sash.

Thank you for think about the problem.
For me and for most of my customer projects, both options are not optimal. Although, point 1 is closer to the solution. The page should always be available because I would use it for all information and the FAQ for the 2FA settings, for example. In my opinion this should be adjustable independently of your plugin. The link to this custom page should also be visible as a link in your popup as well as in the profiles (WP-Profile / Fronted-Profile).

1. However, I would say goodbye to the wizard popup after login and do it fundamentally differently.
– If the user has to set the 2FA immediately, he will be redirected to the WP profile, the Frontend profile or according to his own choice, to a custom page (all Url should be changeable in the settings.)
– A small pop up says that you cannot do anything on the site until you have completed the 2FA settings with a customizable Button ….that’s it.
Each user can provide instructions etc. himself on the custom page. My customers, who are mostly German-speaking, don’t want to be forwarded to a plugin owner page anyway to read some information in English; they prefer to provide their users with their own information in their own CI. For larger projects, the focus is clearly on the appearance.

I personally find exactly that, a big problem with many plugins (free and paid),… everyone implements their own design and we developers can then either not or only with difficulty css overrides adapt our customer projects to the customer’s CI with. Why not just adapt the plugin to the native wordpress design. That would save us a lot of work and then we might be ready to pay again for another plugin.

@iamhere that would only work if the user didn’t have to set the 2FA immediately. When setting up immediately, after login there is a redirection to the WP 2FA page (where the frontend shortcode is used). That is why this is not possible.

• This reply was modified 3 years, 1 month ago by Sash.
• This reply was modified 3 years, 1 month ago by Sash.

Mhmmm Okey
I don’t quite understand that. The redirection to the 2FA in the frontend (where our information and the shortcode is) and all other settings are OK. Actually, all we needed is a function or a small code change that prevents the micromodal from starting immediately with the page load. Basically, I don’t like to write changes in the code of third-party plugins myself if I can’t fully understand the code structure. I’m a little disappointed that there is no solution from you, that would made things a lot easier. However, we need this Way for our project. That’s why I asked about this before I turn to someone else to adjust it.

Anyway, thanks for the plugin and the work.

Cheers Sash

Hi,

Thank you for your message. No, the setting that the 2Fa must be set up immediately is correct. After logging in for the first time, users will be directed to the 2FA page. And this is exactly where the PopUp starts immediately. We don’t want a time delay, the users should set it up immediately! However, they should first be able to read our own information on the 2FA page without the wizard immediately start on page load. They have to click on the button themself after reading our information. The plugin does not offer that by default and there is also no solution in the docs, otherwise I would not have written because I always look in the docs first. I hope you can offer us a solution for this.

Cheers

• This reply was modified 3 years, 1 month ago by Sash.