Fomantic Theme Issue on latest version dt-1.13.4

Fomantic Theme Issue on latest version dt-1.13.4

foxy_stoatfoxy_stoat Posts: 16Questions: 5Answers: 0

Hi Apologies in advance if I am being a muppet...

I just decided to update a system (which is working) to the latest versions from the download builder as a drop in replacement. I am now having a problem as the buttons/search/paging has all gone weird.

Recreated the problem using the same download string components (but with different versions) - did not do buttons as the search and paging are wrong so presume its not needed.

Example (Working): https://live.datatables.net/xehusive/1/edit
Example (Not Working): https://live.datatables.net/jukuhiwe/1/edit

I am using JQuery 3.6.4 and Fomantic 2.9.2

Playing with it - it seems dt-1.13.4 is broken but dt-1.13.3 works. https://live.datatables.net/jimeqiye/1/edit

Did I miss something important when upgrading to the latest build?

Thanks in advance for any help.

Pete

This question has an accepted answers - jump to answer

Answers

  • allanallan Posts: 62,099Questions: 1Answers: 10,183 Site admin

    Hi Pete,

    No that's not you - there is something wrong with our download builder. I'm looking into it.

    Allan

  • allanallan Posts: 62,099Questions: 1Answers: 10,183 Site admin

    Hi Pete,

    Fixed - here is an updated link: https://live.datatables.net/jukuhiwe/4/edit . I've add to add a ?123 to bypass the cache for the JS url.

    The issue appears to be that the two Semantic / Fomantic JS integration files weren't copied across to the server for the CDN server. I can only guess that my connection dropped at that point (it is a bit rubbish here...).

    Allan

  • foxy_stoatfoxy_stoat Posts: 16Questions: 5Answers: 0

    Hi Allan Thank you so much for looking at this (support is very impressive). I can see its fixed in the example now - but strange thing on my site I had missed adding in the datetime extension - with this its still a problem:

    e.g https://live.datatables.net/xiripefu/1/edit

    Is it a similar issue?

    Thanks
    Pete

  • allanallan Posts: 62,099Questions: 1Answers: 10,183 Site admin
    Answer ✓

    Probably. If you've loaded that exact URL before then it will have been cached and the broken version held :(. I'll need to do a release soon to fix this, but if you add ?123 (or any other random string) at the end of the JS url, that should work around it for the moment.

    Allan

  • foxy_stoatfoxy_stoat Posts: 16Questions: 5Answers: 0

    Missed that gem from your first comment - apologies - working fine - thanks again for the help

Sign In or Register to comment.