Problems with cloned payment methods: get a warning!

Hi ! As I needed several payment methods as the cash on delivery one (cod) , I made several of them. In fact, I am really only interested in making buyers select a payment method so that I know which one they chose .

Anyway my problem is the following:

I have cloned the payment methods (both cod.php files) and I have installed them correctly . They appear during the checkout and I can choose them , BUT once I click on the final step "confirm order" , I don't get the normal confirmation page , I get the following error :

Warning: Cannot modify header information - headers already sent by (output started at /.../includes/languages/english/modules/payment/cod3.php:27) in /.../includes/functions/functions_general.php on line **44

**can anyone help me, please ?

Thanks a lot in advance !
Jack

Sounds like you might have space(s) or blank line(s) at the end of the file listed in the error ...

Using a good TEXT editor and not something like MSWord or your Control Panel ... remove the spaces and blank lines after the closing php tag ?> at the end of the file ...

Hi ! thanks for your help and your fast reply !

Well, I checked if there were spaces or empty lines after the ?> but there were not. I used an editor that i also used for programing I think, it should be ok (like the ones for latex).

Would you have another suggestion ?
It must really be something I did when I changed all the cod to cod2 (or 3,4) ...but I don't know what ...what else could it be ?

Thanks a lot again !
Jack

You checked this file:
/includes/languages/english/modules/payment/cod3.php

And there is nothing after the closing php tag ?> at the bottom of the file? No spaces no blank lines?

Putting your cursor at the end of the ?> you should not be able to move right nor down ...

:oops: I checked the wrong file, sorry !

There were indeed some empty lines and now it works great !

Thanks a lot !
Jack

Thanks for the update that you found the solution and were able to remove those nasty ol' space(s) and blank line(s) ...

php hates those before the opening php tag <?php** or following the closing php tag **?> and will throw those horrible looking errors ... :eek:

You'd think if it knows what is wrong it would just fix the fool things and go on on its own self ... :lamo: