Good…until version 2.7

  • PIW

    (@dbaldan)


    11 years, 4 months ago

    This plugin was great, until version 2.6.96.
    After that, the coders decided to change the way the plugin works, now using Custom Posts. This leads me to many errors:

    – I had to convert all the old downloads
    – I had to fix, manually, more than 100 links because the old codes doesn’t works
    – Now you will have duplicated posts thanks to the Custom Posts. For example, if you make a download called “strawberry”, there will be a post called “strawberry” on your blog and you will need to modify the loop to ignore that new category.

    The last two reasons above totally defeats the plugin. Its not cool to obligate people to edit ALL the entries on our blog just to keep something working fine – when it should be working to start with.

    It was my fault, at the end. I should read all those reviews before update it. At least something good happened: I updated the pluging to test the new version to, finally, buy the PRO version.

    But after this so much headache, I won’t buy it, sorry. I’ve been a user of this plugin since the version 2.3.0

    So, if any other user wants a honest opinion…don’t update it.

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter PIW

    (@dbaldan)

    11 years, 4 months ago

    For who updated it, here is my solution (backup your database first):

    – using FTP, rename the folder “download manage” under plugins folder
    – Download version 2.6.96 here https://wordpress.org/plugins/download-manager/developers/
    – upload install the old plugin by uploading the .zip

    Now my old links are working fine.

    I have a deep respect for the authors, but this were a very bad move guys, sorry.

    Plugin Author Shahjada

    (@codename065)

    11 years, 4 months ago

    Sorry for your trouble, but before v2.7, the plugin plugin using very old and insecure code and each files were using custom data table. But latest version developed using custom post type and taxonomy, which will make it more stable and secure as now it is using native features and functions or WordPress. As it is not using post table rather then custom table, so why data migration is required, but after migration you don’t have to change old file short-code, they should work fine.
    About the duplicate post, actually until 2.7 you had to create 2 post for same thing, 1 for post another for file, now you don’t have to create post separately, as file has its own single details page, you only need to add download with all details. Again extremely sorry for your trouble, but what we did all those extra work to make the thing better.
    Irony is you were a user from v2.3.0, but never came here to give a thanks, but at first change of trouble you come here through all of your anger, you are angry because you needed 1-2 hours of custom work but you never considered 100s hours of works of developer behind the plugin to make it better.

    jleach

    (@jleach)

    11 years, 4 months ago

    I agree. I just updated and had to reverse… at very least, one would expect a “be careful, this breaks your existing files” warning in the release notes/update log.

    I didn’t have quite so many files, so after updating I thought I’d give it a spin, but didn’t found the new interface to be quite a pain to set up and use, so I reverted back.

    Besides which the advertising is really invasive.

    Thread Starter PIW

    (@dbaldan)

    11 years, 4 months ago

    Shaon, I have to disagree with you in some points:

    1- “but after migration you don’t have to change old file short-code, they should work fine.”

    This is half true. Because for the old {filelink X} codes, you still need to update it manually.

    2- “About the duplicate post, actually until 2.7 you had to create 2 post for same thing, 1 for post another for file, now you don’t have to create post separately, as file has its own single details page”

    I’ve update it yesterday at night, so the only option was that one. And I only updated it because there was a BIG warning at the Admin area about unsafe things on the old version. So, the version you are talking about wasn’t avaliable when I updated it.

    And now is my most important point:

    3- “Irony is you were a user from v2.3.0, but never came here to give a thanks, but at first change of trouble you come here through all of your anger, you are angry because you needed 1-2 hours of custom work but you never considered 100s hours of works of developer behind the plugin to make it better.”

    Guys, you really need to learn how to handle feedback. English is not my native language as you can guess, but if you check my post, I never said that I was angry with the authors, I haven’t yelled by using exclamation points, I never attacked any of the authors. I just told that I didn’t like the upgrade, explained my points, and reverted it back.

    But you guys choosen to “backfire” everyone who posted any feedback in a very aggressive way. I saw a lot of “you made this account just to give this bad feedback”, which really don’t sounds a mature way to talk with your costumers.

    The “you are angry because you needed 1-2 hours of custom work but you never considered 100s hours of works of developer behind the plugin to make it better.” was the the icing on the cake. I never said anything close to that. Neither that I don’t respect the 100 of hours behind it. That was kinda childish, sorry.

    You have a valid point: I should come here to thank you, after all those years. My apologizes.

    A final tip for you: If you don’t want (or can’t handle) feedback for something you release publically, don’t release it.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Good…until version 2.7’ is closed to new replies.