Connor Tumbleson

Ever since this commit: f18c81f814ca7a4f0d82dc76b78d2790b277c0f5 My regular 4.2 application fails with `honeypot method does not exist`. I reverted back to the commit prior to that one and everything worked.

``` 'providers' => array( 'Illuminate\Foundation\Providers\ArtisanServiceProvider', 'Illuminate\Auth\AuthServiceProvider', 'Illuminate\Cache\CacheServiceProvider', 'Illuminate\Session\CommandsServiceProvider', 'Illuminate\Foundation\Providers\ConsoleSupportServiceProvider', 'Illuminate\Routing\ControllerServiceProvider', 'Illuminate\Cookie\CookieServiceProvider', 'Illuminate\Database\DatabaseServiceProvider', 'Illuminate\Encryption\EncryptionServiceProvider', 'Illuminate\Filesystem\FilesystemServiceProvider', 'Illuminate\Hashing\HashServiceProvider', 'Illuminate\Html\HtmlServiceProvider', 'Illuminate\Log\LogServiceProvider', 'Illuminate\Database\MigrationServiceProvider', 'Illuminate\Pagination\PaginationServiceProvider', 'Illuminate\Queue\QueueServiceProvider', 'Illuminate\Redis\RedisServiceProvider', 'Illuminate\Remote\RemoteServiceProvider', 'Illuminate\Database\SeedServiceProvider', 'Illuminate\Session\SessionServiceProvider', 'Illuminate\Translation\TranslationServiceProvider', 'Illuminate\Validation\ValidationServiceProvider', 'Illuminate\View\ViewServiceProvider', 'Illuminate\Workbench\WorkbenchServiceProvider', 'GrahamCampbell\Markdown\MarkdownServiceProvider', 'App\Form\Providers\FormBuilderServiceProvider',...

Yes that fixed it, but then removed all my custom `Form` functions that I had created, so can't really use that fix.

`FormBuilderServiceProvider.php` ```

Yep my custom `FormBuilder` extends laravel. ``` use \Illuminate\Html\FormBuilder as IlluminateFormBuilder; class FormBuilder extends IlluminateFormBuilder { ``` Which then changes the Facade in `app/config` to point to my custom one,...

That worked. Thank you! No idea why I used `formbuilder` vs `form`.

https://bulma.io/documentation/components/breadcrumb/

Thanks for the sample. Guess this new styled string handling is full of edge cases. Possible duplicate: https://github.com/iBotPeaches/Apktool/issues/2890

This is the workaround I've been using to use events in an HTTP sense after I noticed this same behavior from L10 -> L11. ```php // We must load the...

At the moment there is parity between the docs and tool header. This will break the parity - any reason you feel strongly the hyperlinked [here] is not sufficient?