DTH Development

[edit - update] I have done some further investigation and it 'appears' that it's the eWay payment option that is giving Firefox grief (but only in Hosted mode)? I have changed to several other payment options to test and everything works as it should.
Nathan, this may be a genuine bug that has not shown up as yet. (I don't know how many of your clients use this Australian gateway in Hosted mode with the following config?) It works in my Joom1.5 site with no apparent problems?!
Unfortunately I need to use the hosted eWay gateway method for my payments.


Hi,
I'm having an issue with Firefox on a test site that is using the latest of all the software. i.e. Joomla 2.5, DTreg 2.7.17 where, when I go through the checkout to the billing/payment page where it says "Event Registration:My Cart" and click on 'Checkout', I'm then sent to the "Event Registration:Payment" page that 'stops' at the credit card expiry date fields. (see below).

FIREFOX VIEW


If I use IE(9) to do the same thing everything works as expected?

IE VIEW


Admittedly this is on a test site but I have a live site that is using Joomla 1.5 and DTreg 2.7.16a that works just fine with the same setup??

BTW I'm using Firefox 13 but have also tried an earlier version and have also used another PC to test and get the same result regardless?!

The differences between the sites, besides the obvious software versions, are that the live site uses SSL when doing the payment 'thing' while the test site is set up without the SSL for testing purposes only.

Really need to to be confident before I go live with this and the deadline is looming... any thoughts?

It gets even stranger! Just paid a bit more notice to the fields in the attached images and may have stumbled upon the issue causing the problems.

If you look carefully at the image that is the IE screenshot, you will see that the 'Expiration Date' field is repeated (sort of). One of them is in a drop down format (Month + Year) and the other a text format (mm/yy)??!! Is this the reason that Firefox doesn't proceed beyond the first instance of the Expiration date? Whereas IE is more forgiving and displays them both'?

I've checked my live (Joom1.5) site and the only field that I see is the text version (mm/yy) and not the drop down one.

The next question then is ... why two?? Followed closely by.. how to fix??

OK I've edited the eWay.php file found under:- /components/com_dtregister/lib/payment to get this working in both browsers (Firefox and IE). Seems like there was some code in there not commented out completely/correctly.
However I now have a formatting issue when in the 'Payment' screen after I register for more than one event. I have the 'Multiple Event Cart Option' enabled in the configuration screen so that I can allow a single payment if someone wants to register for more than one event.
Don't know if this issue is related to the previous one?

Hi Admin,
Can someone have a look at the Eway.php file Version 2.7.15 found in:-
".../public_html/components/com_dtregister/lib/payment" - Line 83 in particular.
I believe there's a space after the last hyphen in the closing commented </dl-- > which gives 'grief' at the checkout page.

I have to re-edit it after every update.
Cheers.

Dazzler - Checked this file that you referenced and there is no space there in the current package. Actually don't see it in 2.7.15 either... however, that file HAS received some updates since that version. If you haven't yet, get the current version in place.

Hi Admin,
There must be some mistake because I still see it in the latest package 2.7.18 (re-downloaded moments ago to be sure).

Just to be clear I am referencing the Eway.php file for the 1.7/2.5 Joomla package which is clearly commented at the beginning of the file as version 2.7.15 and date stamped 19/04/12 (dd/mm/yy). This is bundled with the latest downloaded package (2.7.18) from DTregister.
Here are some screen grabs to illustrate my point.




There is of course the equivalent Joomla 1.5 version in the same package which is date stamped 04/05/12 (dd/mm/yy) and is commented as version 2.7.2. A later file and version than the one above. I'm assuming that this is where the misunderstanding is.

Hope this helps.
Cheers.

Bump. Still not resolved/solved! (2.7.18a)

As a suggestion, can we not see [SOLVED] in the subject line until the original poster of the issue/problem is satisfied that it is in fact solved for that person's issue!!!
I currently have at least two [SOLVED] issues that are indeed not solved!

I think it sends a misleading message, even if done with the best intentions/beliefs. The casual observer would think that issues are being resolved when in fact they may not be, at least for the original poster.
I for one would be only too happy to plaster SOLVED everywhere when a 100% solution is forthcoming for a particular issue.

Moderators, please take this as constructive criticism.

Please consider.

What can I say ... same issue some 9 months after my last post!!

Is it just me? Maybe so!!