I get this error when running php artisan migrate:refresh --seed

{"error":{"type":"ErrorException","message":"PDO::quote() expects parameter 1 to be string, object given","file":"/home/dd/project/vendor/darsain/console/src/models/console.php","line":44}}

I haven't actually looked into L4 yet, and dunno when I will (no PHP projects on a horizon for me atm), so if someone can give me a quick write up of how to restructure this for L4, you'd be really helpful :)

Also, some ideas on how to retain support for L3 without creating a new repo?

OSX 10.6.8 Apache 2.2.22 PHP 5.3.15

When I direct my browser to /console I receive the following exception:

Unhandled Exception

Message:

Call to undefined method Console::attach()

Location:

/Users/woodstreet/Sites/star-communities/bundles/console/start.php on line 42

To work around this (for the time being), I just mapped the class by hand. So something is going on with Autoloading this class.

Autoloader::map(array(
    'Console' => Bundle::path('console') . 'models/console.php',
));

Otherwise when you execute this command:

Role::create( array('name' => 'admin') );

This unreadable SQL log appears:

insert into "roles" ("name", "updated_at", "created_at") values ('admin', '2013-09-09 13:27:43', '2013-09-09 13:27:43') returning "id"

The login process throws an error with Sentry and Console https://github.com/cartalyst/sentry This error dissapears when you remove this line in your app.php 'Darsain\Console\ConsoleServiceProvider',

"error":{"type":"ErrorException","message":"PDO::quote() expects parameter 1 to be string, object given","file":"vendor\\darsain\\console\\src\\models\\console.php","line":44}}

There is a bug about get_file_size(), the parameter can't be zero. So, if you use

'output_size'  =>  get_file_size(strlen($output),

to get the output size, it will throw error exception when there is no output. It should be changeed to

'output_size'  => (strlen($output)) ? get_file_size(strlen($output)) : 0,

I am not sure the bug only happened to me or everybody.

My php is 5.3.10.

Mark

I would like to reduce the editor (and display) font size if possible. I am sure I can find out where to hack this stuff out (probably in a css somewhere) but just curious if there was an exposed method for doing this?

If not, I can surely hack around and find out where to do it (heck, maybe even enhance to make this possible for others)

I understand the reason to have whitelist location, however Scribe bundle for example use filter as an easy authentication middleware to authenticate everything that route to console.

See https://github.com/daylerees/laravel-scribe

Hi I just wanted to notify that some time ago I forked this package and created standalone alternative (standalone means that can be used with any framework or with vanilla PHP). The general functionality and appearance of this application stayed the same, but I improved a lot and added some other functionality. I just released version 1.0.0.

Link to repository: https://github.com/meebio/php-eval-console

When I click execute after entering code, I get this error:

{"error":{"type":"Symfony\\Component\\Debug\\Exception\\FatalErrorException","message":"syntax error, unexpected '\"', expecting T_STRING","file":"\/Users\/user\/www\/project\/vendor\/darsain\/laravel-console\/src\/Darsain\/Console\/Console.php(111) : eval()'d code","line":1}}

After adding stripslashes() to the $code var method before eval(), the error goes away

I'm running Laravel on MacOS Mavericks, PHP 5.3 on MAMP

Currently, when an exception is thrown in the apllication, the current callback does not behave correctly. The issue comes from the Route::currentRouteName call. Changing the if condition fix the problem for me.

When I created this, there was nothing better to use, but now (and apparently some time in L4 too), there is artisan tinker which is a core component of Laravel, and provides the same kind of functionality. You can run code from your app context with all files loaded, you have access to your models, you can run ORM queries...

With that in mind, I think I'd rather deprecate this project in favor of tinker.

But, I'm not using Laravel right now, and have no tinker experience, so if there is anyone in here that does, and has a valid reason why this shouldn't be deprecated, speak up :)