What I did

1. Install laravel and the package normally following the instructions
2. Create a new user from the frontend (app.dev/register)
3. Then Login to the admin and try to delete that user, and shows me this error:

Use of undefined constant undefined - assumed 'undefined'

However, the second time I tried, the user was deleted successfully.

I'm having some difficulties grasping how would I add a field in /user/1/edit to add the relationship User - Roles, could you give me an example how I would achieve that?

Awesome package by the way !

I'm not aware of any way to add Users to Roles through Voyager. It would be nice to have this UI feature across the board.

I'm thinking something like this:

• Many-to-Many: http://www.bootply.com/yexwIRM76L.
• One-to-Many: Perhaps some type of dropdown/select element?

Got error while running : php artisan voyager:install
[Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the "storage" namespace.

Hi, could you please update the license under which this code is released?
Thanks.

When installing Voyager on my existing laravel application it gives me an error.

[RuntimeException]                                       
  Error Output: PHP Fatal error:  Class 'App\Http\Control  
  lers\Controller' not found in /home/hawkleaf/Desktop/Pn  
  euGraph-V3/vendor/tcg/voyager/src/Controllers/VoyagerCo  
  ntroller.php on line 14  

Anyone know what this would mean? I did change the App namespace, but after changing it back (on the cnotroller itself) it doesnt work either

A clean installation,is not working create new page, error
Warning: 1265 Data truncated for column 'status' at row 1

fresh install, after entry admin and password,

~/admin/login

BadMethodCallException in Controller.php line 107:
Method [hasTooManyLoginAttempts] does not exist.
.....................

first of all thanks for this great job keep it up.
where can i edit the create new item page .
I am trying to build a restaurant admin page and i want to add a map to the edit page so i can set the latitude and longitude when i drag the marker.

Always get error:

BadMethodCallException in Controller.php line 107: Method [hasTooManyLoginAttempts] does not exist.

laravel on local host with running MAMP PRO

It would be nice if we could specify different connections to Voyager and main tables. By "main" I mean tables that are in main project. I prefer using admin panel as a separate project. So we could specify another connection in database.php.

Similar to Issue #23, would it be possible to restructure how the routes are included so we can have control over where they're included? I'm working on a multi-tenant setup and only want this admin page available for one of them.

Great project by the way! I'd love to help contribute in some way.

I was unable to integrate to my project due to already having a roles table.

I worked with migrations and seeding for a little while but gave up and started new. I can afford a fresh install but I'm sure many people couldn't.

Perhaps voyager could work in its own namespace for these things to better integrate to existing applications.

Great tool, BTW, and many thanks!

Not found some files, which link from menus/browse.blade.php

  <link rel="stylesheet" href="{{ config('voyager.assets_path') }}/remark/global/vendor/datatables-bootstrap/dataTables.bootstrap.css">
  <link rel="stylesheet" href="{{ config('voyager.assets_path') }}/remark/global/vendor/datatables-responsive/dataTables.responsive.css">


    <script src="{{ config('voyager.assets_path') }}/remark/global/vendor/datatables/jquery.dataTables.js"></script>
	<script src="{{ config('voyager.assets_path') }}/remark/global/vendor/datatables-fixedheader/dataTables.fixedHeader.js"></script>
	<script src="{{ config('voyager.assets_path') }}/remark/global/vendor/datatables-bootstrap/dataTables.bootstrap.js"></script>
	<script src="{{ config('voyager.assets_path') }}/remark/global/vendor/datatables-responsive/dataTables.responsive.js"></script>
	<script src="{{ config('voyager.assets_path') }}/remark/global/vendor/datatables-tabletools/dataTables.tableTools.js"></script>

[Doctrine\DBAL\DBALException]

Unknown database type enum requested, Doctrine\DBAL\Platforms\MySQL57Platform may not support it.

in posts add - edit blade there is a sanity check for featured image

<div class="panel-body">
                        @if(isset($dataTypeContent->excerpt))
                        <img src="{{ Voyager::image( $dataTypeContent->image ) }}" style="width:100%" />
                        @endif
                        <input type="file" name="image">
                    </div>

Should it not be?

<div class="panel-body">
                        @if(isset($dataTypeContent-> image))
                        <img src="{{ Voyager::image( $dataTypeContent->image ) }}" style="width:100%" />
                        @endif
                        <input type="file" name="image">
                    </div>

I'm not sure if it's intended or not, but when you delete database table from admin panel, model that was created with it is not deleted.

Edit:
Models are created using artisan make:model command, but there is no command to delete it. I guess it must be deleted from App folder directly.

I use postgresql as my database. When I want to register a new user, I get the error:
QueryException in Connection.php line 763: SQLSTATE[23505]: Unique violation: 7 ERROR: duplicate key value violates unique constraint "users_pkey" DETAIL: Key (id)=(1) already exists. (SQL: insert into "users" ("name", "email", "password", "updated_at", "created_at") values (rockxsj, [email protected], $2y$10$Gc3f4jg/99KZCzavEctL.OZwvBEdysPGmkkYBleTW2FMDCRohu2Mq, 2016-11-01 10:31:56, 2016-11-01 10:31:56) returning "id")

Adding new table in voyager needs to make sure that the Primary ID has an auto_increment value otherwise you may receive an error when adding a new data type and not specifying an ID

I login as admin,when I want to view a post, eg:http://localhost:8000/post/latest-post.
I will get the error message like this:
`Sorry, the page you are looking for could not be found.

1/1
NotFoundHttpException in RouteCollection.php line 161:`

/admin/database/edit-table

Whoops, looks like something went wrong.

1/1
ErrorException in VoyagerDatabaseController.php line 176:
Undefined offset: 11
in VoyagerDatabaseController.php line 176
at HandleExceptions->handleError('8', 'Undefined offset: 11', '/Library/WebServer/Documents/voyager/vendor/tcg/voyager/src/Controllers/VoyagerDatabaseController.php', '176', array('request' => object(Request), 'query_rows' => array('increments('id')->nullable(false)', 'integer('menu_id')->nullable()', 'string('title')->nullable(false)', 'string('url')->nullable(false)', 'string('target')->nullable(false)->default('_self')', 'string('icon_class')->nullable()', 'string('color')->nullable()', 'integer('parent_id')->nullable()', 'integer('order')->nullable(false)', 'timestamps()->nullable()', 'timestamps()->nullable()'), 'index' => '11', 'row' => '', 'field' => 'sdsdsd', 'type' => 'string', 'nullable' => false, 'key' => '', 'default' => '', 'query' => 'timestamps()->nullable()')) in VoyagerDatabaseController.php line 176
at VoyagerDatabaseController->buildQuery(object(Request)) in VoyagerDatabaseController.php line 89
at VoyagerDatabaseController->update(object(Request))
at call_user_func_array(array(object(VoyagerDatabaseController), 'update'), array(object(Request))) in Controller.php line 55
at Controller->callAction('update', array(object(Request))) in ControllerDispatcher.php line 44
at ControllerDispatcher->dispatch(object(Route), object(VoyagerDatabaseController), 'update') in Route.php line 190
at Route->runController() in Route.php line 144
at Route->run(object(Request)) in Router.php line 642
at Router->Illuminate\Routing{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing{closure}(object(Request)) in VoyagerAdminMiddleware.php line 24
at VoyagerAdminMiddleware->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in SubstituteBindings.php line 41
at SubstituteBindings->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in VerifyCsrfToken.php line 65
at VerifyCsrfToken->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in ShareErrorsFromSession.php line 49
at ShareErrorsFromSession->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in StartSession.php line 64
at StartSession->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in AddQueuedCookiesToResponse.php line 37
at AddQueuedCookiesToResponse->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in EncryptCookies.php line 59
at EncryptCookies->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in Pipeline.php line 104
at Pipeline->then(object(Closure)) in Router.php line 644
at Router->runRouteWithinStack(object(Route), object(Request)) in Router.php line 618
at Router->dispatchToRoute(object(Request)) in Router.php line 596
at Router->dispatch(object(Request)) in Kernel.php line 267
at Kernel->Illuminate\Foundation\Http{closure}(object(Request)) in Pipeline.php line 53
at Pipeline->Illuminate\Routing{closure}(object(Request)) in CheckForMaintenanceMode.php line 46
at CheckForMaintenanceMode->handle(object(Request), object(Closure)) in Pipeline.php line 137
at Pipeline->Illuminate\Pipeline{closure}(object(Request)) in Pipeline.php line 33
at Pipeline->Illuminate\Routing{closure}(object(Request)) in Pipeline.php line 104
at Pipeline->then(object(Closure)) in Kernel.php line 149
at Kernel->sendRequestThroughRouter(object(Request)) in Kernel.php line 116
at Kernel->handle(object(Request)) in index.php line 54

I rename the App via
php artisan app:name Pollr

When I install via voyager:install something wrong with service call. I checked in directory
Vendor\tcg\voyager\src\controllers
most of them still called App as the prefix, why not adapt to the new App Name?
use {App}\Http\Requests;
use {App}\Http\Controllers\Controller;

Class 'App\User' is not found if the app User model has been moved (in my case to App\Models\User). There appears to be a namespace config already for the service provider, however App\User is hard coded in the User model as well as the index view. Is it possible to use the config in both of those files as well, or even just the Auth config?

Hello,

How we can assign roles to users?

Thanks,
Faraz

After installing voyager.

php artisan voyager:install

If you try to run any command (php artisan make:model TwitchStream) it throws an error:

PHP Fatal error:  Uncaught Symfony\Component\Debug\Exception\FatalThrowableError: Type error: Argument 2 passed to Illuminate\Routing\UrlGenerator::__construct() must be an instance of Illuminate\Http\Request, null given, called in /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Routing/RoutingServiceProvider.php on line 60 in /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Routing/UrlGenerator.php:103
Stack trace:
#0 /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Routing/RoutingServiceProvider.php(60): Illuminate\Routing\UrlGenerator->__construct(Object(Illuminate\Routing\RouteCollection), NULL)
#1 /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Container/Container.php(290): Illuminate\Routing\RoutingServiceProvider->Illuminate\Routing\{closure}(Object(Illuminate\Foundation\Application))
#2 /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Container/Container.php(746): Illuminate\Container\Container->Illuminate\Container\{closure}(Ob in /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Routing/UrlGenerator.php on line 103

Fatal error: Uncaught Symfony\Component\Debug\Exception\FatalThrowableError: Type error: Argument 2 passed to Illuminate\Routing\UrlGenerator::__construct() must be an instance of Illuminate\Http\Request, null given, called in /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Routing/RoutingServiceProvider.php on line 60 in /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Routing/UrlGenerator.php:103
Stack trace:
#0 /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Routing/RoutingServiceProvider.php(60): Illuminate\Routing\UrlGenerator->__construct(Object(Illuminate\Routing\RouteCollection), NULL)
#1 /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Container/Container.php(290): Illuminate\Routing\RoutingServiceProvider->Illuminate\Routing\{closure}(Object(Illuminate\Foundation\Application))
#2 /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Container/Container.php(746): Illuminate\Container\Container->Illuminate\Container\{closure}(Ob in /home/vagrant/Code/Voyager/vendor/laravel/framework/src/Illuminate/Routing/UrlGenerator.php on line 103

Because the voyager config file gets published, it is used every time the app is bootstrapped, so it tries to run the asset() function in the config file which excepts a Request object as the second argument and it crashes.

The solution is simply remove the asset() function from the line:
'assets_path' => asset('/vendor/tcg/voyager/assets'),
To:
'assets_path' => '/vendor/tcg/voyager/assets',

And actually everything works because there is no need to use the function.

I will send a pull request.

I've removed Posts table from database manager and dashboard crashed.

SQLSTATE[42S02]: Base table or view not found: 1146 Table 'voyager.posts' doesn't exist (SQL: select count(*) as aggregate from posts)

There is no views when i publish vendor files. and no option to customize dashboard view.
Would be good if you make possible to publish views

Hello,

I am new to Voyager, i have installed it as you directed in the documentation, its installed successfully, but when i try to login with default credentials [email protected]/password then i get following error.

Thanks,
Faraz

Do you plan to provide a unit tests suit to prove to stability of the project?

I like this admin, but, its have other language, spanish, francais, etc, not only english??

I don't know why I'm running into this now, but hey, Murphy's law! ;)

Getting a
[Doctrine\DBAL\DBALException]
Unknown database type enum requested, Doctrine\DBAL\Platforms\MySqlPlatform may not support it.

Research suggests that the Doctrine platform has never supported enum and never will given that people have reported the issue for years. Most solutions seem incredibly hacky.

Anyways, for what it's worth, I'm dropping this here as I ran into it and don't have time to solve something that's clearly very complicated.

http://docs.doctrine-project.org/projects/doctrine-orm/en/latest/cookbook/mysql-enums.html
laravel/framework#1346
laravel/framework#1186
https://wildlyinaccurate.com/doctrine-2-resolving-unknown-database-type-enum-requested/

Catchable fatal error: Argument 2 passed to Illuminate\Routing\UrlGenerator::__construct() must be an instance of Illuminate\Http\Request, null given, called in /Applications/MAMP/htdocs/voyager/vendor/laravel/framework/src/Illuminate/Routing/RoutingServiceProvider.php on line 62 and defined in /Applications/MAMP/htdocs/voyager/vendor/laravel/framework/src/Illuminate/Routing/UrlGenerator.php on line 103

The font awesome icons used in "breadcrumbs" are missing.

I have the solution for it going to send the PR.

I would like to know what is the location of view files of newly created table. Although i have searched everywhere in tcg/voyager/src folder but i find nothing ?

can you fix this ?

On thing that caught my eye while browsing the code was the usage of eval in the BreadController.
I'm sure there are other options, but you may instantiate the classes with:

$dataTypeContent = (new $dataType->model_name)->find($id);

I have been working on building out simple blog for our website using Voyager. This is hands down the best option I've worked with. Thanks for it.

I have run across some issues as follows. Not sure if you have plans to build it out further, if it was missed, or if something more dynamic that I haven't seen is not working properly. It mainly revolves around Posts.

I don't see any relationships for the author or the category in the Post model. There doesn't appear to be a category_id in the posts migration. I manually added these and attempted to attach a category to a post, but it didn't get writte to the db making me wonder if there is a $guarded or $fillable property being created dynamically.

If this is all stuff you are okay with me adding in, let me know and I can put it a PR for you. Otherwise, tell me to pipe down ;)

I'm currently using postgresql as my database and it seems 'SHOW TABLES' is not supported by it. I saw some workarounds by using google but that would mean I need to alter files in the vendor folder (which I don't like to do as I'll be pushing my app to bluemix).

I get an error when trying to login using the updated(015b3dc) User model:

FatalThrowableError in EloquentUserProvider.php line 114:
Type error: Argument 1 passed to Illuminate\Auth\EloquentUserProvider::validateCredentials() must be an instance of Illuminate\Contracts\Auth\Authenticatable, instance of App\Models\User given, called in [...]/vendor/laravel/framework/src/Illuminate/Auth/SessionGuard.php on line 387

I'm using my own User model, that inherits from Voyager's User model so I can add in a little of my own functionality (using my own subclass would be unnecessary if/when #23 is completed, but \Illuminate\Foundation\Auth\User should probably still be used).

Thoughts?

Not so much a issue however to be able to add users without having a image would be cool out of the box. At the moment it spits out a SQL Error. However im guessing its a fairly simple fix of allowing avatar to be null.

Error:

"
QueryException in Connection.php line 763:
SQLSTATE[23000]: Integrity constraint violation: 1048 Column 'avatar' cannot be null (SQL: insert into users (name, email, password, avatar, updated_at, created_at) values (Dad, [email protected], $2y$10$jZPJuDv/gyXLwSKVhx7Z7uohCf1/MqUmZv7cNJnIVrcLIEsESgAay, , 2016-10-28 02:33:34, 2016-10-28 02:33:34))
"

Hi. Could you add the ability to upload multiple files and images?

I've followed the steps exactly, I get to the login page, and when I click sign in, just the icon turns once, and nothing else happens. Am I missing something?

Whenever I try to edit an user I receive an InvalidArgumentException in Carbon.php line 425.

This probably is because Voyager/Laravel saves the created_at differently than expected, as indicated by at Carbon::createFromFormat('Y-m-d H:i:s', 'January 28th, 2016 11:20 AM') and at Model->__set('created_at', 'January 28th, 2016 11:20 AM') in VoyagerBreadController.php line 220

on : /admin/pages/create

FatalErrorException in Page.php line 12:
Class 'TCG\Voyager\Models\Auth' not found

Is there a way to publish the views?

It would be better to have full control over views, controllers and models instead of keeping it inside the package folder.

Thanks

I followed the installation instructions for Laravel from https://laravel.com/docs/5.3 and created a new project by composer create-project --prefer-dist laravel/laravel blog

Inside the project folder I installed voyager as stated in the docs by requiring voyager composer require tcg/voyager and then adding voyager service provider and Image Intervention service provider to the config/app.php file in the 'providers' => [ array

When I try to perform php artisan voyager:install I get Class 'TCG\Voyager\VoyagerServiceProvider' not found

Yo, your admin looks awesome! One problem, I've already got a users table and what have you, so how do I integrate this with an existing structure. Starting from blank is not an option.

When using the Database feature, since it's hard coded the query to select all tables and other specific MySQL queries it crashes when using sqlite driver.

SQLSTATE[HY000]: General error: 1 near "SHOW": syntax error (SQL: SHOW TABLES) (View: /Users/afsardo/Code/.../vendor/tcg/voyager/src/views/tools/database/index.blade.php)

So since i am really in love with this package (seriously it's awesome <3) i will try and add compatibility to all major database drivers.

try to access to the website https://the-control-group.github.io/voyager/docs/index.html
and the return response say
Y'arr!!! These docs be coming soon!

using the default admin user and password

it says logging in

but just returns to the same screen with no error