Skip to content
Sudonix

Upload Problem

Solved Customisation
Log in to reply

Did this solution help you?
Did you find the suggested solution useful? Why not buy me a coffee? It's a nice gesture, and a great way to show your appreciation 💗

Related Topics
  • kadir ay 0undefined

    navbar

    Solved Customisation
    2
    2 Votes
    2 Posts
    9 Views
    phenomlabundefined
    Marking as resolved, based on https://community.nodebb.org/topic/18625/navbar/2
  • JACundefined

    Forum customisation

    Customisation
    11
    2
    6 Votes
    11 Posts
    320 Views
    JACundefined
    Thank you Mark, the changes look fantastic!!
  • DownPWundefined

    Fancybox zoom

    Unsolved Customisation
    2
    1
    0 Votes
    2 Posts
    93 Views
    phenomlabundefined
    @DownPW Technically, it should be possible with the addition of the below Toolbar: { display: { left: ["infobar"], middle: [ "zoomIn", "zoomOut", "toggle1to1", "rotateCCW", "rotateCW", "flipX", "flipY", ], right: ["slideshow", "thumbs", "close"], }, }, Meaning your code block becomes function fancybox() { if (top.location.pathname !== '/login') { $(document).ready(function() { $('a').not('.forum-logo').not(".avatar").not(".emoji").not(".bmac-noanimate").each(function() { $('a[href*=".jpg"], a[href*=".jpeg"], a[href*=".png"], a[href*=".gif"], a[href*=".webp"], a[href*=".svg"]').addClass("noanimate"); }); }); Fancybox.bind( 'a[href*=".jpg"], a[href*=".jpeg"], a[href*=".png"], a[href*=".gif"], a[href*=".webp"], a[href*=".svg"]', { Toolbar: { display: { left: ["infobar"], middle: [ "zoomIn", "zoomOut", "toggle1to1", "rotateCCW", "rotateCW", "flipX", "flipY", ], right: ["slideshow", "thumbs", "close"], }, }, } ); } } Note, that you just need to add/remove the elements in the toolbar you do not need. Obviously, zoomIn and zoomOut are the ones you are specifically interested in. However, if Fancybox detects that the image has already been zoomed as far as possible, then this will not work. You’d need an external library such as zoom.js to add this functionality, or perhaps simpler https://www.jacklmoore.com/zoom/ A good example of how you’d make these two independent libraries work together is below https://codepen.io/ezra_siton/pen/VgrjKw It’s worth nothing that this specific code is based on Fancybox 3, so may need to be refactored to work with the latest version 5.
  • DownPWundefined

    Glitch effect when refreshing the home page

    Customisation
    17
    14 Votes
    17 Posts
    388 Views
    DownPWundefined
    No problem dude ! I hope you have a good vacation. Enjoy your loved ones!
  • JACundefined

    NodeBB recent cards customisation

    Solved Customisation
    3
    1
    2 Votes
    3 Posts
    141 Views
    JACundefined
    @phenomlab thank you very much for the assistance Mark, massively appreciated as always. The great thing about this is it’s all documented for other NodeBB users that come looking for solutions . Looks far better .
  • crazycellsundefined

    CSS code customization for the link preview plugin

    Solved Customisation
    6
    2
    3 Votes
    6 Posts
    667 Views
    phenomlabundefined
    @kadir-ay-0 marking as resolved based on https://community.nodebb.org/topic/17109/manual-build-a-night-mode-for-harmony/5 Please do not raise requests in two places - here and the NodeBB forums. All this does is create unnecessary load for both parties.
  • crazycellsundefined

    Page control arrows for PWA

    Solved Customisation
    27
    25 Votes
    27 Posts
    2k Views
    phenomlabundefined
    @crazycells it is, yes - I think I’ll leave it as there is no specific PWA CSS classes I know of. Well, you could use something like the below, but this means multiple CSS files for different operating systems. /** * Determine the mobile operating system. * This function returns one of 'iOS', 'Android', 'Windows Phone', or 'unknown'. * * @returns {String} */ function getMobileOperatingSystem() { var userAgent = navigator.userAgent || navigator.vendor || window.opera; // Windows Phone must come first because its UA also contains "Android" if (/windows phone/i.test(userAgent)) { return "Windows Phone"; } if (/android/i.test(userAgent)) { return "Android"; } if (/iPad|iPhone|iPod/.test(userAgent) && !window.MSStream) { return "iOS"; } return "unknown"; // return “Android” - one should either handle the unknown or fallback to a specific platform, let’s say Android } Once you’re in that rabbit hole, it’s impossible to get out of it.
  • DownPWundefined

    New message CSS problem

    Unsolved Customisation
    11
    1
    2 Votes
    11 Posts
    749 Views
    phenomlabundefined
    @DownPW hi. Sorry for digging up an old post, but I’m going through items still unresolved and was looking to get an understanding of where you are currently with this?