Menu does not work on iOS and Safari

Technical Support

Suggested Topics


  • 0 Votes
    2 Posts
    70 Views

    If you want to re-render something client side you can use

    const html = await app.parseAndTranslate('path/to/template', 'blockName', data);

    Where block name is the name used in the tpl file for a loop like {{{ each topics }}} and then once the render is done you can replace the html with jquery $('#some-target').html(html);.

    If you search core code you will see many uses of app.parseAndTranslate to update the DOM.

  • 0 Votes
    3 Posts
    1k Views

    Not my browser, its a friends computer 🙂 But i will tell him 😛

  • 0 Votes
    11 Posts
    4k Views

    @julian I'm still determining what is best. I think once a month depending on the timing could be problematic (although a manual renew isn't the worst thing in the world).

    Even the letsencrypt walkthrough says twice a day

    Note: if you're setting up a cron or systemd job, we recommend running it twice per day (it won't do anything until your certificates are due for renewal or revoked, but running it regularly would give your site a chance of staying online in case a Let's Encrypt-initiated revocation happened for some reason). Please select a random minute within the hour for your renewal tasks.

    I might go with that or I might go weekly. We'll see.

  • 0 Votes
    3 Posts
    2k Views

    Very good points about Bluebird. Its performance numbers are surprising, and the utility it brings with Promise.promisifyAll makes it so easy to convert callback code to promises.

  • 0 Votes
    7 Posts
    3k Views

    Yes, as @Schamper recommends, do not use relative paths to break out of the plugin's root directory, just use module.parent.require to require from the context of plugins.js, or require.main.require to require from the context of app.js

    To answer OP, I use npm link to link my folders together. I have one big messy NodeBB install ( 😉 ) and next to it is a plugins/ folder where all the plugins live.

    @psychobunny integrated grunt into NodeBB, so I just use grunt --verbose to develop now, instead of ./nodebb dev 😄