[Fixed] Link fields in collections don't fire when added to buttons

Helpdesk Report a bug
1

Hi.

I’ve got a ticket open with support at the moment, but not had anything back. Just wanted to see if anyone else has had issues where they create a “link” field type in a collection, and then try to bind that field to a button’s link settings. I’ve tried this, and whilst I see the URL of the link appear in the browser when I hover over it, clicking the button does not fire that link. In my case, it’s a link to a file stored externally on Cloudflare R2 (although I have also tried using a file in the file manager with the same outcome). Clicking the button does not work. The only way I’ve managed to get the file to begin downloading is to set the link target to be “overlay” - and by doing so, the link fires and the file downloads.

Anybody experienced this, or have any ideas as to how I can get this working without trigerring an overlay? I’ve tried on a number of sites within my Sitejet studio, and the same results each time, so it’s not site specific (and even on a live site published to a domain).

Dave

2

Hi Dave,

I had the same problem last week. It seems to be a bug. I’ve used this before and never had any issues. I hope Sitejet takes this seriously and fixes the problem.

In the meantime, I was able to resolve the issue with the following code:

<script>
(function () {
  function removeOnclickAttribute() {
    const buttons = document.querySelectorAll('.collection-button a');

    buttons.forEach(function (link) {
      link.removeAttribute('onclick');
    });
  }

  document.addEventListener('DOMContentLoaded', removeOnclickAttribute);
  window.addEventListener('load', removeOnclickAttribute);

  setTimeout(removeOnclickAttribute, 500);
  setTimeout(removeOnclickAttribute, 1500);
})();
</script>

For the JS code to work, you need to assign the class .collection-button to your button.

Insert the code at the very end of the body tag.

Best regards, Patrick

3

Dear @Dave_Parker

Thank you for posting this here as well.

This has been reported by you via a ticket. As I checked the status, you have been informed that this is a bug and the developers work on a fix.

@Patrick_Luescher of course we take this seriously and fix this with the current sprint. :pray:

5

Thanks for the code Patrick. Adding it has indeed made the links work on buttons. Don’t suppose you also have a workaround for the filter buttons and search field do you, which seem to not be working also!!

6

I wanted to check whether there is an updated ETA for a full fix to the current collections issues. I discovered the problem while on a call with a client whose site I’m actively building, and it has put me in a difficult position. At the moment, the inability to use search and filtering on collection items is blocking a key part of the project, and without a clear timeline I’m unable to give my client any reassurance.

I appreciate the update from Martin yesterday confirming that the cause has been identified and that a solution is in progress, but the lack of a timeframe makes planning extremely challenging. Even a rough estimate would help manage expectations on my side.

I’m also concerned that new features—such as the AI Section Generator—are being rolled out while core functionality like collections appears to be unstable. Reliable fundamentals are far more important for day‑to‑day client work than additional AI features. Similarly, the long‑requested ability for limited‑access CMS users to create and edit collection items with basic widgets still seems to be missing.

One of the reasons I’m moving away from WordPress and Elementor is to avoid situations where essential features break unexpectedly. Having collections fail this week has understandably raised concerns.

Andre, could you please provide an ETA for the collections fix? If this is likely to extend beyond the next couple of days (ideally no later than Wednesday 13th May), I will unfortunately need to move this particular project back to WordPress to avoid risking the client relationship.

Thank you.

7

Hey everyone, this bug has been fixed and released.

As far as I know, all additional topics are discussed in separate tickets.