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

Can't open card-details on read-only deck #2033

Closed
firlevapz opened this issue Jun 16, 2020 · 9 comments · Fixed by #2206 or #2249
Closed

Can't open card-details on read-only deck #2033

firlevapz opened this issue Jun 16, 2020 · 9 comments · Fixed by #2206 or #2249

Comments

@firlevapz
Copy link

Describe the bug
If you want to open a card and see the details of a card of a deck, which is shared to you as read-only, then nothing happens and an error in the console shows up.

To Reproduce
Steps to reproduce the behavior:

  1. Go to a deck, where you just have read-only permissions (no edit, no sharing, no managing)
  2. Click on any card on the deck
  3. Nothing happens (actually the card-details should show up)
  4. Error in console appears

Expected behavior
Details should be visible (assignee, due-date, description)

Client details:

  • OS: Ubuntu 20.04
  • Browser firefox, brave, chromium
  • Version recent versions
  • Device: desktop
Server details

Recent snap installation of nextcloud

Logs

Browser log

Firefox

TypeError: "e.scope is undefined"
    ia CardSidebar.vue:1
    bt VueJS
    ia CardSidebar.vue:1
    VueJS 7
        _render
        r
        get
        run
        pn
        rt
        Ke
main.js:62:9
    errorHandler main.js:62
    VueJS 9
        $e
        Ge
        _render
        r
        get
        run
        pn
        rt
        Ke

Chromium

main.js:62 TypeError: Cannot read property 'option' of undefined
    at CardSidebar.vue?4120:1
    at i.bt [as _l] (vue.esm.js:2639)
    at i.<anonymous> (CardSidebar.vue?4120:1)
    at i.e._render (vue.esm.js:3557)
    at i.r (vue.esm.js:4075)
    at mn.get (vue.esm.js:4488)
    at mn.run (vue.esm.js:4563)
    at pn (vue.esm.js:4319)
    at Array.<anonymous> (vue.esm.js:1989)
    at Ke (vue.esm.js:1915)


n.default.config.errorHandler | @ | main.js:35
-- | -- | --
  | $e | @ | vue.esm.js:8
  | Ge | @ | vue.esm.js:8
  | e._render | @ | vue.esm.js:8
  | r | @ | vue.esm.js:8
  | mn.get | @ | vue.esm.js:8
  | mn.run | @ | vue.esm.js:8
  | pn | @ | vue.esm.js:8
  | (anonymous) | @ | vue.esm.js:8
  | Ke | @ | vue.esm.js:8
  | Promise.then (async) |   |  
  | Ve | @ | vue.esm.js:8
  | rt | @ | vue.esm.js:8
  | (anonymous) | @ | vue.esm.js:8
  | mn.update | @ | vue.esm.js:8
  | pe.notify | @ | vue.esm.js:8
  | set | @ | vue.esm.js:8
  | (anonymous) | @ | deck.js?v=2983bf8c:1339
  | (anonymous) | @ | deck.js?v=2983bf8c:1339
  | Ie.updateRoute | @ | deck.js?v=2983bf8c:1339
  | (anonymous) | @ | deck.js?v=2983bf8c:1339
  | (anonymous) | @ | deck.js?v=2983bf8c:1339
  | r | @ | deck.js?v=2983bf8c:1339
  | r | @ | deck.js?v=2983bf8c:1339
  | ye | @ | deck.js?v=2983bf8c:1339
  | (anonymous) | @ | deck.js?v=2983bf8c:1339
  | r | @ | deck.js?v=2983bf8c:1339
  | (anonymous) | @ | deck.js?v=2983bf8c:1339
  | (anonymous) | @ | deck.js?v=2983bf8c:1339
  | (anonymous) | @ | deck.js?v=2983bf8c:1339
  | m | @ | deck.js?v=2983bf8c:1339

@juliushaertl
Copy link
Member

@jakobroehrl Maybe something small for you 😉

@jakobroehrl jakobroehrl self-assigned this Jun 23, 2020
@jakobroehrl
Copy link
Contributor

Can't reproduce it on the latest master, I can see the sidebar:
grafik

@juliushaertl
Copy link
Member

Closing as fixed then since the report doesn't mention a deck version number and we can't reproduce.

@drunkmen
Copy link

I can reproduce this in Deck 1.0.5 if the card is assigned to a user.

@firlevapz
Copy link
Author

Yes, still exists on read-only boards when the card is assigned to a user in version 1.0.5 with following error message in the console:

image

@jakobroehrl jakobroehrl reopened this Jul 19, 2020
@Siruv
Copy link

Siruv commented Aug 17, 2020

I have exactly the same problem as you.
As the screenshots show, did you find a solution to the problem?
Because it's embarrassing not to see the details of a card that another user has shared with you.

Thank you

Regards,
Capture d’écran de 2020-08-17 13-47-32
Capture d’écran de 2020-08-17 13-46-56

@juliushaertl
Copy link
Member

@jakobroehrl Could you reproduce this?

@jakobroehrl
Copy link
Contributor

Yes, on my setup it only occours if a user is assigned.

@Siruv
Copy link

Siruv commented Aug 19, 2020

Hello,

Yes, it suffices for user A to assign a card from his table to user B for example so that user B cannot see the details of the card which has been assigned to him.

Thank you

Regards,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants