Jump to content


  • Content count

  • Joined

  • Last visited

Profile Information

  • Real Name
  • Gender

Recent Profile Visitors

4,001 profile views
  1. Not sure if this is a bug or if I am missing something. I just found that my shop does not send out the bank transfer data (like the IBAN etc.) in the confirmation email anymore, in case when 'money order' is the chosen payment option. The commit from May 3 commented out a line in moneyorder.php which made it stop working here: - $this->email_footer = MODULE_PAYMENT_MONEYORDER_TEXT_EMAIL_FOOTER; + //$this->email_footer = MODULE_PAYMENT_MONEYORDER_TEXT_EMAIL_FOOTER; When I remove the two // it works again. What am I missing here, should there be any new module instead that sends out this data and which is not setup correctly yet? And why is the line commented out and not simply removed when not needed anymore?
  2. Hi,

    Could you provide me the link to your website to see how does it happen please ?

    Thank you. :smile:


    PS: You could find the only dowload product I offer from this link : https://www.infinitydream.com/xecuter-sx-os-n-switch-p-1449.html

    1. milerwan


      It's ok in my payment module I have this that block the script in case of virtual product :


            // disable the module if the order only contains virtual products
            if ( ($this->enabled == true) && ($order->content_type == 'virtual') ) {
              $this->enabled = false;


  3. inra311


    Works fine now !
  4. inra311


    I checked again and this time I made 100% sure I have only original files. The problem is still there! (Tested with Firefox and Microsoft Edge) I guess you missed it because of this: There seem to be (at least) two different 'error levels'. With just a 'minor' mistake the page 'reloads' like in the screenshot, with a popup note. No problem in this case, the MATC behaves correctly: Sometimes however the page reloads with a WARNING ON TOP (like password errors? or multiple errors? repeated errors? not sure why and when this is in contrast to the first error type): In this case the MATC button seems to be 'offset' with the checkbox (which is checked but no button): Unchecking will show the button now, 'Continue' will result in a MATC error: "you need to agree with the T & Cs.."
  5. inra311


    I used Firefox, PHP 7.1 I made some little cosmetic changes to some files, like replacing the text next to the box with one with two html links (to conditions and to privacy_policy), and I set the check box left of the text instead of right. But I also tried with the original, unmodified files (I hope all...) to make sure that the problem was not related to my changes, and it was still there. Maybe I missed something? Will check again tomorrow.
  6. inra311


    I found a problem with the MATC module on the create_account page. When the customer enters data incorrectly so that the Continue button does not lead to the success page but reloads the page with an error warning , the MATC module bevaves weird. (I am talking about the case when there is a warning box on top of the page, small or first (?) errors like too short entries sometimes just open a pop-up hint, no problem in this case) The problem: all entered data is still there and the matc checkbox is still checked (which is alright) BUT the Continue button is hidden. The button will be shown when you UNCHECK the checkbox now!! A click on the button will reload the page with the error note that you must check the checkbox! At least then the checkbox is again unchecked, when you check it the button appears and this time the account will be succesfully created. Apparently, the customer's data and the state of the check box were recovered when reloading the create_account page after the first error but the button is hidden by the code on top of matc.php nevertheless. So the button state (show/hide) does not match the state (checked/unchecked) of the checkbox. I found a solution for me but it is probably not the ideal one. Maybe anyone better in coding can sort out how to fix it properly (maybe to set 'checked' always to false whenever the page is loaded) (My solution was to show the button always, by removing the script on top of matc.php. I am fine with this as it is the way it is on many websites. I had to paste in the script in the template of the buy button on checkout_confirmation instead as otherwise you could buy there without checking the MATC checkbox)
  7. inra311


    Unfortunately I don't really understand what the code does but I can confirm that the error seems to be related to the 5th parameter of tep_draw_button which is 'id="TheSubmitButton"' When I change tep_draw_button(IMAGE_BUTTON_CONTINUE, 'fa fa-angle-right', null, 'primary', 'id="TheSubmitButton"', 'btn-success'); to tep_draw_button(IMAGE_BUTTON_CONTINUE, 'fa fa-angle-right', null, 'primary', null, 'btn-success'); it does not produce the error, and still seems to work (I don't have the popup or textarea option enabled, is the parameter needed for some javascript for these??) ... but as said I don't really understand what I am doing there so probably not a good idea?! Also I found that 'id="TheSubmitButton"' does not appear in any core files, neither in the addon except within the tep_draw_button. Shouldn't it be defined somewhere? error_reporting(E_ALL & ~E_NOTICE & ~E_DEPRECATED & ~E_STRICT & ~E_USER_DEPRECATED); This did not change anything (the error is in the error log, not onscreen)
  8. inra311


    I set the MATC to checkout_confirmation. It works fine it seems but I get the following error warnings when calling up checkout_confirmation.php (PHP 7.1): PHP Warning: Illegal string offset 'type' in .../includes/functions/html_output.php on line 350 PHP Warning: Illegal string offset 'type' in .../includes/functions/html_output.php on line 353 PHP Warning: Illegal string offset 'type' in .../includes/functions/html_output.php on line 354 PHP Warning: Illegal string offset 'type' in .../includes/functions/html_output.php on line 357 PHP Warning: Illegal string offset 'type' in .../includes/functions/html_output.php on line 367 PHP Warning: Illegal string offset 'type' in .../includes/functions/html_output.php on line 375 PHP Warning: Illegal string offset 'type' in .../includes/functions/html_output.php on line 394
  9. https://github.com/gburton/Responsive-osCommerce/commit/3c82890e63dbb647e0ede849eb4d9f19d8abb0b4 --> Default to XS so buttons sits side by side. Clearfix the first button to solve long description or long gallery.
  10. I put the <div class="clearfix"></div> at the end of the button template so that it can be used with any module to follow!? Seems to work so far..
  11. There is the option 'Require telephone number' in the PWA settings (admin/modules/content --> Login without account form) that must be set to true. Then the telephone number can be entered at the bottom of the form.
  12. Thanks, will do... But you are right that it depends on the sort order. The buy button works when it is not followed by certain modules. It works e.g. before e.g. the product name but not before description. Maybe it works when the module coming next to it contains two DIV in the template, at least this is what the ones that are allright have in common??!!
  13. This cures the review button but still not the buy button
  14. Just found this has nothing to do with PC / Android but just with screen size: when I resize the window on the desktop more and more smaller, the button finally stops working. Does not change colour when mouse hovering, and does not work. Just try here yourself: https://tbyb.co.uk/product_info.php/microsoft-internet-keyboard-ps2-p-25