News:

Looking for documentation? Take a look on our wiki

Main Menu

Debugging spinning wheel problem

Started by nistune, February 09, 2025, 06:41:52 AM

Previous topic - Next topic

nistune

Joomla 4.4.10
Virtuemart 4.4.4 11101 (upgraded to 4.4.6 11109 today)

Other things:
Template Creator 5.5.2
VP One Page Checkout 7.27 (updated to 7.28 today and also ran it disabled last few weeks)
Stripe Checkout for VM 3.8

Problem: Spinning wheel when adding to cart. This has been reported by one first time, and several long term users (registered since 2017) over the last month. See image attached.

They log into the website, add to cart and it sits there spinning. They have tried different computers and different browsers

I cannot repeat the issue here (!). I've tried VPN to USA and also different browsers and tried the same thing with their accounts.

The problem just started happening with first report mid-January, and several other customers have repeated the same thing.

My hosting (hostgator) changed its DNS lookup around 24 Dec and no other changes prior to the site since 18 March 2024.

Errors in error_log are varied:

QuotePHP Warning:  Undefined array key 1 in components/com_virtuemart/router.php on line 800,805
Undefined array key "virtuemart_manufacturer_id" in /components/com_virtuemart/router.php on line 905
Attempt to read property "virtuemart_category_id" on bool in components/com_virtuemart/router.php on line 1576
Attempt to read property "virtuemart_product_id" on bool in components/com_virtuemart/router.php on line 1577

I have custom fields on my products:
QuoteAttempt to read property "customfields" on bool in components/com_virtuemart/models/product.php on line 3271

QuoteUndefined array key 1 in libraries/vendor/joomla/application/src/Web/WebClient.php on line 387
Undefined array key "txn_type" in plugins/vmpayment/paypal/paypal/helpers/paypal.php on line 452,454,456,458,460,463

QuoteUndefined array key "username" in components/com_virtuemart/models/user.php on line 671

QuoteAttempt to read property "customfields" on bool in /components/com_virtuemart/models/product.php on line 3271
Attempt to read property "customfields" on bool in components/com_virtuemart/models/product.php on line 3305
foreach() argument must be of type array|object, null given in /components/com_virtuemart/models/product.php on line 3305

Could any of these be related to my issue? How to I rectify these problems? I've been running Joomla/VirtueMart since 2016 and it seems home of these errors are related to something not available in my PHP database

Any other advise on debugging and locating the issue?

Jumbo!

Share the site link so someone can review and understand the problem and provide you with a solution. Screenshots and those error logs do not help identify the cause.

nistune

Here is the page as per the screenshot:
https://www.nistune.com/sw-licence-menu

Two of the customers reporting the problem are registered and then login here:
https://www.nistune.com/component/users/?view=login&Itemid=101

Jumbo!

I could not reproduce the problem on your site.

nistune

That is the issue, neither can we (even with their accounts from here)

The feedback so far is:

QuoteCustomer 1:
> Jan 14: I am trying to place an order through the online store and I just get the spinning wheel when I try to add to cart. I've tried two different web browsers and laptops.
> Feb 7: I can't place the order online. I still get the spinning wheel.
> Feb 10: I just attempted to try and add items to the cart and it still will not allow me to do so

Customer 2:
> Jan 29: I'm trying to purchase an individual license, but I just get a spinner forever after clicking "Add to Cart." I tried on a different browser, and had some coworkers try too
> Feb 10: Actually still doing it for me. Normally on Chrome, I tried it in Firefox too

Is there any other web logs I can access to dig in further on those days what might be happening?

Jumbo!

This is a client-side issue, so there won't be any relevant entries in the server's log. To understand the problem, you should check the errors in the browser's console. I was unable to reproduce the issue and did not find any errors reported in the console either.