Voyager: Problem when deploy to internet

Created on 1 Jan 2017  路  10Comments  路  Source: the-control-group/voyager

I got the problem when i deploying my project with Voyager Package, But when i look on admin page
i got the page with style.

screen shot 2017-01-01 at 10 00 59 pm

Most helpful comment

@arogant7000 find voyager.php in the config file, open it you will see assets_path , I dont know what's your project path anyway set a new value for assets_path like "assets_path" => "/parent's folder name of your voyager/vendor/tcg/voyager/publishable/assets" because all the resources under that path, You can move to your resources to anywhere you want then set assets_path properly ,hopefully this can help u out

All 10 comments

@arogant7000 Can you open up your developer tools and look at the console and share the error message with me. The CSS file does not seem to be loading from the correct location.

i got same problem because you didn't put voyager on the root directory, you can set a new value with "assets_path" in the voyager.php under config path. By the way check issue #470

@tnylea : I don't know how can i set up that's.. But i will send the capture of my developers tools.
screen shot 2017-01-02 at 3 28 59 pm

@taoyu65 : so, how can I manage this? Please help me 馃槬

@arogant7000 find voyager.php in the config file, open it you will see assets_path , I dont know what's your project path anyway set a new value for assets_path like "assets_path" => "/parent's folder name of your voyager/vendor/tcg/voyager/publishable/assets" because all the resources under that path, You can move to your resources to anywhere you want then set assets_path properly ,hopefully this can help u out

Thank you, i will try that first

Closed due to missing update from @arogant7000.

Please ping me to reopen if this is still an issue.

sorry, i don't understand, i still low skill
@marktopper

@arogant7000 there are videos tutorial here https://devdojo.com/series/laravel-voyager-010/ follow the tutorial first until your project working, and you can make changes after that.

This issue has been automatically locked since there has not been any recent activity after it was closed. If you have further questions please ask in our Slack group.

Was this page helpful?
0 / 5 - 0 ratings