ArtcoInc

@milerwan Thank you for your feedback.

@tgely As @JcMagpie pointed out, this does indeed work in Phoenix under BootStrap v4. The issues I am having seem to have to do with the changes I made when I converted it from a Header module to a NavBar module. I'm still working on those. In the mean time, I do have a question ... In your module, you have the option to "Enable Extended Store Search Functions", where it can search the product Description. The only two places in your code where I see the product Descriptions referenced are 1) In /ext/content/modules/header/store_search/content_searches.php, where you have this ... if ($r > 5) { $array[] = array('icon' => "plus-circle", 'title' => MODULE_CONTENT_HEADER_STORE_SEARCH_MORE_PRODUCT, 'href' => tep_href_link('advanced_search_result.php', 'keywords=' . urlencode(str_replace(' ', '+', $query)) . '&search_in_description=' . (MODULE_CONTENT_HEADER_STORE_SEARCH_FUNCTIONS == 'Descriptions' ? 1 : 0), $request_type), 'price' =>null); break; } else { 2) And in /includes/modules/content/header/cm_header_store_search.php, where you have this ... if (tep_not_null($description) && ($description === true)) { $search_link .= tep_draw_hidden_field('search_in_description', '1'); } Can you explain how this toggles the search function to include searching the descriptions or not? @milerwan You used the same code from above in your version of this module. When you added the option to search the Model or Key Words, you added the following check in your file /ext/modules/content/header/store_search/content_searches.php ... //Add products_head_keywords_tag search option if (MODULE_CONTENT_HEADER_STORE_SEARCH_MODEL_OR_KEYWORDS == 'Model') { $like_statement_product .= " (pd.products_name LIKE '%" . tep_db_input($product) . "%' OR p.products_model LIKE '%" . tep_db_input($product) . "%') AND "; } else { $like_statement_product .= " (pd.products_name LIKE '%" . tep_db_input($product) . "%' OR pd.products_head_keywords_tag LIKE '%" . tep_db_input($product) . "%') AND "; } In order to ensure that I was able to toggle the Description search on or off, what I ended up doing was changing the above to: //Add products_head_keywords_tag search option if (MODULE_CONTENT_HEADER_STORE_SEARCH_MODEL_OR_KEYWORDS == 'Model') { if (MODULE_CONTENT_HEADER_STORE_SEARCH_FUNCTIONS == 'Descriptions') { $like_statement_product .= " (pd.products_name LIKE '%" . tep_db_input($product) . "%' OR pd.products_description LIKE '%" . tep_db_input($product) . "%' OR p.products_model LIKE '%" . tep_db_input($product) . "%') AND "; } else { $like_statement_product .= " (pd.products_name LIKE '%" . tep_db_input($product) . "%' OR p.products_model LIKE '%" . tep_db_input($product) . "%') AND "; } } else { if (MODULE_CONTENT_HEADER_STORE_SEARCH_FUNCTIONS == 'Descriptions') { $like_statement_product .= " (pd.products_name LIKE '%" . tep_db_input($product) . "%' OR pd.products_description LIKE '%" . tep_db_input($product) . "%' OR pd.products_head_keywords_tag LIKE '%" . tep_db_input($product) . "%') AND "; } else { $like_statement_product .= " (pd.products_name LIKE '%" . tep_db_input($product) . "%' OR pd.products_head_keywords_tag LIKE '%" . tep_db_input($product) . "%') AND "; } } It's a bit messy, but it does ensure that the Search in the Description function is toggleable . Malcolm

@JcMagpie Thank you for the offer. I had converted the original search add-on to a NavBar module, instead of a Header module. That's what I'm trying to work with. M

@JcMagpie I tried installing the add-on into Phoenix, and while it does create the drop-down, I am having issues ... After a clean page refresh, when I first click into the search box, the cursor does not blink at the beginning of the search field. If I move my mouse pointer over the magnifying glass, the blinking cursor appears. When I move the mouse pointer off of the magnifying glass, the blinking cursor disappears. If I click on another tab in my browser (Firefox), then click back on the tab with the Phoenix page, the blinking cursor appears. When I start typing in the search box, IF the blinking cursor is NOT blinking, the letters I type do not show up (initially). The drop-down box DOES drop down, and the suggestions are shown. Now, this may just be an issue with the WAMP server I am testing this on. I don't know ... <shrug>

For osC versions up to Frozen, I have been using an add-on that uses the typeahead feature using a file called bootstrap3-typeahead.min.js. Now, working with Phoenix, I need to find a version of this file that works with Bootstrap v4. I have tried to install the existing BS3 add-on into Phoenix, and it sort of functions, but some things are missing. A Google search did not come up with a ready-made version of this file for BS4. I know NOTHING about javascript. Can anyone point me towards a solution? (I have asked the author of the original add-on for assistance, but his focus is currently elsewhere) TIA Malcolm

@pete2007 Which version of osC? The 'official' version, or the Community Edition? In either case, v2.3.4 is a bit old. M

@tgely Is there any chance that you will be updating this to BootStrap v4, to be used in the latest Phoenix release of osC? In this add-on, you have a file called bootstrap3-typeahead.min.js. I have concerns of how this will work under the new Bootstrap v4. TIA Malcolm

@Jack_mcs I had considered that too. The screen shot above was from early in my testing. Afterwards, I did indeed add an image to the second category. No change ... *** HOWEVER *** This works! You may wish to include this in your next update of this module. Thank you! M (and yes, I am still working on making everything look 'pretty' with CSS) *** UPDATE *** To make this work, I needed to apply the code edit above *AND* the New Equal Height Module. If I turned the Equal Height Module off (after applying the code edits), the boxes revert back to different sizes. HTH

@Jack_mcs Thank you for your contribution! I have just installed your new version into Phoenix. (please ignore the colors, background texture, and other CSS changes) In your Install_Readme.txt file, you state: 5 - If the boxes are not aligned properly and you are using a Bootstrap shop, you may need to install this addon: https://apps.oscommerce.com/2G1Sc&new-equal-height-module-bootstrap I have installed it. As you can see from the screen shot above, it had no effect. Do you have any suggestions for getting these boxes equal height in Phoenix? Thanks in advance! Malcolm

@zefeena The add-on that @bonbec linked to in the 2nd post in this tread allows you to go into and out of maintenance mode through Admin. It will backup .htacces file and create a new one automatically when you go into maintenance mode. When reverting back to online mode, it restores your original .htaccess file. I do not see many (if any) core file changes in it. (I do not use this add-on. I actually use a much older add-on, which did modify core files. Apparently, the one listed above was inspired by the older one I am using.) Also, @burt created a Maintenance Mode module in one of his earlier 28-day bundles (2016-#18). HTH M

@weser As @raiwa recommended, your best bet is to upgrade to the latest Community Edition of osCommerce. The version you are currently running (v2.3.3.4) is quite old. It is not an in-place upgrade ... you basically install it fresh into a different directory, migrate your data over, and add any styling and/or add-ons you want. If this all sounds too much for you, you can post an RFQ in the commercial support area in this forum to have someone do it for you. M PS: Who set up your shop the first time?

@Jack_mcs

@kennyk Which OSC BS version? DO NOT go by the version number. What is the date on the original ZIP package? Or, if not available, what is the date on any unaltered/untouched file? M

@coelroy (At the risk of repeating myself ...) Which OSC BS version? Don't go by the version number. What is the date on the original ZIP package? M

@241 If line 3 'ENABLE_SSL' is true, than line 1 needs to change 'http:// ... ' to 'https:// ... ' (add the S to https) M