Opened 2 years ago

Closed 20 months ago

#992 closed enhancement (wontfix)

Make XMLRPC endpoint field always visible

Reported by: isaackeyet Owned by:
Priority: major Milestone: 3.2
Component: Add Blog/Site Version:
Keywords: setup Cc: isaackeyet

Description

Brought up by Alex here: http://alexking.org/blog/2012/03/15/sparrow-for-iphone-simple-failure

Occasionally we get support requests about people not being able to add their WP install to the site, often this is because the xmlrpc endpoint is not in the default location and so the set up process becomes confusing. Currently the app should display the field only when the automatic check has failed, but we should instead add it as a permanent field and simply specify that it's Advanced, and have the placeholder text be "Optional".

As a part of this update, let's improve the "no xmlrpc endpoint" error message to be a little more helpful, directing people to the new field, and making sure there's an FAQ item on ios.wordpress.org to cover xmlrpc issues (primarily "not found", but 401s as well).

Change History (10)

comment:1 Changed 2 years ago by beaucollins

Instead of adding an additional field. I think we should just be more explicit in our error message. Something like:

We tried to find your XML-RPC URL but weren't able to. Need help figuring out your XML-RPC URL?

Then have yes/no buttons and yes goes to directions on how to figure out what your XML-RPC URL is why you should even care what an XML-RPC URL is. "No" can just close the alert.

That way there will be less confusion on what we really want in the URL field.

comment:2 Changed 2 years ago by koke

Related: #1000

For 3.0, just check the error messages are decent

comment:3 follow-up: Changed 2 years ago by mrroundhill

I tested this a bit, and it works fine if you enter a custom XML-RPC path into the URL field. We could change the error message if the path isn't found to something like this:

"Couldn't connect to your site. Please try entering the full path to the xmlrpc.php file on your site or tap 'Need Help?' and read the FAQ for more information on XML-RPC."

Thoughts?

comment:4 in reply to: ↑ 3 ; follow-up: Changed 2 years ago by koke

Replying to mrroundhill:

"Couldn't connect to your site. Please try entering the full path to the xmlrpc.php file on your site or tap 'Need Help?' and read the FAQ for more information on XML-RPC."

I don't like mentioning xmlrpc.php.

What can go wrong when adding a blog:

  • No connection: maybe you're offline, maybe your site is down, or your DNS -> "Can't connect to that URL" / "Your internet connection is down" / other server errors, see #1000
  • You're trying to add example.com and your WordPress is at example.com/blog -> "We can't find a WordPress site at that URL"
  • You're trying to add a site that's not WordPress (indistinguishable from previous one)
  • You're trying to add a WordPress site with the xmlrpc.php file somewhere else -> Maybe check for wp-login.php to be sure it's WordPress and ask about xmlrpc.php then?

But seriously, it's one thing to adapt to bad ISP configurations and plugins. If the user actively changed the way the API works, I'd say they can't really expect everything to work.
What if they decide to put xmlrpc.php in a different domain? That'd probably break previews and the link to the dashboard.

comment:5 in reply to: ↑ 4 ; follow-up: Changed 2 years ago by mrroundhill

Replying to koke:

Replying to mrroundhill:

"Couldn't connect to your site. Please try entering the full path to the xmlrpc.php file on your site or tap 'Need Help?' and read the FAQ for more information on XML-RPC."

I don't like mentioning xmlrpc.php.

What can go wrong when adding a blog:

  • No connection: maybe you're offline, maybe your site is down, or your DNS -> "Can't connect to that URL" / "Your internet connection is down" / other server errors, see #1000
  • You're trying to add example.com and your WordPress is at example.com/blog -> "We can't find a WordPress site at that URL"
  • You're trying to add a site that's not WordPress (indistinguishable from previous one)
  • You're trying to add a WordPress site with the xmlrpc.php file somewhere else -> Maybe check for wp-login.php to be sure it's WordPress and ask about xmlrpc.php then?

But seriously, it's one thing to adapt to bad ISP configurations and plugins. If the user actively changed the way the API works, I'd say they can't really expect everything to work.
What if they decide to put xmlrpc.php in a different domain? That'd probably break previews and the link to the dashboard.

I get that, it probably makes sense to have a more generic error message. Isn't the real source of this problem that Alex actually had a redirect in place on his site that made it impossible to point to the xmlrpc.php file anyways?

comment:6 in reply to: ↑ 5 Changed 2 years ago by koke

Replying to mrroundhill:

I get that, it probably makes sense to have a more generic error message. Isn't the real source of this problem that Alex actually had a redirect in place on his site that made it impossible to point to the xmlrpc.php file anyways?

Yep, that was the case. I've seen he fixed the redirect and the app should work now, since the first thing we try is appending xmlrpc.php to the base url

comment:7 Changed 2 years ago by isaackeyet

At this point, the only thing this ticket should resolve is the case where the endpoint was moved. I guess I don't see a harm in being a little extra smart too though, like checking for example.com/blog and blog.example.com before we resort to showing them such a message. The Need help? button could link to a FAQ item that explains that you can in fact enter a full path to the URL in that feel - but again, since this is so edge case, it's basically just something we want to make a little bit more visible to the end user (and a FAQ item should work for that imo).

comment:8 Changed 2 years ago by koke

  • Milestone changed from 3.0 to 3.1

comment:9 Changed 22 months ago by koke

  • Milestone changed from 3.1 to 3.2

comment:10 Changed 20 months ago by mrroundhill

  • Resolution set to wontfix
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.