A few minor dashboard issues

Prismic Administrative Support
1

Hi Prismic folks!

I've got a few minor dashboard usability issues to report. Have attached some screenshots which I hope are helpful with troubleshooting.

  1. Repository dates are not currently updating on the ‘All repositories’ dashboard, on our end at least. Many of our repositories are updated every day, but we haven’t seen the date updated in 100 days. This makes it a little tricky to keep an eye on who’s been updating their content and who hasn’t.

    prismic_last-update-dates
    prismic_last-update-dates2612×917 98.8 KB

  2. Disabled content models have begun appearing in the ‘Type’ dropdown, whereas they didn’t appear here before. This has caused confusion with a few folks who are curious why there are new content types which weren’t available to them before.

    prismic_disabled-custom-types
    prismic_disabled-custom-types2614×1418 203 KB

    prismic_disabled-custom-types-visible-on-dash
    prismic_disabled-custom-types-visible-on-dash2614×1418 276 KB

  3. Older repositories which don’t use the Slice Simulator now display errors on their slices in the sidebar. As these slices already pull through preview images (used when adding a new slice to the page), can the sidebar preview fall back on these preview images? This would look a lot more professional than a simple ‘Error’ message.

    prismic_error-in-sidebar
    prismic_error-in-sidebar2614×1418 265 KB

    prismic_slice-preview
    prismic_slice-preview1920×1042 76.7 KB

I don't believe that these should be too time-intensive to troubleshoot and would make the dashboard experience feel a lot more polished.

On another note, I also noticed that the issue with updating primary images on repositories has been fixed, so thanks very much for that! :)

4

Hi @services!

Thank you for your detailed feedback! For the error display on the slices, could you send me your repository so we can investigate? Feel free to DM me it if you'd like.

The other bugs have been passed on to the dev team:

https://prismic.atlassian.net/browse/BT-136
https://prismic.atlassian.net/browse/BT-201

And delighted to hear you're happy with the updating primary images bug fix :slight_smile:

1 Like
5

Hi @Ezekiel! The repository which I referred to when describing our slice display errors is called "ecotrust", though we're experiencing it on a number of legacy repositories.

Let me know if there's any other information that I can provide which might be helpful to you and your team!

6

Hi @services,

Thank you! We'll investigate, and get back to you on that :slight_smile:

I'm also happy to report the disabled content models still appearing in the 'type' dropdown bug has been addressed and fixed!

8

Hi again @services,

Regarding the errors displayed in the sidebar slices, how is your preview set up? This can happen depending on your configuration. Are you using the URL of your website for it?

9

Hi @Ezekiel!

Glad to hear that the disabled content model bug has been fixed! Thanks very much for the prompt response on that. :)

Regarding the sidebar slice errors, Development and Production page preview are configured and working on these projects. The projects with this error are built with Next.js using some older Prismic libraries such as prismic-javascript (3.0.2) and prismic-reactjs (1.3.4). These projects were not built using Slice Simulator since they predate it by a few years, so there hasn't been any Slice Simulator configuration implemented on these projects.

It's great that new projects built with Slice Simulator can take advantage of this new sidebar preview functionality--and we love using this feature on some of our newer projects--but that doesn't mean that older repos have to appear outdated or buggy because they're not configured for this feature. Hence the idea of displaying a fallback image instead of an error message.

Let me know if you have any other questions that might help with troubleshooting!