-
Notifications
You must be signed in to change notification settings - Fork 73
Type error: substr() expects parameter 2 to be integer, boolean given #19
Comments
Hey @WouterFlorijn --
Yes, they are character codes used to identify the header and it's various key/value pairs. Do the models function normally when you enable encryption? I.e.: do they encrypt/decrypt automatically to the database correctly? Those headers should never be visible to the model, as they're stripped off before actual cryptographic operations. It's important to note: all calls to |
@austinheap I found out I was decrypting the data twice. I made my own method to get the raw encrypted string, but it didn't work and returned the decrypted string. Then I tried to decrypt that, which obviously failed. Perhaps a good idea to throw a clear exception like |
@WouterFlorijn Just pushed a commit that'll throw
Re: migration issues: take a look at |
When using the
decryptedAttribute
function on an encrypted value, I get the following error:I am encrypting/decrypting data from a migration to ensure that existing data will still work.
My migration looks like this:
The encryption part works fine, but rolling back the migration throws the exception. Also, the encrypted values look like this:
Are the �� characters supposed to look like this?
The text was updated successfully, but these errors were encountered: