Jump to content

Demitry

Members
  • Content count

    333
  • Joined

  • Last visited

  • Days Won

    8

Everything posted by Demitry

  1. Hi, I’m finishing up a module for the checkout success page. It’s a short email form designed to get customer feedback on their purchase experience right at the final step in the checkout process. I could store their feedback in the database, but this is bad because it will quickly bloat the database. There are two issues that I am facing with this modification. First: While writing this module, I realized that this checkout_succes page contains all of the modules inside a form. I’m a bit confused about this form because It is designed to update any customer changed data inside of it (such as product notifications and/or PWA keep account), but the button included inside this form is the Continue button, which redirects the user to the index.php page. So, if a customer makes changes on this form and does not click the Continue button, but instead closes the browser tab, then all of their changes are not saved to the database, right? The point is, many other osC pages apply the Continue button to load the index.php page. Having been on the site, a customer quickly becomes aware of this and may opt to not click that button on the checkout_success page because they are finished shopping and do not want to go to the home page. Additionally, they are likely to believe that their selections on that page are automatically saved upon any changes they make. Why? ..well, because there is no button to save the changes. Therefore, shouldn’t that Continue button be renamed to Update Changes or Save Changes? And, there should be a message displayed on the index.php page post redirection, to let the customer know that their changes were saved. Second: I am now faced with a challenge where (in order to avoid nested forms), I must add my module. I would need to either add it below this form in a separate module block or include it as a button/link to a modular popup. Any ideas on how to better structure this, where I can include the module with the other checkout_success modules and be able to use the related sort order feature to position it where I want?
  2. I get the concept, but as far as I know an email has to be structured as a form and if I included it as a module in the checkout_success block, then it will become nested inside of that page's order form. What I can do is add the module as a request for the customers feed back and when they click on the link (which would be a feedback question), that would open a modal window with the email form inside of it. The modal code would then have to be added to that checkout_success.php page after the main order form. Or, I could add it as an on-page form directly on that checkout_success.php page after the main order form. Either way, I would have to alter a core file, which is something I was trying to avoid.
  3. @kgtee Thanks KG, I always thought nesting forms was bad coding practice. I'll read through that stackoverflow link and see what I can get out of it.
  4. ok man, ..we're waiting on your version. ...whenever you get time.
  5. I did not know that. I assumed that they would have been removed if they were not going to be used. Ah, that is part of the module, but I could never figure out what that description meant because it did not make much sense to me. Here is the screenshot of it below. Thanks for explaining it.
  6. Jack, thank you for the explanation. The CC module adds only the card number, expiration date, and card type to the customers database table, but so do the other CC processing modules. And even the latest version of osC Phoenix has these columns in the customers database table. what do you mean by split option? I could not find anything related to this. ~~~~ Vicent, I did not plan on it because it was removed from osC and introducing it back in as an addon will likely conflict with the underlying purpose of why it was removed in the first place. As Jack said, it was a PCI compliance issue, but I am not 100% sure if this was the only reason. There may have been other security issues that were part of that decision to remove it as well. Aside from that, I do not use the left or right columns in the osC layout so, my CSS is not structured for that layout - specifically, when resizing the browser. Here is a screenshot of what my payment page looks like. I am currently just using these modules for testing and only plan on having a CC module (via a merchant account) and a PayPal module as payment options.
  7. @domiosc hi Vicent, Thank you for that information. Actually, I redid the old Credit Card module (cc.php) for BS Edge. I have not tested it yet, but it should work for what I'm looking to do before actually getting a merchant account. hi Matt, I took a look at the customers database table and even in the latest version of Phoenix there is a column for credit card numbers. I'm not sure if these are now encrypted or as per Vicent, you still have to get a separate addon installed for that. Anyway, having these in the customers table does not kill the PCI compliance. I ran a PCI complaisance test on my BS Edge site on https://www.immuniweb.com and it came back with everything good except for the Content Security Policy, which goes in the main htaccess file. See screenshot below. @Jack_mcs hi Jack, From our prior conversation, you mentioned that the Credit Card module was removed for PCI non-compliance, however, I ran a test with that module redone for BS Edge on https://www.immuniweb.com and it came back clean for PCI compliance. I'm not sure if there is something else that was the cause, but I just wanted to let you know my findings.
  8. thanks Jack, I'll take a look at it. I'll see if they have some sort of a sandbox option for testing prior to going live, ..preferably one that is free to test. I really did not want to use authorize.net as the merchant account/gateway, but will see.
  9. Thank you for the explanation, Matt. I was not aware of all that. So, basically I need to sign up for a gateway / merchant account first, ..then install and modify the available osC credit card payment modules that is made for that account?
  10. hi Matt, I think that MS2.2 payment module stored CC numbers in the database, but not any CVV or CVC2. PCI compliance prohibits storing these numbers but not the CC numbers, otherwise sites like Amazon and eBay (and many others) would require you to enter your CC number each time you make a purchase. So, as I understand it, I have to select a merchant account first and then apply a module for that account from the payment modules list to be able to process cards? I don't think this was the case with MS2.2 ..What if I just want to use a CC module to test it and different features related to it without selecting a merchant account? What I am saying is that the payment gateway was separate from the CC module and you could previously install that module and manage it without actually processing payments via a gateway. Is this no longer the case?
  11. hi, I'm not sure if this is the best page to pose this question, but this forum page has more recent posts than some of the other ones I looked at. I'm working on BS Edge with PHP7.2 and am trying to figure out what credit card payment module to install. MS2.2 had the following payment module in /includes/modules/payment/cc.php ..however, BS edge and later versions do not have this file. So, ..do I update that file and install it in BS Edge or is there a simpler Credit Card module solution? Does anyone know?
  12. Because I do not use the Navigation Bar, I cannot say whether enabling the Hamburger menu button for the Navigational Bar would affect the display position of the Categories Menu button in the Horizontal Menu. I would say, that this is likely not the case. Again, I don't know because my modified version does not include the Navigation Bar. I have the three aforementioned modules that I imported into the Horizontal Menu from the Navigation Bar and those display in both desktop and mobile. And as long as it works, that's all that matters! On a side note, always test any changes you make to your site on both desktop and mobile. I primarily use FireFox due to its security features and because it does not scrape as much of my personal info as the other browsers do (plus, its faster). However, I usually also do cross-browser testing in Chrome, MS Edge, IE, and Safari. And, Google Chrome has a feature I often use to identify issue on a page via their More Tools > Developer Tools settings menu option. There, you can view your changes on select mobile devices as well. I mention this here not just FYI, but for anyone reading through these posts who's making code changes or installing new features on their site.
  13. This is a CSS setting for that button of position:absolute; You need to find the class that controls that Categories button and change the position setting to position:relative; This should work, but may need another tweak depending on the div structure and other related CSS.
  14. Yeah, that's strange that it works without the Extra Small (XS) module for mobile. Maybe based on the BootStrap nav class? Though, that module is really easy to install. Are you sure you did not install that XS module?,.. because I thought that Categories button for the menu dropdown is part of it. Mine is completely different, .. with lots of modifications. I installed it in 10/17 so its been a while.
  15. Make sure your Categories Menu XS is enabled. Go into your admin panel Modules>Content>Categories Menu XS and make sure it is installed and enabled. If that is enabled and you are still seeing that desktop horizontal menu, go into the template for the catmenu and look at the code that follows this line if (MODULE_CONTENT_HEADER_CATMENU_XS_STATUS == 'True') { That code is what determines hiding the desktop version of the horizontal menu when the screen width is smaller than desktop. As I mentioned before, my version is modified and I actually use some of the Navigation Bar modules in my Horizontal Menu (like Account, Cart, and Checkout). Therefore, it makes it a bit more challenging for me to test or replicate issues on my end without having a fresh install of each osC version.
  16. @Kurre If you used the second CSS script I posted, then it should work. If it does not, then just use what did work for you that Andrea posted. I appreciate you testing it.
  17. this is with the adjusted CSS? ..strange, it should not be doing that. What version of osC do you have?
  18. That's ok, you probably have a newer release of this addon. The point is, just replace all of the navbar-nav classes you find in that file, if there are any. Hey, just a minor correction to the CSS code block above. I missed that the last @media call was for min-width and placed my code above it, when it should be below it. So, here is the corrected CSS for this to work properly. Use this one instead. /* BOF: Horizontal Menu Links Centered */ .navbar-nav-h-menu { margin: 7.5px -15px; } .navbar-nav-h-menu > li > a { padding-top: 10px; padding-bottom: 10px; line-height: 20px; } .navbar-nav-h-menu > li > .dropdown-menu { margin-top: 0; border-top-left-radius: 0; border-top-right-radius: 0; } .navbar-fixed-bottom .navbar-nav-h-menu > li > .dropdown-menu { margin-bottom: 0; border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-right-radius: 0; border-bottom-left-radius: 0; } .navbar-default .navbar-nav-h-menu > li > a { color: #777; } .navbar-default .navbar-nav-h-menu > li > a:hover, .navbar-default .navbar-nav-h-menu > li > a:focus { color: #333; background-color: transparent; } .navbar-default .navbar-nav-h-menu > .active > a, .navbar-default .navbar-nav-h-menu > .active > a:hover, .navbar-default .navbar-nav-h-menu > .active > a:focus { color: #555; background-color: #e7e7e7; } .navbar-default .navbar-nav-h-menu > .disabled > a, .navbar-default .navbar-nav-h-menu > .disabled > a:hover, .navbar-default .navbar-nav-h-menu > .disabled > a:focus { color: #ccc; background-color: transparent; } .navbar-default .navbar-nav-h-menu > .open > a, .navbar-default .navbar-nav-h-menu > .open > a:hover, .navbar-default .navbar-nav-h-menu > .open > a:focus { color: #555; background-color: #e7e7e7; } .navbar-inverse .navbar-nav-h-menu > li > a { color: #9d9d9d; } .navbar-inverse .navbar-nav-h-menu > li > a:hover, .navbar-inverse .navbar-nav-h-menu > li > a:focus { color: #fff; background-color: transparent; } .navbar-inverse .navbar-nav-h-menu > .active > a, .navbar-inverse .navbar-nav-h-menu > .active > a:hover, .navbar-inverse .navbar-nav-h-menu > .active > a:focus { color: #fff; background-color: #080808; } .navbar-inverse .navbar-nav-h-menu > .disabled > a, .navbar-inverse .navbar-nav-h-menu > .disabled > a:hover, .navbar-inverse .navbar-nav-h-menu > .disabled > a:focus { color: #444; background-color: transparent; } .navbar-inverse .navbar-nav-h-menu > .open > a, .navbar-inverse .navbar-nav-h-menu > .open > a:hover, .navbar-inverse .navbar-nav-h-menu > .open > a:focus { color: #fff; background-color: #080808; } @media (max-width: 767px) { .navbar-nav-h-menu .open .dropdown-menu { position: static; float: none; width: auto; margin-top: 0; background-color: transparent; border: 0; -webkit-box-shadow: none; box-shadow: none; } .navbar-nav-h-menu .open .dropdown-menu > li > a, .navbar-nav-h-menu .open .dropdown-menu .dropdown-header { padding: 5px 15px 5px 25px; } .navbar-nav-h-menu .open .dropdown-menu > li > a { line-height: 20px; } .navbar-nav-h-menu .open .dropdown-menu > li > a:hover, .navbar-nav-h-menu .open .dropdown-menu > li > a:focus { background-image: none; } .navbar-default .navbar-nav-h-menu .open .dropdown-menu > li > a { color: #777; } .navbar-default .navbar-nav-h-menu .open .dropdown-menu > li > a:hover, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > li > a:focus { color: #333; background-color: transparent; } .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .active > a, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .active > a:hover, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .active > a:focus { color: #555; background-color: #e7e7e7; } .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .disabled > a, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .disabled > a:hover, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .disabled > a:focus { color: #ccc; background-color: transparent; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .dropdown-header { border-color: #080808; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu .divider { background-color: #080808; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > li > a { color: #9d9d9d; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > li > a:hover, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > li > a:focus { color: #fff; background-color: transparent; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .active > a, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .active > a:hover, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .active > a:focus { color: #fff; background-color: #080808; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .disabled > a, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .disabled > a:hover, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .disabled > a:focus { color: #444; background-color: transparent; } } @media (min-width: 768px) { .navbar-nav-h-menu { margin: 0; } .navbar-nav-h-menu > li > a { padding-top: 15px; padding-bottom: 15px; } } /* this will center the menu links */ .navbar-nav-h-menu { width:100%; text-align:center; } .navbar-nav-h-menu > li { float:none; display:inline-block; } /* EOF: Horizontal Menu Links Centered */
  19. If you have this addon installed AND will use the Navigation Bar AND you want the Horizontal Menu to display the links centered, here are the changes to make. I put this together, but have not tested it. Therefore, I need someone to actually apply these 3 changes and let me know if this works. I searched through the last version of osC Flatline (Frozen) BootStrap CSS file to find all instances of .navbar-bar. I then combined them and changed all these .navbar-bar classes to .navbar-bar-h-menu which is going to be the new CSS class for the Horizontal Menu with centered links. That osC Flatline version is based on BootStrap 4, however, this should not affect anything if you have BS3 because this is only for the Horizontal Menu. First, back up your site files,.. as always! So that you could easily reverse these changes, if needed. Then, add the following CSS code to the end of your user.css file: /* BOF: Horizontal Menu Links Centered */ .navbar-nav-h-menu { margin: 7.5px -15px; } .navbar-nav-h-menu > li > a { padding-top: 10px; padding-bottom: 10px; line-height: 20px; } .navbar-nav-h-menu > li > .dropdown-menu { margin-top: 0; border-top-left-radius: 0; border-top-right-radius: 0; } .navbar-fixed-bottom .navbar-nav-h-menu > li > .dropdown-menu { margin-bottom: 0; border-top-left-radius: 4px; border-top-right-radius: 4px; border-bottom-right-radius: 0; border-bottom-left-radius: 0; } .navbar-default .navbar-nav-h-menu > li > a { color: #777; } .navbar-default .navbar-nav-h-menu > li > a:hover, .navbar-default .navbar-nav-h-menu > li > a:focus { color: #333; background-color: transparent; } .navbar-default .navbar-nav-h-menu > .active > a, .navbar-default .navbar-nav-h-menu > .active > a:hover, .navbar-default .navbar-nav-h-menu > .active > a:focus { color: #555; background-color: #e7e7e7; } .navbar-default .navbar-nav-h-menu > .disabled > a, .navbar-default .navbar-nav-h-menu > .disabled > a:hover, .navbar-default .navbar-nav-h-menu > .disabled > a:focus { color: #ccc; background-color: transparent; } .navbar-default .navbar-nav-h-menu > .open > a, .navbar-default .navbar-nav-h-menu > .open > a:hover, .navbar-default .navbar-nav-h-menu > .open > a:focus { color: #555; background-color: #e7e7e7; } .navbar-inverse .navbar-nav-h-menu > li > a { color: #9d9d9d; } .navbar-inverse .navbar-nav-h-menu > li > a:hover, .navbar-inverse .navbar-nav-h-menu > li > a:focus { color: #fff; background-color: transparent; } .navbar-inverse .navbar-nav-h-menu > .active > a, .navbar-inverse .navbar-nav-h-menu > .active > a:hover, .navbar-inverse .navbar-nav-h-menu > .active > a:focus { color: #fff; background-color: #080808; } .navbar-inverse .navbar-nav-h-menu > .disabled > a, .navbar-inverse .navbar-nav-h-menu > .disabled > a:hover, .navbar-inverse .navbar-nav-h-menu > .disabled > a:focus { color: #444; background-color: transparent; } .navbar-inverse .navbar-nav-h-menu > .open > a, .navbar-inverse .navbar-nav-h-menu > .open > a:hover, .navbar-inverse .navbar-nav-h-menu > .open > a:focus { color: #fff; background-color: #080808; } /* this will center the menu links */ .navbar-nav-h-menu { width:100%; text-align:center; } .navbar-nav-h-menu > li { float:none; display:inline-block; } @media (max-width: 767px) { .navbar-nav-h-menu .open .dropdown-menu { position: static; float: none; width: auto; margin-top: 0; background-color: transparent; border: 0; -webkit-box-shadow: none; box-shadow: none; } .navbar-nav-h-menu .open .dropdown-menu > li > a, .navbar-nav-h-menu .open .dropdown-menu .dropdown-header { padding: 5px 15px 5px 25px; } .navbar-nav-h-menu .open .dropdown-menu > li > a { line-height: 20px; } .navbar-nav-h-menu .open .dropdown-menu > li > a:hover, .navbar-nav-h-menu .open .dropdown-menu > li > a:focus { background-image: none; } .navbar-default .navbar-nav-h-menu .open .dropdown-menu > li > a { color: #777; } .navbar-default .navbar-nav-h-menu .open .dropdown-menu > li > a:hover, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > li > a:focus { color: #333; background-color: transparent; } .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .active > a, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .active > a:hover, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .active > a:focus { color: #555; background-color: #e7e7e7; } .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .disabled > a, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .disabled > a:hover, .navbar-default .navbar-nav-h-menu .open .dropdown-menu > .disabled > a:focus { color: #ccc; background-color: transparent; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .dropdown-header { border-color: #080808; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu .divider { background-color: #080808; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > li > a { color: #9d9d9d; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > li > a:hover, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > li > a:focus { color: #fff; background-color: transparent; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .active > a, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .active > a:hover, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .active > a:focus { color: #fff; background-color: #080808; } .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .disabled > a, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .disabled > a:hover, .navbar-inverse .navbar-nav-h-menu .open .dropdown-menu > .disabled > a:focus { color: #444; background-color: transparent; } } @media (min-width: 768px) { .navbar-nav-h-menu { float: left; margin: 0; } .navbar-nav-h-menu > li { float: left; } .navbar-nav-h-menu > li > a { padding-top: 15px; padding-bottom: 15px; } } /* EOF: Horizontal Menu Links Centered */ /includes/modules/content/header/cm_header_catmenu.php Find this line: if (empty($class)) $class = 'nav navbar-nav'; Change it to this: if (empty($class)) $class = 'nav navbar-nav-h-menu'; /includes/modules/content/header/templates/catmenu.php Find this line: echo '<ul class="nav navbar-nav"> Change it to this: echo '<ul class="nav navbar-nav-h-menu"> My module & class files are all modified for this addon, so you basically want to find any instance of navbar-nav class in the files for this addon and change them to navbar-nav-h-menu …and be sure to leave out the leading period (.) as those are mainly used in the CSS file. These changes apply to all the same attributes that the original navbar-nav class has, but they are separate from, and do not affect the Navigation Bar. Therefore, if you need to make formatting changes only to your Horizontal Menu, you should now be able to do that from this CSS block of code in the user.css file. This block of CSS code is more than required for the Horizontal Menu, however, this is as good as it gets for a quick solution. Let me know if this solution works for you.
  20. Ah,.. yeah, I do remember you mentioned that this change affects the top Navigation Bar. And hence, why the need to change the name of the classes. However, to do that (if using the Navigation Bar as well), you would need to copy and paste the entire block for .navbar-nav from the BootStrap CSS file into the user.css file. Then rename all of these classes (in the user.css file) to .navbar-nav-h-menu and then add the following code to the bottom of the user.css file (after the newly added .navbar-nav-h-menu classes). /* this will center the menu links */ .navbar-nav-h-menu { width:100%; text-align:center; } .navbar-nav-h-menu > li { float:none; display:inline-block; } Then go into the horizontal menu file and change all the navbar-nav classes to navbar-nav-h-menu and do the same in the class file for this addon (if there are any in that class file). It's a bit more involved but not difficult.
  21. Yes, I thought this was only regarding the links in the horizontal menu. I don't use the Navigation Bar, so never ventured to change those links.
  22. The classes for .nav and .navbar-nav are defined in the BootStrap css file so, changing the names of those classes removes the prior attributes assigned to them. I just added the following to my user.css file and it works as it should,... centering all the links in the horizontal menu. No need to change anything else. /* this will center the menu links */ .navbar-nav { width:100%; text-align:center; } .navbar-nav > li { float:none; display:inline-block; }
  23. No, actually I have version 2.5 ...I keep a spreadsheet of all the changes and addons I install and this is the latest one I have. That version 2.4 I got from the /admin/orders.php file top header part. I must not have updated that when moving to 2.5 Anyway, thanks Rainer. Looks like I need to just update everything to version 3.0.5 ...I just downloaded it and am on my way. Thanks again!
  24. So, I just read the compatibility and looks like version 3.0.5 is as high as I get? is that correct?
  25. Looks like version 2.4 And after looking at the addon download page the latest version is 4.0.0 ... so, I need to update. Is the latest version compatible for BS Edge or is it designed for Phoenix? ~~~~ Also, just a suggestion, ..to make the invoice link in the Order Update email clickable, as opposed to having the customer copy and paste it into a new browser window. Though you may already have that changed in the newer versions. //$link = $check_status['customers_guest'] != '1' ? EMAIL_TEXT_INVOICE_URL . ' ' . tep_catalog_href_link('account_history_info.php', 'order_id=' . $oID, 'SSL') . "\n" : ''; $link = $check_status['customers_guest'] != '1' ? EMAIL_TEXT_INVOICE_URL . ' <a href="' . tep_catalog_href_link('account_history_info.php', 'order_id=' . $oID, 'SSL') . '" target="new">' . tep_catalog_href_link('account_history_info.php', 'order_id=' . $oID, 'SSL') . '</a>' . "\n" : '';
×