Project:
UbercartCategory:
bug reportPriority:
normalStatus:
closedI don't speak inglish 
warning: array_shift() [function.array-shift]: The argument should be an array in
[path to]modules\ubercart\uc_store\uc_store.module on line 2741.
Can you help me?



Re: warning: array_shift() [function.array-shift]: The argument
When is this error message showing, and have you configured credit card encryption?
Re: Re: warning: array_shift() [function.array-shift]: The argum
1. This error message showing on link admin/store/orders/...
2. I have not configured credit card encryption
Re: Re: Re: warning: array_shift() [function.array-shift]: The a
Not sure why the error message should be turning up there, but configuring encryption should clear it. If you're just doing testing right now, you can simply browse to the payment methods settings form, open the credit card settings fieldset, and put in files to generate a temporary encryption key in your files directory.
Re: Re: Re: Re: warning: array_shift() [function.array-shift]: T
ок. Thanks
same here except happens when encrypting old cc data
I created the folder outside of my doc root but I get this error when encrypting old data. It also says the credit card data has been encrypted. So I have no idea whether it actually did it or not.
Chisholm Technologies, Inc.
Custom software development since 1999!
www.chisholmtech.com
Re: same here except happens when encrypting old cc data
Ok, I fixed the warning (Had to set the correct permissions on the folder). But now how can I run the encryption again? Not that it really matters since I'm still using dummy data, but I thought it would be good to know.
Chisholm Technologies, Inc.
Custom software development since 1999!
www.chisholmtech.com
Re: Re: same here except happens when encrypting old cc data
I don't have the exact link off the top of my head, but it's in the CC configuration docs that I link to from that field's description.
Re: Re: same here except happens when encrypting old cc data
out of curiosity, what are the correct permissions for the encrypted keys folder? I am getting an error using '644' as the folder permissions.
Re: Re: Re: same here except happens when encrypting old cc data
Hmm... I imagine you can just set it to 666 while creating the key and then back to 644 when you're done. Thanks for bringing this up... if what I said works, can you let me know so I can add it to the documentation?
Re: Re: Re: Re: same here except happens when encrypting old cc
I had the folder set to 666 to create the keys, which worked fine. Setting the directory to 644 (file is always at 644) seems to 1) prevent me from viewing the directory and 2) cause the 3 array_shift() errors on line 2471. Resetting the directory to 777 removes all of the errors. After playing around I have found that 744 works without errors as well.
Re: Re: Re: Re: Re: same here except happens when encrypting old
In further testing I found that you had to give execute permission to the folder so fopen() could work properly for reading the keys.
Re: Re: Re: Re: Re: Re: same here except happens when encrypting
so what is the final verdict on the correct permissions?
Re: Re: Re: Re: Re: Re: Re: same here except happens when encryp
755 is probably the best. Read is 4, write is 2, and execute is 1. Add them up and put them in each digit for owners, groups, and everyone else. It's really uncommon to have directories without execute permissions because you can't do anything with its files without it. Read permission only tells you what the names of the contained files are.