dev
Forum Replies Created
-
is there not a way to be complaint without the premium version ?
Hello,
There is no error and we’ve had to hide the button using CSS for the time being. WPS hide login now has a notice saying the hidden login URL is exposed.
Do you have an email to send that to?Hello
Thanks for looking at this but this is not about after authentication redirect, it’s the Login URL itself added into the “Login” button on the reviews section of the page.
The login button contains the wordpress login URL not the woocommerce login.
Hello,
This happens under the product page, do you have an email I can send that to?Forum: Plugins
In reply to: [WooCommerce] HPOS: “The link you followed has expired”We have the same issue
Forum: Plugins
In reply to: [WooCommerce PayPal Payments] Issue with Shipstation IntegrationI commented on this and my comment was removed. The patched update fixed the issue.
Forum: Plugins
In reply to: [Customer Reviews for WooCommerce] Notice in WP CRONHello,
The error is the same in debug.log[03-Oct-2023 11:15:13 UTC] PHP Notice: Function wpdb::prepare was called incorrectly. Unsupported value type (array). Please see Debugging in WordPress for more information. (This message was added in version 4.8.2.) in /home/<>/wp-includes/functions.php on line 5905
[03-Oct-2023 11:15:14 UTC] PHP Notice: Function wpdb::prepare was called incorrectly. Unsupported value type (array). Please see Debugging in WordPress for more information. (This message was added in version 4.8.2.) in /home/<>/wp-includes/functions.php on line 5905
[03-Oct-2023 11:16:08 UTC] PHP Notice: Function wpdb::prepare was called incorrectly. Unsupported value type (array). Please see Debugging in WordPress for more information. (This message was added in version 4.8.2.) in /home/<>/wp-includes/functions.php on line 5905
[03-Oct-2023 11:20:51 UTC] PHP Notice: Function wpdb::prepare was called incorrectly. Unsupported value type (array). Please see Debugging in WordPress for more information. (This message was added in version 4.8.2.) in /home/<>/wp-includes/functions.php on line 5905
[03-Oct-2023 11:31:38 UTC] PHP Notice: Function wpdb::prepare was called incorrectly. Unsupported value type (array). Please see Debugging in WordPress for more information. (This message was added in version 4.8.2.) in /home/<>/wp-includes/functions.php on line 5905
[03-Oct-2023 11:41:11 UTC] PHP Notice: Function wpdb::prepare was called incorrectly. Unsupported value type (array). Please see Debugging in WordPress for more information. (This message was added in version 4.8.2.) in /home/<>/wp-includes/functions.php on line 5905Forum: Plugins
In reply to: [WPC Frequently Bought Together for WooCommerce] Hidden products being shownExclude unpurchasable is already set to “yes”
Deactivating COT resolves the issue, seems to be caused by the new WC High performance tables added in the last update.
Forum: Plugins
In reply to: [Top Image SEO] HPOS SupportWe’re in need of this also, has been disabled until resolved
Forum: Plugins
In reply to: [LiteSpeed Cache] Multisite crawler issueThis is from litespeeds settings/toolbox on the subsite, the crawler config etc is different from the main primary site.
Forum: Plugins
In reply to: [LiteSpeed Cache] Multisite crawler issueOn the subsites litespeed toolbox settings, it shows it as enabled and has a config:
Server Variables SERVER_SOFTWARE = LiteSpeed DOCUMENT_ROOT = /home/ksc5577p/REDACTED/ X-LSCACHE = on,crawlerThere’s a config there from testing as well.
) img_optm-webp_replace_srcset = true img_optm-jpg_quality = 82 crawler = true crawler-usleep = 500 crawler-run_duration = 400 crawler-run_interval = 600 crawler-crawl_interval = 302400 crawler-threads = 3 crawler-timeout = 30 crawler-load_limit = 3 crawler-sitemap = https://REDACTED/sitemap_index.xml crawler-drop_domain = true crawler-map_timeout = 120 crawler-roles = array ( )Doesn’t show any recent activity on the subsite for crawling but does appear to be enabled yet if its manually run
Current sitemap crawl started at: 07/22/2023 01:09:30 The next complete sitemap crawl will start at: 08/08/2023 20:59:30 Last complete run time for all crawlers: 1237800 seconds Current crawler started at: 1s ago Current server load: 0.63 Last interval: 1s ago Ended reason: crawler_disabled- Start watching…
- 01 Jan 1970 01:00:00 Size: 473 Crawler: #5 Position: 1 Threads: 0 Status: crawler_disabled
- ..
- This reply was modified 2 years, 10 months ago by dev.
Forum: Plugins
In reply to: [LiteSpeed Cache] Multisite crawler issueHello,
They have done that which has enabled the multisite primary site to have the crawler but all subsites are still disabled.
Is there a multi-site specific config required? They’ve not been able to get it enabled on any subsite yet.
Forum: Plugins
In reply to: [LiteSpeed Cache] Multisite crawler issueAt the moment, due to the subsites not being able to run the crawler (A2 host can’t seem to resolve this, it shows as “crawler_disabled”). All of the sitemap URLS are within the multisite primary, if drop domain is added it then won’t have any pages to crawl.
We would need to resolve the crawler_disabled issue for subsites first. Any ideas on how to resolve that ?
Much appreciated for your support with this!
Forum: Plugins
In reply to: [LiteSpeed Cache] Multisite crawler issueHello,
Our cron is working as expected and is a system cron. Is there a specific one we can run just for the crawler? WP Crons shows the crawler being scheduled as expected.
We thought it could just be being reset rather than a cron issue as it wordpress cron doesn’t have any other issues. It runs every 10 minutes for the site.
The primary management site is often in maintenance mode, subsites are not, would this disable the crawler?