Product Category Selection Broken

Note: I now see that products previously published with the plugin are broken and the category that was set has been removed. Please advise ASAP.

• This reply was modified 1 year, 2 months ago by hypergolica.

Additional note: more screenshots showing admin view and the previously published product, now broken:

https://www.dropbox.com/scl/fi/bk3yz50n5oqgs43g60foi/Screen-Shot-2023-12-17-at-17.06.00.png?rlkey=o6e46b8qsq8otchn1wa532abv&dl=0

https://www.dropbox.com/scl/fi/x1qi7mi6aoaatgj0hxqg4/Screen-Shot-2023-12-17-at-17.06.15.png?rlkey=d9nj1f5t1e2qsey5tsah0rg5p&dl=0

Hi @hypergolica

Thanks for using PublishPress Future.

Could you please try this beta version and let us know if the issue persists?

https://drive.google.com/file/d/11S9QRHHBoha8mXuOLWq22EVtdxmwILsn/view?usp=sharing

@rizaardiyanto

Thank you for your reply. Negative. This does not solve the problem. (Is this the same beta I mention in my original post?)

Question: is there a repository of previous versions of this plugin?

@hypergolica You can always download the previous version here: https://www.ads-software.com/plugins/post-expirator/advanced/

Anyway, I could not replicate the issue in the beta version. Can you elaborate more about your setup?

This is for Products from Woocommerce right?

Thanks,

@rizaardiyanto

I have reverted to version 2.7.8, as it was the only backup of your plugin I had. It works. Screenshot of what I now see:

https://www.dropbox.com/scl/fi/96wah0vecxl15mgwfqj2k/Screen-Shot-2023-12-18-at-13.42.49.png?rlkey=imk0fv61olgvwm1q9io2r4vf1&dl=0

Why on Earth the development team thought it would be a good idea to replace the Expiration Taxonomy checkbox list with a search box that makes you type in what you want escapes me. Even if the search box worked, it is inconvenient.

@rizaardiyanto

Yes, this is for Woocommerce products. I’m running WordPress 6.4.2 with the Enfold theme version 5.6.9, editor set to “Block editor”, not “Classic editor”.

Can you share with me a screenshot of what you see at your end?

Conditions:

• Replace Taxonomy, meaning remove category and replace it with a different one.

Thank you.

@hypergolica

In the previous versions, we had separate boxes for Gutenberg and the Classic Editor.

The search box is always there for Gutenberg, and it was not possible to apply the Classic Editor style to it.

We never made these changes without a reasons. There were issues with the box for the Classic Editor before. And having two separate boxes for each editor made it difficult to maintain.

That’s why, in version 3.1.4, we centralized all the boxes for Gutenberg, the Classic Editor. This was necessary to make maintenance much easier. We appreciate your understanding as we work to improve the plugin.

If you want to keep using the old version where the old classic editor still applied, please continue using it.

However if you want to use the latest version, we will need more information about this issue as we are not able to replicate the issue while creating new product on WooCommerce.

@hypergolica Is there any something special about your product category? Something like custom taxonomies or else? Or is it just straightforward product category that you directly create from here?

Additionally, can you check your console tab if there is any error there?

@rizaardiyanto

In my humble opinion, the list of check boxes is better. The search box means I have to memorize the category I want to replace the current category with, and this is a challenge as the categories are many. I would also point out that the search box is not working, so even if I do type in the exact name of the category, nothing appears.

The categories are simple categories.

https://www.dropbox.com/scl/fi/hcn05rbh1pkiaut9v4cmw/Screen-Shot-2023-12-18-at-14.17.33.png?rlkey=qtfnsq5v2cf5h7lu1lx6a31q8&dl=0

However, I do use the following plugin:
“Category Order and Taxonomy Terms Order”
This has never before caused a conflict.

I’ve already reverted back to a previous version of the plugin and have gone through and fixed all of the products that were broken.

I’d be happy to assist with the development and switch back to the latest version to check logs, etc., but I need to know we will solve the problem.

Shall I proceed? Please advise.

Thank you.

@hypergolica Do you have any staging/test site where you could install the latest version of our plugin?

By doing that you can help us investigate the issue without having to worry breaking your live site.

If you could do that, I would really appreciate it as it will help us tackle this issue.

@rizaardiyanto

Good idea. I can do that. Unfortunately, I have to go now, so I’ll have to report back later tonight. Thanks again for your help.

@hypergolica Thanks for doing that. No worries, take your time.

We appreciate your cooperation helping us investigate this issue.

@hypergolica We have new beta available.

Could you please try this beta version and let us know if the issue persists?

https://github.com/publishpress/PublishPress-Future/releases/download/3.1.6-beta.4/publishpress-future-3.1.6-beta.4.zip

@rizaardiyanto

I now have an active staging site. Apologies for the delay.

Error(s) are still there for 3.1.5. I will install the new beta as instructed and report back.

Thank you.