10 replies to this topic

[KenshinH]

Despite my best efforts for the past half hour, I have not been able to get HiPAY to work, and it's gotten extraordinarily frustrating.

This is the latest version of Prestashop. The module is installed and enabled. It is configured. It is configured to allow all countries.

Yet still, even when registered and signed in, HiPAY does not list as a payment option.

Is there some fault here with this module or Prestashop entirely?

[shokinro]

Please check here for a check list of why a payment module does not show up, hope it will give you some information.

[KenshinH]

shokinro, on 08 August 2011 - 11:31 PM, said:

Please check here for a check list of why a payment module does not show up, hope it will give you some information.

1. Have you installed the module? - Yes
2. If it is installed already, then try to check the configuration is correct. Make sure is there is configuration errors or warnings. - There are no errors or warnings.
3. The module has been configured correctly. That all required parameters are set correctly. - Check.
4. Check if payment currency restrictions are set correctly. Some module require you select only currency, some modules you can select multiple currency. - No problems here.
5. Check if the the region (country) restrictions is set correctly. Some module by default, only set a specific country or no country to use the module. You need to set country explicitly and click save button. - All countries checked.
6. Check if group restriction is set correctly. Modules can be limited to different customer groups. See above screen for more details. - All groups are given access.
7. Check if the modules requires some other conditions. For example, some module requires SSL (HTTPS) environment, if you don't set this SSL in your store, the module will not show up either. - SSL is enabled. I'm not aware of any other special circumstances HiPAY requires. None are clearly defined.

[KenshinH]

Bump.

Anyone else have any other suggestions?

[KenshinH]

As a quick update, I've confirmed this is as well not a caching issue based on someone elses suggestion.

Still looking for a solution.

[KenshinH]

After 3 days of persistence, I believe I've finally gotten the module working.

It turns out it was indeed a fault of the module itself.

Thanks to the help of affect on the #prestashop IRC channel via Freenode.

Here's a copy of our IRC conversation, since I don't think I could really properly format the entire issue here:

Spoiler

