Jump to content
  • Checkout
  • Login
  • Get in touch

osCommerce

The e-commerce.

LuckyPiedro

Members
  • Posts

    11
  • Joined

  • Last visited

About LuckyPiedro

  • Birthday 09/22/1948

Profile Information

  • Real Name
    Piet
  • Gender
    Male
  • Location
    Vlaardingen The Netherlands

Recent Profile Visitors

1,347 profile views

LuckyPiedro's Achievements

  1. Thanks for your comment. After making the change, there are no PHP messages anymore. The 3 activated payment methods give better results in the test mode but do not always function properly in the case of simulated actions such as 'cancel' or 'error' in the bank transfer. I imagine this has to do with the work-around. The actual error is still in the code. What I don't understand is that because of this change, an extra check on "is_string ($ payment)", there is no PHP message anymore.
  2. Hi, Well it looks like I took the wrong way to switch from osCommerce version 2.3.4 to, at that time, the most current Phoenix version 1.0.4.0. There is a Dutch payment module from DigiWallet available in the apps market. However, it does not work in Phoenix version 1.0.4.0. and therefore I received, on request, a payment module from DigiWallet for Phoenix. However, this payment module also does not work with Phoenix and also gives the same error as described below. Although the provider indicates that it works if they test it themselves on Phoenix version 1.0.4.0. The road to Phoenix 1.0.6.0. seems to me to be a dead end at the moment because the structure has changed so much that it undoubtedly requires a rigorous update in the payment module. I hope there is someone in this forum with DigWallet payment module experience for Phoenix and maybe help me further. The error message: Warning: Illegal offset type in isset or empty in /home/mytest/domains/mytestsite.com/public_html/includes/classes/order.php on line 241 part of the cart () function ( in order.php) where the warning is generated. line 137 function cart () { 138 global $ customer_id, $ sendto, $ billto, $ cart, $ languages_id, $ currency, $ currencies, $ shipping, $ payment, $ comments, $ reference, $ customer_default_address_id; .... .... .... .... 241 if (isset($GLOBALS[$payment]) && is_object($GLOBALS[$payment])) { 242 if (isset($GLOBALS[$payment]->public_title)) { 243 $this->info['payment_method'] = $GLOBALS[$payment]->public_title; 244 } else { 245 $this->info['payment_method'] = $GLOBALS[$payment]->title; 246 } 247 248 if ( isset($GLOBALS[$payment]->order_status) && is_numeric($GLOBALS[$payment]->order_status) && ($GLOBALS[$payment]->order_status > 0) ) { 249 $this->info['order_status'] = $GLOBALS[$payment]->order_status; 250 } 251 } .... .... .... .... 352} // end function cart Thank you in advance.
  3. Thank you for your quick response and clear explanation. I will see if I can find the point where it goes wrong and as soon as I know anything about where in the Phoenix code or a solution in the code of the plugin I will let you know. Sincerely,Piet
  4. Hi Matt, thank you for answering my question. Your first answer is an option that I don't want to make at the moment because of a lot of changes such as layout, order_id with extension, etc. and the limited time. I don't quite understand your second answer, "Another issue though is that $payment should be a string, not an object". part of the cart () function where the warning is generated. line 137 function cart () { 138 global $ customer_id, $ sendto, $ billto, $ cart, $ languages_id, $ currency, $ currencies, $ shipping, $ payment, $ comments, $ reference, $ customer_default_address_id; .... .... .... .... 241 if (isset($GLOBALS[$payment]) && is_object($GLOBALS[$payment])) { 242 if (isset($GLOBALS[$payment]->public_title)) { 243 $this->info['payment_method'] = $GLOBALS[$payment]->public_title; 244 } else { 245 $this->info['payment_method'] = $GLOBALS[$payment]->title; 246 } 247 248 if ( isset($GLOBALS[$payment]->order_status) && is_numeric($GLOBALS[$payment]->order_status) && ($GLOBALS[$payment]->order_status > 0) ) { 249 $this->info['order_status'] = $GLOBALS[$payment]->order_status; 250 } 251 } .... .... .... .... 352} // end function cart The warning is generated in line 241, where it is checked whether it is an object. Maybe you want to tell me what I am missing / misinterpreting here. I will certainly contact Digiwallet again and ask them to double-check the code of the plugin. Sincerely, Piet
  5. Hi, I have a problem with a DigiWallet payment module in Phoenix version 1.0.4.0. If I make a payment in DigiWallet's test mode with an abnormal outcome i.e. payment canceled or interrupted then I get a warning i.e. Warning: Illegal offset type in isset or empty in /home/mytest/domains/mytestsite.com/public_html/includes/classes/order.php on line 241 Line 241 is in the cart () function in /includes/classes/order.php A payment with a normal expiry, payment successful, which is handled well without any error messages. The parameter $ payment, used in the class order.php, function cart (), with a var_dump gives the following result: function cart () { global $ customer_id, $ sendto, $ billto, $ cart, $ languages_id, $ currency, $ currencies, $ shipping, $ payment, $ comments, $ reference, $ customer_default_address_id; var_dump ($ payment); // i have added this statement result see below $ this-> content_type = $ cart-> get_content_type (); if (($ this-> content_type! = 'virtual') && ($ sendto == false)) { etcetera..... Result of var_dump: object (__ PHP_Incomplete_Class) # 19 (3) {["__PHP_Incomplete_Class_Name"] => string (7) "payment" ["modules"] => array (6) { [0] => string (17) "targetpay_ide.php" [1] => string (17) "targetpay_mrc.php" [2] => string (17) "targetpay_deb.php" [3] => string (16) "targetpay_cc.php" [4] => string (14) "moneyorder.php" [5] => string (7) "cod.php" } ["selected_module"] => NULL } I got the software for this module (addon) from Digiwallet and would be suitable for Phoenix. I also reported this Warning to DigiWallet and they could not reproduce this error. Is there anyone who has experience with this payment module or can say something about the result of var_dump? I would really appreciate it if you could give me any direction or solution to this problem. general data: website software: Phoenix version 1.0.4.0. Server: System Linux Server API: LiteSpeed V7.6 PHP: Version 7.1.33
  6. Hi Jack, Thanks for your quick response. I understand what you mean by adjusting the web browser title in the Admin. Perhaps I think I have not made my question clear.. 🙂 In your installation instructions it is stated that after installation of the "catalog" part a check is possible for correct functioning, i.e. The (default) web browser title "Replace me in Page Control under index.php - oscommerce-solution.com" should then be visible on the index.php page. If the (default) web browser title is not visible, it must first be resolved before installing the Admin part. The (default) web browser title is not visible to me and will not be visible if I manually change the relevant database fields. Before I install admin I would like to fix this. Can you tell me where in the code / which file this (default) web browser title will be inserted? Thanks in advance, LuckyPiedro
  7. 909/5000 Hi Jack, I have installed Header Tags SEO V 3.3.7 (Catalog part) in OSCOM CE Phoenix v1.0.4.0. I used the instal_category.txt file for the 5 files i.e. template_top.php, application_top.php, product_listing.php, category_tree.php and advanced_search_result.php. after installation I saw no more category names in the categories box. The link to the sub category / product list still works. This was caused by the (new) empty fields in the category_description table. (the category_description field and the new ...._ htc _.... fields are still empty.) So far so good, I would say. But what I still miss is the title "Replace me in Page Control under index.php - oscommerce-solution.com" can you tell me how important this is, or will this be fine after installing the admin part? If not can you give me a direction what I can check / change?
×
×
  • Create New...