garyjh28

Seriously, pack it in! You didn’t help me – I got the help from another forum and via my Litespeed purchase. You were absolutely no help at all. You directed me here – incorrectly. You told me to raise the issue with WP as it wasn’t related to Litespeed – incorrectly. No complaints from me, only an intense desire that our paths don’t cross again. Perhaps volunteering and actually being supportive is not your thing. Thank goodness for the other volunteers out there who helped. Thank you to them.

Wow, this is a first for me, in all the years I’ve been on posting on forums, getting support and sometimes offering support, I’ve never been stalked before.

@serpentdriver, you are the person on the litespeed web server forum that told me to post my issue here, despite knowing the issue was nothing to do with the LS Cache plugin. You could have given me that tip there instead of wasting my time.

I have already opened a support ticket, thankfully someone else helped and pointed me in the right direction. I’m getting the help and support I was looking for and, as expected, the issue I had was nothing to do with WordPress and nothing to do with the LC Cache plugin.

Hi Joost,

I’ve figured this out for myself – and for all future requests for support regarding bulk exclude from sync setting when uploading products.

When using Woocommerce CSV Import Suite to upload products in bulk, Woocommerce allows you to map the zettle_sync_visibility taxonomy to data in the csv file.

The value in the CSV file must be set to zettle-excluded.

So in the CSV sheet that has all the products to be imported, there should be a custom column with a header like “Zettle Sync” for example. Next to each product that is to be excluded from the sync, the value zettle-excluded must be inserted in the “Zettle Sync” column.

When using the import suite, the zettle_sync_visibility taxonomy in the dropdown list should then be mapped to the “Zettle Sync” column (or whatever column name has been chosen to have the zettle-excluded value).

When the import takes place, the checkbox for Exclude from Sync? under Product Library Sync will be checked for all products that had the zettle-excluded value.

I’ve sucessfully done this in bulk for 1500 products.

Hi Joost,

Thanks for getting back to me.

The github link 404 errored for me.

I understand that this is something that you are developing but the wooccomerce csv import already has zettle_sync_visibility as a taxonomy that can be used to map when importing data. So I guess I was just looking for what the value in the mapped data would need to be in order to place the product in the zettle_sync_visibility taxonomy. It would normally be a value like yes, 1 or something like that.

Thanks

Gary

Hi guys,

Apologies, this was related to SSL and Cloudflare. Everything is working as expected now.

Getting exactly the same issue:

We’re using Elementor and this was happening when we were developing new templates in the them builder. Deactivating Yoast take the issue away. Issue was not there prior to updating to 16.1

Server error log (repeated multiple times):

Stack trace:
#0 …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php(175): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build(false)
#1 …/lcc-site-2021/wp-includes/class-wp-hook.php(294): Yoast\WP\SEO\Integrations\Watchers\Indexable_Ancestor_Watcher->build_post_hierarchy(2353)
#2 …/lcc-site-2021/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
#3 … in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 102

Email message with error info:

An error of type E_ERROR was caused in line 102 of the file …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php. Error message: Uncaught TypeError: Argument 1 passed to YoastWPSEOBuildersIndexable_Hierarchy_Builder::build() must be an instance of YoastWPSEOModelsIndexable, bool given, called in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php on line 175 and defined in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:102
Stack trace:
#0 …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php(175): YoastWPSEOBuildersIndexable_Hierarchy_Builder->build(false)
#1 …/lcc-site-2021/wp-includes/class-wp-hook.php(294): YoastWPSEOIntegrationsWatchersIndexable_Ancestor_Watcher->build_post_hierarchy(2334)
#2 …/lcc-site-2021/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
#3 …

