Menu
Forums
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Trending
What's new
New posts
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Upgrades
Log in
Register
What's new
Search
Search
Search titles only
By:
All threads
Latest threads
New posts
Trending threads
New posts
Search forums
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
Software Development
Programming
Programming Q&A
Laravel moving from production to dev
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="RastaLulz" data-source="post: 368352" data-attributes="member: 1"><p>Here's a few things you could try:</p><ul> <li data-xf-list-type="ul">Look at your access/error logs, see if anything sticks out.</li> <li data-xf-list-type="ul">Replace everything on "public/index.php" with just text, to make sure it's Laravel, and not your web server.</li> <li data-xf-list-type="ul">I assume you transferred your vendor folder (and all of its contents) over, in that case try: composer dump-autoload</li> </ul></blockquote><p></p>
[QUOTE="RastaLulz, post: 368352, member: 1"] Here's a few things you could try: [LIST] [*]Look at your access/error logs, see if anything sticks out. [*]Replace everything on "public/index.php" with just text, to make sure it's Laravel, and not your web server. [*]I assume you transferred your vendor folder (and all of its contents) over, in that case try: composer dump-autoload [/LIST] [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Software Development
Programming
Programming Q&A
Laravel moving from production to dev
Top