omulec

Force cookies in you admin and the osCsid session ID will disappear from the urls. Regards Szymon

Hi there. I've installed USU5 and was happy with it. Working really nice and smooth. After setting the page I started the test of all functions and I've noticed that I have some small problem during the checkout with addresses. I can use multiple defined, I can add and delete. When I want to edit however I receive: The line 103 from database.php is the return line in the following function function tep_db_num_rows($db_query) { return mysql_num_rows($db_query); } The line 50 from general.php is header('Location: ' . $url); as the part of the USU5 function function tep_redirect($url) { if ( (strstr($url, "\n") != false) || (strstr($url, "\r") != false) ) { tep_redirect(tep_href_link(FILENAME_DEFAULT, '', 'NONSSL', false)); } if ( (ENABLE_SSL == true) && (getenv('HTTPS') == 'on') ) { // We are loading an SSL page if (substr($url, 0, strlen(HTTP_SERVER)) == HTTP_SERVER) { // NONSSL url $url = HTTPS_SERVER . substr($url, strlen(HTTP_SERVER)); // Change it to SSL } } if ( false !== strpos($url, '&') ){ $url = str_replace('&', '&', $url); } session_write_close(); header('Location: ' . $url); exit; } Any hint what can be messed up? Error in the code or some error change in the database? Regards Szymon

Dear All, I've checked a lot of modules and solutions, unfortunately I didn't find a configuration that fits. Probably is a general issue for all the shops. As some local shops, I would like to have few options for customer - pick up in the store, local delivery and courier. Self pick up is existing and it's out of the discussion. Local delivery can be found or created out of some existing, but I need to have it active only for defined city (not post codes as there is over 100 post codes in my city). Courier is existing with it's own tracking. On top of that I will use ship2pay module to show selected payments for chosen shipping method. 1) Most of the modules create the cost table related to weight. I would like however to offer free delivery for local and courier option related to a order total cost. I don't need weight restriction, so anyone would advise which code is responsible for that or suggestion how to modify that? 2) I would like to restrict local delivery to my city, so I was trying to play with the zones (countries, zones, tax zones). I can restrict the shipping zone to one of the defined tax zones that I set up related to defined zones. But I don't have any clue how the address can be related to such zone. Once registering the user have to fill some address fields that come to my mind (Suburb, Post-code, City, State/Province) but it seems that no one of those is related to a definition of the zones. Any hint on this? Any hints on the above appreciated. Regards Szymon

Thanks Jim, after uploading that product_filter.php the last part, the front-end filter started with the results. Thanks for the work on this, and for the help. I understood the filters section in admin as I told you, once I realized that it must be related strictly to a specification values added if it's possible to add few "filters". The other way it would be a nonsense to have possibility to define few filters in one specification. And don't get me wrong, I just think that for new users the section on the right side in admin when you click add new filter or you edit existing somewhere around the filed where you input the filter should have some comment under explaining that the field should contain the filter values related to values defined for the specification: extact specification if defined value is exact, range of values if defined value is ranged, etc. Or at least the field itself should be called rather Filter Value instead of Filter. BTW - as still there are missing definitions in the files I see in this section when adding new filter or editing one the 3 buttons - Save, Cancel and IMAGE_SORT. What is supposed to do with IMAGE_SORT? It returns the list of filters in the specification, the same way as Cancel button do. You said that you are just working on a v 1.2, but at this moment I have a working package that with your help we tuned here. If to the files that you uploaded to http://kymation.com/pub/products_specifications_1_1_2.tar.gz you will add the missing </div> in catalog/includes/modules/product_listing.php and the catalog/includes/languages/english/products_filter.php it can be a working v 1.1 for noobs like me ;) Again, thanks for this great contribution and work spent on developing and supporting. If you would like to have one to test a little v 1.2, I volunteer.

Jack, do you mean this?: If so, I'm not a coder, or sql professional - does it mean that I should delete this empty row once selected from the table? If so, why it's not corrected simply in original sql update file? Kind regards Szymon

Ok, starting with the top: There is one group of specifications at the moment. Inside there is one specification at this moment with settings: Filter Class: exact, Display the Filter as: pulldown, Filter Show All: True, Enter Specification Values as: pulldown. Its active to be visible in comparison, product info page and in filter. This Specification has 2 values added, both applied to some products. There are two filters defined, one of them has the same name as the specification (not the same as the specification defined values). Now, after your questions I had some thought about those filters. I applied the second filter to this specification just to see what will happen on the front-end. But now I realized that probably each filter is rather a "value to be filtered" so I renamed filters into the same names as the specification values that I've added, and they became active. I think that this should be better described in documentation or in the filters section in admin, not to create the misunderstanding. So, the filter became active now, and let's go to a next step as I managed to select a value to filter the product listing. Now it's displaying: I've checked the original archive with the contribution as well as the updates you linked in this thread. There is no product_filter.php in catalog/includes/languages/english, so probably the sript is missing some definitions that should be in this file. Regards Szymon

Filter class exact, display as pulldown. I added some products with selected specification values that were defined previously in the specifications, because maybe you misunderstood me before. When you click on the pulldown it's showing only inactive names of the filters, no values.

I suppose that you are talking about assigning them inside a specification in filter section. I defined the values to a specification and than added to products, but I just don't know where to assign a value to the filter. There is just one mysterious button once I edit a filter close to "save" and "cancel" but due to definitions it's called "IMAGE_SORT", but even if I hit it nothing happens in theory. I've checked the manual and I don't see any explanation where to assign them too. Regards Szymon

Jim, As far as formatting of front end is fine and it's listing the products now without any problems as well as admin side works, there is a problem with filters enabled by default. They appear in the right places and look good, but they are inactive. The drop-down have just the default field "Show all" and once clicked only one additional and inactive named the same as the specification/filter. The values to be selected even if defined properly in admin and added properly to products doesn't appear as a list of a drop-down. Any hint on this? Regards Szymon

Dear Jack, As for test 1.57_6 installed on top of stock OSC 2.3.1. with Header Tags SEO V 3.2.6. The addon appears in admin, it's possible to define authors and configure it. Trying to enter topics/articles however returns the error: As alexnut mentioned I've changed the database engine from MyISAM to InnoDB, but it doesn't fix it. And it's not a fault of any modification of your code as I've used DOT files for both contributions. Any ideas? Regards Szymon

Ok, as nobody helped, I managed to spend an evening to learn more about PHP and I've found a solution by myself. The idea was to have the filter drop-downs not as a vertical list with the name of each drop down above it, but to compose it in a nice horizontal line side by side with the name of the drop down filter inside it as a default not filtered. To make it you need to: 1) Open index.php and to change line: echo sprintf(TEXT_RESTRICT_TO, $e['label'], tep_draw_pull_down_menu($e['field'], tep_build_epf_pulldown($e['id'], $languages_id, array(array('id' => '', 'text' => TEXT_ANY_VALUE))),'', 'onchange="this.form.submit()"')) . '<br />'; with echo sprintf(TEXT_RESTRICT_TO, '', tep_draw_pull_down_menu($e['field'], tep_build_epf_pulldown($e['id'], $languages_id, array(array('id' => '', 'text' => $e['label']))),'', 'onchange="this.form.submit()"')) . ' '; 2) Open all your main language files (here example of default english) /includes/languages/english.php and change the line: define('TEXT_RESTRICT_TO', 'Select <b>%s</b> : %s'); with define('TEXT_RESTRICT_TO', '<b>%s</b>%s'); Those mdoification change only the code added with EPF.

Is there anyway to change the look of the filter on product listing page from this vertical to nice horizontal, where the description if above the drop down? I have been looking into the code to think about it, but for me as a noob it's quite impossible. The code looks like it's general self repeating creation of drop down if they exist. This way I don't have any clue how I can position the drop downs... If my feeling is right, the piece responsible for that is in product_listing.php: // begin extra product fields $extra = ''; foreach ($epf as $e) { if ($e['listing']) { $mt = ($e['uses_list'] && !$e['multi_select'] ? ($listing[$e['field']] == 0) : !tep_not_null($listing[$e['field']])); if (!$mt) { // only list fields that aren't empty $extra .= '<br><b>' . $e['label'] . ': </b>'; if ($e['uses_list']) { if ($e['multi_select']) { $epf_values = explode('|', trim($listing[$e['field']], '|')); $epf_string = ''; foreach ($epf_values as $v) { $epf_string .= tep_get_extra_field_list_value($v) . ', '; } $extra .= trim($epf_string, ', '); } else { $extra .= tep_get_extra_field_list_value($listing[$e['field']],$e['show_chain'] == 1); } } else { $extra .= $listing[$e['field']]; } } } } // end extra product fields Anyone did this?

Thanks Jim, formatting came back to normal ;) Regards Szymon

Thanks Jim for such extensive service on this. And sorry for being such pain in the ass as a tester ;P At this moment the fix of product_listing.php changes the situation in the way that the product list is already displayed, however the formatting still goes in the way prtscr'ned in my first post. The only thing that comes to my mind is that the css is loosing it's ability to fit both columns and main content in the limited space. I may be wrong, but I have a feeling that the main content because of some strange reason becomes too wide loading product_listing.php and both columns being position related drop down-left...

Jim, Thanks for the update. Right now the definitions on the admin side are corrected in some places. I'm not a coder so I don't know if it's relevant, but once adding a new product to a category (doesn't matter if any specification is applied to that category or not) at the bottom of new product page there is still a piece of the code, which may be important: jQuery(document).ready(function () {$('#products_date_available').datepicker({ dateFormat: 'yy-mm-dd' });}); From the front-end the main page still loose it's formatting once you click on any category and doesn't display any existing products on the listing.

Don't be, I'm just still not sure which product page version do I have - I suppose from what did you say that standard tabbed. Again Jim, as you said the issues in admin are cosmetic, cause I confirm that Product specifications work there. The serious issue is with the front-end, so if you will have any questions regarding the install I still keep on the server. If you would prefer the access to ftp or sql to watch for that strange behavior live, PM me. Regards Szymon

Thanks Jim I suppose that standard. In the way that the one that is default with fresh osc once installed if you are asking if there was some contribution with alternate product page. I don't see anywhere in standard osc any option to switch the product page to an alternate too, so I suppose standard ;) But define tabbed (standard) better and lets see Regards Szymon

Hi Jim and thanks for the work on this. I just downloaded and installed, however it seems there is some small issue with the code. I performed the install on a fresh osc install to double check eliminating my mistakes in modifying my already modified shop. Fresh osc, fresh sql database, fresh drop-on-top of the contribution, no anything else modified. The thing is visible in the admin, even if from functional point of view it seems to be working - you can add all steps for specifications as well as the categories and products. I marked with red rectangles where I see the issues. Once the specification group is created and the Filters in Specification display a code in a button: See the picture In Categories section you can see more of that: See the picture Once adding the product: See the picture Now, front-end with installed specifications was still looking fine, but once I added specification, linked them with categories and added their values to products, the front-end format went wrong. More the categories box displays number of products added, but the products are not displayed. See the picture Again, maybe is some small issue with the code, or some issue with my server (I don't know). The platform I used was: Pure osc 2.3.1 from here Database: localhost Server OS: Linux 2.6.18-238.9.1.el5 Database: localhost @ MySQL 5.1.57-rel12.8 with utf8 unicode HTTP Server: Apache PHP Version: 5.2.17 (Zend: 2.2.0) What do you think about that?

Thanks Jim! It came in the right moment before I started to upload the products. This way I will try to drop the Extra Product Fields for the moment and will test Product Specifications. Regards Szymon

Coming back to the subject, some highlights for other noobs like me {if there are ;P} I saw around this forum, as well as around the other that some people feel limited to standard product attributes, which in fact are more so called options. Many of us saw the shops with ability to filter products using their attributes. I saw Year Make Model contribution that has minimal functionality needed, and can be easily modified from module supporting automotive stores to anything that would like to filter two text field and one numerical. With a bunch of code updates given in the support thread over years by other users it's even working. But it seems that part of the script is incompatible with seo contribution, which with no support from creator and no coding knowledge is a wall. The other contribution which seems to be just great are mentioned above Product Specification, however not for 2.3.1. In the support thread it's mentioned that it's compatible with 2.3.1 code, however there is just drop on top files for version 2.2 attached. I even started comparing the code of 2.2 with contribution drop on top files and in a second step for each file with code of 2.3.1, but after few files I found completely different code structure in one of the files, so I dropped. And yesterday I've found and installed Extra Product Fields. Works. Functional. You can add the the attribute, apply it to selected categories, than define possible values for attribute. Form front end it's possible to include those added attributes in the search, but in the way that advanced search becomes also a filter page (you don't have to type a text for search) and filter box too. If you search for something like this, give it a try.

