Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple pages not working #1258

Closed
5 tasks done
saravanaskanda opened this issue Jul 11, 2023 · 8 comments
Closed
5 tasks done

Multiple pages not working #1258

saravanaskanda opened this issue Jul 11, 2023 · 8 comments
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working ✅ Fixed [ISSUE] Auto-Assigned to Tickets whose fix has been deployed

Comments

@saravanaskanda
Copy link

Environment

Self-Hosted (Docker)

System

Firefox 113.0 , pop os 20.04 , docker 23.06

Version

2.1.1

Describe the problem

Multiple pages not working. giving me error section not found. have added routingMode: hash in appconfig

showing response 200 for pages and only error is showing in console no section "ctf"

2023-07-11_11-55

below are starting lines from conf.yml

  ---
  pages:
  - name: CTF
    path: 'ctf.yml'
  - name: sysmon
    path: 'sysmon.yml'
  - name: homelab
    path: 'homelab.yml'
  pageInfo:
    title: Page
    navLinks:
    - title: Home
      path: /
    - title: About
      path: /about
  appConfig:
    routingMode: hash
    theme: one-dark
    fontAwesomeKey: 13014ae648
    enableFontAwesome: true
  sections:
  - name: Productivity
    items:
    - title: ProtonMail
      description: Secure Encrypted Email
      icon: favicon
      url: https://mail.protonmail.com/

below id starting lines from ct.yml

---
pageInfo:
  title: CTF Toolbox
sections:
- name: ctf
  icon: far fa-wifi
  displayData:
    rows: 2
  items:
  - title: BurpSuite
    description: A graphical tool to testing website security
    icon: #
    url: https://portswigger.net/burp
  - title: Commix
    description: Automated All-in-One OS Command Injection and Exploitation Tool
    icon: #

Tried yarn build-start in the docker not succeeding

Additional info

No response

Please tick the boxes

@saravanaskanda saravanaskanda added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Jul 11, 2023
@mkin701
Copy link

mkin701 commented Jul 17, 2023

Running into the same issue, was working until recently.

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Jul 17, 2023
@ninthwalker
Copy link

ninthwalker commented Aug 21, 2023

She notes this in the doc for pages:

Note that since page paths are required by the router, they are set at build-time, not run-time, and so a rebuild (happens automatically) is required for changes to page paths to take effect (this only applies to changes to the pages array, rebuild isn't required for editing page content).

I also did not have pages work after adding them to the config, and I think the issue is the "(happens automatically)" in the doc. That part doesn't seem to happen. So you can either completely delete/re-install the docker image, or you can run 'yarn build' in the container. ie: docker exec -it dashy yarn build

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Aug 22, 2023
@retnuh-code
Copy link

I also did not have pages work after adding them to the config, and I think the issue is the "(happens automatically)" in the doc. That part doesn't seem to happen. So you can either completely delete/re-install the docker image, or you can run 'yarn build' in the container. ie: docker exec -it dashy yarn build

Disclaimer: I am not a Linux guru by any means

I ran the build command you mentioned and I am still not able to get this to work with gist (also tried the manual button in settings).

I got it to work with a local yaml file (this is more preferred for my case anyway); but on the new page, it shows the sections from the main page as well as the sections configured on the new page. Is there a way to delete these sections from the new page or hide them somehow?

That's the only drawback I have with Dashy; the customization of the layout of sections/pages :(

Love the project, super functional, and honestly, it's a huge help. I am not talking bad about it at all, and the dev seems super awesome <3

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Sep 23, 2023
@rajivvishwa
Copy link

I downloaded the newest docker image and deployed it again, but it still does not work. I can create the pages in the config and they appear as buttons on the top, but none of them link to the right page/load the corresponding config yml. I'd a sandbox yml page with all the experimental stuff and I cant access it anymore.

So, the pages feature in Dashy is essentially broken for all? Tagging @Lissy93 in case she can think of any workarounds.

@rajivvishwa
Copy link

Updating here. Looks like I got it to work by forcing a Rebuild Application in Configuration options in the UI.

image

@liss-bot liss-bot removed the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Nov 25, 2023
@ManuelReschke
Copy link

It works only with a rebuild. But why?

The solution docker exec -it dashy yarn build works also the solution from @rajivvishwa described in the picture works.

But is it possible to solve this without permanent rebuilding?

@liss-bot liss-bot added the 👤 Awaiting Maintainer Response [ISSUE] Response from repo author is pending label Feb 27, 2024
@Lissy93
Copy link
Owner

Lissy93 commented Feb 27, 2024

But is it possible to solve this without permanent rebuilding?

Currently, a rebuild is required for changes to take effect. I'm working on a solution to this.

@CrazyWolf13
Copy link
Collaborator

Hi
This problems seems to be related to dashy not automatically rebuilding on changes, see #1479 and #1290 (comment)
A new release has just been published, which should fix this issue, so please upgrade to the latest version.
If this is not the case just respond back to this ticket and I'll reopen this issue.
Thanks and have a nice day.

@CrazyWolf13 CrazyWolf13 added the ✅ Fixed [ISSUE] Auto-Assigned to Tickets whose fix has been deployed label Mar 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working ✅ Fixed [ISSUE] Auto-Assigned to Tickets whose fix has been deployed
Projects
Status: Done
Development

No branches or pull requests

9 participants