I have a website that is currently using Paypal. The staging version of this site is linked to the Paypal sandbox, and used to work perfectly until i recently noticed that it was not working anymore. I updated the Paypal_Merchant_SDK.dll to the most recent version using NuGet, and now i'm being thrown this message:
BC30456: 'GetProperty' is not a member of 'PayPal.Manager.ConfigManager'.
Dim paypalUrl As String = ConfigManager.Instance.GetProperty("paypalUrl").ToString()
I'm not sure what the previous version of the DLL was, but it was implemented some 3 or 4 years ago, so it was obviously dated. Do i need to completely redo all my code, or are there simple adjustments that will make this work properly again?
Thanks in advance
Related
I have been searching so long for this, and couldn't find a solution.
So, I have developed a pretty basic dialog flow project and deployed it onto firebase using inline editor.
Now the 1st deployment works perfectly fine with the simulator.
However, I changed some content to include suggestion chips and modify the responses as well; this gets reflected fine in dialog flow. And I can see the changes I have made.
But when I update the Draft and try to test it again in simulator/google assistant device, it doesn't load the newer changes. I am not sure if what I am doing is correct or not.
Please help :(
Just now found this - https://discuss.api.ai/t/actions-on-google-integration-agent-updates-do-not-always-publish-correctly/7483
It seems many users are facing this issue.. :/
Dialogflow had a bug causing this issue which should now be fixed.
I started a developing an app back in ~2009. It seems somehow there are 7 copies of the app I started developing. I'd love to delete all of them, but none of the 7 copies will load a dashboard page... you know... the dashboard page with the "delete" button. How should I proceed to remove these apps?
I get an HTTP500 from Facebook's servers via each link.
As suggested I reported this to Facebook as a bug mid Monday. I gave them my personal info so they could see my exact data. They were able to reproduce the "bug" and confirmed to me that something was wrong right away (within hours). Just now (mid Friday) I got a message stating essentially, "yeah, some system somewhere messed up when creating your apps, so they got made in a broken state. We manually deleted them for you." So while there may or may not still be a bug out there, my problem was solved in ~4 working days by reporting it directly as a bug.
Please can someone help?
I've had facebook integration scripts running on my website for many years already with no problem. However, I am now being flooded with complaints from customers who use INTERNET EXPLORER saying that since an update to IE a week or so ago they are constantly getting the long-running script errors...
"Stop Running This Script.
A script on this page is causing Internet Explorer to run slowly.
If it continues to run, your computer might become unresponsive."
I've worked it out (by disabling scripts) that the problem is with the Facebook scripts.
Nothing has been changed in months on the website so it's not something I can figure out how to fix.
Scripts: Invite your friends, Like, Share page, etc
Please, please help
Thanks
Matt
I've ran into the same issue. I can reproduce the issue not just on my site, but on others as well when using IE 9 or IE 10 (have not tested with older IE versions). The issue seems to be a result of IE's compatibility view feature. If that is enabled for a website, which also has the facebook like button on the page of the site you're trying to load, a long running script error is produced (error from a function called _t). When I disable compatibility view for that website, the error goes away. I'm not sure if the issue is with the IE feature, or with facebook's button...I'm not getting same error from other scripts, nor other social buttons like google+, which makes me think the issue is on Facebook's end. I've been trying different IE setting configs for days now...so far, the only fix I can come up with is turn compatibility view off. And of course resolve issues so that compatibility view are not needed. Though telling your users they have to turn off compatibility view doesn't seem like an appropriate response...so I hope a better fix is found.
I've tried posting this on the Umbraco forums to no avail. Hoping to find some help here.
I thought I upgraded successfully from 4.0.4.2 to 4.5.2 (on my way to 4.8...) as I received no errors and everything seemed to go smoothly. However, in the backoffice, when I click on any section other than Content, I get redirected back to Content. I can manually reach each section by typing in the name of it after the # sign like: #media, but as soon as I click on a tree item, it redirects me back to Content. Any ideas would be appreciated.
2 thoughts:
You're cacheing some of the old javascript in your browser. Try clearing your cache. IE can be stubborn in this regard; preferably try in Chrome.
Personally, if your site is working under 4.5.2, I wouldn't sweat the back office issue and just continue with the upgrade to 4.8.1. There will likely be new problems to solve there anyway :) and the backoffice issue may go away.
Updating the icons via the following script fixed this problem. Links must run off the appIcon field. Not sure why this is not executed when the database is updated via the 4.5.2 upgrade.
update umbracoApp
set appIcon = '.tray' + appAlias
where appAlias IN ('content','media','users','settings','developer','member')
I was using Google::Voice perl module (version 0.03) to automatically login to google voice
and send sms. So far it was working fine. From past say, 2 weeks it stopped working.
The related modules and their versions are given below.
IO::Socket::SSL -v 1.44
Mojolicious -v 1.98
Net::SSLeay -v 1.36
I could see that when try to login to google voice, now it shows the error "Your browser's cookie functionality is turned off. Please turn it on."
Could anybody help me on this issue ?
Thanks
Google modified their markup; it happens from time to time.
I'm sure you've already discovered that the latest version in CPAN works as expected. In the future, submit an issue at https://github.com/tempire/perl-google-voice to notify the author of the problem. In this case, another user informed the author (me!) and found what Google had changed, so I was able to fix it quickly.
The source is fairly simple to understand; if it happens again, feel free to look into the code on github and see what you can do.