Home » Posts tagged 'masslandlords'
Tag Archives: masslandlords
In late 2013 we switched our membership management system from a Google spreadsheet to WildApricot. It was so good I got giddy. I could search specific fields across all members. It would send automatic renewal reminders. We could have members-only forms, event registration, and a directory. I was over the moon.
Alas, all good things… The same time we chose WildApricot as our back-end, we chose WordPress as our front-end. This, it turns out, meant WildApricot’s days were numbered.
iFrames as Wild as an Apricot
WildApricot says it integrates with WordPress via iframes. There’s a little web page inside your main web page. They call this a widget. I’m fine with “widget.” But this is not an integration. There is no communication with WordPress whatsoever. And use of iframes causes problems for browsers that block third party cookies. This includes all iThingies and Macs. In our case, that’s 25% of our users. These folks couldn’t log in until they first visited a WildApricot site, received the cookie, and returned to the original page.
WildApricot’s help docs claim you can resize iframes to fit your site. But some developer at WildApricot didn’t get the memo and started using CSS floaters. These notify users about special messages. They are important to see. The one in the image below is trying to say that your membership is overdue for renewal, so “click here!” But the floater has ignored the iframe width and carved out space off-frame, beyond the iframe. It actually looked like this on our site:
We hacked their floater to wrangle it down into view the way you have to leap onto a stack of helium balloons to squeeze them into your car.
PayPal Integration Guarantees Lowest Possible Conversion Rate
Maybe I picked the wrong version of WildApricot’s plethora of payment options. I don’t know. All I do know is that we switched to stripe. We used wpstripe without any back-end API connection. Even though we then had to manually add new members to WildApricot, we were FAR better off. Suddenly new members were converting left and right.
In November 2014 I made the following note in my log, “The PayPal integration is awful.”
In general, any time you have to leave a site to pay, or enter too much information, you’re giving your customers a bad experience. It’s like pushing your grocery cart next door to pay. You ask, “Am I in the right place?” And they reply, “Maybe, give me your social security number and I will check.”
Our members tend to be of the generation that’s somewhat distrusting of PayPal. They would rather pay via what they perceive to be a secure paper check. Our simple stripe checkout generated none of these complaints about perceived security.
A Forum for Quiet Meditation
WildApricot members can’t post to the forum via email. This is a huge barrier to adoption with less computer savvy members.
The forum experience for members who are admins is really difficult. They can’t view the forum when logged in as an admin. Not allowed.
We switched to Google Groups. This left us with a lack of connection between our forum and our membership database. But again, even though we had to have someone add people manually to Google Groups, we were far better off. Our Google Groups stayed in sync and participation was robust.
Meanwhile, in the WildApricot forum, I sat quietly and pondered the meaning of life all by myself.
Good Email Reminders
I like the way WildApricot sends email reminders for new members, lapsed members, and other things.
But I have more complaints
I don’t really like the way WildApricot does members-only documents, where the link is public but just hidden. That’s open to brute forcing and sharing.
Their HTML edit windows are awful. If you paste in rich text from another editor they’ll say, “Cleaning html!” and then delete everything you’ve pasted in. (I wasn’t pasting anything crazy. WordPress handles the same text correctly.)
Their customer support is unfeeling. The number one answer I received: “try a different browser.” (Okay, so I will email all my customers and tell them to use a different browser.)
But here’s the thing about WildApricot: it took us three months and almost a dozen WordPress plugins to replace what they were offering.
Back in November 2014 I wrote, “We’re using WildApricot as an integration with a WordPress front-end, which I realize puts us in a class above your target user, in terms of sophistication. As we head down that road, I anticipate outgrowing WildApricot. But in the meantime, you’ve given us a lot of value and we’re not looking to leave just yet.”