WordPress.org

Ready to get started?Download WordPress

Forums

Flattr
[resolved] flattr widget displays error / settings not saved (8 posts)

  1. akos.maroy
    Member
    Posted 3 years ago #

    I just installed the flattr plugin, connected my flattr id with it, but the plugin doesn't seem to work.

    after adding the flatter widget to the sidebard, it displays an !error message. when clicking on the flattr button, it brings me to the flattr integration page.

    moreover, the settings are not saved by the flattr plugin preferences menu (for example, the 'insert flattr button automagically', or the language setting

    is this a common issue? how to solve it?

    http://wordpress.org/extend/plugins/flattr/

  2. Michael Henke
    Member
    Plugin Author

    Posted 3 years ago #

    Do you use a public webserver?

  3. akos.maroy
    Member
    Posted 3 years ago #

    no, this is on my own server

  4. Michael Henke
    Member
    Plugin Author

    Posted 3 years ago #

    your server must allow communication to the flattr service and must be reachable by the flattr service...

  5. akos.maroy
    Member
    Posted 3 years ago #

    can you elaborate?

  6. Michael Henke
    Member
    Plugin Author

    Posted 3 years ago #

    Two things. You can use the JavaScript implementation of the Flattr button with any website as long as it is on websites accessible by public users.

    To use the automatic submit and rss feed button you need to do the complete oAuth procedure. (Like Twitter for example)

    If the button disblays an error (!) this usually means that one of the parameters submitted by the javascript is invalid. Could you point me to your blog so that I can have a look at the website?

  7. akos.maroy
    Member
    Posted 3 years ago #

    Thanks for the detailed info. unfortunately the blog is not as yet publicly available (it's protected by a htaccess password)

    as soon as it is, I'll provide more details...

  8. Michael Henke
    Member
    Plugin Author

    Posted 3 years ago #

    (it's protected by a htaccess password)

    This could be your very problem.

Topic Closed

This topic has been closed to new replies.

About this Plugin

About this Topic

Tags