i have developed paypal pro by using omnipay.And i need to do card validation before payment process start.
Helper::validateLuhn($cardnumber)
But i am getting error like this:- Fatal error: Class 'Helper' not found
What is the reason for getting this error?Need to include any other file?Any help?
In order to use the Helper::validateLuhn() function, you need to add this to your php file:
use Omnipay\Common\Helper;
Related
QFtp Ftp;
When i have Ftp loggedIn and i try to get a file that does not exist on the server using
Ftp.get(RemoteFile, LocalFile.data()); i received a warning
I know it is because of writting direct to data of LocalFile.
This is the warning:
QIODevice::read (QTcpSocket, "QFtpDTP Passive state socket"): device not open
What is the best way to treat this warning?
I tried Try Catch(...) to fix the issue and still happenning.
Forget about. I use the list command before the get to check if file was there and avoid the issue.
I did a FTP.list(RemoteDirectory) and if the file is there i call FTP.get(RemoteDirectoy, localFile.data()), if is not there i do not call The FTP.
I am trying to integrate Zapier and Odoo. For the most part all integrations work, however when I attempt to use Stock Move module I am getting the error,
Fault (code object of type 'DateTime' has no len()) occurred. Message: Traceback (most recent call last):
Zapier Form
I have a suspicion it is the way I am entering the date. I have tried multiple times, with different format but with no luck.
Check-in your code where you try to search the result Like,
result = self.env['obj.obj'].search([('date_field', '=', now.date())]) someting like So try to convert into str formation str(now.date())
The reported issue only occurs where the proper value is not stored [for that check the python date type formation use and applied with same.]or either you can try to search with these things.
Hope this may help you.
Thanks
Turns out it was a bug in zapier. Confirmed with their team, no known solution at this time.
I just discovered GitLab's groups and decided that it would be ideal for the kind of work I am doing. I created a private group and am getting the following error when I try to create a project under it:
The form contains the following error:
PG::QueryCanceled: ERROR: canceling statement due to statement timeout CONTEXT: while rechecking updated tuple (0,187) in relation "site_statistics" : UPDATE "site_statistics" SET "repositories_count" = "repositories_count"+1
I attempted to do the same in a new subgroup; however, I still get the same error. I must add that I am not using a paid plan of GitLab.
Thank you.
I have the same issue. I think only thing that we can to do is to wait until this error will fix.
Found this issue page: https://gitlab.com/gitlab-org/gitlab-ce/issues/53778
I'm trying to learn JavaScript for Odoo. I've created a new class in my custom module's js file.
openerp.odoojs = function(instance){
console.log('instance: ',instance);
console.log('session: ',instance.session);
}
This is what I'm getting when I browse the session object in the console.
But when I try to access the uid or any other attribute or parameter like instance.session.uid, I'm getting it as undefined. Please help! I'm stuck with this. I'm unable proceed further.
Try to extend the 'Backbone.Model' like 'PosModel' in 'model.js' file. Try to define the 'initialize' function, where you will find two parameters in function arguments as 'session' and 'attributes'. Here you can find the uid using 'session.uid'.
I can't figure out what I'm always getting 400. This is my model:
class G2
extend Garb::Model
metrics :pageviews
end
and this is my call:
G2.results(profile, :filters => {:pageviews.gte=>3})
and I get this:
Garb::BadRequestError: [400] Invalid Value : https://www.googleapis.com/analytics/v3/data/ga?ids=ga:XXXXXXXX&start-date=2013-01-07&end-date=2013-02-06&metrics=ga:pageviews&filters=ga:pageviews%3E%3D3
If I don't include the :filters symbol, then the request will be successful. I tested this query using the GA Query Tool and it works.
Any thing I have missed?
It turns out that this is a bug caused by a recent check-in to garb. The author (sija) has reverted the change and this issue no longer reproduces: https://github.com/Sija/garb/issues/17