X-Cart forums

[Duramax 6.6L]

I have been using x-payments for some time now, and now I am looking to install xpayments on it's own domain in order to point another store at it.

Could someone please help me in setting up x-payments on it's own domain. How would you prevent someone from viewing the domain site while allowing stores to communicate with x-payments.

Frank

[ambal]

Use iFrame -
http://help.x-cart.com/index.php?title=X-Cart:IFrame_integration_for_X-Payments_%26_X-Cart_checkout_routines
http://www.youtube.com/watch?v=JyPD1Tr9Eow

[Duramax 6.6L]

I know how to use the i-frame method, I was talking bout how set x-payments on its own domain name. How would you stop it from being indexed by search engines and from some one viewing it on the domain home page.

set up xpayments on domain www.xxxxxxxxxx.com
stop anyone from viewing the domain but let calls for payment processing go through

[carpeperdiem]

the htaccess file takes care of that

[ambal]

I think I've got your point. You can setup X-Payments on a separate domain name e.g. yourstorecheckout.com and setup robots.txt file to forbid Google index your X-Payments. Also, .htaccess file can help, too, but password protection of checkout area does not seem to be a good idea to me.

[cflsystems]

You should not count on robots.txt - many bots disregard its entries and pages still may end up indexed somewhere. Google/Bing/Yahoo do respect it though....

[Duramax 6.6L]

Originally Posted by cflsystems

You should not count on robots.txt - many bots disregard its entries and pages still may end up indexed somewhere. Google/Bing/Yahoo do respect it though....

Exactly I know that some robots do not pay attention to robots.txt, can I block every one from accessing with .htaccess and only allow ip address that I want to let access the site. Will blocking everyone in .htaccess work or will someone still be ale to get through.

[cflsystems]

If you set IP restriction in htaccess only the IPs listed as allowed will be able to pass the restriction

[carpeperdiem]

There is an htaccess in x-payments by default.
Uncomment the IP of your server.
This is built into x-payments by default.

# Uncomment the lines below to allow access to the admin script
# only from specific IP-addresses
# (replace 192.168.10.32 below to your IP-addresses)

# Uncomment the lines below to allow access to the api script
# only from specific IP-addresses
# (replace 192.168.10.32 below to your IP-addresses)

If you do this, there is no need to do a robots.txt because IP blocking will prevent anyone that is not you or your server from seeing the files.

[Duramax 6.6L]

OK what am I doing wrong.
#
# Uncomment the lines below to allow access to the admin script
# only from specific IP-addresses
# (replace 192.168.10.32 below to your IP-addresses)
#
<Files ~ "admin.php*">
Order deny,allow
Deny from all
Allow from myxxx.xx.xxx.xxx home ip address
</Files>

Admin log-in works fine.


#
# Uncomment the lines below to allow access to the api script
# only from specific IP-addresses
# (replace 192.168.10.32 below to your IP-addresses)
#
<Files ~ "api.php*">
Order deny,allow
Deny from all
Allow from xxx.xxx.xxx.xxx ip of store web address
</Files>

Now with this uncommented, the xpayments connector can not communicate with x-payments. If I comment the lines back out, the x-payments connector can communicate with xpayments fine.

The store and x-payments are on the same server but with different ip address and domain names.

Does anyone have any ideas on why this will not work.

Regards,

Frank