benchpress warning (@value)

Technical Support

Suggested Topics

  • 0 Votes
    3 Posts


    I don't really know, if this will help you, but:

    Bildschirmfoto 2021-04-19 um 15.13.41.png

    If you change e.g sorting inside recent-Page from All Topics to New Topics the page refreshes and the URL turns from


    Once the page reloads, your hook filter:topics.get should be fired again. But in this case, with the filtering changed via dropdown. You have the get parameter ?filter=new to work with serverside.

    Maybe this is an option for you. You can use your template in combination with javascript to trigger an .change() or .click() -Event on your custom dropdown menu.

    Here is a little snippet.

    $(window).on('action:ajaxify.end', function(data) { let currentUrl = $(location).attr('href'); $('div#content').prepend('<a href="#" id="reloadTrigger">This is a example</a>'); $('a#reloadTrigger').click(function(){ window.location.href = currentUrl + "?filter=true"; }) });

    This prepends a a-Element before content-Div:

    Bildschirmfoto 2021-04-19 um 15.27.38.png

    Once you click on This is a example the url turns from to

    And your hook filter:topics.get should be fired again. Now you could work with the GET-Parameter filter=true.

    Hope this helps and inspired you. 🙂


  • 0 Votes
    2 Posts

    @0xA4B16 you can ignore those warnings, or you can install the packages they recommend by running npm i <package name>

  • 0 Votes
    10 Posts

    @yariplus Work! Thanks 🐶

  • 0 Votes
    2 Posts

    @Jenni-D'Silva if you share the topic it's a permalink. The meta tags should be correct in the share.

    Meta tags only matter for SEO and that sort of thing, which use raw loads anyways, so I don't see the issue.

  • 0 Votes
    5 Posts

    Nope- problem seems gone now, since the machine migration everything is fine and I get no more errors. Thanks though 😊