search

fabacab / tumblr-crosspostr

:left_right_arrow: Tumblr Crosspostr is a bi-directional WordPress and Tumblr bridge inspired by Tumblrize.
https://wordpress.org/plugins/tumblr-crosspostr/
9 stars 3 forks source link

"Click here to connect to Tumblr" not working #10

Closed squidbunny closed 9 years ago

squidbunny commented 10 years ago

Noverse Bug Reporting Template

Title: "Click here to connect to Tumblr" not working

Class: Serious Bug e.g. "Feature Request", "System Error", "Serious Bug"

Date: 5/1/2014 Reported By: squidbunny Email: erin@squidbunnies.com

Product: Tumblr Crosspostr Version: 0.7.13 Platform: Version: Browser: Firefox / Chrome Version: URL:

Is it reproducible: Yes, for me! Although I don't know how to advise you reproduce it as I've installed Crosspostr on another WP blog with zero issue and followed the same steps this time.

Description

Installed and activated the plugin without issue. On the Settings page (/wp-admin/options-general.php?page=tumblr_crosspostr_settings), I correctly input the Tumblr API key/OAuth consumer key & the secret key. Then I click "click here to connect to Tumblr." The browser loads a new URL as if it's doing something (/wp-admin/options-general.php?page=tumblr_crosspostr_settings&tumblr_crosspostr_oauth_authorize&_wpnonce=cdb121915d) but nothing else happens. There is no error message, and the plugin is not connected to Tumblr.

Steps to Produce/Reproduce

See above. I followed the same procedure as when I've successfully installed this plugin on another blog/tumblr combination in the past.

Expected Results

Actual Results

Workarounds

None found. I have attempted clearing cookies, restarting the browser (Firefox), and using an entirely different browser (Chrome).

Attachments

Other Information

See also: https://wordpress.org/support/topic/click-here-to-connect-to-tumblr-not-working

intelligence commented 10 years ago

Is it possible to circumvent this problem by manually connecting the two? Really stuck with this problem.

fabacab commented 9 years ago

This problem is almost certainly caused by a misconfiguration of the session.save_path PHP configuration variable, as described in this support forum thread. It's usually possible to resolve this by ensuring that the session save path PHP is using exists and is readable.