Jera Nirodha Simpson

Fixed by editing the sandbox api url as mentioned above and then adding this to class.cf7pe.php at line 117

				 $execution = new PaymentExecution();
				 $execution->setPayerId($_GET['PayerID']);
				 $execution->addTransaction($payment->transactions[0]);

				 $result = $payment->execute($execution, $apiContext);

				 $posted_data = $from_data->get_posted_data();
				$data = [
					'transaction_id' => $payment->getId(),
					'payment_amount' => $payment->transactions[0]->amount->total,
					'payment_status' => $result->getState(),
					'invoice_id' => $payment->transactions[0]->invoice_number
				];

				add_filter( 'wpcf7_mail_components', array( $this, 'filter__wpcf7_mail_components' ), 888, 3 );
				$this->mail( $from_data, array_merge($posted_data, $data) );

You can also then use [payment_status] inside the mail template to see the status etc.

Hey,

We’re working on a completely new version of the plugin.

It should be complete in the next month or so.

The new version will be fully tested in 5.* and will include a bunch of extra safety measures.

Cheers,

Jera

Hey Hein,

My apologies for not getting back to you sooner.
I am not sure what you mean by having two tickets running, I could only see one message in our system from a couple of weeks ago.

I wish we could provide you with the correct support to get your website working with those 3rd party security plugins.
Unfortunately at this time my priority is rebuilding the WP Remote update functionality to include better safe guards, as there were a few problems with the update feature when we inherited the plugin.

While you personally may be having more issues, please be aware that before we took over the project there was no support provided at all and there was absolutely no safe guards in place to validate plugin updates.

Anyway, I have just sent you a message on our ticketing system, as it is much easier to track the conversation on there.

Kind Regards,

Jeramy Simpson

Hey,

I just pushed a fix to this problem.

As I am unable to replicate the original problem that caused the legacy update to proceed, I cannot test your particular scenario.

If you have any problems, please send me a message on intercom (bottom right corner).
I’ll be around all weekend, if you have any further issues.

Kind Regards,

Jeramy Simpson

Hey,

The alternative updates is something that happens when a website starts responding that WP Remote is not installed, when it is.

I am still working on determining exactly what causes the website to respond like that, however I haven’t been able to replicate the problem on my server; making debugging a little difficult.

It should not however update all plugins when it fails. I think there must be a hole in the logic, making it think that it was an update all function.

I will investigate this right away and report back.

Kind Regards,

Jeramy Simpson

Hey,

More than happy to help you with any issue you may be having.
This is the first I’m hearing of a false positive issue.

When is the last time you had an issue updating a website?
We did have an issue with a new “safe update” feature that would be blocked by certain firewalls, however everyone is so far reporting that it has now been resolved.

We also have a version of the application from before the “safe update” feature available at https://app.maek.it/old-remote
While it is missing these newly integrated safety features, it is a tried and tested build of the application that has been around for years.

If you would like me to investigate your issue further, I do need you to send us a message through intercom, the chat icon in the bottom right corner.
This will allow me to see all of the logs relating to your account so I can find out what is going wrong.

Kind Regards,

Jeramy Simpson

Hey,

We are actively working on getting Premium Plugins and Themes updating through WP Remote.

I just created an issue on GitHub so you can track the progress of this feature.
https://github.com/MyWorkAus/WP-Remote-WordPress-Plugin/issues/180

Rest assured this feature is at the top of my priority list and expect to continue work on it the first week of the new year.

Kind Regards,

Jeramy Simpson

• This reply was modified 6 years, 11 months ago by Jera Nirodha Simpson.

Just an update on my previous message.

I have made a change to the update process so that if the ‘safe update’ fails, it falls back onto the older method for updating.
That means you won’t have to use the old-remote url to perform updates.

I will continue to work on the underlying issue and try to figure out why certain hosts are blocking the new requests.

You can track the progress of this issue at:
https://github.com/MyWorkAus/WP-Remote-WordPress-Plugin/issues/179

Hi Mitch,

It appears a few web hosts are blocking our new “Safe Update” method that got pushed earlier this week.

I am working on this as my highest priority, but in the mean time you can continue to use the previous version of the application by visiting:
https://app.maek.it/old-remote

In future, I would recommend sending all support requests through the intercom chat application that is located on the bottom right hand side of the screen.
This allows me to easily respond to your requests quickly, as I only check the forums once a day.

Kind Regards,

Jeramy Simpson

Hey,

It looks like I’ve been able to resolve John’s issue.
It appears that the server was responded with a 401 code because of a get param’ being sent.

Not sure if the two issues are related, however I can see hundreds of updates processing successfully on other accounts.

I’ll continue the conversation with both of you over on our Intercom messenger.

Kind Regards,

Jeramy Simpson

Hey,

We just pushed a new ‘safe update’ method today, which could explain this issue.

Everything appears to be working in all of our test accounts, so there might be something specific to your account.

If you visit this link, you’ll be taken to the old version that uses the previous update method: https://app.maek.it/old-remote.
In the meantime, you can go to this link and perform all your updates like normal.

Normally I would be able to jump in and see the problem straight away, but because you’re using the WordPress support system, I am unable to see your user details.
Can you please send us a separate support request through our intercom messenger (bottom right corner of the screen, when logged in).
This way I can work out why your updates aren’t working correctly.

Kind Regards,

Jeramy Simpson

Hey,

I have been working very hard to fix the speed issues and connection drop outs that some customers have been receiving.

In particular, I resolved an issue last week where our load balancer would drop connections and timeout when a large amount of queries were sent at once.
Since resolving this issue we’ve had no reports of this ‘drop out’ issue occurring.
If it is still happening then the issue will most likely be some sort of connection problem between our servers and the website; normally caused by a firewall. I am more than happy to look into this issue if you send us a message via our support system found inside maekit.

I have also released a new version of the WP Remote page today to reduce initial load time and subsequent refreshes. On a slow 3g connection I have found the load time to have decreased by more than half.

Lastly in regards to the plugin deactivation issue, this is something that has been a problem since before maekit took over the project. We have put in several fallbacks to try and rectify this problem. Even if the plugin gets deactivated by a failed update, WP Remote will now try to re-activate the plugin and inform you if it is still unable to do so.
When was the last time you experienced this problem?

Kind Regards,

Jeramy Simpson

Hey John,

I have returned the “remember me” functionality to the login form.

There is a chance that if you leave the page open for a very long time, eg a couple of days without refreshing, that some tokens may expire. If this happens you should get a message telling you to refresh the page; which will fix the issue.

Please let me know if you have any problems.

Kind Regards,

Jeramy Simpson

Hey John,

Thanks for the explanation.
At the moment I believe it is linked to your current session, so if you close the browser it should also end the session.

At any rate I will be ensuring that it doesn’t have this same persistent login issue that the previous version encountered.

Kind Regards,

Jeramy Simpson

Hey John,

I actually have time scheduled in for tomorrow to re-implement the “remember me” functionality.

We unfortunately had to disable this functionality a little while ago as we have some power users that require special security measures.

I will update this ticket as soon as the functionality has been re-implemented for all normal users.

Kind Regards,

Jeramy Simpson

• This reply was modified 7 years, 2 months ago by Jera Nirodha Simpson.