Support

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!

• J! 4.4.4
• HikaShop - Business 5.0.4 
• AdminTools  7.5.2
• Payment Gateway : eWay - https://www.eway.com.au/

eWay payment plugin functions as expected

Installation of Admin Tools and the payment process fails.

Customer Order Process :

1. Customer orders products
2. Customer sent to eWay site for completion of card details
3. On completion the customer then clicks pay.
4. The customer receives a 404 error

Expected action: In step 4 Customer is sent back to the site payment confirmation page

What needs to happen:

To enable the Customer to return back to site the eWay plugin included in HikaShop has to create a file ewayrapid_xx.php  in the root folder of the website.
This is carried out when the payment method is saved in the admin backend of HikaShop and the customer is returned to the payment confirmation page.

My limited understanding is that the changes made to the .htaccess blocks the creation of the ewayrapid_xx.php file.

Each order creates a new ewayrapid_xx.php file.

Looking for a solution to overcome this issue while maintaining AdminTools functionality.

Hoping this is possible

Thanks

I understand that Davide having read that

My challenge is that say ewayrapid_64.php then becomes ewayrapid_65.php is added and then additional files are added for each order which will rapidly see a new file added for each individual order.

We saw 2500 individual files created last year.

Given these files are added in the root directory this could be problematic

Can you provide some guidance in relation to creating a catchall of some form?

Thanks

Am looking see if we can modify the location of the eWay file generation to /eway/ewayrapid_xx.php as a way around this situation

Will update accordingly

Thanks so much for the prompt response

OK a discovery and warning if you are using J!, Hikashop, eWay (Aussie payment gateway) and AdminTools then this is essentially a disaster

To have things functioning as required, then hacking of core code is not on for me

With 4 different code bases being updated, chasing down what needs to be hacked again to maintain the system for me is a bridge way too far.

No reflection on any of the code bases, the combination isn't a happy marriage.

 I'm testing on three other sites with different payment gateways to ascertain if it's just eWay that is the recalcitrant issue.

Davide I'll revert when I learn more

Thanks for a great product