• wmclaa

    (@wmclaa)


    The problem with the Google Drive Embedder not loading and getting x-frame options is caused by users not completing all of the steps of the setup. Most importantly, you have to make sure the (1) Drive API and Calendar API are enabled after the credentials created and (2) the Authorized Javascript origins and Authorized redirect URIs are added for youru site. All of this is explained in the instructions for the Gooogle Login plugin.

    At the same time, Gooogle reports that the app has not been verified yet, so I had to move through a few security warnings to get to my Drive files.

    Definitely can be cleaned up..a.nd the support forum is poorly served. These issues could easily be explained there in the amoount of time it took me to write this review.

Viewing 3 replies - 1 through 3 (of 3 total)
  • danlester

    (@danlester)

    Thank you very much for your honest review.

    A lot of the Google-related problems do change over time as they tweak things at their end, and that’s one reason it seems to me sensible to provide support directly by email. I’m always very happy to help all users – [email protected].

    In any case, unfortunately I don’t think I’m the first plugin author to find the forums unworkable as a ‘helpdesk’, so I do try to direct people to email. Sorry if you feel that is inconvenient.

    I currently have a couple of ‘sticky’ FAQ support threads at the top of the forum, but I don’t think people notice them there. There is a lot of info on our site.

    Please also understand that people arrive at the plugin(s) in different ways. Some find the Drive plugin after they have already been using the Login plugin. Many just find Drive by searching within their own site’s Plugin pages, which means they never arrive at the plugin homepage on this site anyway. So I have tried to build in as many steps to help along the way, within the plugins. If you install Drive, it will advise if Login is not installed. If Login is not configured, it leads you through that, etc.

    But ultimately the problem for the Drive plugin lately has been that Google’s client library doesn’t provide a way to display the configuration errors on the screen. So the plugin can apparently break without any clear error, but the same thing could happen due to non-Google WordPress configuration issues too. So tracking down errors like that probably does just need experience…

    As you have also found, Google’s latest fraud-detection efforts sometimes lead to extra steps (described here). These are subject to change – which is another important reason that I really appreciate users getting in touch directly via email: so I can learn the latest about the way different users are being affected by Google’s latest changes! They aren’t necessarily the same for everyone…

    Thanks again for taking the time to work through the plugin and letting me know your thoughts. I really appreciate it, and will see if I can further refine the user experience for everyone, again acknowledging that people come at this from many different angles.

    As ever, I can’t promise to spot replies on the forum here, so please do email if anyone has any follow-up! ([email protected])

    Regards,

    Dan

    Thread Starter wmclaa

    (@wmclaa)

    I understand the forum issues…but the fact that they’re there leads users…especially those sitting up at 2am trying to get things to work on their sites…to think that help is available there. That may not, in fact, be your fault.

    I, unfortunately, had to remove the plugins because, for some reason, the login plugin began trying to sign in with Google automatically, even if I’d like to login with another user account (e.g., test account) manually.

    The Google OAuth stuff is tricky and constantly changing…but it needs to be so. We have to consider this a website luxury and deal with it.

    WM

    danlester

    (@danlester)

    Thanks again. Agreed it is important to keep up with Google changes, and of course that’s the real value I believe I need to provide to all users of these plugins. As before, everyone is encouraged to report their experiences directly to me so I can collate and understand what Google is doing overall.

    For anyone else facing the same issue that Google Apps Login seems to be forcing ‘Login with Google’ automatically, you have most likely turned on the setting ‘Automatically redirect to Google from login page’ in the Advanced Options tab of the plugin settings page. See here: https://wp-glogin.com/docs/google-apps-login/configuration/advanced-options/

    Dan

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Works…if you follow all of the instructions’ is closed to new replies.