Posted 1 year ago #
What happens is that the first time you are flattred the item is created in flattr.com.
What you don't have is the automatic creation of flattr-items at the time you publish your blogpost.
I still have the same problem btw, can you confirm that when you click (re-)authorize on the application the token part of the url are empty?
This is how my looks: oauth_token=&
//LE
Posted 1 year ago #
Do you by any chance have some crazy values in blog url and wordpress installation url?
Posted 1 year ago #
@berinder : that's it, when I post my post, an item is automatically created on flatrr, but when I'm on my account, theses posts seems not "linked" to.
@Michael Henke : sorry (french) but i don't understand, what do you mean? which values?
Edit for @berinder : yes, same for me, after token=, it's empty, i just have [...]oauth_token=&access[...]
Posted 1 year ago #
In your wordpress dashboard you have to configure a blog url and a wordpress installation url if that differs from the blog url.
And what do you mean by "not linked to". What's your flattr account name?
Posted 1 year ago #
@michael okay, the url (pixellibre.net) is the blog, it was installed automatically by OVH, in a "www" directory, on my account so, i suppose that's it's good? if not, where i can check theses informations?
For flattr : My account name is numendil too. When you click on a flattr button on my blog, you can see the flattr page, my name and my account but, when i'm logged into flattr, i can't see theses post (in "My Latest things")
Posted 1 year ago #
You can't see them, because there is no "Thing" created for any entry on picellibre.net. It will be created as soon as somebody flattrs a blog post by you OR you finally get the authorization done ;)
Posted 1 year ago #
Uh?
you mean, if all my posts which are automaticaly flattered stay with 0 flattr, i'll be unable to see them in my flattr acount, "linked" to me?
if it's this, okay, but, for the authorization? :(
Edit : omg, ok, i was looking for your flattr and your comment on one of my post, it works!
So, first part of the problem resolved, my posts are my posts :) but now, how can I authorize the blog with flattr?
Posted 1 year ago #
I think there is a slight missunderstanding here.
1. All your posts are not flattered unless somebody decides to click the flattr button.
2. If someone clicks it for the very first time, the configured URL is submitted to flattr.com and a corresponding THING will be created. That is the representation of you blog post in your flattr account.
3. If you are authorized with the plugin correctly, your blog post is submitted to flattr.com as soon as you publish it. It is NOT flattred!
Clear? :) Yes Your Posts are Your Posts and will stay your Posts.
Now, for the authorization, the problem is that the plugin can not correctly communicate with the flattr server.
It could be a problem with your webserver that does not allow communication of your hosted server to the flattr server. I might figure out what is the reason for that but there is a little chance that (If I'm correct) it might never work on your webserver because of your hosters regulations.
Posted 1 year ago #
okay :), I understand for the 1st point
for the second too
for the third point, i understand too and that's "the problem", I mean, before and on another blog (without the widget because of javascript restrictions), when my post (on my blog) was finished, i was going my flattr account, submit a thing, obtain a static html code and then the post (of my blog) was also a post on my Flattr account.
If I understand all (really sorry =/), the plugin will generate a thing on flattr IF and ONLY IF someone click on the flattr button. Then, except if one post is flattred, it will not appear on my account and on flattr if someone is looking for all my posts, right?
So, the plugin works great and it's a very good news :)
For the authorization problem, i understand too and it's okay but, if you wanna try, contact me, i'll give you all informations i have.
Just a last question, when you're saying my hoster regulations, it the way my hoster works (the way he receive or send requests etc etc?)
In all cases, thanks a lot for all theses informations and for your help :)
Edit : @berinder : what is your hoster?
Posted 1 year ago #
As for the hosts restrictions i think i shall look thru the lib and output som debug-messages, i believe there is some lib that uses some resource i don't have access to on my hosts php-installation. Since it is before the request is sent to flattr it fails to create the oauth_token...
Will check it out when i get the time and return with my findings.
Posted 1 year ago #
Having the same issue. All settings are correct, the oauth token is not in the authorize URL. Using WP 3.1.1. with multisite.
Any ideas?
Posted 10 months ago #
I have the same problem. I have already cleared all cache and cookies and tried to use another browser. It doesn't have any effect. How to authorize the application?
Posted 10 months ago #
After some Flattr plugin debug, I have found the source of the problem. The problem is out of sync time between oauth server and blog server. I have added print_r() to flattr_rest.php file on line 506 (after request to oauth server), and it shows me this:
Array ( [oauth_problem] => Expired timestamp, yours 1311753375, ours 1311752892 ).
As I noticed, the difference in time is always 483 seconds (maybe different). So I changed my generated time in oauth.php on line 477:
return time() - 483;
And after that all works fine :). I can't synchronize server time, so it was the only way.
I think this comment will be useful for you.
Posted 10 months ago #
I've also the same problem.
Following the instructions of TheSteelRat, i've got another error :
oauth_problem=OAuth version '1.0a' not supported
Posted 10 months ago #
Do you have the latest plugin version?
Posted 10 months ago #
Yes, I've the 0.9.25.4.1
Posted 10 months ago #
Then I recommend you to reinstall plugin (delete the plugin directory).
Posted 10 months ago #
I've tried to remove/reinstall the plugin and delete options in DB, but always the same error.
Posted 9 months ago #
So, there's no solution for my problem ?
Posted 9 months ago #
This can very well be a problem at your hoster and totally unrelated to the plugin or API code...
Posted 9 months ago #
I run the latest Wordrpess (3.2.1) and the latest Flattr Plugin (0.9.25.4.1). I tried the cookie/cache deletion. I tried 3 different browsers. I tried different callback domains - no help. I always end up with "Callback Error. Please clear..." after I click Authorize.
I cannot test TheSteelRat's suggestion. I'm not sure where and how to add print_r. For me line 506 is a "return" - so I don't see what to do there. I'm not a real programmer.
I have a very widespread German/English host (Host-Europe). They should be configured fine.
So I dunno what else to do - and get a bit annoyed having to put everthing by hand on flattr.
Posted 9 months ago #
Anybody alse with Host-Europe NOT experiencing this problem? It could very well be that your hosters firewall rules forbid direct communication of the flattr plugin API with the flattr webservice... Numerous people report communication issues with their cheap-hosters...
Posted 9 months ago #
I've finally found the source of my problem. It's due to the "WP To Twitter" plugin who have also OAuth classes but use 1.0a version.
I've rename the oAuthRequest class in Flattr plugin and now it works ^^
Posted 9 months ago #
I wouldn't know how to rename any oAuthRequest in the Plugin. This is all a bit over my head. I don't even know what an oAuth really is. I don't have "WP To Twitter" - and the only plugin that sends stuff to other sites is Akismet, for all I see.
That one works fine though. And the provider is good quality - considering their size I would think they wouldn't have unusual settings. Maybe I could check with them. What specifically should I ask them for?
Posted 9 months ago #
The problem is historical,
Flattr and some Twitter plugins use a generic oAuth class that they derived their specific subclasses from. As we first discovered the problem with duplicate function definitions, we decided to encapsulate Flattrs oAuth implementation. This would result in class definitions if not yet defined. Now whatever plugin occupies the oAuth namespace first can define it's functions and Flattr will use them as well because they should be generic, right?
But if Twitter plugin developers claim that oAuth and especially Flattr are not their concern this can become a hassle as soon as they make specific additions to the otherwise generally used classes and functions. Developers can get very reluctant on that :(
Best thing to fix the problem would be to encapsulate Flattr oAuth library to a private namespace. This would fix all incompatibilities at once at the cost of additional memory overhead in the php engine.
Posted 9 months ago #
In addition I have to say that I can't work on the plugin anymore until middle of september as I'm pretty occupied with live and work stuff. I've got some fixes on the test bench already thanks to bloggers extensive feedback but I'm lacking the time for proper testing and further fixing... Sorry about that.
Any development on this issue?
I'm using the plugin version 0.9.25.5, WordPress 3.3.1. Disabled all plugins that use Twitter, didn't help. Still the problem that "token" is empty.
thanks
Posted 4 months ago #
I'm also still struggling to authorize the plugin. For some reason I can only choose "(re-)Authorize with Flattr."
I've tried to delete the plugin and re-install it. Still, when I push "(re-)Authorize with Flattr" I get "An error with the sent parametrs occurred. Go back"
This is the address: https://api.flattr.com/oauth/authorize?oauth_token=&access_scope=read,readextended,click,publish
Anybody have a clue what's going on?
Posted 4 months ago #
Please install the update as soon as it is available for download. It should fex all authorization issues.
Posted 4 months ago #
Hm. I've just installed the Flattr plugin from scratch — it's my first time (so I've got a clean database!) and I'm a brand new Flattr user.
I have the same issue as @mabahi above. The URL for authentication is the same, the error is exactly the same, the page seems to be the same.
Plugin version is 0.9.25.5. My hosting provider is Dreamhost, which usually has no problems in contacting external sites, with three (possible) issues:
1) Sometimes, Jetpack also fails to connect under PHP 5.3. The solution is to go back to PHP 5.2, attempt to connect, and try again. Should I do the same for Flattr? What do you think?
2) I'm using W3 Total Cache.
3) My blog (http://gwynethllewelyn.net/) runs behind CloudFlare. Again, this usually doesn't make any difference, but it might — I would probably need to punch a hole through CloudFlare.
I've registered another site as a test, which is also hosted on Dreamhost (but with PHP 5.2 FastCGI instead of PHP 5.3), uses W3 Total Cache, but doesn't use CloudFlare. I got precisely the same errors.
This latter site has an advantage: I can bring it down (it has next-to-zero visitors). So I did the following experiments:
- Downgrade to PHP 5.2 (not FastCGI). Same errors.
- Deactivate W3 Total Cache. Same errors.
- Deactivate all plugins except Flattr. Same errors.
So my guess is that Dreamhost is to blame. Jetpack is also misbehaving, so that could be a hint. I'll try again tomorrow early morning (less traffic on the 'net) and see if the problem remains.
And I'll try to install Flattr on a different hosting provider, too.
This topic has been closed to new replies.
