gzt

“Just to clarify, you would like that when the Yoast SEO sitemap feature is disabled, it would automatically enable the WordPress sitemap?”

You people are astonishingly clueless.

Your plugin BREAKS the core built-in WordPress sitemap functionality that’s already enabled. When the Yoast sitemap plugin is disabled, or the Yoast sitemap feature is disabled there should be no “enabling” required because it’s core functionality that’s already enabled by default – because *drumroll* it’s core functionality.

Yoast is breaking the core functionality.

When Yoast sitemaps are disabled the core built-in functionality should work, just like it does when your plugin is not installed at all.

STOP BREAKING IT!

How hard is that to understand?

• This reply was modified 4 years, 2 months ago by gzt.
• This reply was modified 4 years, 2 months ago by gzt.
• This reply was modified 4 years, 2 months ago by gzt.
• This reply was modified 4 years, 2 months ago by gzt.

“Since disabling the Yoast SEO sitemaps doesn’t automatically enable the WordPress core sitemaps and there isn’t a documented way to enable it, we’d like to make sure that you get the right response.”

This is such a BS response from Priscilla, she’s basically suggesting that it’s WordPress fault, and WordPress has no documentation for enabling it.

FACT: It’s CORE functionality that works out of the box, it doesn’t need enabling because it’s already enabled, and it’s Yoast that’s breaking it.

So ridiculous that Yoast can’t understand the concept of “core functionality”.

This plugin is BROKEN since today’s WordPress update.

The problem has nothing to do with the cache or cookies, I have cleared them and tried in incognito and private browsing on different browsers and it makes no difference.

• This reply was modified 5 years, 2 months ago by gzt.

Having the same issue.

EDIT: Ok, the documentation that says set order=”ASC” or order=”DESC” lies, that shortcode gets ignored and there’s a setting tucked away in the bottom of the options panel where you set it.

• This reply was modified 5 years, 7 months ago by gzt.

It’s a flaw in the design of the plugin, without the plugin it takes under 1 second to upload the image, with the plugin enabled it never happens.

I have a high-end web server, there’s no question the plugin is at fault because I’ve tested it thoroughly and get consistent results.

I found this article WooCommerce Stripe Subscriptions that lists a few options and ranks them. They’re pretty cheap compared to the official plugin.

I found a good review of alternatives here

https://arador.com/woocommerce-stripe-subscriptions/

Wow, that was easy! I now have an Android app running in the virtual device.

Thanks for help guys.

@nchisley how did you create the Play app?

Thanks for the detailed reply Jose!

I now have it installed on two sites and I’m very impressed.

Awesome plugin!

Ok, thanks for the response.

If your plugins were reasonably priced I’d buy them but they aren’t, your pricing is extremely greedy. All your plugin prices including the starter ones are ridiculous and your strategy of forcing people to have to buy “multiple plugins” to get full functionality is very lame.

The sad thing is if you priced them reasonably at codecanyon price levels you’d probably sell a lot more.

That’s unfortunate, did you find another plugin that does the job?

Enabled cloudflare, problem resolved.

I just looked at the headers and they’re all set to:

cf-cache-status:HIT

So yes they are cached, and the site is working fine so I’m no longer concerned about it, strange they don’t get removed by your plugin though because all other strings do.

No I don’t use cache plugins, I just use cloudflare instead and I set it to “ignore query strings” now, a feature I didn’t know existed until after I posted this.

• This reply was modified 7 years, 7 months ago by gzt.
• This reply was modified 7 years, 7 months ago by gzt.