Mobile Responsive Issue on Sidebar and Footer

  • Hello @administrators

    Global Sidebar is coming below the global footer.

    actually it should come like Below the sidebar content footer should come.

    Mobile Screen. Footer content is Coming First and Sidebar Content Coming Next
    Screenshot from 2020-06-05 20-29-49.png
    Footer Contents in Computer Screen
    Also See Footer Content is Not Exactly in Middle when i add sidebar widgets
    Screenshot from 2020-06-05 20-29-31.png
    Sidebar Contents in Computer Screen
    Screenshot from 2020-06-05 20-29-28.png

    I think Some Bootstrap Layout issue if Bootstrap is Used.
    This issue only if i use Global Widget
    Please Consider it and Fix in Next Update

Suggested Topics

  • 0 Votes
    1 Posts

    I'm trying to setup a Digital Ocean app using the Dockerfile below - this is based on the original Dockerfile from the Docker container packages. I managed to get this working locally having little changes made to the original Dockerfile, since I'm using a custom template and this is pulled from a public git repo on the NodeBB package.json file, so no major changes from the normal setup.

    Here's the Dockerfile I'm using:

    FROM --platform=linux/amd64 node:lts as npm RUN mkdir -p /usr/src/build && \ chown -R node:node /usr/src/build WORKDIR /usr/src/build ARG NODE_ENV=production ENV NODE_ENV $NODE_ENV # nodebb-docker/ folder contains the repo COPY --chown=node:node nodebb-docker/install/package.json /usr/src/build/package.json USER node RUN npm install --omit=dev FROM --platform=linux/amd64 node:lts RUN mkdir -p /usr/src/app && \ chown -R node:node /usr/src/app WORKDIR /usr/src/app ARG NODE_ENV ENV NODE_ENV $NODE_ENV COPY --chown=node:node --from=npm /usr/src/build /usr/src/app USER node RUN npm rebuild && \ npm cache clean --force COPY --chown=node:node nodebb-docker /usr/src/app ENV NODE_ENV=production \ daemon=false \ silent=false EXPOSE 4567 CMD test -n "${SETUP}" && ./nodebb setup || node ./nodebb build; node ./nodebb start

    Even though the build is running successfully (locally and in production) and I can run the container locally, I get this message on failed deployment:

    [2023-07-27 13:56:26] 2023-07-27T13:56:26.239Z [3] - info: Launching web installer on port 4567 []

    Anyone has had this before? Thank you 🙏

  • 0 Votes
    2 Posts

    It is possible to some degree with this plugin now:

  • 0 Votes
    7 Posts

    To piggyback off of @rod's line of questioning... can you access the forum when you navigate to the ip:port directly?

  • 0 Votes
    3 Posts

    Those errors usually mean websockets are not proxied correctly, make sure your nginx setup is correct. If you are using cloudflare you need to disable acceleration. They don't support websockets on smaller plans.

  • 0 Votes
    8 Posts

    I'm not sure -- it depends on the API call that that template calls. I believe @psychobunny might have a better idea?