ArtcoInc

Table names are now hard-coded. Change : $check_query = tep_db_query ("select zone_id from " . TABLE_ZONES_TO_GEO_ZONES . " where geo_zone_id = '" . MODULE_SHIPPING_FEDEX_WEB_SERVICES_ZONE . "' and zone_country_id = '" . $order->delivery['country']['id'] . "' order by zone_id"); to $check_query = tep_db_query ("select zone_id from zones_to_geo_zones where geo_zone_id = '" . MODULE_SHIPPING_FEDEX_WEB_SERVICES_ZONE . "' and zone_country_id = '" . $order->delivery['country']['id'] . "' order by zone_id"); ie: changing " . TABLE_ZONES_TO_GEO_ZONES . " to zones_to_geo_zones . M

Please note that the original post was 5 years ago. What else has changed in the osC code since then? M

Admin -> Modules -> Dashboard -> Select 'Last Certified Add-Ons' -> Edit -> Set 'Enable' to False

@TomB01 Typical convention uses the table name to come up the the 'arbitrary' character(s). So, the table 'products' would use the letter 'p', the table 'products_description' would use the letters 'pd', etc. Malcolm

While the SQL 'select' statement is written as one long sentence, I like to format it into several lines, making it easier for me to read. So, I'll format it like this: select p.products_id, pd.products_name, pd.products_description, p.products_model, p.products_quantity, p.products_image, pd.products_url, p.products_price, p.products_tax_class_id, p.products_date_added, p.products_date_available, p.manufacturers_id, p.products_gtin from products p, products_description pd where p.products_status = '1' and p.products_id = '1637' and pd.products_id = p.products_id and pd.language_id = '3' This breaks the 'select' statement into its three components: Select .... this lists the fields it wants to select. From .... this lists the tables in which to find the fields. Note that the table names are followed by a letter or two. This is the same letter preceding the fields in the Select list, letting the Select command know which table the field is in Where .... this lists the conditions for the search. Only select the records if these conditions are true. And, as @TomB01 pointed out, there error is saying that the Select function is asking for a field that does not exist in the appropriate table. HTH Malcolm

@puggybelle All of the Community Editions were called that. As you suggested, sometimes the folder date may reflect the date you downloaded. However, all of the files within the folder should all have the same date. Regardless, with a date of May 2018, this was before the release of Frozen, which was released in August 2018. @ecartz explained it well. Malcolm

@spacegremlin As has been said before, the Community Edition did not have an accurate version numbering system, so there is often confusion as to which version a shop may be using. When Burt started this project back in 2014, osC was at version 2.3.3.4. So, the Community Edition, all through its early development, was also v2.3.3.4. Every release of the Community Edition during these early times was called v2.3.3.4. When osC upgraded to v2.3.4, Burt brought the Community Edition code base up to the v2.3.4 code base, and the Community Edition became (and stayed at) v2.3.4 while further development was happening. In January 2015, Burt released the 'Gold' fixed release. Development still continued, with every release still being called v2.3.4. When osC had the v2.3.4.1 Hot Patch applied, Burt also applied the Hot Patch, and the Community Edition was bumped up to v2.3.4.1. Once again, development continued, with every new release still being called v2.3.4.1. Burt released the 'Frozen' fixed release in August 2018. No additional development is being done on 'Frozen'. Some bugs have been identified in 'Frozen', and there is a thread on the forum identifying them (and some fixes too). At lease one member here is maintaining a patch file of these fixes needed for 'Frozen'. Development still continues (usually called 'Edge', although that is not a fixed release), and the version number is *still* v2.3.4.1. Some significant changes have been made since 'Frozen' (such as the 'upgrade' from BootStrap v3 to v4), causing some compatibility issues with prior versions, and many (most?) add-ons out there. So, there is no one 'Edge' version. Releases prior to 'Frozen' could technically be called 'Edge', and every release since 'Frozen' is also technically 'Edge'. A release of 'Edge' from a month ago may not (and probably is not) the same as 'Edge' today. Also, there is no 'Frozen' BS4. All changes to upgrade to BootStrap v4 came *after* the release of 'Frozen'. In July of 2019, the 'Phoenix' edition was released. As of this writing, Phoenix is the latest release, now with a consistent version numbering system in place. This numbering system does not relate to the 'official' osC numbering in any way. So, the only real way to know what version you are running is to look at the date of the original ZIP file that held your original osC code. HTH Malcolm

@Smoky Barnable Back in 2016, @burt made a 'Fuzzy Search' module in his 28 days bundle. It might help. One other thought is to integrate the Google search function into your shop. I have seen that used before. HTH Malcolm

@puggybelle @Dan Cole While I was trying to install a different TypeAhead search module, I too had the same issues that both you and Dan reported. You can start reading about them here: I was getting different results on my in-house development server and my 'live' public server. I was getting different results with different browsers. I asked different people to test the public server, and different people experienced different results. I never determined what was causing the problem. I wish I had better news ... Malcolm

@SCM Minis Seems to be working now ....

@rossosiya I realize you are new here, so I'll just point out that you are answering a thread that happened 14 years ago. M

@DAVID3733 IIRC, any changes to httpd.conf requires a restart of Apache. Is this something you really want to do in a production environment, especially if you are on a shared server? M

12/31/2999 ?

@DAVID3733 Did you stop and restart Apache?

@TomB01 (and the line or two following this) M