Recent content by Hardcore

Good call. Just did the same thing to avoid confusion. Time to expedite upgrading!

Update: Just tested. It's definitely broken. You have to manually cancel in PayPal (or Stripe, etc). Sucks.

More like this (I left two lines of code to explain why): public static function runTlsTest(&$error = null) { // Both PHP and cURL support TLS1.2 $result = 4; return $result; } Again, this is based on the update that @Chris D posted in the other thread and it...

Based on the thread that @sbj posted and the core fix posted by @Chris D in that thread (thanks!)... Edit: /(XF install dir)/library/PemBer/Model/Paypal.php Find public static function runTlsTest Assuming your installs of both PHP and cURL support TLS 1.2, replace everything in the function...

It appears to be broken now. TLS errors with PayPal and members are no longer able to cancel their memberships.

@Xon: Is it safe to assume that installing Conversation Improvements is optional (knowing the search/likes would be removed) and that it's something that could be easily installed post-upgrade of Conversation Essentials? And was pruning conversations removed? I no longer see it in the feature list.

We created an account specifically for the anonymous Warning Alerts and just shut down access to its profile and whatnot. We'd use the same one for anonymous Warning Conversations and simply disable replying.

@Xon: Loving the new update. Thanks! Any thoughts on extending the new "Anonymize As" feature to sending the conversation (if applicable)?

Thanks. I'm aware of how to set it up. I'd like to know how and when these fields sync up once I've set them up. Upon joining? Upon change in XF or MailChimp? Etc ...

Merge fields, and they are custom fields that we pull into XF using the User model. Thanks. Just wondering how it works.

Just installed. Couple of questions ... How do custom fields sync up? For instance, we plan on adding a user location table to the list under the add-on options, and then add hidden fields on MailChimp for state and country. We'd then sync this up with the campaign using the add-on. Location is...

There's no error. It's simply not applying the warning points or expiration when selecting the custom warning, which is grayed out when issuing a warning (with the 1 and 1). This behavior exists with the latest versions of Chrome, Firefox and Safari and is consistently happening regardless where...

Running 1.5.5(a). Add-ons: 4 custom that have nothing to do with warnings, Add-On Install & Upgrade, Change Thread Starter, Conversation Essentials, Prefix Forum Listing, Trophies by Waindigo, Warning Improvement, Xen Notices. As mentioned we did use Warning by Waindigo at one point. Editing...

I believe I used to (but no more, and no other warning add-ons), and it does error. "Duplicate entry '0' for key 'PRIMARY'"

@Xon: We have the ability to change warning points/points expiry disable. Our custom warning defaults to 1 and 1, however, when it gets applied it's 0 and n/a. Other warning defaults under this add-on seem to be working fine.