<affect> with half of the items resetting to none on error
<affect> true, doesn't get displayed
<affect> if ($hipayAccount AND $hipayPassword AND $hipaySiteId AND $hipayCategory AND Configuration::get('HIPAY_RATING'))
<affect> well
<affect> if it doesn't get displayed then one of these fails
<affect> and for me, it's all empty strings
<affect> and their module is as ugly as their website
<Ichigo> affect, Ahah :/
<affect> well
<affect> var_dump($currency->iso_code);
<affect> that shows GBP somehow
<affect> $currency = new Currency($this->getModuleCurrency($cart));
<affect> var_dump($currency->iso_code);
<affect> I mean this
<affect> although my cart has EUR
<Ichigo> Mine is USD.
<affect> oh
<affect> it's their function
<affect> I bet it's wrong
<affect> ps_module_currency
<affect> ffs
<affect> what's this
<affect> some ugly piece of crap
<affect> ok I'll set EUR as default
<Ichigo> USD is my default, heh
<affect> and you've got hipay acc for usd?
<Ichigo> Yeah
<affect> string(3) "EUR" int(0) string(0) "" string(0) "" string(0) "" string(0) ""
<affect> true
<affect> it just fails in getting it's own data
<Ichigo> :/
<Ichigo> Currency: US dollar
<affect> $hipayAccount = ($this->prod ? Configuration::get('HIPAY_ACCOUNT_'.$currency->iso_code) : Configuration::get('HIPAY_ACCOUNT_TEST_'.$currency->iso_code));
<affect> ok
<affect> basically
<affect> $this->prod is empty for me
<affect> so instead of taking my account data
<affect> it takes some test account data
<affect> which is empty so it doesn't display the module template
<affect> now just to figure out what's prod
<Ichigo> It's funny though. This bug was reported in 1.4.3
<Ichigo> and it was said to be fixed
<Ichigo> Maybe they just broke it further
<affect> $this->prod = (int)Tools::getValue('HIPAY_PROD', Configuration::get('HIPAY_PROD'));
<affect> well
<affect> HIPAY_PROD configuration value is empty for me
<affect> public function install()
<affect> {
<affect> Configuration::updateValue('HIPAY_SALT', uniqid());
<affect> // Force using Prod mod
<affect> Configuration::updateValue('HIPAY_PROD', 1);
<affect> somehow that fails on install
<affect> lemme reinstall and see
<affect> hm it's set to 1 on install
<affect> lol
<affect> and then it's deleted
<affect> on update
<affect> good fucking job
<affect> umm
<Ichigo> o.O..
<affect> bool(false)
<affect> Configuration::updateValue('HIPAY_PROD', Tools::getValue('HIPAY_PROD'));
<affect> yeah
<affect> great job
<affect> the only problem is that
<affect> there's no element with HIPAY_PROD id or name on the page
<affect> so basically
<affect> it just erases the hipay_prod value when you configure the module
<affect> and if hipay_prod is false it takes wrong account data from the db
<affect> and if it takes wrong data it doesn't display itself on payment page.
<Ichigo> Oh wow. :/
<affect> =
<affect> if you configure the module - it doesn't display itself on payment page
<affect> clever.
<Ichigo> Hahah.
<affect> so if you remove that line it should work
<affect> at least the display part
<Ichigo> <affect> bool(false)
<Ichigo> <affect> Configuration::updateValue('HIPAY_PROD', Tools::getValue('HIPAY_PROD'));
<Ichigo> All of that?
<affect> just the second line
<affect> or just find the public function hookPayment($params)
<affect> and add $this->prod = 1 right in the beginning
<affect> not really sure what it's supposed to do
<affect> but basically it looks like
<affect> $hipayAccount = ($this->prod ? Configuration::get('HIPAY_ACCOUNT_'.$currency->iso_code) : Configuration::get('HIPAY_ACCOUNT_TEST_'.$currency->iso_code));
<affect> that should be vice versa
<affect> if $this->prod is set means the module hasn't been updated yet so it should take test values
<affect> if it's not set it should take user-defined values
<affect> they're doing the opposite
<Ichigo> Deleting Configuration::updateValue('HIPAY_PROD', Tools::getValue('HIPAY_PROD')); didn't seem to do anything sadly. :/
<affect> you'll have to either reinstall the module or set HIPAY_PROD to your db
<affect> in your db*
<affect> fakdfjaskdff
<affect> I MEAN.
<affect> set HIPAY_PROD to 1 in your db

So basically, the simple fix is to open your prestashop database, select the ps_configuration table, and find the row with the name "HIPAY_PROD"

For me, the value field was completely blank. You need to change the value field to "1"
If you're using phpMyAdmin, you may need to delete the row, the re-insert it using the same information (excluding the value field).

So afterwards it should look something like this:
 Screenshot-3.png   178.87K   49 downloads

[shokinro]

so actually it was a bug?
thanks you very much for sharing the information.
it is a great tips.

maybe I will add a link to this thread to my blog as references later.

[KenshinH]

Yes. It is a bug.

The API system also does not work, so I'm afraid I have to say HIPAY is nowhere near worth ever bothering with, unless you are willing to rewrite half of the module yourself.

[shokinro]

Quote

The API system also does not work, so I'm afraid I have to say HIPAY is nowhere near worth ever bothering with, unless you are willing to rewrite half of the module yourself.

If you have time, you and make it work and make it better.
Then can make it as free or maybe paid module?

[thiagorobis]

KenshinH, on 10 August 2011 - 09:45 PM, said:

After 3 days of persistence, I believe I've finally gotten the module working.

It turns out it was indeed a fault of the module itself.

Thanks to the help of affect on the #prestashop IRC channel via Freenode.

Here's a copy of our IRC conversation, since I don't think I could really properly format the entire issue here:

Spoiler

<affect> with half of the items resetting to none on error
<affect> true, doesn't get displayed
<affect> if ($hipayAccount AND $hipayPassword AND $hipaySiteId AND $hipayCategory AND Configuration::get('HIPAY_RATING'))
<affect> well
<affect> if it doesn't get displayed then one of these fails
<affect> and for me, it's all empty strings
<affect> and their module is as ugly as their website
<Ichigo> affect, Ahah :/
<affect> well
<affect> var_dump($currency->iso_code);
<affect> that shows GBP somehow
<affect> $currency = new Currency($this->getModuleCurrency($cart));
<affect> var_dump($currency->iso_code);
<affect> I mean this
<affect> although my cart has EUR
<Ichigo> Mine is USD.
<affect> oh
<affect> it's their function
<affect> I bet it's wrong
<affect> ps_module_currency
<affect> ffs
<affect> what's this
<affect> some ugly piece of crap
<affect> ok I'll set EUR as default
<Ichigo> USD is my default, heh
<affect> and you've got hipay acc for usd?
<Ichigo> Yeah
<affect> string(3) "EUR" int(0) string(0) "" string(0) "" string(0) "" string(0) ""
<affect> true
<affect> it just fails in getting it's own data
<Ichigo> :/
<Ichigo> Currency: US dollar
<affect> $hipayAccount = ($this->prod ? Configuration::get('HIPAY_ACCOUNT_'.$currency->iso_code) : Configuration::get('HIPAY_ACCOUNT_TEST_'.$currency->iso_code));
<affect> ok
<affect> basically
<affect> $this->prod is empty for me
<affect> so instead of taking my account data
<affect> it takes some test account data
<affect> which is empty so it doesn't display the module template
<affect> now just to figure out what's prod
<Ichigo> It's funny though. This bug was reported in 1.4.3
<Ichigo> and it was said to be fixed
<Ichigo> Maybe they just broke it further
<affect> $this->prod = (int)Tools::getValue('HIPAY_PROD', Configuration::get('HIPAY_PROD'));
<affect> well
<affect> HIPAY_PROD configuration value is empty for me
<affect> public function install()
<affect> {
<affect> Configuration::updateValue('HIPAY_SALT', uniqid());
<affect> // Force using Prod mod
<affect> Configuration::updateValue('HIPAY_PROD', 1);
<affect> somehow that fails on install
<affect> lemme reinstall and see
<affect> hm it's set to 1 on install
<affect> lol
<affect> and then it's deleted
<affect> on update
<affect> good fucking job
<affect> umm
<Ichigo> o.O..
<affect> bool(false)
<affect> Configuration::updateValue('HIPAY_PROD', Tools::getValue('HIPAY_PROD'));
<affect> yeah
<affect> great job
<affect> the only problem is that
<affect> there's no element with HIPAY_PROD id or name on the page
<affect> so basically
<affect> it just erases the hipay_prod value when you configure the module
<affect> and if hipay_prod is false it takes wrong account data from the db
<affect> and if it takes wrong data it doesn't display itself on payment page.
<Ichigo> Oh wow. :/
<affect> =
<affect> if you configure the module - it doesn't display itself on payment page
<affect> clever.
<Ichigo> Hahah.
<affect> so if you remove that line it should work
<affect> at least the display part
<Ichigo> <affect> bool(false)
<Ichigo> <affect> Configuration::updateValue('HIPAY_PROD', Tools::getValue('HIPAY_PROD'));
<Ichigo> All of that?
<affect> just the second line
<affect> or just find the public function hookPayment($params)
<affect> and add $this->prod = 1 right in the beginning
<affect> not really sure what it's supposed to do
<affect> but basically it looks like
<affect> $hipayAccount = ($this->prod ? Configuration::get('HIPAY_ACCOUNT_'.$currency->iso_code) : Configuration::get('HIPAY_ACCOUNT_TEST_'.$currency->iso_code));
<affect> that should be vice versa
<affect> if $this->prod is set means the module hasn't been updated yet so it should take test values
<affect> if it's not set it should take user-defined values
<affect> they're doing the opposite
<Ichigo> Deleting Configuration::updateValue('HIPAY_PROD', Tools::getValue('HIPAY_PROD')); didn't seem to do anything sadly. :/
<affect> you'll have to either reinstall the module or set HIPAY_PROD to your db
<affect> in your db*
<affect> fakdfjaskdff
<affect> I MEAN.
<affect> set HIPAY_PROD to 1 in your db

So basically, the simple fix is to open your prestashop database, select the ps_configuration table, and find the row with the name "HIPAY_PROD"

For me, the value field was completely blank. You need to change the value field to "1"
If you're using phpMyAdmin, you may need to delete the row, the re-insert it using the same information (excluding the value field).

So afterwards it should look something like this:
Screenshot-3.png

Works very well here!
Thank you

[drew_m]

KenshinH, on 10 August 2011 - 09:45 PM, said:

So basically, the simple fix is to open your prestashop database, select the ps_configuration table, and find the row with the name "HIPAY_PROD"

For me, the value field was completely blank. You need to change the value field to "1"

This fixed the module for me too, thanks! I can confirm that Hipay is now working and receiving payment.