Justin Handley

I didn’t put a link as it is in the admin that the form was missing. However, we resolved this issue.

Awesome – thanks!

I’m running 2.0.21 which is the latest version, and the code fix referenced is not in the code.

It is line 1394 – adding the check to make sure wp_doing_ajax isn’t true when you lock a user out.

Current version:
if(!current_user_can(‘manage_options’) && $this->get_setting(“wp_userlockout”) && !isset($_POST[“action”])) {

Working version:
if(!current_user_can(‘manage_options’) && $this->get_setting(“wp_userlockout”) && !isset($_POST[“action”]) && !wp_doing_ajax()) {

Hi Frank – yes, it has been resolved in that code. Whether WP Engine or Infinite WordPress use calls to admin-ajax is a moot point, there are plenty of plugins and usages for the API that may use that technique.

This update technique is on Flywheel, which is actually owned by WP Engine, so to say WP Engine doesn’t use it isn’t actually correct.

In any case, the whole point is – it is a less than one line code change, it would be nice if it were actually part of the plugin instead of us having to hack it every upgrade. Is there any good reason not to just build it in?

I wouldn’t actually consider this a resolved issue until this change is merged into the core source code. This is still an issue – pilotpress breaks anything else that needs to make calls to ajax.

Justin

I don’t have a solid idea. We are still in communication trying to get the rewrite approval ready – that will hopefully happen this week – so maybe sometime next week if all goes well.

Hey Guys – sorry – just an update.

We should be submitting the new version using Oauth and the current REST API to WordPress tomorrow or the next day. We have it all working, and the only issue right now is that data mapping is different, so when you upgrade your maps are all lost. We are working on resolving that, but a shiny new version should hopefully be out in a week or so.

Sorry for the delay. We basically ended up having to rewrite the whole thing from scratch. On a positive note, our version does some cool things like.. let’s gravity form cookie just like Infusionsoft so affiliate tracking and web based automation work.

Hey There,

So, two things..

1. That error doesn’t (really) matter – it won’t break anything. You shouldn’t have debug mode on in production, and it is just a warning, not a failure, so if you are on a live site you shouldn’t see that show up at all.

Having said that, it is deep in the core of a legacy Infusionsoft SDK, which we are trying to get rid of entirely, which is why it is taking so long. Even our updated version currently throws that error – until we can replace the whole Infusionsoft connection it will stay there, as it is in their old XMLRPC api code, notthe plugins code at all.

Hey @michaelbourne, @ste5en and @russ2204 – we are actively working on taking over the plugin – we’ve had the code reviewed and it failed a security audit, so we need to fix some things up (these are existing issues in the plugin, not related to our new work, but it is a pretty complex plugin and we haven’t reviewed it line by line – I guess we will now!)

As soon as it is secure we’ll submit again – unfortunately the whole process takes some time so it might still be a couple of weeks.

actually – one more attempt- I don’t have commit access to the plugin – can you grant that?

Never mind – sorry – got it – I’m in. Thanks!

Hi There – can you send me the subversion URL – I’m not seeing it on the advanced screen and I didn’t get an email or any notice that I was added to the project?

Did you guys ever figure this out? I’m getting this now – also have used it successfully on a lot of sites, not sure what causes this?

Thank you – I really appreciate you giving me that much detail.

It is variations on this theme

[gdoc key=”https://docs.google.com/a/justinhandley.com/spreadsheets/d/15q2H_X0nohUJs8vgZ6NFiHrtU5lBKrEQLM1dJoQgB6E/edit” gid=”2078888428″ class=”no-datatables” query=”SELECT B,N,C,D,E,F,I,J,L,K WHERE A=’Long – Bullish Index'”]

using different where statements.

That one powers the top block, where columns F and I aren’t showing.

I did just notice one thing – both of those columns are generated using formulas, not hard coded values. Could that be the issue (although, as I said, this was working for a very long time as is)