rainsey

Hi Ross,

I tested your update and confirm our issue is now resolved. Thank you for your prompt response!!

Kind regards
Andrew

Done, our admin php errorlog shows the following error for the eway plugin.

[26-Jun-2019 08:42:55 UTC] PHP Fatal error: Cannot redeclare wc_add_notice() (previously declared in /wp-content/plugins/eway-payment-gateway/includes/wc-compatibility.php:16) in /wp-content/plugins/woocommerce/includes/wc-notice-functions.php on line 72

same email here after updating to the latest version.

Thanks Kevin,

Works perfect! Our outdated welcome email is no longer sent.

Unfortunately, mc cannot remove our old final welcome email so our only workaround is to use single opt-in. Creating a new final welcome email in mc does not replace the old email. Support at mc have been looking into our issue for sometime.

Cheers

No real or remote cron enabled. The issue occurs when cron is enabled in the wp-config file (as needed for the plugin to work). Our access logs shows the following for each website visit and it is appears the feed is stuck on step 5.

121.200.x.x – – [16/Jan/2019:01:26:00 +0800] “POST /wp-admin/admin-ajax.php?_fs_blog_admin=true HTTP/1.0” 200 15 “…/wp-admin/admin.php?page=woo-product-feed-pro%2Fwoocommerce-sea.php&action=edit_project&step=5&project_hash=xxx&channel_hash=xxx” “Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.98 Safari/537.36”

I fixed our php error by reinstalling the “Schema & Structured Data For WP” plugin. i previously installed this plugin and removed it as we use WPSSO pro.

Unfortunately, installing amp for wp and amp for woocommerce only causes the php error due to installing the new structured data plugin using ampforwp > settings > structured data.

Please fix the php error caused when “Schema & Structured Data For WP” plugin is disabled or uninstalled. A reinstall of ampforwp and amp for woocommerce did not fix the issue.

thanks

We brought your plugin and have a redirection issue when rewards are claimed. I think this issue is caused by our 404 plugin – WP 404 Auto Redirect to Similar Post! This 404 plugin only redirects when a 404 error is generated.

The url link to claim rewards is https://www.example.com?lws-wr-claim=xxxx. Clicking this url redirects to our blog page with the wooreward coupon code popup. I believe this url may be triggering a 404. Advice from the 404 plugin developer suggests that reserved terms need to be used to avoid any redirects i.e. ?lsw-wr-claim-nonce.

Looking forward to seeing the September update.

• This reply was modified 6 years, 3 months ago by rainsey.
• This reply was modified 6 years, 3 months ago by rainsey.
• This reply was modified 6 years, 3 months ago by rainsey.

The new html minify option also breaks our website. The older minify code worked fine.

i have the same issue with amp for woocommerce, where can i add the code above to disable the plugin for urls with /amp or ?amp

thanks,
andrew

Thank you for your prompt response!

We tested pro and found customers are redirected to our blogpage with a popup when rewards are unlocked on ‘my account’ page. We do not have a redirection page set in the reward settings. How do i keep customers on the same page?

Looking forward to the September update. Hopefully the following features may be on the road map:
1. display/use current reward points at checkout, and
2. display reward points earned by buying a product at product page.

Kind regards,
Andrew

we got amp pages to work using the category and product slug options. These options may be generating high cpu usage, we usually average 48,000 cpu usage over 24hrs in cpanel, but now 60,000 cpu usage over 24hrs.

i am not sure if the high cpu usage is due to the removal of base slug or increase in bots yet.

cheers

• This reply was modified 6 years, 5 months ago by rainsey.

fixed, needed to change blog posts number in settings > reading to make the change.

it has an option for caching using memcached

Sitegrounds shared hosting plans only permit 30sec execution time before returning a php timeout error. Unfortunately, Sitegrounds will not increase execution time on our go geek plan.

An option could be added to limit execution time to avoid timeout errors with Sitegrounds (and other low resource hosts)?

great – thank you!

yes, save was not working and no errors were shown. The save button just did not work with those values entered.