Stable version?

For now, it appears that this project is abandoned. If you're interested in stepping up as a maintainer to continue development on the module you might want to contact and ask a maintainer if they will add you as one. Another option would be to consider devoting funds to the project and contacting the maintainers with your offer.

However, all that said, this module is fairly stable as far as I can tell. It just lacks a lot of UI that I think it needs before it's fully usable and merits a production release. I may be spending some time on this project in coming months, but it all depends on where my clients want me focusing my efforts. =)

This project still considered abandoned?

Yes, the last commit was 2 years ago. Co-maintainers welcome!

@bojanz, is there a list we can point to on what's needed?

The list is on the module page.

You got a taker: https://www.drupal.org/node/2448355

Can I get an update? We are once again looking at setting this up and using it. I will be trying to install and test tomorrow as is, but I'm wondering if there is any unseen progress that should be committed so that I can test?

@deggertsen The module works. We are using it in a production eCommerce website. We even modified our custom modules for email address subscriptions to take in the code. You just have to build your own reports which right now sometimes requires a little SQL work. But the good news is all of the data is there, you just have to build your own reports.

That is fantastic news! Been waiting with bated breath, most appreciated! Will test soonest :)

Here's what Perignon and I had to do to get this to work....First, you have to enable all three modules that is bundled here because you need to get to where the rules are located, which ends up being in the last module you enable. Then, you will need to write a rule to add the commission amount to occur on order completion. Everything we needed for reporting was being written out to the commerce_affiliate_commission table and you can write your queries against that, using the parent_entity_id as key to relate to other parts of the order.

Have you tested the other commission types? For some reason I'm unable to enable the other types (see #2506639: Error when trying to enable or disable commission types). Order commissions appear to be working as expected, but not any of the types that come included in commerce_affiliate without the commerce_affiliate_order module.

We tested them and couldn't get them to work the way we thought they should work. Same thing for the Admin screens as we couldn't get any of them to work. We were able to get the functionality we needed through rules by taking action based on the existence of the affiliate cookie. Problem is that you have to have those other two modules enabled to get to the rules.

I saw your other ticket and we'll look into it. In a greenfield scenario, I'd like to get this down to a single module where we get rid of the additional content type modules and admin ui module, leaving the base fuctionality plus rules, and expose the affiliate commission table to views with a base view being included. Would that give you the functionality you need?

@deaconblues, I believe that would give me the functionality I need. We especially need to get the affiliate commission table exposed to views so that we can create reports. I will likely be working on that soon so if you've already got a start on that I'd love to see it (though that should probably be posted in another issue).

I think the idea behind having a separate ui module is so that you can disable it once you're done setting things up to minimize impact on site performance; however, if you have to have the ui modules enabled in order for the module to even function then that defeats the purpose so you might as well not have them as two separate modules...

Having the additional content type module "commerce_affiliate_order" gives a nice example of how others could use the api and build off of commerce_affiliate's base functionality. I personally wouldn't get rid of it. It's also nice to have the option to leave those commission types off if you don't need them.

So I looked into creating reports with views and it looks like it's already setup to work pretty well. Might need some work, but I think we can continue that discussion here: #1608458: Displaying Commissions?

Ok. Let's leave this ticket open for that discussion.

Alright, just to get a list going for what I think this module might still need before we can really call it "stable":

1. #1387810: Edit functionality
2. #2512408: Deleting commissions in a custom view
3. #2506639: Error when trying to enable or disable commission types
4. Need for a separate UI module? As discussed in #12 and #13.

As a side note, I'm happy to be a co-maintainer if you need anyone else. I'm fairly invested in this module at this point so I'd be happy to continue to watch the issue queue and commit patches as needed.

@deggertsen - Agreed. I think it would be great to have you on board as a co-maintainer. The patches that you have submitted have been of good quality and I think it should be green lighted. I tried to add you as a co-maintainer and could not. Can you create a ticket requesting access and one of the module owners can grant access? Note that you really need access to the Affiliate Ng project as well.

@deaconblues
You now have access to add maintainers :)

@bojanz - Thanks for taking care of this quickly!!

@deggertsen - Try this out as you should have access as a co-maintainer now.

Closing this item out as all concerns in this ticket seem to have been addressed.

@deggertsen - Maybe add the list from #16 to the project main info page so it's clear what's left. Or add a new ticket with the list, just something that has better visibility. :)

I've added 1-3 on the project page. #4 I'm still not sure about and was hoping others would weigh in on what they thought. @bojanz, is there a reason a separate UI module was created?

Because Commerce did it, and I wanted to imitate the "best practise". In retrospective, it makes no sense for contribs, and we aren't even doing it anymore for Commerce 2.x. You're free to kill the UI module and merge the code.