Jump to content


  • Content count

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Tiffany_Waggoner

    Chrome samesite issue

    I need to update my site, running PHP 5.6.31, to allow SameSite=None; Secure, but I'm having difficulty, as my PHP version is outdated. (I'd love to update, but I just do not have the skillset for that task). I found on the following link https://github.com/GoogleChromeLabs/samesite-examples/blob/master/php.md that the below is the recommended code to accomplish the task, but it does not mention which file that I should place it in, or where. // Set a same-site cookie for first-party contexts header('Set-Cookie: cookie1=value1; SameSite=Lax', false); // Set a cross-site cookie for third-party contexts header('Set-Cookie: cookie2=value2; SameSite=None; Secure', false); Any help with this issue would be appreciated, as I'm still a novice when working within this system. Thank you in advance!
  2. Hi @milerwan, I'm wondering if you could help me with the installation of your Country State Selector module?

    I have it downloaded, but due to my lack of experience, I'm just unsure that I'm doing it correctly, and thought I'd come to the source for help first.

    Thanks in advance!

    1. milerwan



      What is your oscommerce version ?

      Have you got live website or are you working in localhost ?

    2. Tiffany_Waggoner


      Thanks for the reply. We are working on osCommerce 2.2-MS2 (I know very outdated, but our system is older, and I don't have a clear enough understanding of the system as a whole to attempt an update).

      The website is live.

      Our issue...The store is linked to a procurement system that requires Tax information to be passed. However, when the user enters a ship-to location with an abbreviated US state, the database address book creates the entry under "entry_state" instead of "entry_zone_id", which from what I can tell is what is tied to the tax zone functionality. So I'm hopeful by using this module will resolve this issue.

      Any guidance you have would be appreciated.

      Thank you!


    3. milerwan


      I don't see what you mean but you need the appropriate version for your v2.2 because front end is different https://apps.oscommerce.com/xRZzM&country-state-selector

      Do you have the module installed (even not functional at the moment)?Where can I see the result ?


  3. Tiffany_Waggoner

    Password Protected Category

    Thank you! I'm going to be out of the office for the rest of the day, but I'm going to give this a try first thing tomorrow morning!
  4. Tiffany_Waggoner

    Password Protected Category

    I'm hoping for help to find where I need to interject code to redirect a category link to a password protected page. In my index.php file, I have examples of how to do that on the main catalog view, but I'm at a loss as to how to add it to the subcategory. I believe the line of code that I need to interject is the following. <td class="pageHeading2" align="center">Dual Logo Stationery<br><Br><a class="hvr-grow" href="https://REDACTED/restricted-access2.php"><img src="https://REDACTED/images/Dual-Logo.png" width="325px"></img></a></td> The source code for the above works perfectly if added to the main category page, but now I just need to get it moved to cPath=8 Any help is appreciated. index.php
  5. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    First, I want to thank everyone for their help yesterday. With that, I found that all of the stores that we had in Store Maker are all out of date, and never updated to our current PHP Version back in 2019. After discovering this I cloned one of our live storefronts, and everything works perfectly. We are still getting a few PHP deprecation errors, but nothing that is breaking the store's checkout process. I'm hopeful in the future we'll be able to hire a full-time person who understands osCommerce and PHP at an expert level, but in the meantime, I've very thankful for your help!
  6. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    I'm going to apologize because I don't think I'm explaining my situation properly. So I'm sorry if we're all going around in circles. I know my inexperience is definitely causing me frustration on my end, so you guys are my heroes right now! -- All of the storefronts are all on the same server, nothing has moved, we are only adding a new store to our list of already existing customers. (we have a web2print business so each customer has their own dedicated store). All are set with the same version of OsCommerce and PHP and running through the same version of PHPMyAdmin. To create this new storefront (after I trashed the previous iteration of it) I completed the following steps. Created a new storefront database in PHPMyAdmin and imported the proper SQL database Created a new image database in PHPMyAdmin and imported the proper SQL database Our store builder is broken, so to create the file structure for osCommerce we duplicate the necessary files of a fully functional store and do a bulk find and replace for the database name or URL paths While the above is not ideal, that is the current protocol we have for creation of new stores. Our next step is to check that both the User facing side and admin side are functional. Which in this case the store is, up to the point of checkout. -- *IMPORTANT - I added the same script to a store that is fully functional, and I see several of the same errors coming through in regard to the PHP Deprecation. So I'm assuming when we upgraded in early 2019 the developer we hired didn't fully "fix" things. BUT, the store I'm currently building does have additional ones that the other successful store does not. And I have those pasted below. [24-Feb-2020 16:02:59 America/New_York] PHP Warning: curl_setopt() expects parameter 1 to be resource, null given in [REDACTED]\includes\modules\shipping\upsxml.php on line 692 [24-Feb-2020 16:02:59 America/New_York] PHP Strict Standards: Only variables should be assigned by reference in [REDACTED]\includes\classes\xml_5.php on line 70 [24-Feb-2020 16:03:13 America/New_York] PHP Warning: mysql_num_rows() expects parameter 1 to be resource, boolean given in [REDACTED]\HyperPublishing\hps_database_utility.php on line 190 [24-Feb-2020 16:03:13 America/New_York] PHP Warning: Invalid argument supplied for foreach() in [REDACTED]\checkout_process.php on line 422 [24-Feb-2020 16:03:14 America/New_York] PHP Warning: mail(): SMTP server response: 501 5.1.3 Invalid address in [REDACTED]\includes\classes\email.php on line 533 [24-Feb-2020 16:03:14 America/New_York] PHP Warning: mkdir(): No such file or directory in [REDACTED]\product_details.php on line 166 So, from here, any steps forward would be appreciated. I'm still waiting to hear back from our IT to see if any updates were made by them in the last two weeks, when a store build was completed successfully without issue. Thank you again!
  7. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    AND, I'm not sure if it matters, but the order does send out a confirmation email, and it also appears in the Admin Orders section. The above has been functioning all along, it seems the only hang-up is moving from process to success.
  8. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    The starting from scratch didn't work. (Sorry I think we were both posting at the same time). All of our other storefronts 65+ all use the same php version and the OSCommerce version, and they are all working without issues. For whatever reason, this new store build is the only one with the error. I'm a complete novice here, but wouldn't the issue be with the code of this specific storefront, and not with the OsCommerce or PHP version if everything else is working just fine?
  9. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    Well...That didn't solve the problem. Which is strange because a new store build worked a few weeks ago. I've sent a message to our IT team to see if they did anything to our server over the last few weeks that might have caused this issue to occur on new store build to fail. All of our other stores are still fully functional.
  10. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    Well, we have over 65+ existing storefronts, so upgrading to something new would be a large overhaul, and in need of someone with WAY more experience than me. 😂 But, I have that noted for our team to look into for the future.
  11. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    No updates have been made to our php or OsCommerce since early 2019. The store I'm working on, our previous administrator created some time ago (not sure when actually), so perhaps that is the source of the issue. It is not customer-facing yet, and no catalog has been built yet. So it might just be best to delete everything and spend the 30 minutes to start from scratch, as there is not any user history that would be lost at this point. That might help me establish a baseline if there is a larger issue at hand.
  12. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    Thank you for your quick response! OsCommerce 2.2-MS2 PHP Version 5.6.31 Old Version PHP 4(something) The php update was something that we did in early 2019, and the store we use as the clone, from the store maker, was created after that.
  13. Tiffany_Waggoner

    Dreaded White Screen at Checkout

    So take pity on me, as I know not what I do, and I'm tasked to make this whole thing work (long story that ends with our person leaving that knew what he was doing). Well, I have the same story as everyone else. Checkout goes fine, but then after I hit confirm order I'm stuck on a blank screen at checkout_process.php At first, I thought it was linked to the payment module, but changing that yields no success. This store is an exact clone of a previous working store, with the only difference of the stylesheet, but obviously something major is broken. I saw another post that gave instructions for an error log, and I have that attached. Short of that I honestly have no clue how to go about fixing the problem, as it seems there isn't one fix. Any help appreciated, and remember I'm such a novice with this stuff, so If I'm not understanding you I'm sorry. Thank you in advance!!! StoreError.txt