Although I usually have it turned off because it's indexing the CSS classes in the project and it bogs down my potato hard drive.
I don't write a lot of CSS but there's a plugin in VS Code that does this: https://gyazo.com/309863ccad142b0b9ec4bc63a43966ba
I meant the value
navajowhite. I thought it was some joke or something I'm not nerdy enough for. Maybe he just really meant that PHPStorm is actually suggesting
First time I heard about that
@Terry Apodaca I know about the vendor-expose thing. In our case, the issue was the
/public folder and the
resources folder is being generated in
public/resources. We just deleted her
/public folder and ran
composer vendor-expose and it's all fine now.
@guci0 commented on @Dennis Basa Guinto’s file https://silverstripe-users.slack.com/files/U9DQDARKQ/FAE358M52/screen_shot_2018-04-27_at_1.15.07_pm.png: Check is /resources is on root of project, it's need to be in public and (just move) and run
OK. It seems that she has a
public folder and the
resources folder is being placed there while the CMS is referencing them on
resources instead of
public/resources. Sorry, let's get back to @nontgor. https://silverstripe-users.slack.com/archives/C36U3BDHN/p1524806310000189
A front-end dev co-worker* of mine
Hello! A front-end dev of mine is having trouble loading her CMS. She's using Chrome on a Mac. I really don't have much skill troubleshooting it there and I haven't seen this issue so if anyone can have an insight, I'll be very grateful for any help.