Any possibility/suggestion than to switch off USU5 on category URLs? Anyway, thanks Robert. For both - contributions and being present in the support thread.

Thanks for quick reaction. I'm not saying that it's an issue generated by USU5, which without the YMM is working well (standard, rewrite is not supported by the hosting). YMM standalone is working also fine (well, with all the regards to the creators, it's the only free filter I've found for 2.3.1). I think that the issue is related to the fact that YMM may filter several parts of the shop - new products, specials, search result, catalog and categories. For most of those purposes SEO link looks simple: catalog - index.php, new products - products_new.php, etc. When entering to any category the url changes due to a proper USU5 reaction into the one containing already the category name: ex.: http://www.cantine.pl/sklep/index.php/wina-czerwone-c-1 This seems to be a no-go for YMM filter. It seems that it's not able to filter such page. Once I disable USU5, the YMM filter works also here without the error. I think that the solution might be to switch off somehow USU for categories, keeping them on product urls. But I don't think there is an option for that, is it? I think that code responsible for that SQL error is inside index.php, added by YMM. But I'm not a coder, almost blind there, so I don't know if YMM code could be modified to have them working both USU5 and YMM. And unfortunately I don't think I will get some support from YMM thread here. The part of index.php: // show the products of a specified manufacturer if (isset($HTTP_GET_VARS['manufacturers_id'])) { if (isset($HTTP_GET_VARS['filter_id']) && tep_not_null($HTTP_GET_VARS['filter_id'])) { // We are asked to show only a specific category $listing_sql = "select " . $select_column_list . " p.products_id, p.manufacturers_id, p.products_price, p.products_tax_class_id, IF(s.status, s.specials_new_products_price, NULL) as specials_new_products_price, IF(s.status, s.specials_new_products_price, p.products_price) as final_price from " . TABLE_PRODUCTS . " p left join " . TABLE_SPECIALS . " s on p.products_id = s.products_id, " . TABLE_PRODUCTS_DESCRIPTION . " pd, " . TABLE_MANUFACTURERS . " m, " . TABLE_PRODUCTS_TO_CATEGORIES . " p2c where " . (YMM_FILTER_PRODUCT_LISTING == 'Yes' ? $YMM_where : '') . " p.products_status = '1' and p.manufacturers_id = m.manufacturers_id and m.manufacturers_id = '" . (int)$HTTP_GET_VARS['manufacturers_id'] . "' and p.products_id = p2c.products_id and pd.products_id = p2c.products_id and pd.language_id = '" . (int)$languages_id . "' and p2c.categories_id = '" . (int)$HTTP_GET_VARS['filter_id'] . "'"; } else { // We show them all $listing_sql = "select " . $select_column_list . " p.products_id, p.manufacturers_id, p.products_price, p.products_tax_class_id, IF(s.status, s.specials_new_products_price, NULL) as specials_new_products_price, IF(s.status, s.specials_new_products_price, p.products_price) as final_price from " . TABLE_PRODUCTS . " p left join " . TABLE_SPECIALS . " s on p.products_id = s.products_id, " . TABLE_PRODUCTS_DESCRIPTION . " pd, " . TABLE_MANUFACTURERS . " m where " . (YMM_FILTER_PRODUCT_LISTING == 'Yes' ? $YMM_where : '') . " p.products_status = '1' and pd.products_id = p.products_id and pd.language_id = '" . (int)$languages_id . "' and p.manufacturers_id = m.manufacturers_id and m.manufacturers_id = '" . (int)$HTTP_GET_VARS['manufacturers_id'] . "'"; } } else { // show the products in a given categorie if (isset($HTTP_GET_VARS['filter_id']) && tep_not_null($HTTP_GET_VARS['filter_id'])) { // We are asked to show only specific catgeory $listing_sql = "select " . $select_column_list . " p.products_id, p.manufacturers_id, p.products_price, p.products_tax_class_id, IF(s.status, s.specials_new_products_price, NULL) as specials_new_products_price, IF(s.status, s.specials_new_products_price, p.products_price) as final_price from " . TABLE_PRODUCTS . " p left join " . TABLE_SPECIALS . " s on p.products_id = s.products_id, " . TABLE_PRODUCTS_DESCRIPTION . " pd, " . TABLE_MANUFACTURERS . " m, " . TABLE_PRODUCTS_TO_CATEGORIES . " p2c where " . (YMM_FILTER_PRODUCT_LISTING == 'Yes' ? $YMM_where : '') . " p.products_status = '1' and p.manufacturers_id = m.manufacturers_id and m.manufacturers_id = '" . (int)$HTTP_GET_VARS['filter_id'] . "' and p.products_id = p2c.products_id and pd.products_id = p2c.products_id and pd.language_id = '" . (int)$languages_id . "' and p2c.categories_id = '" . (int)$current_category_id . "'"; } else { // We show them all $listing_sql = "select " . $select_column_list . " p.products_id, p.manufacturers_id, p.products_price, p.products_tax_class_id, IF(s.status, s.specials_new_products_price, NULL) as specials_new_products_price, IF(s.status, s.specials_new_products_price, p.products_price) as final_price from " . TABLE_PRODUCTS_DESCRIPTION . " pd, " . TABLE_PRODUCTS . " p left join " . TABLE_MANUFACTURERS . " m on p.manufacturers_id = m.manufacturers_id left join " . TABLE_SPECIALS . " s on p.products_id = s.products_id, " . TABLE_PRODUCTS_TO_CATEGORIES . " p2c where " . (YMM_FILTER_PRODUCT_LISTING == 'Yes' ? $YMM_where : '') . " p.products_status = '1' and p.products_id = p2c.products_id and pd.products_id = p2c.products_id and pd.language_id = '" . (int)$languages_id . "' and p2c.categories_id = '" . (int)$current_category_id . "'"; } } Where added in the original code is only " . (YMM_FILTER_PRODUCT_LISTING == 'Yes' ? $YMM_where : '') . " in all 4 lines