Any help you and give would be much appreciated.`

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

Hi there,

We’re having similar issues and getting 500 internal server errors since updarting today to 16.1

Server error log (repeated multiple times):

Stack trace:
#0 …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php(175): Yoast\WP\SEO\Builders\Indexable_Hierarchy_Builder->build(false)
#1 …/lcc-site-2021/wp-includes/class-wp-hook.php(294): Yoast\WP\SEO\Integrations\Watchers\Indexable_Ancestor_Watcher->build_post_hierarchy(2353)
#2 …/lcc-site-2021/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
#3 … in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php on line 102

Email message with error info:

`An error of type E_ERROR was caused in line 102 of the file …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php. Error message: Uncaught TypeError: Argument 1 passed to YoastWPSEOBuildersIndexable_Hierarchy_Builder::build() must be an instance of YoastWPSEOModelsIndexable, bool given, called in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php on line 175 and defined in …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/builders/indexable-hierarchy-builder.php:102
Stack trace:
#0 …/lcc-site-2021/wp-content/plugins/wordpress-seo/src/integrations/watchers/indexable-ancestor-watcher.php(175): YoastWPSEOBuildersIndexable_Hierarchy_Builder->build(false)
#1 …/lcc-site-2021/wp-includes/class-wp-hook.php(294): YoastWPSEOIntegrationsWatchersIndexable_Ancestor_Watcher->build_post_hierarchy(2334)
#2 …/lcc-site-2021/wp-includes/class-wp-hook.php(316): WP_Hook->apply_filters(NULL, Array)
#3 …

Any help you and give would be much appreciated.

Hi guys – any update on the release of the fix for this? Might have to give up using it if it continues to cause this error. Many thanks.

@wpxpo thank you for your quick response – much appreciated ??

Sorry, meant to add that we have version 2.0.1 installed.

Having the same issue so following ??

Hi guys, I’m having the same issue – Ryte has picked up that https://neurolanguagecoachnetwork.com/sitemap.xml.gz is not found 404.

Hi @wfgerald ,

I’ve been able to fix this by uninstalling WF and then use the WF Assistant to delete the WF tables and data.

I’ve sent a diagnostics report via WF with my forum username.

Details are:
### wp-core ###

version: 5.4.1
site_language: en_GB
user_language: en_GB
timezone: +00:00
permalink: /%postname%/
https_status: true
user_registration: 0
default_comment_status: open
multisite: false
user_count: 540
dotorg_communication: true

### wp-paths-sizes ###

advanced-cache.php: true

### wp-active-theme ###

parent_theme: Extra (Extra)
theme_features: custom-background, automatic-feed-links, post-thumbnails, title-tag, et-post-formats, et_widget_areas, html5, lifterlms-sidebars, widgets, menus

### wp-parent-theme ###

name: Extra (Extra)
version: 4.4.8
author: Elegant Themes
author_website: https://www.elegantthemes.com

### wp-themes-inactive (1) ###

Twenty Seventeen: version: 2.3, author: the WordPress team

### wp-mu-plugins (1) ###

installatron_hide_status_test.php: author: (undefined), version: (undefined)

### wp-plugins-active (36) ###

Advanced Comment Form: version: 1.2.0, author: Thomas Maier
Akismet Anti-Spam: version: 4.1.6, author: Automattic
Authors List: version: 1.1.3, author: WPKube
Cache Enabler: version: 1.3.5, author: KeyCDN
CDN Enabler: version: 1.0.9, author: KeyCDN
Colorlib Login Customizer: version: 1.2.96, author: Colorlib
Contact Form 7: version: 5.1.9, author: Takayuki Miyoshi
Divi/Extra Layout Injector: version: 3.1, author: Sean Barton – Tortoise IT
Easy Username Updater: version: 1.0.4, author: Yogesh C. Pant
Enable Gzip Compression: version: 1.0.3, author: Moki-Moki Ios
Flamingo: version: 2.1.1, author: Takayuki Miyoshi
Header Footer Code Manager: version: 1.1.7, author: 99robots
i2SDK: version: 3.99, author: David Bullock
Loco Translate: version: 2.4.0, author: Tim Whitlock
Memberium: version: 2.171, author: David Bullock
Menu Items Visibility Control: version: 0.3.9, author: Hassan Derakhshandeh
Monarch Plugin: version: 1.4.12, author: Elegant Themes
PublishPress Authors Pro: version: 3.3.1, author: PublishPress
PublishPress Checklists Pro: version: 2.1.0, author: PublishPress
PublishPress Pro: version: 2.0.6, author: PublishPress
PublishPress Revisions Pro: version: 2.3.5, author: PublishPress
Redirection: version: 4.8, author: John Godley
Shortcode in Menus: version: 3.5, author: Gagan Deep Singh
ShortPixel Image Optimizer: version: 4.19.2, author: ShortPixel
Term and Category Based Posts Widget: version: 4.8.1, author: TipTopPress
UpdraftPlus – Backup/Restore: version: 2.16.26.24, author: UpdraftPlus.Com, DavidAnderson
URL Params: version: 2.2, author: Jeremy B. Shapiro
User Menus: version: 1.2.3, author: Code Atlantic
User Role Editor: version: 4.55.1, author: Vladimir Garagulya
Wordfence Assistant: version: 1.0.7, author: Wordfence
Wordfence Security: version: 7.4.7, author: Wordfence
WP HTML Mail: version: 3.0, author: Hannes Etzelstorfer // codemiq
WP Mail SMTP: version: 2.1.1, author: WPForms
WP System Info: version: 1.3, author: Nurul Amin
WP User Avatar: version: 2.2.6, author: ProfilePress
Yoast SEO: version: 14.3, author: Team Yoast

