Any PHP devs here, that also use MembershipPro?

Hi All,

I cleared this post with Tuan and would like to put it out there, as I'm tearing my hair out and you wouldn't believe how ignorant the 'Freelancer' based project sites are, loads seem to bid but simply don't know how to communicate effectively = slowing me right down.

First things first, are you a PHP dev AND do you actively have working knowledge and the inside workings of MembershipPro component? If so, I'd like you to digest the below and consider getting in touch with me.


Project Description:

I am seeking trustworthy and well-reviewed Joomla plugin dev's on here, that would be open to an Urgent small project that I have, to help me get my 2 x OS Solutions MembershipPro subscription plugins 100% working please.

I've already paid out for the completion on these 2 plugins, quite a substantial sum and I am not willing to be "Burnt" again, with lack of timely Dev communication.

See main component here: joomdonation.com/joomla-extensions/membe...ip-subscription.html

See their Developer Documentation here: membershipprodoc.joomservices.com/developer-documentation

I've had them previously developed and they are in my possession but that dev didn't complete to 100% working functionality, before he went totally "Dark"; even though each plugin only has what should be deemed a singular minor misconfiguration somewhere within them both, I am led to believe they should be quite simple fixes for a dev.

They are both Joomla plugins, both are for a Membership / Subscription component called "Membership Pro" which is made by Joomdonation;

1) A ‘GoCardless Direct Debit Payment’ plug-in, gives my sites clients the option of paying for their monthly subscription, by recurring direct debit (this is a hugely used payment option by business in the UK) developer.gocardless.com/ & gocardless.com/features/

The plugin is originally Joomdonation's own "GoCardless Direct Debit" payment plugin but Joomdonation didn't make it work with GoCardless's "Recurring" part of their system. The prev developer made this happen.

The current issue with this plugin, is that the dates of "Recurring" collection for payments once the first initial purchase of a subscription plan of my sites is done, doesn't seem to 100% respect the dates of a clients recurring actual MembershipPro Subscription Plan date collection, that is set by me in the backend, when I create new product / subscription service plans.

Therefore, it seems to have an issue with the "gocardless payment collection times being out of sync for when the plan is set to collect payments"... so likely a misconfiguration in this plugins link to the gocardless api and back to the membership pro system.

I did have a sandbox account that the previous dev setup, for me to test with test membership subscriptions but of course, will need a new one setting up if you take this project on.

2) A ‘3rd Party Supplier Notification’ plugin to once a client has paid for their first months recurring subscription of any of my current or future product / service subscription plans.

This in effect acts like a Purchase Order for my supplier, so they can provision and then deliver my clients services as required. Also a copy of the systems invoice to be sent to my supplier upon ANY MembershipPro account action, such as New Subscription, Renewal, Upgrade or Cancellations, of a clients recurring subscription, so the supplier can configure the services at their end and gain the correct information to do this.

The stock MembershipPro notification emails and messages are triggered on [TAGS] action, which work on the whole in this past dev's "3rd Party Supplier Notification" system he did for me.

However, it doesn't seem to be picking up my custom subscription plan fields for this component, so it doesn't actually populate any of my additional email notification messages, when I insert custom field [TAGS]

membershipprodoc.joomservices.com/basic-setup/emails-messages See the stock Email & Messages system documentation here.

The previous Dev created this plugin, that sits in a new tab in all Current or future created Subscription Plans, called "Notifications"

Note #1 is the stock membership pro emails and messages ability, available to send admin (me) and end users various action messages, I still make use of this.....

Note #2 is the new additional "Notification" tab, which enables me to send action messages, including stock subscription field tag data AND custom field data, to 3rd party suppliers, so they can provision my clients services and this is the one that's having the issue with not ALL of the possible [TAGS] populating.

The issue with this one, that he didn't finish, is that under further testing by creating some demo subscription plans; the stock [TAGS] populated in the "Notification" emails to my supplier seem to work and populate with the correct "action / information", but the MembershipPro "Custom Field" [TAGS] didn't.

I asked a Dev of this Joomdonation MembershipPro component, what could be the reason and he replied with this;

"Hello. As you figured out, this is not related to Membership Pro. The email has issue is from third party developer plugin code, so he will need to check and fix it If he re-use some code in Membership Pro, please tell him that Membership Pro use [TAG_NAME] syntax instead of {TAG_NAME} as I can see in the email. Anyway, please ask the developer to check it for you. It should not be hard to check and solve this issue as he wrote the code. It is just a matter of str_replace call, I guess."

I have many custom field choices so these are just as important to give me the scope to personalise the "3rd Party Supplier Notification" email messages.

membershipprodoc.joomservices.com/basic-setup/custom-fields Custom Field documentation here.

I look forward to possibly hearing from somebody soon, if you have any further questions to further understand my requirements / needs and end result, then please do not hesitate to send me a private message.

However, please only reply if you're trustworthy, know your stuff and can bug fix these 2 plugins, implement the required code tweaks and deliver the final version plug-ins in a SECURE manner, the latter is hugely important due to the nature of my business.
Thanks in advance.
*PLEASE NOTE* no canned bids / replies, only personalised contact about the project will be considered.

Now I'm more than open to releasing these 2 completed plugins for other members of the MembershipPro paying community, should anybody also like the sound of both or either and you can put it to use on your site. As for how we collectively keep these 2 plugins in tip-top shape and the code secure and so forth, in this kind of offer - I'm not too sure but open to ideas.

I only have a budget of $200 for these bug / compatability fixes, having already forked out $880 for the 2 plugins, which admittedly are probably 95%+ working, it's just getting the 1 issue in each one ironed out, to reach 100% working capacity and then happy days.

If you are interested, please get in touch with me and I will still have to ask for references, portfolio of some form of similar work that you have done in the past and of course, if you agree to help out due to the nature of my business, I will need you to look over and sign a standard Mutual Non Disclosure Agreeement (MNDA) but that's purely a formality and nothing to be concerned about, it helps protect both parties.

I look forward to hopefully hearing from somebody in due course.

Regards,