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

[studio-ui] Sites screen is grayed out on fresh install #1865

Closed
alhambrav opened this Issue Feb 12, 2018 · 1 comment

Comments

@alhambrav
Member

alhambrav commented Feb 12, 2018

Expected behavior

On fresh install, after logging in, "Sites" screen should not be grayed out

Actual behavior

On fresh install, after logging in, "Sites" screen is grayed out , so you can't click on anything. To be able to click anything, you need to refresh the page

screen shot 2018-02-12 at 11 25 02 am

Steps to reproduce the problem

  • One way to reproduce is to delete your crafter cms install, then do a git clone
  • Init, build, deploy and start craftercms
  • Open Studio in your browser (localhost:8080/studio), notice after logging in that your "Sites" screen is grayed out
  • Another way to reproduce is to stop craftercms, delete your data folder, then start again and login to Studio

Log/stack trace (use https://gist.github.com)

Specs

Version

Studio Version Number: 3.0.6-SNAPSHOT-82bbb0
Build Number: 82bbb05631638a2054117bd4e7622ebee5daf886
Build Date/Time: 02-12-2018 09:12:28 -0500

OS

OS X

Browser

Chrome browser

@sumerjabri sumerjabri added this to Backlog in Crafter CMS v3.0.x via automation Feb 12, 2018

@sumerjabri sumerjabri added this to the Crafter CMS v3.0.6 milestone Feb 12, 2018

vestrada added a commit to vestrada/studio-ui that referenced this issue Feb 12, 2018

@vestrada vestrada referenced this issue Feb 12, 2018

Merged

#1865 #772

@alhambrav

This comment has been minimized.

Member

alhambrav commented Feb 12, 2018

Verified fixed.

@alhambrav alhambrav closed this Feb 12, 2018

Crafter CMS v3.0.x automation moved this from Backlog to Completed Feb 12, 2018

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