Why lock entire plugin with private etc?

  • Zahak

    (@zahak)


    10 years, 10 months ago

    Hi,

    First when I found this plugin I thought that it was great. Didn’t look inside the code, just picked the function and everything was fine.

    However, now I do have an issue, as someone not only want the users tweets, but an entire list.
    https://dev.twitter.com/docs/api/1.1/get/lists/list

    I can understand that the plugin don’t have this or all other features out of the box, and I thought that I could just extend the class to add the functionality I wanted. However, as pretty much everything is using the prefix private, it is not possible to create a decent extension. I also noticed that everything else is pretty locked up as well.

    If the plugin really are for developers, it should be flexible and easy to extend. My suggestion is to make it easier for others to use same authentication process in order to do other requests as well. One step towards this is to change those private parts to protected etc.

    Best regards,
    Johannes

    http://wordpress.org/extend/plugins/oauth-twitter-feed-for-developers/

Viewing 1 replies (of 1 total)
  • Plugin Author Liam Gladdy

    (@lgladdy)

    10 years, 8 months ago

    Hey Johannes,

    Sorry for the delay – we’ve been really busy and neglected the plugin a bit! But we’re going to make some changes soon and absolutely want to make this more inclusive.

    If you’re interested, you can edit our code on github and submit a merge request if you want to help out! https://github.com/stormuk/storm-twitter

    But stay tuned, and we’ll get this stuff sorted in the coming weeks 🙂

    Thanks,
    Liam

Viewing 1 replies (of 1 total)
  • The topic ‘Why lock entire plugin with private etc?’ is closed to new replies.