[ovaislak@hotmail.com]

5 years ago in reply to: WPSOLR: error on term #11844

https://prnt.sc/nh62mx

I have explained the case in the above link, I you have any solution to fix this taxonomy problem please advise

[ovaislak@hotmail.com]

5 years ago in reply to: WPSOLR: error on term #11832

You firewall is blocking me to write the code.

I really want to use this plugin, please help.

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #11093

It broked my site 🙁

I had multiple taxonomies and after your suggestions I changed the code to

register_taxonomy( 'manufacturer', 'product', $args );

From

register_taxonomy( 'Manufacturer', 'product', $args );

It was just case sensitive problem. So I changed the codes for other taxonomies, the error from backend (returning 0) was solved but my site template was crashed.

Is there a way to change the taxonomies without loosing the data ? or get them indexed without making changes in the code ?

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #11016

Do you know the fix ?

I can successfully print this taxonomy on frontend

See here — > https://medicalstore.com.pk/product/monis-tablet-xr-60-mg-30s/

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #11008

I can not use plugin to manage these taxonomies since it required data entry which is a huge task for a store with 87000 products

You already have my admin details, please look at this problem since there will be more people using custom taxonomies and solution for my problem will help others too.

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #11006

I unchecked all custom taxonomies and the indexing is working fine. But my new orders are not indexing automatically . I have to run the index again and again to get them indexed.

Give me some solution to index custom taxonomies since these will be used as filters too.

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #10992

Gives the same error for another custom taxonomy called drug_form

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #10990

ERROR by WPSOLR

WPSOLR: error on term 534 for taxonomy ‘manufacturer’: Invalid taxonomy.

The product is published already

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #10987

No, It’s a custom Taxonomy registered using the following function

/* WooCommerce custom taxanomy Manufacturer */
add_action( ‘init’, ‘custom_taxonomy_Manufacturer’ );
function custom_taxonomy_Manufacturer() {
$labels = array(
‘name’ => ‘Manufacturer’,
‘singular_name’ => ‘Manufacturer’,
‘menu_name’ => ‘Manufacturers’,
‘all_items’ => ‘All Manufacturer’,
‘parent_item’ => ‘Parent Manufacturer’,
‘parent_item_colon’ => ‘Parent Manufacturer:’,
‘new_item_name’ => ‘New Manufacturer Name’,
‘add_new_item’ => ‘Add New Manufacturer’,
‘edit_item’ => ‘Edit Manufacturer’,
‘update_item’ => ‘Update Manufacturer’,
‘separate_items_with_commas’ => ‘Separate Manufacturer with commas’,
‘search_items’ => ‘Search Manufacturer’,
‘add_or_remove_items’ => ‘Add or remove Manufacturer’,
‘choose_from_most_used’ => ‘Choose from the most used Manufacturer’,
);
$args = array(
‘labels’ => $labels,
‘hierarchical’ => false,
‘public’ => true,
‘show_ui’ => true,
‘show_admin_column’ => true,
‘show_in_nav_menus’ => true,
‘show_tagcloud’ => true,
);
register_taxonomy( ‘Manufacturer’, ‘product’, $args );
register_taxonomy_for_object_type( ‘Manufacturer’, ‘product’ );
}

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #10985

I executed the query successfully, used the id to edit the product. There were no manufacturer attached to that post, I just updated the post and tried to run the index again but got the same error.

Then I added a manufacturer to the same post and then resumed the indexing but got the same error again.

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #10945

I tried running the following command but it says the syntax is not correct.

SELECT ID, post_modified, post_parent, post_type FROM wp_posts AS posts WHERE ((post_modified = ‘2018-04-20 11:59:55’ AND ID > 12289) OR (post_modified > ‘2018-04-20 11:59:55’)) AND ( post_status IN (‘publish’) AND ( post_type = ‘product’ ) ) AND ID NOT IN (124038) ORDER BY post_modified ASC, ID ASC LIMIT 1

Can you share the right syntax

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #10942

I ran the index with batch 1 and debug enabled

It still shows the same error.

An error occured:

WPSOLR: error on term 534 for taxonomy ‘manufacturer’: Invalid taxonomy.

Posts excluded from the index:
124038

******** DEBUG ACTIVATED – Beginning of new loop (batch size) *******

******** DEBUG ACTIVATED – Query documents from last post date *******

Query:
SELECT ID, post_modified, post_parent, post_type FROM wp_posts AS posts WHERE ((post_modified = ‘2018-04-20 11:59:55’ AND ID > 12289) OR (post_modified > ‘2018-04-20 11:59:55’)) AND ( post_status IN (‘publish’) AND ( post_type = ‘product’ ) ) AND ID NOT IN (124038) ORDER BY post_modified ASC, ID ASC LIMIT 1

Last post date:
2018-04-20 11:59:55

I opened the post 12289 but the custom taxonomy manufacturer was empty there.

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: WPSOLR: error on term #10935

Can you guide me to edit that ? I have visited the manufacturer taxonomy page change the ID from url to 534 it says

You attempted to edit an item that doesn’t exist. Perhaps it was deleted?

Any guess how to fix this.

And can you further explain why the orders are not showing up ?

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: Server configuration #10927

I am sorry, I do not have access to those commands, a developer friend did the tweaking 🙁 I would love to contribute.

[ovaislak@hotmail.com]

5 years, 1 month ago in reply to: Server configuration #10925

though I have completed the server configuration but you are still requested to share the document shown in installation video so that others can use those commands to configure the server.