Open GoogleCodeExporter opened 9 years ago
What is the URL that generates the 404?
Original comment by mizeh...@gmail.com
on 2 Sep 2010 at 5:48
HI Michael,
When clicking on the "sign in to Twitter" icon this is the response.
http://jannstuckey.com.au/wp-content/plugins/tweetly-updater/redirect.php?callba
ck=http%3A%2F%2Fjannstuckey.com.au%2Fwp-admin%2Foptions-general.php%3Fpage%3Dtwe
etly-updater%2Ftweetly_updater.php
This happens on a number of my blogs since the update.
Kind Regards
Mike
URL that
Original comment by mikeandr...@gmail.com
on 2 Sep 2010 at 7:26
the issue happens when trying to link the plugin to our Twitter accounts after
upgrading. On the edit page for the plugin (tweetlyupdater), we're seeing a
messages that states "your twitter login could not be verified". I have several
domains using this plugin (maybe 25-30) and have thus far have updated just 5.
For the first 3, I updated the plugin and after logging into the "bit.ly" site
I tried the "Sign in with Twitter" button and everything went fine. But for the
last two domains I've updated the plugin, I get the callback "page not found"
error message reported above. I've checked the button "link" under the plugin
edit page and pasted it below. The "anydomain" is the only part that's
different from domain to domain and yes, the button link is exactly the same on
all 5. The question is why won't it authorize the last two domains after
everything went fine on the first 3? FYI, all domains are hosted on the same
server and all are sub domains.
http://www.anydomain.com/wp-content/plugins/tweetly-updater/redirect.php?callbac
k=http%3A%2F%2Fwww.anydomain.com%2Fwp-admin%2Foptions-general.php%3Fpage%3Dtweet
ly-updater%2Ftweetly_updater.php
Original comment by usp...@gmail.com
on 6 Sep 2010 at 3:30
Hi Michael,
It would be good to get a solution to this issue as I have the plug in on a
number of sites that are giving me the same response.
Cheers
Mike
Original comment by mikeandr...@gmail.com
on 7 Sep 2010 at 3:46
Getting same problem since update. 100+ blogs, all have the same problem.
Original comment by nexusja...@gmail.com
on 8 Sep 2010 at 12:23
this is the link its going to:
http://www.domain.com/wp-content/plugins/tweetly-updater/redirect.php?callback=h
ttp://www.domain.com/wp-admin/options-general.php?page=tweetly-updater/tweetly_u
pdater.php
Original comment by nexusja...@gmail.com
on 8 Sep 2010 at 12:27
I am having the exact same problem listed above and mine is also redirecting
to:
http://www.domain.com/wp-content/plugins/tweetly-updater/redirect.php?callback=h
ttp://www.domain.com/wp-admin/options-general.php?page=tweetly-updater/tweetly_u
pdater.php
It works for some domains and others it doesn't. Please Find a fix soon!
Original comment by swanson....@gmail.com
on 4 Oct 2010 at 3:20
Hi Michael,
You have a great plugin that I loved using but it now is really useless, I've
tried to add it to every new blog that I create for my clients and i t will not
work in any of them, it still generates the same 404 response as the original
blog that I commented on earlier, this is a shame.
Regards
Mike Andrew
Original comment by mikeandr...@gmail.com
on 20 Oct 2010 at 6:19
I would need more information about your wordpress installtion to help you. The
URL
http://www.domain.com/wp-admin/options-general.php?page=tweetly-updater/tweetly_
updater.php is the normal callback path back to the option page. Please post
the relevant parts of your webserver logs. Are there any redirect configuration
via the main apache or htacces configuration?
Original comment by osberlin...@gmail.com
on 20 Oct 2010 at 5:40
Hi There,
After installing the Tweetly Updater plugin and clicking on the "sign in with
Twitter" button, this is the responce generated by clicking on the button,
"http://bayrealestateupdate.com.au/wp-content/plugins/tweetly-updater/redirect.p
hp?callback=http%3A%2F%2Fbayrealestateupdate.com.au%2Fwp-admin%2Foptions-general
.php%3Fpage%3Dtweetly-updater%2Ftweetly_updater.php"
I cannot get the plugin to work as It is not possible to link it with Twitter.
Original comment by mikeandr...@gmail.com
on 25 Oct 2010 at 11:55
Original issue reported on code.google.com by
mizeh...@gmail.com
on 2 Sep 2010 at 5:47