MrMaz

This is so motivating right here:

https://www.ads-software.com/support/topic/author-unwilling-to-keep-plugin-updated

Just in case you weren’t sure, I don’t respond positively to public shaming, demands for answers, bullying, etc.

I have had several people who payed for pro support contact me and I fixed their issues immediately with newer code. Not sure what is so hard to understand. It’s very simple: Supporting the free version is not a priority for me right now.

I’m not going to be pressured into retiring the plugin because my current personal and business circumstances don’t match up with someone else’s plans.

If you don’t like the current state of the plugin, don’t use it. If you have pro support and you need help, open a ticket here: https://presscrew.freshdesk.com/support/home

If that isn’t clear enough, I don’t know what to tell you guys.

This is libel. You might want to look it up.

If anyone has purchased the pro version in the past year, which is how long the support is good for, please open a ticket here: https://presscrew.freshdesk.com/support/home

I will fix the issue asap, or refund your money.

I am closing this thread, because it’s not productive at all. I’m getting tired of defending myself for making the choice to not to work for free.

I understand that there is frustration. Please also understand that I have been maintaining the plugin on and off for 5 years by myself. I have many hundreds of hours invested and very little return on that investment. No other developers in the community have stepped up to help.

If the community “expects” authors to put in a ton of work for free, the community needs to step up as well. Do you know how many donations for the free version I have received in 5 years? Three! One for $25, one for $25 that charged back so I got a $25 fee, and another for $1. So for 5 years of free work I have been thanked with a net total of $1 of donations and very, very few code contributions (except for translations).

On top of that, I have made many many fixes over the years for people promising to buy a pro license if I help them out, and maybe two people have followed up on that.

So as you can see, it can be very difficult to find the motivation to spend time away from working on paying clients and products to work only for the love of the code.

Sorry for the rant, but hopefully this gives you guys some perspective on what it’s like on this side of the table ??

@yves

Thanks for the feedback. The main problem is that other projects of mine did gain more traction (for instance my involvement with CBOX) so they got more attention merely by natural selection.

I agree that it needs to be fixed. Personally I love the plugin and the free usage of it is very widespread, and I want to keep it going.

One more thing to consider is that I have tried many times to get other developers on board to share the workload, but they are all busy with their own stuff, lol.

I apologize this is taking so long. To be honest it’s not a top priority because the pro version always had very low sales. I have never really profited from this plugin. I do plan to release updates asap, though.

The best way you can help is to buy a copy of the pro version when the next version comes out. I am also considering switching to a membership model were you get access to all plugin updates for a reasonably quarterly fee to see if that improves investment into the code.

I wasn’t identifying anything specific, it was more of a public service announcement. If something is different from one theme to the next, it’s likely a theme compatibility issue.

You can make feature requests here:
https://presscrew.freshdesk.com/support/home

Please create a separate issue for each feature. I just got the new support site rolling, so the knowledge base is empty.

Thanks for all of the feedback guys.

This plugin was originally developed when the only theme that worked was the default BP theme, and before custom post types were even on the roadmap. Since then quite a bit has changed, and it has admittedly been difficult to keep up since this is arguably one of the most deeply integrated BP plugins.

It needs a significant overhaul to become *mostly* compatible with *any* theme that supports BP. I have only been testing it against the bundled WordPress themes for this hotfix because I know they work well with BP. So the baseline I am trying to reach short term is bundled WP theme support, and then go from there. It’s not feasible for me to test it against a lot of community contributed themes right now, but long term I want to support as many as reasonably possible.

@rosyteddy Yes, the test release I posted was developed on WP 4.1 and BP 2.2. There are still some known issues, but the release resolves the broken page issue that many are encountering.

Thanks for taking the time to test and respond. Very much appreciated! ??

Any feedback?

I posted an update with a link to a test release in the other thread on the same issue:
https://www.ads-software.com/support/topic/links-seems-to-have-stopped-working-with-buddypress-22

Please close this review for comments to avoid any confusion. Thanks again for the report ??

I put up a test release on GitHub: https://github.com/PressCrew/buddypress-links/releases/tag/0.9.1a

You will need to rename the folder to buddypress-links manually after unzipping and before uploading.

Please post all feedback in this thread to avoid confusion, thanks ??

If anyone has a current support contract for the pro version and wants to test that out, e-mail [email protected] and I will get it to you via e-mail.

The fix is done locally but it needs quite a bit of testing. I will try to post a link to a testable release later today in case anyone wants to help with testing.

I’m looking into this issue now. Thanks for the report.