Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by raiwa

  1. As I do not know which PWA version you are using, it's difficult to give exact advice. If you remove the hook call in checkout_procerss.php, the order confirmation e-mail will not be modified and still contain the link to the order in the customers account. This doesn't make sense for guest orders. If you are using PWA 3 series, the hook call is that one you posted. For the 2.x series the hook call is different. Please use the version for your store and follow exactly the instructions. Your other modifications are up to you. I'm sure that everything works correct in a correct installation for the correct version. Please consider that PWA is out since years and used in many shops. No one reported the problems you have until now. It makes sense to keep the guest orders flagged even the customer opts in to create a regular account. Shop owners like to keep track on which orders have been made with gueat checkout. This modification is up to you.
  2. This not normal. You probably have a problem withyour sessions. The other errors may be subsequent errors.
  3. I mean check if you did the installation correct and complete. Check if your sessions work correct and if your config files are correct. If you have other modifications in the relevant pages, switch them temporary off/ remove the code to be sure nothing else interferes. I can’t give more or more specific advice as I do not know what else you have modified/ added in your store.
  4. Please recheck your installation. It works fine in my develop/test-store.
  5. Please, neither this is a general support forum for your problem. This is for the PWA add-on. Please openm a new thread for your problem in the general support section for your store version.
  6. Hello @Mirko89, which exact OsCommerce version are you using.
  7. Please post this question in a general support thread. This is not related to Discount Codes.
  8. Hello @edo.script, PWA series 3.x is intended for BS CE FROZEN. All instructions, files and references are for this version only. If your store version is a previous EDGE version, you need to know how hooks work and to be able to adapt the instructions/code references to your store. Otherwise please use the last series 2 version ( Purchase without account BS 2.5r2 ) The most important difference in FROZEN is that hooks registry is done automatically in application_top.php. But you do not need to adit this file in any PWA version. Tht's whi it is not included in the package and there is no need for it. If your store version is previous you need to add the hook registry manually like I posted befor to the page files where hooks are used. The modification in the instructions are the hook call which is the second part you need to get the hook working. Please understand that it is impossible to include accurate instructions for all BS CE versions which are out there. There are hundreds of them. The latest versions of my add ons are all for FROZEN which is the recommended actual and stable version for users which are not skilled in coding.
  9. In bm_category.php use: $category_titel = $OSCOM_CategoryTree->getData($current_category_id, 'name'); You just have to add a check if $current_category_id is not empty or zero and use MODULE_BOXES_CATEGORIES_BOX_TITLE for that case.
  10. raiwa

    Hack attempt - is there a way to prevent this?

    I guess this input example has been cleaned with: tep_db_prepare_input: function tep_db_prepare_input($string) { if (is_string($string)) { return trim(tep_sanitize_string(stripslashes($string))); } elseif (is_array($string)) { foreach($string as $key => $value) { $string[$key] = tep_db_prepare_input($value); } return $string; } else { return $string; } } which uses tep_sanitize_string: function tep_sanitize_string($string) { $patterns = array ('/ +/','/[<>]/'); $replace = array (' ', '_'); return preg_replace($patterns, $replace, trim($string)); } If it is enough I do not know neither.
  11. raiwa

    Hack attempt - is there a way to prevent this?

    malicious/problematic code has already been filtered out in this example: Bob Smith"__sCRiPt sRC=//jb.gy/i__/sC 244 Whatever St"__sCRiPt sRC=//jb.gy/i__/sCrIpT_
  12. Hello Ros @Rosyweb, In the category box module you can pass a fixed root category to the category class like this (example for root category 1): $OSCOM_CategoryTree->setRootCategoryID(1); or you can pass the actual category id as root category id. So the category box will dynamically show only the subcategories of the actual category: $OSCOM_CategoryTree->setRootCategoryID((int)$current_category_id); in this case you need to add $current_category_id to the globals list of the module: global $oscTemplate, $cPath, $current_category_id;
  13. Hello Ed @edo.script, Point 1: It looks like you tried to install/update PWA 3.0.5 over the old GOLD version from @De Dokta. It also seems you are mixing code provided from older PWA 2.x versions with PWA 3.0.5. The code you mention under point 1 is not used any more in PWA 3.0.5. Please complete uninstall your old PWA version before installing PWA 3.0.5, there are no update instructions available for that old version. For the hook call in checkout_process.php: $OSCOM_Hooks->call('pwa', 'PwaCheckoutMailMod');) . This is from an older PWA 2.x version. Please do not try to mix code from older version. Use only the coding provided in PWA 3.0.5. PWA 3.0.5 is for FROZEN BS which includes the hook call in application_top.php at the very end: $OSCOM_Hooks->register(basename($PHP_SELF, '.php')); Only if you do not have this in application_top.php you need to add to checkout_process.php: $OSCOM_Hooks->call('checkout_process', 'PwaCheckoutMailMod'); Observe that the "echo" you have in front is totally wrong. Point 2: Redo your installation like explained before. Make sure that you have the Header Tag module and the checkout_success content module correct installed.
  14. I remember a thread where this was discussed for the PHP7 update of EDGE with @BrockleyJohn but can't find it any more. He developed and tested the class constructer name updates in EDGE. Maybe he can explain the reasons better. I only remember that without this trick (there are also just empty class constructors used in some classes) function not found errors were thrown and his solution solved them.
  15. It is required where done like this. Otherwise the function "Glotz" if called from outside will not be found, just like you say.
  16. New coded content module for Bootstrap. This add-on is based on the idea of the older Holiday Message Add-Ons by fimble: http://addons.oscommerce.com/info/7648 http://addons.oscommerce.com/info/6127 It has been complete new written for BS. Easiest install: upload 2 files+language file. Install content header module in Admin. Message Header and Text can be introduced for each language in the content module set-up. Selectable pages where to show the modue. Download: http://addons.oscommerce.com/info/9331
  17. Updated to Holiday-Promotional Message 2.1.2 BS Changes version 2.1.2: - added additional fix in admin/modules_content.php to prevent escape backslash for sql sensitive special characters to be duplicated when edited. Changes version 2.1.1: - reverted wrong fix introduced in 2.1. - applied correct fix in admin/modules_content.php to allow sql sensitive special characters like single quote (apostrophe) in Text definitions.
  18. This could be achieved with javascript. But it's much easier to just show the $ sign permanent outside before the inputfield. <?php  echo '$ ' . tep_draw_input_field('enquiry', '', 0, 1, NULL, 'required aria-required="true" maxlength="6" id="inputEnquiry" placeholder="' . ENTRY_OFFER_TEXT . '"'); echo FORM_REQUIRED_INPUT; ?> shipping not included </div>
  19. Constant in text definition is: MODULE_NAVBAR_ABOUTUS_PUBLIC_TEXT Constant in template is: MODULE_NAVBAR_ABOUT_US_PUBLIC_TEXT Hope you see the difference.😉
  20. Make sure to include the variable which holds the product id in the globals list of your module. In your case it should be $printlist.
  21. raiwa

    QTPro BS

    QTPro BS 5.0 I'm working on a new version based on QTpro for osc 2.3 version 4.6.1 plus newer updates and fixes. Planned Changes: coding updates for latest 2.3.4 BS EDGE Community version with hardcoded filenames, database table names, paths and superglobals content modules for product info, shopping cart hooked modifications or separate functions where possible to avoid core file changes (stock checks etc in checkout pages) final product prices shown in option/attribute combinations on product info page also for more than one option/combinations general code clean up language constants/definitions for all texts for full multilanguage support To do list: update qtprodoctor.php hardcoded stuff, superglobals language constants/definitions update stats_low_stock_attrib.php hardcoded stuff, superglobals language constants/definitions update stock.php hardcoded stuff, superglobals language constants/definitions replace mods in admin/boxes/tools.php by separate file replace mods in admin/boxes/reports.php by separate file avoid mods in admin/includes/functions/general.php load function file in modules replace core function mods by own functions? modularize product info options modularize product info stock table versions for Modular Product Page by kymation alternative product listing module for modularized shopping cart order class extension to avoid mods in core order class replace all mods in checkout files by hooks? check compatibility with ajax attribute manager add support for attribute sort order update instructions It would be great if there appear testers for the mods. Who has the old version already installed: - replace the admin files - upload and install the product info content modules and (IMPORTANT!) uncomment the complete options/attributes section in product_info.php For new installations: - instructions are not updated yet follow the old instructions except A.: don't modify admin/includes/boxes/tools.php and reports.php, upload the nwe files instead B.: upload and install the product info content modules and (IMPORTANT!) uncomment the complete options/attributes section in product_info.php instead to apply the mods Most important for now are the changes in the product info option modules to show final prices according to the option selection even if there are muliple option combinations (single drop down and single radios) GitHub repository Thanks and best regards Rainer
  22. YEs, or maybe using a external payment service like PayPal standard he didn't come back to your store after payment and the account didn't get auto deleted on checkout success page. So in these cases you can identify guest accounts and delete them yourself in admin if you wish.
  23. Hello Peter, If you are using the BS Community version you do not need javascript. You can use the Bootstrap built in Modal Popup: https://getbootstrap.com/docs/4.0/components/modal/ This link is for BS4 but it's also available for BS3 OK it uses also javascript buit can be triggered with simple css/html code.
  24. raiwa

    QTPro BS

    Hello Fredrik @redrum, First of all to say that I didn't write the contribution from the beginning. I only updated and adapted it to the BS Community edition and higher PHP versions. I didn't digg into these functions until now, but tried to follow up how it works. If you check the mentioned functions, you'll see that they use "qtpro_product_exists". Which checks if the product whos id is stored in the stock table still exists. If you delete a product and don't remove the options/attributes of the product, the stock entry still is in the stock table even the asociated product has been removed. This produces that error message. When I find some time I'll research further how to avoid it. Best regards Rainer