Support » Plugin: Jetpack by WordPress.com » disabling upon testing requires re-login upon activating?

  • Resolved Oclair

    (@oclair)


    disabling upon testing requires re-login upon activating?
    Frack That

    • Choose an account to use Jetpack
    • WTF why do you use POPUPS?

      Totally over complicated over engineered….

      At least delete plugin works….

Viewing 15 replies - 1 through 15 (of 17 total)
  • Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    Jetpack is asking for a WordPress.com account, which is completely separate from how you log in to your WordPress site.

    Since Jetpack brings WordPress.com features to your self-hosted WordPress.org site, it requires a WordPress.com account, much like how a plugin which brought Facebook features to your site would require a Facebook account.

    Almost all of Jetpack’s features make use of heavy processing power (Photon the image CDN, related posts indexing), heavy database usage (stats), or require connections to third-party systems that can be very complicated to setup by yourself (Publicize’s automated sharing to social networks, email subscriptions, etc).

    We take care of that all on WordPress.com’s server cluster so your hosting provider doesn’t suspend you for using excessive resources.

    In order to do any of that, we need a WordPress.com account.

    Oclair

    (@oclair)

    Thank you for the reply,

    You did not respond to my two comments.

    1. Upon testing and debugging plugins, disabling Jetpack briefly requires re-signing in. That is not acceptable, fix it so the credentials are not cancelled.

    2. When re-signing in the Login screen is not compatible with pop up blockers built into modern browsers.

    I do not need to have the feature set for the plugin explained as that is not relevant to my thread.

    Have a nice day,
    OC

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    1. We don’t consider this broken. Disabling Jetpack purposefully removes the credentials, so that the plugin isn’t reconnected to someone no longer involved with the site simply by reactivating it.

    2. We don’t use pop-ups, and we haven’t noticed any problem with built-in ad blockers. Which browser are you having that problem with?

    Oclair

    (@oclair)

    I know you obviously respond to usability issues by quoting how great the plugin is as if the user has no clue what the product is like using it.

    Ironic that appears to be the case for the development team

    If you make using jetpack a pain in the ass to debug we’ll just get our stats elsewhere thank you very much

    Marked as resolved fracked as intended

    Oclair

    (@oclair)

    there are no error logs for bad architecture

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    We have no plans to change the way the re-connect procedure functions.

    Again, as your it being blocked, which browser are you having that problem with?

    Oclair

    (@oclair)

    guess which seems to randomly work for you folks…
    hint: it’s a pretty major gaffe

    Oclair

    (@oclair)

    QOS what a concept…

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    Again, which browser are you having that problem with?

    Oclair

    (@oclair)

    • This reply was modified 4 months ago by Oclair.
    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    That won’t make any difference, again we do not use pop-ups for Jetpack.

    We do not have the problem you’re describing in the latest versions of Chrome, Firefox, Safari, and Edge.

    Which version of Firefox are you running, and have you tried with all extensions switched off?

    Oclair

    (@oclair)

    like I said there are no error logs for bad architecture

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    I’m sorry, but really, we can’t help you without further information.

    One last time, which version of Firefox are you running, and have you tried with all extensions switched off?

    If you’d rather not, we’ll consider this matter closed, since we cannot reproduce the issue as described in the latest versions of Firefox, Chrome, Safari, and Edge.

    Oclair

    (@oclair)

    I already market this issue Resolved a few hours ago

    Plugin Contributor James Huff

    (@macmanx)

    Volunteer Moderator

    Alright, if you ever want to share that, please let us know.

    Since we cannot reproduce the issue as described in the latest versions of Firefox, Chrome, Safari, and Edge, and have not received simple info we need to investigate and address this further, we consider the matter resolved for now.

Viewing 15 replies - 1 through 15 (of 17 total)
  • You must be logged in to reply to this topic.