catgregory

Solved this one myself.

Turns out, if you connect Jetpack while you’re using a temp url, then when you start using your *real* url, Jetpack gets confused. (And PS, another issue: when you go live with the *real* url, your subscribers will get your temp url in their confirmation email, even though you’re using the *real* url)

Solution: Disconnect from JetPack and reconnect. Voila, problem solved.

Instructions: On your left menu, just below “Dashboard,” Select Jetpack>Jetpack.
Then on that screen, in the upper right, you’ll see a “Connected to WordPress.com” button. Click on it. Once you’re disconnected, then click on it again to reconnect.

I’m not sure if this is relevant, but when I click on “Add New Twitter Connection,” it takes me to the Twitter Authorization page, and THEN I get some Java errors:

Viewport argument value “device-width;” for key “width” is invalid, and has been ignored. Note that ‘;’ is not a separator in viewport values. The list should be comma-separated. authorize:8
Viewport argument value “1.0;” for key “initial-scale” was truncated to its numeric prefix. Note that ‘;’ is not a separator in viewport values. The list should be comma-separated. authorize:8
Viewport argument value “1.0;” for key “maximum-scale” was truncated to its numeric prefix. Note that ‘;’ is not a separator in viewport values. The list should be comma-separated.