sunspot10

This is a HUGE problem because the delay in loading pages cause MASSIVE cpu utilization on my site approaching 100%. This problem MUST be fixed soon.

Download from the plugins page, on the developers tab. Click on the version at the bottom that you want to download:

https://www.ads-software.com/plugins/pmpro-woocommerce/developers/

When I backtrack from 1.4 to 1.3.1 and go to the join screen, the following error occurs:
“A Payment Gateway must be set up before any payments will be processed.”

Now I can’t have new members.

This is entirely unsatisfactory and needs to be fixed ASAP. If it can’t be fixed, I may have to switch to Woocommerce subscriptions.

Backtracked to Plugin version 1.3.1, which is the latest, and the problem goes away.

P.S. This problem appears to be a byproduct of the following change in version 1.4
“BUG/FIX: Moved CSS load to proper WordPress action hook”

SOURCE: SOURCE: https://www.ads-software.com/plugins/pmpro-woocommerce/changelog/

See also: https://github.com/strangerstudios/pmpro-woocommerce/issues/50

Will your Onedrive implementation you will release soon use a temporary download url to prevent sharing the link and stealing content? If not, will there be a way to cloak the url so people can’t find out what it is?

Reason for the previous question:

1. Most store software, including Woocommerce, presently has a file size limit based on the PHP timeout interval. Files above about 100MB will time out regardless, and break the download.

2. So far as we are aware, the Download Manager product also has the same limitations. Please indicate if this is NOT the case.

3. Other competing download management products aren’t dependent on the PHP timeout interval, and yet also don’t reveal the full URL so that it can be shared and the file can be STOLEN by unethical clients. Examples:
https://www.ads-software.com/plugins/wp2cloud-wordpress-to-cloud/faq/

Will the Onedrive extensions you will add support files of unlimited size without timing out PHP and breaking the download?

Excellent!

Thanks.

Thanks.

How do you tell if a theme already implements it?

FYI, I fiddled with the settings on the Download Manager. There is a setting called “Twitter Bootstrap”. If you change the setting from “Active” to “Disable Both”, the problem goes away.

P.S. The version of Download Manager installed is 2.8.0.

Installing the TGM 2.5.2 plugin doesn’t solve the problem. Now:
1. There is a warning to update to 1.3 of the pmpro bbpress addon.
2. When you tell it to update, nothing happens.
3. When you look at the 1.3 changelog, its EMPTY!

There is STILL something wrong.

Thanks anyway, but no cigar.
Here is the fix:
1. You can’t do an auto update from within wordpress 4.3. That will try to update to 1.2 instead of 1.3.
2. The WordPress plugins directory still lists version 1.2 as the latest, even though the plugin itself tries to update to 1.3.
https://www.ads-software.com/plugins/pmpro-bbpress/
3. You have to download the 1.3 update from GitHub and bypass the auto update from within WordPress.
https://github.com/strangerstudios/pmpro-bbpress

Jason needs to add version 1.3 to the wordpress plugin directory so that the auto update from the plugin directory will work. Until he does this, the above manual procedure is necessary.

Here is the fix:
1. You can’t do an auto update from within wordpress 4.3. That will try to update to 1.2 instead of 1.3.
2. The WordPress plugins directory still lists version 1.2 as the latest, even though the plugin itself tries to update to 1.3.
https://www.ads-software.com/plugins/pmpro-bbpress/
3. You have to download the 1.3 update from GitHub and bypass the auto update from within WordPress.
https://github.com/strangerstudios/pmpro-bbpress

Jason needs to add version 1.3 to the wordpress plugin directory so that the auto update from the plugin directory will work. Until he does this, the above manual procedure is necessary.

Installing the TGM 2.5.2 plugin doesn’t solve the problem. Now:
1. There is a warning to update to 1.3 of the pmpro bbpress addon.
2. When you tell it to update, nothing happens.
3. When you look at the 1.3 changelog, its EMPTY!

There is STILL something wrong.

Thanks anyway, but no cigar.