Voyager: Can't access to the admin page in voyager 1.0

Created on 26 Sep 2017  路  20Comments  路  Source: the-control-group/voyager

Description:

Hello!
After composer require tcg/voyager i run php artisan voyager:install --with-dummy .

All things are correct but at the end of my installation i got this issue:

`Attempting to set Voyager User model as parent to App\User
Dumping the autoloaded files and reloading all new files

[Symfony\Component\Process\Exception\ProcessTimedOutException]
The process "composer dump-autoload" exceeded the timeout of 60 seconds.`

And then can't to my admin page.
Need your help! Thanks

question

Most helpful comment

I guess I've found out what the problem is.

I have brought that line back into the picture but first I cancelled the timeout setting for the corresponding process:

$process = new Process($composer.' dump-autoload');
$process->setTimeout(null);
$process->setWorkingDirectory(base_path())->run();

With this in place, the voyager:install command ran without issues. Apparently, here in my environment the "composer dump-autoload" needs a bit more of time to fully run.

All 20 comments

This likely has nothing to do with Voyager.

Can you try running composer dump-autoload manually? If that doesn't work, try deleting your vendor directory and running composer install followed by the artisan voyager:install command again

@fletch3555 I delete wich one the public vendor directory or the '/vendor/tcg ? I've ran composer dump-autoload then php artisan voyager:install but return [Symfony\Component\Process\Exception\ProcessTimedOutException] The process "composer dump-autoload" exceeded the timeout of 60 again

@fletch3555 this's because can't load jquery
screen shot 2017-09-27 at 8 12 34 pm

What can we do in this case? @Maghraby

@Maghraby, the presence or absence of jquery has absolutely nothing to do with this issue.

@BarthFox, I meant delete /vendor/tcg/voyager, not /public/vendor.

@fletch3555 jquery can't load any data
screen shot 2017-09-30 at 6 38 40 pm

Hi @fletch3555 Even i delete the vendor folder it returns the same error. i installed the new version of laravel with the new version of voyager but nothing changes

I have the same problem and still couldn't find the solution.

Even now i can't resolve it

I solved the problem. Its all about the "browser cache". Just clear history, that's all.

Tried on two separate vagrant homestead environments:

  • Ubuntu 16.04 / PHP 7.1.0 / L 5.5
  • Ubuntu 14.04 / PHP 7.0.5 / L 5.4

On both environments, the "artisan voyager:install" command hangs during the "Dumping the autoloaded files and reloading all new files" phase.

Result: no /admin route is available. These are the routes that show when issuing an "artisan route:list" command:

GET|HEAD | / | Closure | web
GET|HEAD | api/user | Closure | api,auth:api
GET|HEAD | arrilot/load-widget | Arrilot\Widgets\Controllers\WidgetController@showWidget |

@yakuter I can't possibly imagine why this would have anything to do with the browser's history cache.

@mpenna, please make sure VoyagerServiceProvider is loaded (either statically (5.4) or dynamically (5.5)). Sounds like artisan voyager:install isn't writing the routes to the routes file. Do you have permissions set up correctly?

Hi @fletch3555 Voyager's service provider is seems to be loading OK. Debugging the install command, I was able to detect that the installation hangs during the dump-autoload phase.

$process = new Process($composer.' dump-autoload');

Just as a test, I commented out that line and once that was out of the equation the installation ran all the way through without issues doing what it is supposed to do, which includes writing Voyager's routes to app's web routes file.

Some other wierdness is going on here, that's for sure.

The actual line that was commented out is this one:

$process->setWorkingDirectory(base_path())->run();

I guess I've found out what the problem is.

I have brought that line back into the picture but first I cancelled the timeout setting for the corresponding process:

$process = new Process($composer.' dump-autoload');
$process->setTimeout(null);
$process->setWorkingDirectory(base_path())->run();

With this in place, the voyager:install command ran without issues. Apparently, here in my environment the "composer dump-autoload" needs a bit more of time to fully run.

@mpenna thanks for this! removing the timeout worked for me. guess my "composer dump-autoload" needs a bit more time to run as well.

$process = new Process($composer.' dump-autoload'); $process->setTimeout(null); $process->setWorkingDirectory(base_path())->run();

@mpenna Which file will I make these changes?

$process = new Process($composer.' dump-autoload'); $process->setTimeout(null); $process->setWorkingDirectory(base_path())->run();
these lines are found in vendor/symphony/process/Process.php at line 165
it is written as $this->setTimeout(null);, note that i have already changed my value to null, you should yours should be 60 if it is unchanged.

This was fixed in #2552

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

Related issues

TXRRNT picture TXRRNT  路  3Comments

Nagendra1421 picture Nagendra1421  路  3Comments

iwasherefirst2 picture iwasherefirst2  路  3Comments

winex01 picture winex01  路  3Comments

wp-src picture wp-src  路  3Comments