### wp-plugins-inactive (8) ###

Autoptimize: version: 2.7.3, author: Frank Goossens (futtta)
Infusionsoft Landing Pages: version: 1.3, author: Infusionsoft & David Bullock
Infusionsoft Official Opt-in Forms: version: 1.0.5, author: Infusionsoft
Jetpack by WordPress.com: version: 8.6.1, author: Automattic
PublishPress Permissions Pro: version: 3.1.6, author: PublishPress
Regenerate Thumbnails Advanced: version: 2.3.0, author: ShortPixel
Resize Image After Upload: version: 1.8.6, author: ShortPixel
SeedProd Coming Soon Page Pro: version: 5.12.5, author: SeedProd

### wp-media ###

image_editor: WP_Image_Editor_Imagick
imagick_module_version: 1690
imagemagick_version: ImageMagick 6.9.10-68 Q16 x86_64 2020-04-01 https://imagemagick.org
imagick_limits:
imagick::RESOURCETYPE_AREA: 31 GB
imagick::RESOURCETYPE_DISK: 9.2233720368548E+18
imagick::RESOURCETYPE_FILE: 786432
imagick::RESOURCETYPE_MAP: 31 GB
imagick::RESOURCETYPE_MEMORY: 16 GB
imagick::RESOURCETYPE_THREAD: 6
gd_version: bundled (2.1.0 compatible)
ghostscript_version: unknown

### wp-server ###

server_architecture: Linux 3.10.0-957.21.2.el7.x86_64 x86_64
httpd_software: Apache
php_version: 7.2.29 64bit
php_sapi: fpm-fcgi
max_input_variables: 3000
time_limit: 300
memory_limit: 256M
max_input_time: 600
upload_max_size: 128M
php_post_max_size: 128M
curl_version: 7.69.1 OpenSSL/1.1.1f
suhosin: false
imagick_availability: true
htaccess_extra_rules: true

### wp-database ###

extension: mysqli
server_version: 10.2.31-MariaDB

### wp-constants ###

WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: true
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_LOCAL_DEV: undefined
DB_CHARSET: utf8
DB_COLLATE: undefined

### wp-filesystem ###

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable

Had to use WF Assistant to delete all WF tables, reinstalled WF and it’s working now. Have sent diagnostics report via the plugin. Have a system info file that I downloaded before deleting WF and reinstalling if it helps at all – could email it to you.

I’m experiencing the same issue.

WP Version: 5.4.1
WP Memory Limit: 256 MB
WP Debug Mode: No
WP Cron: Yes
Server Info: Apache
PHP Version: 7.2.29
PHP Post Max Size: 128 MB
PHP Time Limit: 300
PHP Max Input Vars: 3000
cURL Version: 7.69.1, OpenSSL/1.1.1f
Max Upload Size: 128 MB