Viewing 15 replies - 1 through 15 (of 16 total)
  • Thread Starter Steven Vachon

    (@prometh)

    My WordPress is not installed in the server root, in case this is an issue.

    Thread Starter Steven Vachon

    (@prometh)

    I am no WordPress expert and editing this particular plugin went a little over my head, so after 3 months of waiting I asked for some help on IRC. Thanks goes out to “greuben” for fixing it in, like, 5 minutes.

    Give us credit in the next release, please.

    Change line 30 in ./extends/init.php to:
    'rewrite' => array('slug' => __($custom_slug), 'with_front' => false),

    Thread Starter Steven Vachon

    (@prometh)

    You released a v1.7 update today without this bug fix implementation…. good job, dickhead.

    Plugin Author Patrick Brouwer

    (@patrick-brouwer)

    Mind your language. If you don’t like the plugin don’t use it. I’ve worked hard on it and haven’t checked this page before I released 1.7. In the next update I will consider implementing your given solution. And ofcourse the credits go to you guys, please give me the full names as we speak ??

    Thread Starter Steven Vachon

    (@prometh)

    Of course I like the plugin; it’s awesome. But I emailed you twice, commented on your blog and had questions in here. 3 months and 2 versions went by without a response. ‘Tis aggravating.

    “greuben” didn’t seem to want to give me his full name, and mine is listed here.

    Please look into my other question as well.

    Plugin Author Patrick Brouwer

    (@patrick-brouwer)

    Sorry for the late response, I’m quite busy with some projects and got loads of questions by mail which some of them I haven’t responded to. I will have a look to all the questions listed here and bring up the next update asap.

    Thread Starter Steven Vachon

    (@prometh)

    F*****’ A!
    : )

    Thread Starter Steven Vachon

    (@prometh)

    v1.7.1 released today without this update.

    Dickhead.

    Steven,
    It’s really classy to badger a guy who writes a plugin for free. If you don’t like it, use another damn plugin or write your own.

    As a plugin developer, threads like this are infuriating. No one owes you anything.

    Clif

    Thread Starter Steven Vachon

    (@prometh)

    I am a plugin developer. He has ignored my requests for a very understandable update. I even provided him the solution. If he finds it infuriating that I “justifyingly” complain, sucks being him.

    Plugin Author Patrick Brouwer

    (@patrick-brouwer)

    Thanks Clif,
    I’m working on an major update right now which going to be awesome! But first, some feature requests are added, which you can expect this week I guess ( excluded the feature request(s) from mr. dickhead of course ?? )

    Plugin Author Patrick Brouwer

    (@patrick-brouwer)

    Steven,

    …don’t really like your attitude, but anyway.. I’ve found a way better solution for your issue..

    Next update you can define your custom rewrite here:
    https://grabs.inlet.nl/screen_shot_2011-07-15_at_12.25.24_f356.png

    Thread Starter Steven Vachon

    (@prometh)

    The evidence, complete with dates, is listed above for anyone to read. I don’t like your passive aggressive psycho dickhead attitude, blanketed in politeness. It’s a lie.

    And this new feature doesn’t appear to offer anything new, aside from a “disable” radio box. But, whatever; cool, someone will probably find it useful.

    Thank you for this plugin.

    Thread Starter Steven Vachon

    (@prometh)

    Thank you for implementing my solution in v1.8

    This bug now appears to be fixed.

    Thread Starter Steven Vachon

    (@prometh)

    Oops, no, this was not fixed.

Viewing 15 replies - 1 through 15 (of 16 total)
  • The topic ‘[Plugin: Simple Portfolio] Portfolio slug issue’ is closed to new replies.