-
Notifications
You must be signed in to change notification settings - Fork 25
Undefined property: Collective\IronQueue\IronQueue::$crypt #13
Comments
It looks like in the connecter $crypt is defined but never passed along the the actual IronQueue instance.
This is very weird since I have always used this package with crypt on for ages... now questioning everything about it 😨 |
Same issue here, only can do 'encrypt'=>false. |
@Jmrich can you please provide a Laravel version and an iron-queue version? I use iron-queue in production with encrypt => true and it's working as expected, so I'm guessing a newer laravel version somehow broke the instantiation? I actually took a look at other Queue Connectors shipped with laravel, and none seem to support encryption, so the case where laravel simply broke something is actually quite likely |
Laravel version "5.2.41", Iron-queue "v5.2.4". In my production app my laravel is v 5.2.29 with iron-queue at v 5.2.4, and it works fine. So thats the only thing that I can think of. I just noticed this in my dev env when I tried to add something to the queue |
Same issue here, same version numbers. |
I've created a fix for this. Inability to send encrypted data is serious drawback. Thanks |
bump @tshafer |
I don't know reason of no acceptance for #14 . |
Quick fix.... To be able to use LaraCollective/iron-queue, you have two options
|
@zoomsurhaiti there is pull request that fixes this issue (#14) |
It seems like original authors/maintainers ditched this package. I've decided to fork it and maintain it on my own. You can find it here: https://github.com/HydrefLab/iron-queue Feel free to use it or contribute :) |
Fixes merged into v5.2.5 release |
As the title says it is looking for a variable named
crypt
that is never defined. Not sure when this became an issue. Here is the code that fails:The text was updated successfully, but these errors were encountered: