Dan Cole

John...I use Authorize.net and would be willing to contribute to the effort if you decide to develop a module for whatever service they continue to offer. Dan

@troyw Your post has been removed....please familiarize yourself with the forum guidelines. Dan

@BrockleyJohn John I was looking through the code in the quick_updates file to get a little familiar with it, in preparation for a few changes I wanted to make and noticed that the table defines weren't updated so I went ahead and did that. In case it is of some help the file is attached. Dan quick_updates.zip

Harald is on the only one that can change it but it can always be uploaded as a new version. Dan

The only other downside I can think of is the possible impact it might have on your search engine rankings. It could result in lower/shared rankings or even penalties I really don't know. When the browsers started throwing up warnings on all none HTTPS pages, most e-commerce folks just jumped on board --- taking the easier, softer way. Everyone already had SSL certificates so why not. Good luck in whatever you decide to do. Dan

Using HTTP is always going to be a security issue which is why the change was suggested. If you don't wish to do that, it's on you. Dan

I guess the short answer is...its a security issue. Dan

I wouldn't recommend that...these days browsers just warn about it and frighten customers away........can users actually turn off https? and if so, why would you want too? Dan

It is usually recommended that you change the first line in your configure.php file to https:// as well so it's like this...have you tried that? define('HTTP_SERVER', 'https://www.yoursite.com'); define('HTTPS_SERVER', 'https://www.yoursite.com'); define('ENABLE_SSL', true); Dan

Yeah...sorry about that. I had seen your post in that other thread and Rainers reply where he suggested you roll back to a version where KissIT Thumbnailer is working. I thought you had done that and were having trouble. I didn't realize you were still trying to get this to work on 1.0.5.2, where it probably won't, until he has a chance to update the contribution. Knowing Rainer he will likely update this fairly quick so if I were you I'd just put this contribution aside and work on some other aspect of your build until he has a chance to do so. Dan

That is telling you that you don't have the hooks.php file in that directory. Sounds like you failed to copy it into the right folder some where along the way. Have a look and see if it is indeed missing and if so add it from the appropriate update or from a backup, if you have one. You can also get it from the phoenix build on github if you can't find it. Dan

@Bordersbloke The crt update worked for me....are you using the PayPal APP? Dan

DeDe does this solve the problem of it not working on an initial page load? See the following post. Dan

Fredi...there is no need to be on the bleeding edge....pick a point....1.0.5.0 is probably a good spot and hang out there until things have evolved to a point where you want to step up a version or two. Otherwise proceed with caution and be patient. Dan

John here is the actual notice that I received...using AIM as well. AIM/SIM APIs and Simple Checkout Officially Deprecated Our legacy Advanced Integration Method (AIM) and Server Integration Method (SIM) APIs, as well as our Simple Checkout option, are officially deprecated, meaning we will no longer provide any updates to these APIs. If your website or payment solution uses one of these methods, this means the following: You can continue to process transactions via the APIs and Simple Checkout Your use of the APIs and Simple Checkout is “as is,” meaning you will not receive any new updates, including new features, payment network mandate updates, etc. Because these methods will no longer be updated, you could face penalties and fees associated with transactions that do not meet mandate/compliance requirements Your transaction processing functionality could deteriorate over time If you are using the AIM/SIM APIs or Simple Checkout, we highly encourage you to upgrade your website or payment solution to use the current Authorize.Net API. This will allow you to stay up to date on new releases, network mandates, and more. Please contact your web developer or payment solution provider for further assistance or to find out whether you are currently using AIM, SIM, or Simple Checkout. For me I'm not sure I'd call it urgent but it would be nice to get out in front of the bus. I don't really want to logon some morning only to find that my main payment option is now failing. Dan