Latest News: (loading..)

reflex-ocasion

Members
  • Content count

    43
  • Joined

  • Last visited

6 Followers

About reflex-ocasion

  • Birthday 07/23/1968

Profile Information

  • Real Name
    Alfonso Gonzalez
  • Gender
    Male
  • Location
    Malaga (Spain)

Recent Profile Visitors

10,536 profile views
  1. Thanks for this update!

  2. I am sorry for my bad english. I have corrected another error in the admin/returns.php file. When you have more than one return and you edit the first one, there is no problem. The problem occurs when you have to select another return from the list and click on the edit button. Log in by repeating over and over again the store header below the tabs. To solve search (line 809) $contents[] = array('align' => 'center', 'text' => tep_draw_button(IMAGE_EDIT, 'document', tep_href_link('returns.php', tep_get_all_get_params(array('rID', 'action')) . 'rID=' . $rInfo->returns_id . '&action=edit&oID=' . $rInfo->orders_id)) . tep_draw_button(IMAGE_DELETE, 'trash', tep_href_link('returns.php', tep_get_all_get_params(array('rID', 'action')) . 'rID=' . $rInfo->returns_id . '&action=delete'))); and replace with this $contents[] = array('align' => 'center', 'text' => tep_draw_button(IMAGE_EDIT, 'document', tep_href_link('returns.php', 'rID=' . $rInfo->returns_id . '&action=edit&oID=' . $rInfo->orders_id)) . tep_draw_button(IMAGE_DELETE, 'trash', tep_href_link('returns.php', tep_get_all_get_params(array('rID', 'action')) . 'rID=' . $rInfo->returns_id . '&action=delete'))); Actually what we have done is eliminate tep_get_all_get_params(array('rID', 'action')) that was over and is what causes the loop.
  3. Sorry for my bad English. I changed the buttons tep_image_button by tep_draw_button in admin/returns_reasons.php and admin/refund_methods.php In admin/returns_reasons.php you can not delete a reason, it gives an error and I have solved it in another way. I was looking for an erroneous table in the database. On line 68: $status_query = tep_db_query("select count(*) as count from returned_products where returns_status = '" . tep_db_input($oID) . "'"); Line 79 and successive still continues and is corrected as well: $history_query = tep_db_query("select count(*) as count from returns_status_history where returns_status_id = '" . (int)$oID . "'"); I include the modified files for verification. I have also translated it into the Spanish language, in case someone is interested. They are not included here. returns_reasons.php refund_methods.php
  4. No, I have not been able to solve it, I have not had time and now less because I have a family in the hospital. It should not be complicated, just add missing code at that particular point. Right now I do not remember which line it is, I'm sorry.
  5. For those of us working with limited stock for different reasons (eg second hand products or limited edition products), I observe the lack of a silly detail. If the product has attributes and one of them is out, why you can not display a message warning him? If I want to add an sold out product the system does not allow it and that is correct, but if before out I add it to the list and afterwards I want to buy it already out, there is no warning and the customer can take a disappointment. On sites like eBay it works and I think solving this would help a lot of people, especially when that list is emailed. I regret my bad English, I use an online translator that sometimes does not work well.
  6. As I said before, to solve my problem I had to eliminate the constant. When he asked me to send him my files for review, I had to add it again. It is very possible that at that particular point I did not put all the code, that something happened to me. I apologize for it.
  7. The online translator I use is not always perfect. I regret the bad translations. In my case, in my particular case, The constant is what prevents the minimum length of the telephone field from being checked. Once it is removed, check the minimum length of the field. Do not add anything because the file is basically a clone with some modifications to create_account.php. If one file works perfectly the other must also do it. In fact it does in my case once I have removed the constant, now works correctly. I do not know why it happens, I just know that it happens to me and it seems that my case is unique, nobody else has happened to him. It may also be that no one has checked it before, it is taken for granted the goodwill of the people, it is assumed that the customer will enter all the numbers. I discovered it by mistake, I entered a single number and to my surprise it was not verified if it was correct or not. The question is that if someone else has the same problem already knows what to do, remove the constant. My specific case may be unique or not and there are more users with the same problem without knowing that they have this problem. I give it for solving even if it does not really know why it happened. I repeat. I do not speak English and I use an online translator. If the bad translation has caused any communication problem I apologize.
  8. It is what I say from the first moment, that only serves to show or not the field. That the requirement interferes in some way in the result is another question. The requirement is something so simple that it should not interfere in any way and yet it interferes, at least to me, in my concrete and particular case. I do not know why it happens but it does. I use oscommerce BootStrap EDGE for about 1 year and this is the first time that something like that happens to me. Even in the 9 years that I have been using osCommerce in different versions I had happened before.
  9. @raiwa They are already sent but you will not find anything unusual. I assume you meant the file cm_pwa_login instead of cm_paypal_login as indicated. If I am wrong, let me know. Although I have it installed I do not have the option to identify through PayPal. Deleting the variable will solve the problem, to me now it works me correctly.
  10. If I put a single number in the telephone field, pwa admits it It's what comes in the order. The minimum set pwa does not respect.
  11. I'm going to remove what I have, I'll put your files and I'll make some screenshots.
  12. I have added some extra fields. To avoid conflicts I used YOUR file unmodified. The result is the same, there is an error.
  13. Sorry, I have written it in Spanish, I have not translated it. Everywhere is big, appears as True. There is no difference between upper and lower case.
  14. En todas partes está en grande, aparece como True. No hay diferencias entre mayusculas y minusculas.
  15. Have you tried to put fewer numbers than the minimum set? I did it by mistake and that's why I know there is a bug. For me now it works perfectly without the variable. If I put it gives me the error mentioned, I can put a number of a single number and pwa gives it as valid.