Guys, I would appreciate strong help. I've installed YMM module, that is a kind of filter box rewritten for 2.3.1. With many problems with it finally after some modifications found over the support thread I managed to have it working. The issue is that the module once used for filtering adds to the path ?Make="make"&Model="model"&Year="year". As far as it's working in the main shop catalog SEO is not changing the url. But when you enter into any category SEO adds it's name to the path splitting the path between index.php and the part of the path added by YMM. The result is that the call for SQL is broken. You can see such action here. If anyone could support me how to change that (if it's possible at all), I would appreciate.

Forget about the table issue, now it's working fine and the problem was in /includes/languages/polish/index.php which is not a part of this contribution. The coder that was preparing the translation of the whole OSC 2.3.1 into our language made some improvements into that file that determined behavior of the frontend in few cases. One was interfering with the action of YMM. After modifying the code into original structure YMM module works well. So only the two other questions remain open, if anyone would be so kind, before I will learn too much about php and sql.

Ok, I made the scrip working in quite complicated way. I'm not an expert on coding, to be honest it's my first time with sql, php, etc. I don't know why, because using several tools I've been checking implementation of YMM on my already modified shop, and it doesn't give the result. I made a fresh install and applied drop on top files - they are wrong. To make it working I implemented few corrections mentioned in this thread in several posts: 1. Something with the cache I suppose - post 2. I cutted the red lines from post - link 3. I closed with missing </u> from - post 4. I added //<![CDATA[ from - post In case of no quick support on this contribution, maybe that will help somebody. I don't suggest to implement it an modified shops if you have a problem. It's probably the bast way to make in the way I described above and that to add other contributions as even if I made the changes to my modified shop the implementation seems to be interfering with something that I cannot catch. If anyone will watch this thread and will be able to give any hint on the following, I would appreciate: 1. I still can't make the script fully multi-language. The first and most obvious case is this post. I don't know how to make the array multi-language when it's in the file non language specific. If anyone would give a hint on this, it would be a great support. 2. Second issue on the multi-language is that I added properly and functionally the second language (just simple modifications in two files in second language, exactly the same as in english. YMM is working the same way in both languages, however there is an error on the added language. When the customer is in the main catalog of the shop, and using YMM in both languages it's working, however in added language the name of the result page is "what's new" and the header of the product listing there is still what I described previously: TABLE_HEADING_IMAGE TABLE_HEADING_PRODUCTS+ TABLE_HEADING_PRICE TABLE_HEADING_BUY_NOW instead of proper Product Name+ Price Buy Now. I don't think it's related to a language specific files where the changes of YMM are really simple. Anyone help on this? 3. The last question is not about an error. More to a small issue. Is it possible to configure YMM in the way that it will filter always all products in the shop? Regards Szymon