Bid buttons not available after outbid

Hi,

Thanks for your feedback. I've made a patch which should fix this. Download again the install package of HikaAuction on our website and install it on yours in order to get the patch.
Then, before testing, make sure you hard refresh the page in order to clear the cache of the JS of HikaAuction.

Hi,

Thanks. I've made some further tests and made some additional changes. Please try again.

Hi,

Well, I did reproduce the issue on my end yesterday and the changes I made successfully fixed the problem on my end. I'm not blindly making changes.
So I'm thinking you might be using the wrong install package or maybe the issue remains in a special case I could not reproduce on my end.
I guess I'll need you to provide a backend access and a FTP access in order to look at the issue directly on your website, check your settings and do some debugging directly there.

Could you provide that via our contact form ?
www.hikashop.com/support/contact-us.html

Hi,

I checked your settings and made a similar test on your website with two browsers on the same page ( template-default-test ) and I could confirm the fix is in place and working. I'm not able to reproduce the issue that you reported in your video.

Please double check.

Hi,

I think we're not looking at the same website or you have some caching issue on your local network.
Here is what I see on your website with the user account you provided on the URL you provided:
i.imgur.com/X8Jl8Yv.png
And here is what I see before I'm logged in:
i.imgur.com/5VzrqTG.png
You can see the URL of the website / page I'm using for my tests at the top of the screenshots.
Also, note the look of the icons on my screenshots. They all display as little squares. This is typical of a problem with the font awesome library on a Joomla website. Usually it comes from a setting in the template.
However, I'm surprised you don't have the issue on your end.
Similarly, look at the "LIVE" status label. On my end it take the whole width. That's the expected default behavior without custom CSS.
However, on your new video, I can see it only takes a bit more than the width of the label.

I think that all of this, as well as the fact that I can't reproduce the issue anymore on your website and you can is linked.
You might have some kind of caching proxy or something on your network preventing you from getting the updated CSS / JS I've added and present on your website and you're stuck with the old version in the cache of the proxy, which doesn't have the fixes and changes. And same for font-awesome. You must have the issue on your website, but you don't see it because of the proxy cache.
That, or we're actually looking at two copies of the website, me on the latest copy, you, a copy from before the patches.

Hi,

So, I've looked deeper into it, and I've seen two issues:
First, there was a bug which generated a JS error in some cases. I've made a patch and updated HikaAuction on your website for this. Before the patch, I was able to reproduce the issue this morning once or twice, even though it worked most of the time. Once I added the patch, I was not able to reproduce the issue anymore. Note that the patch requires you to clear your browser's cache (hard refresh).

Second, there are problems with the CORS policy of your website.
It prevents my browsers from loading the proper JS / fonts. See some of the error messages in the console of my browser:

....
13:14:01.467 www.xxx.com/media/mod_gptranslate/js/jsonrepair/index.js?e7eb31:1  Failed to load resource: net::ERR_FAILED
13:14:01.467 template-default-test:1 Access to script at 'https://www.xxx.com/media/system/js/messages.min.js?9a4811' (redirected from 'https://cdn.xxx.com/media/system/js/messages.min.js?9a4811') from origin 'https://xxx.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
13:14:01.467 www.xxx.com/media/system/js/messages.min.js?9a4811:1  Failed to load resource: net::ERR_FAILED
13:14:01.468 template-default-test:1 Access to script at 'https://www.xxx.com/media/com_finder/js/finder.min.js?755761' (redirected from 'https://cdn.xxx.com/media/com_finder/js/finder.min.js?755761') from origin 'https://xxx.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
13:14:01.468 www.xxx.com/media/com_finder/js/finder.min.js?755761:1  Failed to load resource: net::ERR_FAILED
13:14:01.468 template-default-test:1 Access to script at 'https://www.xxx.com/media/system/js/keepalive.min.js?08e025' (redirected from 'https://cdn.xxx.com/media/system/js/keepalive.min.js?08e025') from origin 'https://xxx.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
13:14:01.468 www.xxx.com/media/system/js/keepalive.min.js?08e025:1  Failed to load resource: net::ERR_FAILED

13:14:02.481 fa-solid-900.woff2:1  Failed to load resource: net::ERR_FAILED
13:14:02.481 template-default-test:1 Access to font at 'https://www.xxx.com/templates/flex/fonts/Pe-icon-7-stroke.woff?d7yf1v' from origin 'https://xxx.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
13:14:02.481 Pe-icon-7-stroke.woff?d7yf1v:1  Failed to load resource: net::ERR_FAILED
13:14:02.504 template-default-test:1 Access to font at 'https://www.xxx.com/templates/flex/fonts/fa-brands-400.woff2' from origin 'https://xxx.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
13:14:02.504 fa-brands-400.woff2:1  Failed to load resource: net::ERR_FAILED
13:14:02.527 template-default-test:1 Access to font at 'https://www.xxx.com/templates/flex/fonts/Pe-icon-7-stroke.ttf?d7yf1v' from origin 'https://xxx.com' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource.
13:14:02.527 Pe-icon-7-stroke.ttf?d7yf1v:1  Failed to load resource: net::ERR_FAILED