Roquefort

Confirmed. I can send to Gmail but I can’t send to my own domain hosted in Office 365. To clarify though: emails WILL send for me via the “test” tool built in to this plugin. However, other plugins (like Gravity Forms) will not work properly.

Thanks for posting this here, by the way. I’ve been fighting with WordPress for 2 hours now trying to figure out what was going on. Your comment put me on the right track.

@bthoem,

Hey there. I know this post is old, but if you haven’t yet find a working solution, you may want to give Zapier.com + a forms plugin (like Gravity Forms, Ninja Forms, etc.).

It is a much more elegant solution than this one, with a lot of flexibility and a low cost. I’ve been using this combo reliably for well over a year.

Forgive my ignorance. The records were right where they should be… I just needed to allow for more than 1000 rows to be displayed in MySQL.

SELECT * FROM wordpress.wp_posts LIMIT 0, 5000;

I have the same question. I’ve been scouring the database, and I can’t find a record of my custom post type’s content anywhere.

My understanding is that custom post type should be found in the WP_posts table. Since they’re not… my guess is “Types” is doing something non-standard. Which makes me want to try a different plugin…

+1 from me. Being forced to use the standard WordPress roles is much too limiting in my environment.

Hi there,

I found the issue. It was apparently related to the “Display provider names instead of IP addresses.” option; as soon as I turned that off, my reports loaded within a second or two.

Thanks for the reply, though.

Just put a ‘/’ in the regular expressions section. That worked for me anyway.

I actually was going to buy the product but the ioncube requirement is ridiculous. I’ve fought with this DRM before and I’m not going to go down that rabbit hole again…

It’s unfortunate, because the free version seems to work relatively well.

Nevermind! It was an issue with LDAP support – it doesn’t work. I added the user to SugarCRM manually and all is well.

While I am by no means a pro at ADFS/SAML, I do have it working in a couple of my WordPress environments. My first thought is that not using SSL on your ADFS portal sounds like a really bad idea. You should investigate that first; I don’t think ADFS supports non-SSL scenarios.

I don’t have time at the moment, but I’ll see if I can get you some screenshots of my configuration to use as a point of reference.

@ipstenu This is you?

You make some interesting points, definitely. But I’m still not convinced that this won’t work for me. My thoughts are that with the the proper capabilities management, security (like two-factor), monitoring, auditing, and (most importantly) competent developers, this can be as secure or insecure as I need it to be. It may just be a little more complicated to set up.

Ultimately, integration between the two sites is going to be very important to us in years to come, and I’d really prefer to do this right now so that I’m not hacking together a Multisite years down the road.

Also, as a SysAdmin, I feel like maybe I have a leg up on security, since I have the option to use other forms of it like VLAN’s, domain authentication, firewall restrictions, etc.

Well, the Intranet is more of an internal CMS. There is not any PHI, as our billing system/EMR is entirely separate.

The SAML authentication enforces policies which 1) Require the user to have a domain account and 2) require the use of a one-time password to login. It’s two-factor authentication. Every page is redirected to an SSO portal, nothing is indexed by Google because of this except for that portal. And of course it’s protected by SSL, downloads are disabled, etc. In my estimation, this is pretty secure.

I’m well aware of the security concerns regarding HIPAA and I would not even consider doing this if I wasn’t certain that we could meet a high level of security.

The unfortunate truth is that our business model necessitates that this CMS/Intranet must be publicly accessible, as our physicians bounce around between hundreds of hospitals, and the public computers/cell phones that they use will not be able to connect to our VPN.

The newest 1.6.0 update to BP-Docs fixed my problem! Just figured I’d post back here and let everyone know.

Cool! I’ll give it a try once I see 3.5.7 go live.

For what it’s worth, this issue eventually cropped up with WassUp too.

Must be a bug with IIS and BuddyPress, not Slimstat.