-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not recognize honeypot method #2
Comments
Hi, Does Laravel find the service provider as expected ? Can you call its methods ? |
It's really not working. I tried using |
Are you sure you have the service provider added in the app.php? 'Msurguy\Honeypot\HoneypotServiceProvider', |
Yes. Btw, I'm using L4.1. Perhaps this version is affecting your package? |
I'm using L4.1 and it's ok. I believe you must add the service provider at the end of the providers array, not at the top. It that all right ? |
No, it didn't. Let me check this might be an isolated incident having to do with some of the core classes I've extended. |
Does my recent changes to the service provider fix this issue? |
I have the exact same problem. I'm using Laravel 4.2 and I've added 'Msurguy\Honeypot\HoneypotServiceProvider' to app.php |
@rombat are you using twig too? Do you use twigbridge or anything like that? |
Nope I'm using Blade. |
Here's the Exception:
|
Can you paste your app.php providers array too please. |
|
if possible, can you comment out/remove these providers and see if it honeypot works?
|
Also are you using the latest dev-master of honeypot? Latest tagged version of honeypot is quite old |
Yep, I have "vinicius73/seotools": "dev-master". Is there a way to make it work? I'm using Former and Bootstrapper\Form in almost all my forms. |
Weird how the my time field is not added, what's the actual raw HTML output for the honeypot section? You got quite a lot of dependencies to be honest, could be anything. I did take a look at former and bootstrapper service provider on github as I originally suspected it was replacing Laravel's built in form and therefore overriding the macros, but that doesn't seem like the case. Can you setup a real bare repository on github that replicates the issue in the min number of steps I can take a look. |
Ever since this commit: f18c81f My regular 4.2 application fails with |
@iBotPeaches what's in your |
|
Can you comment out |
Yes that fixed it, but then removed all my custom |
Of course not, just trying to find the cause. Can you post your FormBuilderServiceProvider? |
|
Does your FormBuilder extends Laravels one? How are you using your custom form builder, do you have a facade? |
Yep my custom
Which then changes the Facade in
|
The new service provider in honeypot will listen for when the |
That worked. Thank you! No idea why I used |
@garygreen : here's a test repository with the error: https://github.com/rombat/test-laravel-honeypot |
I've created a PR which will help resolve #25 |
Thanks! |
Getting this too using with L5. Both providers and aliases arrays are setup correctly. |
@purplegriffon are you using the |
@garygreen I have it listed in the aliases array and in my views I'm using {{ Form::honeypot('pot', 'pot_time') }}, that's what's breaking. |
Ah, ignore me. I see the usage has changed. Apologies. |
Yup, we got rid of the form macro as it was a bit of a headache to maintain especially as the form builder is deprecated/no longer maintained, and it's usage didn't really add much value. |
Might just be me but I'm getting:
An exception has been thrown during the rendering of a template ("Method honeypot does not exist.")
in my view. I'm using Twig and access your method as such,form_honeypot('hname', 'htime')
.I also have my own custom macros which I'm able to access as
form_mymacroname('xxx')
so I don't think it's the macro but I might be wrong on this.The text was updated successfully, but these errors were encountered: