gb24

@imodouglas, thank you for the detailed explanation.

It appears, then, that the WooCommerce Square plugin just can’t be used on Kinsta.

I will move on to looking for another payments plugin for Woo.

Thank you.

Hi @imodouglas , PHP comments are disabled in the Kinsta php.ini file.

Attempting to activate the Square plugin gives the error:

All features in Square for WooCommerce have been disabled?due to unsupported settings:
??Invalid OPcache config:?Please ensure the?save_comments?PHP option is enabled.?You may need to contact your hosting provider to change caching options.

Kinsta will not change the PHP.INI save_comments setting. In addition, per the original support issue I referenced, Kinsta says:

“We will be unable to allow the reading the /etc/php/8.0/fpm/php.ini file, I am afraid. In that case I would advise you to contact the plugin developers and report that we can’t support apimatic/jsonmapper.”

https://www.ads-software.com/support/topic/square-plugin-doesnt-work-on-kinsta-hosting/

The original support issue mentioned:

I understand that the issue is still not fixed. That’s currently a limitation for our Square extension, so we created an internal issue to find alternatives to?jsonmapper.

Any progress on “alternatives to jsonmapper”?

Thank you.

Thank you so much for the quick reply and resolution!

Sure.

1. Go to the Version: panel for an existing download
2. Enter a string containing at least one uppercase character [A-Z]
3. Click Update button to save the download.

All uppercase characters are converted to lower case in the version string.

See the screenshot at https://imgur.com/a/tK0Gshi

It seems like you are asking for a “next event” and “previous event” link on a single event page. I don’t think these specific placeholders exist.

However, I have used the #_TAGNEXTEVENTS placeholder to display a list of future events with a specific tag at the bottom of the single event page. For example, create an event tag “meeting” and assign it to all your meeting events.

Go to Settings > Formatting Tab > Events > Single Event Page Format. Insert the #_TAGNEXTEVENTS placeholder where you want to display future events with the same tag in the single event page.

Hi @pulak00

Thank you for your reply. This was apparently a caching-related issue. The issue was resolved when I excluded the page from caching.

Thanks, Mark

Edit: the image is displayed twice (first empty, then correctly) not the view.

• This reply was modified 1 year, 9 months ago by gb24.

Hello @joostvandevijver

There seems to be a conflict with the WP RSS Aggregator plugin on our multisite which affects the WordPress REST API. When that plugin is disabled, REST API calls work fine.

Note that I am unable to re-create this issue on another multisite environment.

Thank you.

Hello @joostvandevijver

I have traced this issue to a conflicting plugin. When that plugin is disabled, the REST API calls work fine. I am working with that plugin support contact.

Please consider this issue resolved.

Thank you.

Thank you for your reply. I do not see these or other errors in the logs.

Note also that I get the “critical error on this website” message on the WooCommerce > System status tab.

Could you provide a public link to your bug report on this issue?

Thank you.

Please mark this as resolved.

Thanks to help from DM support, the issue was determined to be a conflict with another plugin (WooCommerce PayPal Payments) which interfered with the REST API in my WordPress environment.

Contact form message sent.

Could you please show me the response of the link you blurred in the picture if you copy-paste in a browser?

I prefer not to show this full url publicly. Is it possible to PM or email you?

I believe the DM database upgrade may have failed on this site without reporting any errors with 82k+ logs.

Reports page looks fine after database upgrade on two other sites each with 16k+ logs.

@razvan,

– the date picker is not responsive and cannot be opened, nothing happens on click
– same response (no data) after clearing browser cache
– 82,839 logs before update
– see screenshot for developer’s tool console errors: https://imgur.com/a/DyKdxLk

Perhaps the database upgrade could not process 82k+ logs. Note there were no errors reported by the database upgrade.

Thank you.