News:

Looking for documentation? Take a look on our wiki

Main Menu

DIBS logo not showing

Started by Nilsy, June 10, 2014, 16:04:39 PM

Previous topic - Next topic

Nilsy

Joomla 2.5.20
Virtuemart 2.6.6

Here's the problem...
DIBS Payment Window with the module HMAC gives logo options, as all other payment solutions...
However, the DIBS system wants to point to the IMG folder placed in the plugin folder of itself. BUT, the Virtuemart has it's own way of handeling this, and is looking at the PAYMENT folder placed at /images/stories/virtuemart/payment

So due to this mismatch of input, the field is not responding as it should, and on saving the Configuration file, the field box returns empty. At least I think that's the reason.

My solution to this was to enter the PhpMyAdmin.
Look for the table xxxxx_virtuemart_paymentmethods
When you click the Edit button for the DIBS payment module, it will bring up a window that shows all the fields.

Amongst all the fields there, you will see |payment_logos=""|
Change that to |payment_logos="dibs.png"| (or whatever logo you want to use).
Then SAVE.

Now, this will point to the file that is correct for the system.
You will notice that it points to the Virtuemart folder, rather then the DIBS folder.
Ok, no problem, just transfer or upload the logo to the correct position for this, and it works.  ;)

PS, I really hope I am not alone with that problem...

jenkinhill

Have you told the developer of the plugin?
Kelvyn
Lowestoft, Suffolk, UK

Retired from forum life November 2023

Please mention your VirtueMart, Joomla and PHP versions when asking a question in this forum

Nilsy

Yes.
I explained the problem etc... but they didn't have any solution to the issue.

The answer I got was "Fint å høre at det fungerer, om enn suboptimalt. Jeg har dessverre ikke møtt på dette problemet tidligere og kjenner ikke til noen måte å fikse det på."
Which translated means "It is good to hear it is working eventhough suboptimally. I am sorry to inform you that I have not met this problem before and I know of no methods to fix it."

And so I fixed it, and sent them the quick fix method, AND a link to this post.
But... I will take a look at their code, but I had to drop that yesterday due to something else.