Latest News: (loading..)


  • Content count

  • Joined

  • Last visited

  • Days Won


raiwa last won the day on June 22

raiwa had the most liked content!

Profile Information

  • Real Name
    Rainer Schmied
  • Gender
  • Location
    Sant Iscle de Vallalta, Barcelona, Spain
  • Website

Recent Profile Visitors

33,731 profile views
  1. @PiLLaO, Gustavo here is the promised universal version which should do it for both: Sloppy Words Cleaner 3.0 BS -
  2. I uploaded 2 versions, the first one for older stores using $HTTP_POST_VARS and a second one for newer stores using $_POST. I'm working on a universal version which will do it for both. Please use the correct one for now.
  3. Gustavo you should first recover unmodified files. if you have the older sloppy words cleaner modifications in place remove them Use the correct version for your store and try again with new unmodified files.
  4. @PiLLaO, Gustavo, do you have the file "account_pwa.php" in your store?
  5. Just found a bug for the installation if it's the newest 2.3.4 EDGE version with $_POST. Please use this one if your EDGE is new and uses superglobals: Sloppy Words Cleaner 3.0 BS_$
  6. Lets try again: Sloppy Words Cleaner 3.0 This one seems to be ok only for older EDGE versions using $HTTP_POST_VARS
  7. Hello, Following up the thread about the new updated BS version: sloppy words cleaner header tag versus hook I have now prepared a beta test version which solves all the examples posted there by gary and frankl. It is hooked and all settings, functions and installation scripts are packed into a store module. The minimal no invasive core file changes are automatic done on store moduel installation. @burt, @frankl, @14steve14, @Mort-lemur, @PiLLaO and others, If you have a time and interest, there are 2 ways of testing: 1. on my demo store: demo account: user:demo passw: demodemo play in account/address book: 2. download the beta package and install on any 2.3.4 EDGE Easiest installation: copy all files in "upload" folder install: admin -> modules -> store -> Sloppy Words Cleaner NOTE: No file changes, hook register and call is auto added to relevant files on module installation and removed on module uninstall:-) See the included provisional doc "check_report" for detailed info. No instructions included for now. Some observations and known flaws: Firstname: MACDONALD -> Macdonald Firstname: macdonald -> Macdonald Surname: MACDONALD -> MacDonald Surname: macdonald -> MacDonald Surname: Macdonald -> Macdonald => correct spell match first letter upper all other lower -> no conversion. It’s supposed, knowing about his exceptional spelling, a “Macdonald” will take care to type his surname correct. Surname: DE QUINCEY -> de Quincey Note: "de" is in the all lower list, De Quincey needs to be added to the exception list It’s supposed, knowing about his exceptional spelling, a “De Quincey” will take care to type his surname correct. Surname: degennaro -> DeGennaro Note: several of these italian names are added to Word conversión list, adding to prefix list would break other all lower conversions like “der, die” and other terms beginning with “De, Di” Surname: lavecchia -> LaVecchia Note: Same problem like for Macdonald/MacDonald, both variants exist: Laveccia/LaVecchia Thank you for your time rgds Rainer Sloppy Words Cleaner 3.0
  8. I meant to combine (add the modifications) of the qtpro cart function to the core cart function, not to add. I checked now and the only difference is this: $attributes_query = tep_db_query("select popt.products_options_name, popt.products_options_track_stock, poval.products_options_values_name, pa.options_values_price, pa.price_prefix from " . TABLE_PRODUCTS_OPTIONS . " popt, " . TABLE_PRODUCTS_OPTIONS_VALUES . " poval, " . TABLE_PRODUCTS_ATTRIBUTES . " pa where pa.products_id = '" . (int)$products[$i]['id'] . "' and pa.options_id = '" . (int)$option . "' and pa.options_id = popt.products_options_id and pa.options_values_id = '" . (int)$value . "' and pa.options_values_id = poval.products_options_values_id and popt.language_id = '" . (int)$languages_id . "' and poval.language_id = '" . (int)$languages_id . "'"); $attributes = tep_db_fetch_array($attributes_query); $this->products[$index]['attributes'][$subindex] = array('option' => $attributes['products_options_name'], 'value' => $attributes['products_options_values_name'], 'option_id' => $option, 'value_id' => $value, 'prefix' => $attributes['price_prefix'], 'price' => $attributes['options_values_price'], 'track_stock' => $attributes['products_options_track_stock']); "products_options_track_stock" is added to the $attributes_query and the array. If you apply this modification to your core order class and remove the qtpro_order instance, all should work correct. I remember now, this is only needed to restock the attribute stock if an order is deleted in admin, it is not needed for the order stock substraction of attributes, sorry.
  9. for now you could try to merge the modifications made in the order_qtpro.php class into the core order class and remove all instances of: require('includes/classes/order_qtpro.php'); $order = new order_qtpro; When I have a time I'll have a deeper look. Maybe it's because your payment service manipulates the core order class. Which was the exact payment service where it happens?
  10. @jampjamp, the importance of this is the stock substraction for qtpro stock controlled attributes. It would be important to know if you modified the core order class: includes/classes/order.php, if yes, you should replicate your modifications into the order_qtpro.php class
  11. @jampjamp If it works on a unmodified store, you'll have to search for the modification which breaks the code. Go with patience step by step adding relevant modified files/modifications to the clear store installation to isolate the reason of the break. I have no better advice not knowing what you modified. rgds Rainer
  12. @HowardR, These are no bugs. Filenames and Paths are now hardcoded in 2.3.4 Bootstrap and most path definitions in configure.php and the file filenames.php with the filename definitions have been removed. So you are going the wrong way, instead to re-add the definitions to configure.php, you should update the add-ons which have not yet been updated. To get older Add-Ons which are still using filename and path constants to work, you have 2 possibilities: 1. Update all filename constants in the add-on files from Example: FILENAME_DEFAULT to the real filenames Example: 'index.php' Update all path constants in the add-on files from Example: require(DIR_WS_INCLUDES . 'database_tables.php'); to the real path: require('includes/database_tables.php'); or 2. Install the compatibility add-on: Add-On Compatibility for 2.3.4 EDGE 1 is the preferred method Please Google or search the forum about these subjects. You'll find many posts for clearance. rgds Rainer
  13. @14steve14 Thanks Steve, the big minus for header tag is that it loads after the data is already processed and entered in the database: So my idea was now to use hook together with a custom group module "store" which I already use in several other add ons. It would allow to integrate an installation process which can add the few lines of additional code, (hook register and calls) in the related core files. On uninstall theses mods can be also auto removed. This is actually what is planned for the future 2.4 Apps to do. This "store" module can also hold all the configuration entries, exception arrays etc. rgds Rainer
  14. Just to remind: this topic is header tag versus hook for the new modularized version If you wish to see what the existing add-on already does, you are invited to download it and try: Sloppy Words Cleaner