Eugen Mihailescu

A live example, maybe it will help you to understand the result: https://mquvee.com/our-productswine-coolers/#tabs_desc_3923_2

As you can see by opening that page by bookmark #tabs_desc_3923_2 it will trigger automatically the click event for the respective tab, thanks to my custom Javascript mentioned earlier.

No reply since my last comment, I hope it get solved.
Topic closed.

Few questions: what version of PHP are you using?

There was an unexpected error when the plugin tried to use your credentials and connect the WebDAV server. Go to the Support tab and click the Check PHP Setup. Make sure the essential PHP libraries are enabled (green, ie. not with red).

If that’s OK then probably you are unable to use that URL from your server. Usually I use the cadaver command-line utility to check whether the WebDAV is accessible or not. Look at the following example:

cadaver https://www.crushftp.com/demo/
user: demo
password :demo
dav:/demo/> ls

If that works from your web server (note: this must be test at the web server level not on your local station) then there is something odd with the PHP libraries you use.

Btw: does your WebDAV connection use other port than port 80? If that’s the case then make sure your URL has the following format: https://hostname%5B:port%5D/path

Oh, but it should work. Please check your browser Console for an JavaScript error message or alike that looks being thrown by a braintree script file (it could be a script within the plugin itself or even the Braintree JS SDK).

Nevertheless make sure the integration JavaScript loads. Open the checkout page, View Source, lookup a line that contains woo-mynix-braintree-gateway-paypal.js. If there is no such line then for some reasons it wasn’t loaded so the PayPal integration won’t work.

If nothing above verifies then just make sure that:

• you have PayPal enabled within Braintree setup for the merchant account you are using within the plug-in
• your shop currency is supported by PayPal
• your shop currency is supported by Braintree

because in such cases it is the Braintree script that won’t initialize the PayPal button for the mentioned reasons.

Please let me know if you found anything mentioned above.

• This reply was modified 7 years, 8 months ago by Eugen Mihailescu. Reason: typo

If you meant the payment method description (which usually is displayed under the selected payment method) then you should know that it’s fixed although the fix is not yet released.
I will mark this topic as closed as soon as I publish the new version (probably these days).

Hi,
Yes I received your message and I replied you right away (02/23/2017 11:26 PM).
Check your Inbox/Spam/Junk folder for an email from <[email protected]> on that day.
You may even use the product forum page at https://mynixworld.info/shop/forums

Regards,
Eugen

• This reply was modified 7 years, 8 months ago by Eugen Mihailescu.

Great. It will be automatically detected & fixed in the next release.

You should update your PHP to v5.5+.

A quick fix would be to comment the following lines within LogFile.php as below:

• line 181: try {
• line 193: } finally {
• line 195: }

Another option would be to use the previous version of this file (v1.0-2) which can be downloaded from the project’s SVN repo:
https://plugins.svn.www.ads-software.com/wp-mybackup/tags/1.0-2/class/lib/LogFile.php

The plugin would still work. The v1.0-3 will additionally take care of some unusual situations which you might not encounter anyway. So it would be safe to use the prior version of this file.

Until an official hotfix is prepared please try any of the above.

Hi,
This is a “new feature” request. I added it to the TODO list.

Hi,
Please use either the forum or the Contact form.
Since you are using the PRO version this does not address the free version so I will close this topic.

Hi Alexandr,

Thank you for your feedback.

I can understand why you suggest different schedules, the files / database could have different change/edit frequency.

The Pro version allows multiple job definition (eg. you could define a file backup job with its schedule and obviously retention time, another MySQL backup job with its schedule/retention time). Unfortunately I cannot promise any change of this very soon but who knows, maybe on a future version…

I would write 2 WP filters and 2 WP action:

1. add_filter( ‘the_content’, ‘last_but_not_least’ , 99999) with lowest priority as we want to be the very last that will be executed
2. add_filter( ‘the_content’, ‘first_but_angular’ , 0) with the highest priority as we want to be the very first that is executed
3. add_action( ‘save_post’, ‘remove_cached_version_of_post’ );
4. do_action( ‘deleted_post’, $postid );

In the (1) filter I would check if there is a cached version of the current page (given by $post) and if it is then the content I would return would be a hijacked angular version of the page (an angular template that will render the cached version of the content).
In the (2) filter I would save the current content of the post to a file on disk representing its cached version then I would return the value of the function given at (1).
In the (3) action I would delete from the disk the cached version of the post, if any.
In the (4) I would remove the cached version from the disk.

The flow would be the following:
– if there is a cached version of the post then return a angular template that would render the cached version (which is just a dumb .html file)
– if there is no cached version then I would create it although I would not return that content back; instead I would return the angular template which would render the cached version of it.

In order to be sure we are in-sync with the post changes (because a post might be changed at a later time) we drop the cache every time the post is changed (ie. created/updated/deleted). This will force the (2) filter to recreate its updated cached version again.

In theory this should work ??

• This reply was modified 7 years, 11 months ago by Eugen Mihailescu. Reason: clarification

I’m glad you like it.
Maybe later you’ll visit my shop to get the full-option PRO version: https://mynixworld.info/shop/woo-mynix-braintree-pro

• This reply was modified 7 years, 12 months ago by Eugen Mihailescu. Reason: typo

Hej, thank you for your feedback.

I never encountered this error before (with the plug-in). What can I say? With the broad spectrum of WP+Woo possible configurations anything is possible.

The plug-in log files – usually stored at [plugin-root]/tmp/logs (as of v0.2.3-34 on wp-content/uploads/wpmybackup/tmp/logs) – and/or the web server access/error log files should spot the error cause.

• This reply was modified 7 years, 12 months ago by Eugen Mihailescu. Reason: typo