Support » Plugin: Social Share Icons & Social Share Buttons » You don’t work out of box

  • Resolved seasoned_geek

    (@seasoned_geek)



    Your plug-in wanted me to hack the source for a theme.

    NOT COOL!

    Well, you asked why I deactivated and will no un-install. That’s it. A skilled developer would correctly design the plug-in so a theme didn’t have to be hacked.

    That’s what you get with AGILE development, hacking on the fly with no planned architecture and at best marginal quality.

Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author socialdude

    (@socialdude)

    Hacking the theme? Could you please specify what you are talking about? Please copy and paste the relevant text here.

    seasoned_geek

    (@seasoned_geek)

    Error : Please fix your theme to make plugins work correctly. Go to the Theme Editor and insert the following string: <?php wp_head(); ?> Please enter it just before the following line of your header.php file: </head> Go to your theme editor: click here.

    Yours is the only plug-in which has asked me to hack my theme.

    Viciously poor design.

    Plugin Author socialdude

    (@socialdude)

    @seasoned_geek, before you accuse and use such strong language, try to get to the bottom of it first.

    Your theme is missing it, even though it is clearly stated in the wp guidelines that it should be included, see https://codex.wordpress.org/Function_Reference/wp_head.

    So it’s a mistake of your theme. Correcting this mistake is a simple thing, and we give a quick fix for it. You don’t have to apply it of course if you don’t want to, but I think you should rather have a word with the developers of your theme, than leaving comments like this before understanding what’s going on.

    seasoned_geek

    (@seasoned_geek)

    No, It’s a mistake of the developers creating this plug-in, PERIOD.

    I’ve been writing software for over 30 years. I’ve even written a lot of books about writing software. Check out “The Minimum You Need to Know” series.

    A failure caused by a developer reading the word should in a specification and interpreting it as must is just that, a developer failure. One which will never slide through proper software development methodologies, but will take the express lane through AGILE every time.

    This is the first plug-in I’ve ever encountered to make such a mistake.

    Forcing someone to hack a theme creates a broken theme. They will either be trapped into a cycle of having to hack it each and every time an update pushes out or the theme will just cease to work because of your plug-in.

    The language was not too strong. The criticism was and still is accurate. This was a developer failure, believing a “recommended” thing in a “guideline” was a requirement in a specification. Nothing could be further from the truth.

    Take it easy bro. It’s not the end of the world.

    @KOOkaine,

    It is for anyone trying to sell a version of this.

    Alright, I see.

Viewing 7 replies - 1 through 7 (of 7 total)
  • You must be logged in to reply to this topic.