I don't know if this has been resolved, but I have a "different" error and wondered if I could post it here or...?
This is definitely related to updates, although it could be related to the install, but feel free to move this post to where you feel is best.
Everything was working fine until the VM update from (if I remember correctly) May 26, 2022.
I didn't say or do anything about it then because I was trying to run down some answers (and was just too busy).
Mind you, with every update - VM or
any other component update - I always get the error about VM Payment - eWay and custom_download
Update: :Extension: Could not parse
http://virtuemart.net/releases/vm3/plg_vmpayment_eway_update.xmlUpdate: :Extension: Could not parse
http://virtuemart.net/releases/vm3/plg_vmcustom_download_simple_update.xmlI have the eWay plugin unpublished. Obviously, it makes no difference if it's unpublished because the coding is trying to update eWay and cannot. Hence the error.
That's been happening since the first week I installed VM. I "live" with that error because I keep thinking it's going to be fixed with "the next VM update". There have been 2 thus far (since I started getting the error) and the error continues.
I'm running J4.1.4, and VM 4.0.2 10661 on Php 8.
I'm using J4 SEF and no other plugin for that.
I turned off J4 Conservative cache last week when the system started having the VM issue.
Oh...and there are 55 overrides that need to be "checked" in order for the blaring red notice to relax. All 55 of those overrides are from a previous VM update. Again, I hoped the "next" update would resolve that. Since it did not, I have to find the time to go into the database and change the "0" to "1" in each of those updated files...sigh... Well, at the bottom of this post I state that I'm planning to reinstall VM after removing it completely, along with all my products. So I'll leave the db alone for now.
Here is what started me scratching my head.
When I updated, I noticed on the front end that the link to the "Categories view" didn't work right.
Since there is now only the one option, I have the main menu link - Services - set to "Category Layout" with "Top Level Category". That's been working fine for the few months I've had VM installed with J4.
When a user clicked on either of the 2 listed categories, the user would go to the 1 category and see anything assigned to that category.
When I updated, that changed.
Keeping the menu unchanged, I arrived at the categories and products listed - that remained normal.
But when I click on "either" of the categories, I remain on the same page I was brought to from the "Services" link in the main menu.
Looking at the URI when just hovering either of the category icons, in fact, it is the same page as the main menu "Services". That means that now there is no way to get to 1 category or the other. The user is "stuck" on the page with all (in my case 2) categories and all products.
Because I know that there are changes happening with VM in this version, I thought I'd just do some debugging and investigating to see if anything raised any flags.
Before I updated on May 26, I had set a couple of products with the appropriate canonical.
Today, when I attempted to look for any errors with debug, I didn't find any until I went to change the canonical to "No override".
VM was NOT happy!!
danger
vmError: vmTable store updateObject Incorrect integer value: '' for column `dbusername_tagnew`.`dd6nm_virtuemart_products`.`product_canon_category_id` at row 1 UPDATE `dd6nm_virtuemart_products` SET `virtuemart_vendor_id`='1',`product_parent_id`='0',`product_sku`='DDS',`product_gtin`='',`product_mpn`='',`product_weight`=NULL,`product_weight_uom`='KG',`product_length`=NULL,`product_width`=NULL,`product_height`=NULL,`product_lwh_uom`='M',`product_url`='',`product_in_stock`='1000',`product_ordered`='0',`product_stockhandle`='0',`low_stock_notification`='0',`product_available_date`='2022-04-19 00:00:00',`product_availability`='',`product_special`='0',`product_discontinued`='0',`pordering`='0',`product_sales`='0',`product_unit`='KG',`product_packaging`=NULL,`product_params`='min_order_level=\"\"|max_order_level=\"\"|step_order_level=\"\"|shared_stock=0|product_box=\"\"|',`intnotes`='',`metarobot`='',`metaauthor`='',`layout`='default',`published`='1',`has_categories`='1',`has_manufacturers`='0',`has_medias`='1',`has_prices`='1',`has_shoppergroups`='0',`product_canon_category_id`='',`created_on`='2022-04-28 23:58:04',`created_by`='194',`modified_on`='2022-06-02 19:28:52',`modified_by`='194' WHERE `virtuemart_product_id` = '6'
I got that error as soon as I hit "Save".
And, the product I attempted to change reverted back to what it was set before I attempted to change the canonical.
Further, using "Log Almost Everything", I checked the server log and found the following:
2022-06-02 19:28:52 ERROR vmError: vmTable store updateObject Incorrect integer value: '' for column `dbusername_tagnew`.`dd6nm_virtuemart_products`.`product_canon_category_id` at row 1 UPDATE `dd6nm_virtuemart_products` SET `virtuemart_vendor_id`='1',`product_parent_id`='0',`product_sku`='DDS',`product_gtin`='',`product_mpn`='',`product_weight`=NULL,`product_weight_uom`='KG',`product_length`=NULL,`product_width`=NULL,`product_height`=NULL,`product_lwh_uom`='M',`product_url`='',`product_in_stock`='1000',`product_ordered`='0',`product_stockhandle`='0',`low_stock_notification`='0',`product_available_date`='2022-04-19 00:00:00',`product_availability`='',`product_special`='0',`product_discontinued`='0',`pordering`='0',`product_sales`='0',`product_unit`='KG',`product_packaging`=NULL,`product_params`='min_order_level=\"\"|max_order_level=\"\"|step_order_level=\"\"|shared_stock=0|product_box=\"\"|',`intnotes`='',`metarobot`='',`metaauthor`='',`layout`='default',`published`='1',`has_categories`='1',`has_manufacturers`='0',`has_medias`='1',`has_prices`='1',`has_shoppergroups`='0',`product_canon_category_id`='',`created_on`='2022-04-28 23:58:04',`created_by`='194',`modified_on`='2022-06-02 19:28:52',`modified_by`='194' WHERE `virtuemart_product_id` = '6'<pre>#0 vmError() called at [/server/username/public_html/administrator/components/com_virtuemart/helpers/vmtable.php:1289]
#1 VmTable->store() called at [/server/username/public_html/administrator/components/com_virtuemart/helpers/vmtable.php:1978]
#2 VmTable->bindChecknStoreNoLang() called at [/server/username/public_html/administrator/components/com_virtuemart/helpers/vmtable.php:1870]
#3 VmTable->bindChecknStore() called at [/server/username/public_html/administrator/components/com_virtuemart/models/product.php:2560]
</pre>
I'm going out on a limb here and saying, it would seem that only a clean install would be the best option.
However, there's no point in doing that until I can get Milbo (or ?) to authorize that without doing anything prior to a fresh install.
I'm guessing you would all like to review this information and make any appropriate changes before I attempt a new install - which means throwing out all my products and starting over. "Stuff" happens...
Ok. What more do you need? I'm ready to provide whatever, even access to admin.
Thanks.