Forum Discussion

nickyates's avatar
nickyates
Mentor
12 years ago
Solved

I keep getting a message saying 'This widget could not be displayed.'

Hi Im having some issues with a attempt/recover block.  The code i have written below will loop 3 times and retrieve the the attached image url.  I have added this attempt block as some blog articles...
  • nickyates's avatar
    nickyates
    12 years ago

    I have finally got to the bottom of this issue.  It turns out that it wasnt the attempt recover block which was causing the problem it was indeed a permissions issues as Adam mentioned in an earlier post.  If you do a rest call and you do not have the correct permissions the message 'This widget could not be displayed.' is shown, even if you are not currently using the responce from the rest call.  

     

    If you get this message and you are not sure why, check all of your API calls using in a browser and you might find a message similar to this

     

                  User -1 does not have the following permission(s) at XYZ: [ read_board ]

     

    I had to ensure that all my users had a role with the 'see boards' permission set.  This can be done in admin -> users -> roles

nickyates's avatar
nickyates
Mentor
12 years ago
Copy Link
Hi Doug,

No there was nothing else in there. During testing I stripped the recover block down to just a failing API call or assign command (to trigger the recover section of the attempt/recover block) and just added in some text in the recover block to say that it had failed. I got the same 'this widget could not be displayed'. I used #assign to create several different ways which would cause an error each one appears to work when i am testing in studio and when i am logged in as admin but show that error message when i am not logged in. Replace the attempt/recover with a if statement with the same API calls and #assign block and everything works fine.
nickyates's avatar
nickyates
Mentor
12 years ago
Copy Link

I have finally got to the bottom of this issue.  It turns out that it wasnt the attempt recover block which was causing the problem it was indeed a permissions issues as Adam mentioned in an earlier post.  If you do a rest call and you do not have the correct permissions the message 'This widget could not be displayed.' is shown, even if you are not currently using the responce from the rest call.  

 

If you get this message and you are not sure why, check all of your API calls using in a browser and you might find a message similar to this

 

              User -1 does not have the following permission(s) at XYZ: [ read_board ]

 

I had to ensure that all my users had a role with the 'see boards' permission set.  This can be done in admin -> users -> roles