While running the test of the Linkpoint API using the test credit card number I get the below error:
Warning: before_process(/mnt/w0305/d40/s30/b01cdb19/www/blisschicwireless.com/blisschic/catalogincludes/modules/payment/linkpoint_api/lphp.php) [function.before-process]: failed to open stream: No such file or directory in /mnt/w0305/d40/s30/b01cdb19/www/blisschicwireless.com/blisschic/catalog/includes/modules/payment/linkpoint_api.php on line 219
Fatal error: before_process() [function.require]: Failed opening required
'/mnt/w0305/d40/s30/b01cdb19/www/blisschicwireless.com/blisschic/catalogincludes/modules/payment/linkpoint_api/lphp.php' (include_path='.:/usr/local/nf/lib/php') in /mnt/w0305/d40/s30/b01cdb19/www/blisschicwireless.com/blisschic/catalog/includes/modules/payment/linkpoint_api.php on line 219
Could someone please help me figure out what's wrong. Thanks
Latest News: (loading..)
0
132 replies to this topic
#43
Posted 21 October 2008, 16:29
a1steve, on Sep 25 2008, 02:59 PM, said:
Linkpoint works well. Thank you very much. I would like to know what can be done so credit card number will NOT be saved in the database?
Thank you.
Thank you.
#44
Posted 21 October 2008, 16:37
iofast, on Apr 7 2008, 11:19 AM, said:
1) perform check for presence and operation of gateway.
2) if gateway is down, store cc number in full as per standard osc module (this is a backup or failsafe mode to prevent from driving customers away because of error messages and an inability to checkout).
3) create tool to remove middle 8 digits of cc numbers in db once gateway down transactions have been processed manually.
4) if gateway is up, proceed normally and obscure middle 8 digits of cc. Linkpoint performs searches based on first 4/last 4 so we want to keep that much of the information. That is also how various other modules work.
5) keep current pre-auth/ticket and diagnostic system in place but add another processing method option with selection in admin panel.
6) re-enable testing mode in admin panel.
7) as a new transaction method, perform a low value authorization (less than $1) with avs and cvv check so that users who mistakenly use the wrong billing information will not be charged multiple authorizations for the full amount. Once auth has been performed, perform ticket or sale (need to double check current ticket / sale information on this as linkpoint manuals are out of date). We find our website becomes a diagnostic tool for many customers who forget to change their zip code, address information, etc with their credit card company. Despite sometimes performing transactions at many sites, apparently most sites perform little or not address validation for the billing information. This is fine for a user who checks out with a $50 cart and sees 3 charges on their card and two of them drop off in 2 weeks but for the customer charging $50,000 on their card charging them 3 times because of the address errors becomes a serious problem!
8) look into implementing visa Verified by Visa / Mastercard SecureCode system as this results in a 22 basis point drop in rates but is problematic for some sellers are not many people use this service now.
9) look into writing linkpoint order# to database and displaying on admin order panel page and/or writing the order number from the cart to the linkpoint side (not a good idea in some situations).
10) add option to turn on/off debug emails
11) Add IP Address to order comments
12) Change Linkpoint module to properly break out tax, shipping and reflect discounting in subtotal, also flag tax exempt where applicable.
13) Add refund function in OSC admin panel that works seamlessly with linkpoint.
2) if gateway is down, store cc number in full as per standard osc module (this is a backup or failsafe mode to prevent from driving customers away because of error messages and an inability to checkout).
3) create tool to remove middle 8 digits of cc numbers in db once gateway down transactions have been processed manually.
4) if gateway is up, proceed normally and obscure middle 8 digits of cc. Linkpoint performs searches based on first 4/last 4 so we want to keep that much of the information. That is also how various other modules work.
5) keep current pre-auth/ticket and diagnostic system in place but add another processing method option with selection in admin panel.
6) re-enable testing mode in admin panel.
7) as a new transaction method, perform a low value authorization (less than $1) with avs and cvv check so that users who mistakenly use the wrong billing information will not be charged multiple authorizations for the full amount. Once auth has been performed, perform ticket or sale (need to double check current ticket / sale information on this as linkpoint manuals are out of date). We find our website becomes a diagnostic tool for many customers who forget to change their zip code, address information, etc with their credit card company. Despite sometimes performing transactions at many sites, apparently most sites perform little or not address validation for the billing information. This is fine for a user who checks out with a $50 cart and sees 3 charges on their card and two of them drop off in 2 weeks but for the customer charging $50,000 on their card charging them 3 times because of the address errors becomes a serious problem!
8) look into implementing visa Verified by Visa / Mastercard SecureCode system as this results in a 22 basis point drop in rates but is problematic for some sellers are not many people use this service now.
9) look into writing linkpoint order# to database and displaying on admin order panel page and/or writing the order number from the cart to the linkpoint side (not a good idea in some situations).
10) add option to turn on/off debug emails
11) Add IP Address to order comments
12) Change Linkpoint module to properly break out tax, shipping and reflect discounting in subtotal, also flag tax exempt where applicable.
13) Add refund function in OSC admin panel that works seamlessly with linkpoint.
Updates:
7) done
9) done but only on our website... this requires changes to the admin order page which we would have to package for users
10) instructions added to readme on how to do this
11) done, see point #9
For the most current code go to our google svn:
http://code.google.com/p/jared0x90-php/sou...nkpoint_api.php
use at your own risk!!! this code has many structural changes
Here are some fixes for common errors we see (also included in our readme and the linkpoint_api.php file):
* Due to the popularity of this file and the number of requests we receive for
* help we have added this short information section. Unfortunately we simply do
* not have the time to answer everyone and give one on one help as we both are
* full time employees for iofast and are typically working well beyond normal
* working hours to get our own work done.
*
* As most recently pointed out by "shellyky" on the osCommerce forum starting in
* version 1.2 we have forced email records of all CC authorizations/sales both
* outbound and inbound data. If you'd like to disable this simply search this file
* for the term mail( and comment out the lines. It is our preference to keep a
* detailed record of transactions in our email (with the vitals removed) so that
* we can quickly look up past transactions - gotta love GMail.
*
* If you would like to hire iofast to perform any kind of diagnostic, installation or
* code improvement work on this module or have other osCommerce or PHP related projects
* you'd like for us to take a look at feel free to contact us at sales@iofast.com. You can
* find our rates and other services at:
*
* http://www.iofast.com/iofast_services.php
*
* Most of the errors we see are related to incorrect installation, improper use/ copying
* of files into the correct paths, port 1129 not being open (many hosting companies block this)
* or not reading the directions to realize that "Secure Credit Card Transaction" is how the text
* will appear in the payment module section of the oscommerce website.
*
* The PEM file is also a file that people seem to corrupt or mess up pretty often. It's possible
* people are uploaded in ASCII mode or it has invalid permissions for your web server to be
* able to access it. Either way try uploading it again and check which transfer mode your
* FTP client is uploading this file in.
*
* Trying to use the linkpoint module in debug or test mode does not currently work.
* We plan to implement this in the future but at present all of our testing is performed with
* the linkpoint provided test cards and/or real credit cards and small order totals (for final
* validation).
*
* Lastly here are some useful links to the linkpoint website should you be interested
* in working on this module:
*
* LinkPoint API Documentation:
*
* http://www.linkpoint.com/support/sup_index.htm
*
* To go to the API guide directly (This could change 10/21/2008):
*
* http://www.linkpoint.com/product_solutions...ointAPIv3_6.pdf
*
* LinkPoint API Downloads:
*
* http://www.linkpoint.com/viewcart/down_index.htm
#45
Posted 21 October 2008, 17:22
New version posted today with several changes and updates that mostly reflects our current code:
http://addons.oscommerce.com/info/4255
http://addons.oscommerce.com/info/4255
#46
Posted 22 October 2008, 17:51
iofast, on Oct 21 2008, 12:37 PM, said:
Updates:
7) done
9) done but only on our website... this requires changes to the admin order page which we would have to package for users
10) instructions added to readme on how to do this
11) done, see point #9
For the most current code go to our google svn:
http://code.google.com/p/jared0x90-php/sou...nkpoint_api.php
use at your own risk!!! this code has many structural changes
Here are some fixes for common errors we see (also included in our readme and the linkpoint_api.php file):
* Due to the popularity of this file and the number of requests we receive for
* help we have added this short information section. Unfortunately we simply do
* not have the time to answer everyone and give one on one help as we both are
* full time employees for iofast and are typically working well beyond normal
* working hours to get our own work done.
*
* As most recently pointed out by "shellyky" on the osCommerce forum starting in
* version 1.2 we have forced email records of all CC authorizations/sales both
* outbound and inbound data. If you'd like to disable this simply search this file
* for the term mail( and comment out the lines. It is our preference to keep a
* detailed record of transactions in our email (with the vitals removed) so that
* we can quickly look up past transactions - gotta love GMail.
*
* If you would like to hire iofast to perform any kind of diagnostic, installation or
* code improvement work on this module or have other osCommerce or PHP related projects
* you'd like for us to take a look at feel free to contact us at sales@iofast.com. You can
* find our rates and other services at:
*
* http://www.iofast.com/iofast_services.php
*
* Most of the errors we see are related to incorrect installation, improper use/ copying
* of files into the correct paths, port 1129 not being open (many hosting companies block this)
* or not reading the directions to realize that "Secure Credit Card Transaction" is how the text
* will appear in the payment module section of the oscommerce website.
*
* The PEM file is also a file that people seem to corrupt or mess up pretty often. It's possible
* people are uploaded in ASCII mode or it has invalid permissions for your web server to be
* able to access it. Either way try uploading it again and check which transfer mode your
* FTP client is uploading this file in.
*
* Trying to use the linkpoint module in debug or test mode does not currently work.
* We plan to implement this in the future but at present all of our testing is performed with
* the linkpoint provided test cards and/or real credit cards and small order totals (for final
* validation).
*
* Lastly here are some useful links to the linkpoint website should you be interested
* in working on this module:
*
* LinkPoint API Documentation:
*
* http://www.linkpoint.com/support/sup_index.htm
*
* To go to the API guide directly (This could change 10/21/2008):
*
* http://www.linkpoint.com/product_solutions...ointAPIv3_6.pdf
*
* LinkPoint API Downloads:
*
* http://www.linkpoint.com/viewcart/down_index.htm
7) done
9) done but only on our website... this requires changes to the admin order page which we would have to package for users
10) instructions added to readme on how to do this
11) done, see point #9
For the most current code go to our google svn:
http://code.google.com/p/jared0x90-php/sou...nkpoint_api.php
use at your own risk!!! this code has many structural changes
Here are some fixes for common errors we see (also included in our readme and the linkpoint_api.php file):
* Due to the popularity of this file and the number of requests we receive for
* help we have added this short information section. Unfortunately we simply do
* not have the time to answer everyone and give one on one help as we both are
* full time employees for iofast and are typically working well beyond normal
* working hours to get our own work done.
*
* As most recently pointed out by "shellyky" on the osCommerce forum starting in
* version 1.2 we have forced email records of all CC authorizations/sales both
* outbound and inbound data. If you'd like to disable this simply search this file
* for the term mail( and comment out the lines. It is our preference to keep a
* detailed record of transactions in our email (with the vitals removed) so that
* we can quickly look up past transactions - gotta love GMail.
*
* If you would like to hire iofast to perform any kind of diagnostic, installation or
* code improvement work on this module or have other osCommerce or PHP related projects
* you'd like for us to take a look at feel free to contact us at sales@iofast.com. You can
* find our rates and other services at:
*
* http://www.iofast.com/iofast_services.php
*
* Most of the errors we see are related to incorrect installation, improper use/ copying
* of files into the correct paths, port 1129 not being open (many hosting companies block this)
* or not reading the directions to realize that "Secure Credit Card Transaction" is how the text
* will appear in the payment module section of the oscommerce website.
*
* The PEM file is also a file that people seem to corrupt or mess up pretty often. It's possible
* people are uploaded in ASCII mode or it has invalid permissions for your web server to be
* able to access it. Either way try uploading it again and check which transfer mode your
* FTP client is uploading this file in.
*
* Trying to use the linkpoint module in debug or test mode does not currently work.
* We plan to implement this in the future but at present all of our testing is performed with
* the linkpoint provided test cards and/or real credit cards and small order totals (for final
* validation).
*
* Lastly here are some useful links to the linkpoint website should you be interested
* in working on this module:
*
* LinkPoint API Documentation:
*
* http://www.linkpoint.com/support/sup_index.htm
*
* To go to the API guide directly (This could change 10/21/2008):
*
* http://www.linkpoint.com/product_solutions...ointAPIv3_6.pdf
*
* LinkPoint API Downloads:
*
* http://www.linkpoint.com/viewcart/down_index.htm
Another diagnostic issue I forgot to mention is that Curl and SSL need to be installed and active on the site. Many errors are related to servers which do not have proper Curl and SSL installations.
Also an oscmax forum post has a good diagnostic method that tests whether you can connect to linkpoint / api regardless of oscomerce:
http://www.oscmax.com/forums/linkpoint/853....html#post31748
Edited by iofast, 22 October 2008, 17:59.
#47
Posted 26 October 2008, 19:21
I migrated my server to a new hosting. It started working fine. I changed to a new SSL then it stopped working. I had my support guys changed back to the old SSL and still not working either. I then turn on the debug and got the same error as mentioned before:
Warning: htmlspecialchars() expects parameter 1 to be string, array given in /home/realhots/public_html/includes/modules/payment/linkpoint_api/lphp.php on line 172
items =
debugging = true
I've uncommented the two lines in lphp.php fiel as suggested in previous posts. I alos downloaded the new pem file, neither one helped. Did any one really get this problem fixed? If so, can someone provided mea solution?
I've also tried the new version of the contribution. It did not work either.
Someone please help.
Warning: htmlspecialchars() expects parameter 1 to be string, array given in /home/realhots/public_html/includes/modules/payment/linkpoint_api/lphp.php on line 172
items =
debugging = true
I've uncommented the two lines in lphp.php fiel as suggested in previous posts. I alos downloaded the new pem file, neither one helped. Did any one really get this problem fixed? If so, can someone provided mea solution?
I've also tried the new version of the contribution. It did not work either.
Someone please help.
#48
Posted 26 October 2008, 19:23
-RanZ-, on Feb 17 2008, 01:09 AM, said:
It looks like the above problem is because my description contains a " ' " character... is there any way around this? All of my products have " or ' in their description 
Dan,
Did you ever get this problem fixed?
I am having the same issue and can not fix it.
#49
Posted 26 October 2008, 20:16
realhotstuff, on Oct 26 2008, 02:21 PM, said:
I migrated my server to a new hosting. It started working fine. I changed to a new SSL then it stopped working. I had my support guys changed back to the old SSL and still not working either. I then turn on the debug and got the same error as mentioned before:
Warning: htmlspecialchars() expects parameter 1 to be string, array given in /home/realhots/public_html/includes/modules/payment/linkpoint_api/lphp.php on line 172
items =
debugging = true
I've uncommented the two lines in lphp.php fiel as suggested in previous posts. I alos downloaded the new pem file, neither one helped. Did any one really get this problem fixed? If so, can someone provided mea solution?
I've also tried the new version of the contribution. It did not work either.
Someone please help.
Warning: htmlspecialchars() expects parameter 1 to be string, array given in /home/realhots/public_html/includes/modules/payment/linkpoint_api/lphp.php on line 172
items =
debugging = true
I've uncommented the two lines in lphp.php fiel as suggested in previous posts. I alos downloaded the new pem file, neither one helped. Did any one really get this problem fixed? If so, can someone provided mea solution?
I've also tried the new version of the contribution. It did not work either.
Someone please help.
We added filter code with version 1.2. We also have hundreds of products with " or ' in them. If you really think this will help your problem, you would simply add to the filter code in the linkpoint_api.php code.
FROM:
// class methods
function filterLinkPoint($strToFilter){
$strToFilter=str_replace("&", " and ", $strToFilter);
$strToFilter=str_replace("�", "u", $strToFilter);
return $strToFilter;
}
TO:
// class methods
function filterLinkPoint($strToFilter){
$strToFilter=str_replace("&", " and ", $strToFilter);
$strToFilter=str_replace("�", "u", $strToFilter);
$strToFilter=str_replace(""", "in.", $strToFilter);
$strToFilter=str_replace("'", "ft.", $strToFilter);
return $strToFilter;
}
This assumes you want " to become inches and ' to become feet and be certain to USE THE ASCII CODES!!!! http://www.ascii.cl/htmlcodes.htm
However, your problem appears to be more basic and is covered in the diagnostic information I just posted. I am going to re-post the same data in a numbered format that I hope people will step through and actually check as you didn't mention several other diagnostic steps such as validating the port, validating curl or ssl and made specific mention of using the debug mode which, as mentioned many times in the past, does not currently work.
Due to the popularity of this file and the number of requests we receive for help we have added this short information section. Unfortunately we simply do not have the time to answer everyone and give one on one help as we both are full time employees for iofast and are typically working well beyond normal working hours to get our own work done.
1. Trying to use the linkpoint module in debug or test mode does not currently work. We plan to implement this in the future but at present all of our testing is performed with the linkpoint provided test cards and/or real credit cards and small order totals (for final validation). If you wish to write the code or hire us to write the code, please feel free. We have a running list of improvements that should be made and some which we use in our own website but cannot quickly package for other osc users. 2. Curl and SSL must be properly installed. 3. Most of the errors we see are related to incorrect installation, improper use/ copying of files into the correct paths. Validate your ftp settings and your paths! 4. Positively validate that port 1129 (many hosting companies block this) is open on your server!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! This is the single largest error and accounts for several issues that have been attributed to code problems. 5. "Secure Credit Card Transaction" is how the text will appear in the payment module section of the oscommerce website. 6. As most recently pointed out by "shellyky" on the osCommerce forum starting in version 1.2 we have forced email records of all CC authorizations/sales both outbound and inbound data. If you'd like to disable this simply search this file for the term mail( and comment out the lines. It is our preference to keep a detailed record of transactions in our email (with the vitals removed) so that we can quickly look up past transactions - gotta love GMail. 7. The PEM file is also a file that people seem to corrupt or mess up pretty often. It's possible people are uploaded in ASCII mode or it has invalid permissions for your web server to be able to access it. Either way try uploading it again and check which transfer mode your FTP client is uploading this file in. 8. An oscmax forum post has a good diagnostic method that tests whether you can connect to linkpoint / api regardless of oscomerce (provides validation of pem file, ssl and curl outside of oscommerce function: http://www.oscmax.com/forums/linkpoint/853....html#post31748 9. LinkPoint API Documentation: http://www.linkpoint.com/support/sup_index.htm To go to the API guide directly (This could change 10/21/2008): http://www.linkpoint.com/product_solutions...ointAPIv3_6.pdf LinkPoint API Downloads: http://www.linkpoint.com/viewcart/down_index.htm 10. If you would like to hire iofast to perform any kind of diagnostic, installation or code improvement work on this module or have other osCommerce or PHP related projects you'd like for us to take a look at feel free to contact us at sales@iofast.com. You can find our rates and other services at: http://www.iofast.com/iofast_services.php 11. Let us know if you think additional diagnostic steps should be added to this simple guide. And, of course, read the readme and check out the notes in the linkpoint_api.php file! There are diagnostic credit cards and extension change notes in there that can be very useful.
Edited by iofast, 26 October 2008, 20:19.
#50
Posted 26 October 2008, 20:40
Thank you very much for the quick response.
I modified the code as you instructed, but still no good.
This issue is strange, It was working after I migrated everything to a new server. I then installed a new SSL on the server and it stiopped working. I had them switched back to the original SSL and still no good.
I searched the forum and someone had similar problem as I am having now. They claimed that after uncommented out the two lines solved the problem. I did that too but still no good.
Someone also suggested downloade the new pem file. I followed that as well, still no good.
I modified the code as you instructed, but still no good.
This issue is strange, It was working after I migrated everything to a new server. I then installed a new SSL on the server and it stiopped working. I had them switched back to the original SSL and still no good.
I searched the forum and someone had similar problem as I am having now. They claimed that after uncommented out the two lines solved the problem. I did that too but still no good.
Someone also suggested downloade the new pem file. I followed that as well, still no good.
#51
Posted 27 October 2008, 00:15
realhotstuff, on Oct 26 2008, 04:40 PM, said:
Thank you very much for the quick response.
I modified the code as you instructed, but still no good.
This issue is strange, It was working after I migrated everything to a new server. I then installed a new SSL on the server and it stiopped working. I had them switched back to the original SSL and still no good.
I searched the forum and someone had similar problem as I am having now. They claimed that after uncommented out the two lines solved the problem. I did that too but still no good.
Someone also suggested downloade the new pem file. I followed that as well, still no good.
I modified the code as you instructed, but still no good.
This issue is strange, It was working after I migrated everything to a new server. I then installed a new SSL on the server and it stiopped working. I had them switched back to the original SSL and still no good.
I searched the forum and someone had similar problem as I am having now. They claimed that after uncommented out the two lines solved the problem. I did that too but still no good.
Someone also suggested downloade the new pem file. I followed that as well, still no good.
After you applied the new code (presumably with ascii characters), did you go through any of the steps I outlined point by point?
Did you check that the port is open and working? Did you download the test code that works outside of osc for validation? Did you check that you properly have curl installed? Did you turn testing/debug mode off?
#52
Posted 27 October 2008, 03:19
After spending more time on the problem and finally figured out it was caused by my isp's DNS.
My FTP was pointing to the old server and my browser was pointing to the new server. I kept changing the code and ftp it to the old server while testing on the new server. I ftped the new code to the new server and everything worked fine now.
To be clear, I un-commented the 2 lines mentioned before and everything worked.
Thank you iofast for your quick reply. I really appreciate it.
My FTP was pointing to the old server and my browser was pointing to the new server. I kept changing the code and ftp it to the old server while testing on the new server. I ftped the new code to the new server and everything worked fine now.
To be clear, I un-commented the 2 lines mentioned before and everything worked.
Thank you iofast for your quick reply. I really appreciate it.
#53
Posted 27 October 2008, 15:05
My hosting has port 1129 blocked, however I contacted them and they will open it up for me but they need to know if its ingoing and/or outgoing and whether its TCP or UDP.
Does anyone know which protocols I would need opened and in what directions?
Thank you, I appreciate the help.
Does anyone know which protocols I would need opened and in what directions?
Thank you, I appreciate the help.
#54
Posted 27 October 2008, 16:57
RitchiesMusic, on Oct 27 2008, 11:05 AM, said:
My hosting has port 1129 blocked, however I contacted them and they will open it up for me but they need to know if its ingoing and/or outgoing and whether its TCP or UDP.
Does anyone know which protocols I would need opened and in what directions?
Thank you, I appreciate the help.
Does anyone know which protocols I would need opened and in what directions?
Thank you, I appreciate the help.
TCP and ask them for both outgoing / incoming.
#56
Posted 28 October 2008, 16:17
For some reason, I have never been able to get the error codes to show up in anything but the URL bar. I have started to have a larger number of frustrated customers because for some reason they sometimes fail to use the billing address that is linked to their credit card, and then they miss the URL error code. Is their supposed to be a pop-up box that I am somehow missing or where is the error supposed to be generated?
Any help would be greatly appreciated.
Evan
Any help would be greatly appreciated.
Evan
#57
Posted 28 October 2008, 18:08
dsolutions, on Oct 28 2008, 12:17 PM, said:
For some reason, I have never been able to get the error codes to show up in anything but the URL bar. I have started to have a larger number of frustrated customers because for some reason they sometimes fail to use the billing address that is linked to their credit card, and then they miss the URL error code. Is their supposed to be a pop-up box that I am somehow missing or where is the error supposed to be generated?
Any help would be greatly appreciated.
Evan
Any help would be greatly appreciated.
Evan
Evan,
The code creates a red bar just below the breadcrumbs with a verbose description of the problem. We specifically increased the verbosity of the output so you can even see if the address information was just checked (ok for an X code for example) or verified (a Y code). I was going to drop a screenshot here but apparently my workstation needs a reboot. I may put up a screenshot at a later time. The linkpoint information is changing shortly as linkpoint / yourpay become firstdata so we may have a re-release shortly.
#58
Posted 28 October 2008, 19:55
Now that Linkpoint wprks fine for me. I would like to know what lines of code that I need to change so I don't store CC info in my database. I would like to be certified as PCI compliance. It is just a lot easier not to save the CC info.
Thank you for all the great support here.
Thank you for all the great support here.
#59
Posted 29 October 2008, 04:18
realhotstuff, on Oct 28 2008, 03:55 PM, said:
Now that Linkpoint wprks fine for me. I would like to know what lines of code that I need to change so I don't store CC info in my database. I would like to be certified as PCI compliance. It is just a lot easier not to save the CC info.
Thank you for all the great support here.
Thank you for all the great support here.
Quote
We plan to remove the middle 8 digits of all cards stored in the future but have not gotten to it. If you would like us to do this specifically we can but unfortunately we would need to charge for the time to do it as we are scheduled up for months on projects at the moment and our programming staff is already working at full capacity.
#60
Posted 29 October 2008, 13:19
iofast, on Oct 29 2008, 12:18 AM, said:
Someone asked the same question a few posts above yours... our response was:
I paste this as I'm on my 15th hour for the day which is becoming increasingly normal so I hope you understand our time constraints. If you want to get this done within, say the next month, take a look at our website services page (posted above) and we can get it done within a few days. Otherwise I don't expect to revisit this code for several months though we will likely be working on any new issues or compatibility problems brought on by firstdata taking over some of yourpay/linkpoint directly.
I paste this as I'm on my 15th hour for the day which is becoming increasingly normal so I hope you understand our time constraints. If you want to get this done within, say the next month, take a look at our website services page (posted above) and we can get it done within a few days. Otherwise I don't expect to revisit this code for several months though we will likely be working on any new issues or compatibility problems brought on by firstdata taking over some of yourpay/linkpoint directly.
I found the quick way to do it. I modified the code in checkout_processing.php. I put in blanks for all credit card related fields.
