Jump to content

ecartz

♥Ambassador
  • Content count

    3,750
  • Joined

  • Last visited

  • Days Won

    63

Everything posted by ecartz

  1. Product Attributes are part of the stock install. You have four drop downs. Make each an option. Make the price dependent on which of the five quantities is chosen. Do not have different prices for the other three options. You won't get the product code, but you will get most of the rest of your first choice.
  2. ecartz

    Modular means "Modular", right?

    I thought of another way of looking at the relative complexities of a blog and a cart. WordPress uses ten database tables. It stores both tags and categories in the same table. It can do this because there is no real difference in WordPress in how tags relate to each other or relate to categories. You can think of a tag as a special kind of category that displays differently. By contrast, in osCommerce, a manufacturer is not just a special kind of product attribute. A manufacturer has information (e.g. URL) that an attribute does not have. Likewise, an attribute has information (e.g. price offset) that a manufacturer does not have. Categories don't need any of that information. This forces osCommerce to use different tables for relating products to categories, manufacturers, and attributes. As a result, osCommerce (2.2 RC2a) has forty-seven tables (I believe that 3.0 has more). A blog is conceptually simpler than a cart. It has fewer relationships among the data that it stores. This makes it easier to add relationships, as there are fewer old relationships with which they can conflict. WordPress implements this well. It is absolutely true that WordPress is more modular than osCommerce (particularly 2.2 and older, but still true of 3.0). I'm not as convinced that WordPress plus eShop is more modular for e-commerce tasks than is osCommerce. I want to reiterate that I think that this is an area where osCommerce both can and will do better in the future. The 3.0 series is much better than the 2.2 series at this. Parts of osCommerce (in particular, payment, shipping, and order total modules) are already most way there to what you want (you still have to move files manually). New areas are being added for 3.0 (in particular, drop in handling of new product option types).
  3. ecartz

    Modular means "Modular", right?

    Do you have an example of HTML that is not available in osCommerce but is available in a blog? Admittedly, the default Wordpress textarea for posts is better than the default osCommerce textarea for product descriptions. Does Wordpress do threaded replies and discussions by default? Or is that a plugin? I can come up with examples of carts that have that. For example, look at Amazon. Carts can have tags (not sure if osCommerce has a contribution for this or not), again look at Amazon. Product Attributes in osCommerce have much of the same behavior characteristics as a tag (multiple ones can be assigned to a specific product and several products can have the same options). Products can have third party merchants (equivalent to authors), look at Amazon or several contributions for osCommerce. I'm also not convinced that any of this is notionally as complex as a tax rate. For example, can an admin only edit a comment when the commenter is from location A, the author is from location B, and the post has a particular tag? Do you have to determine if the edit permission applies before shipping and coupons or after? What happens if someone wants two pieces of functionality, one of which exists in one plugin and one which exists in a different plugin? I suspect that the answer is that if the two plugins cover the same area, you need to choose between them or write a new plugin. With the installation method used in osCommerce, you could integrate them and get both pieces of functionality. Part of my point is that I think that you will find that this issue (addon conflict) is more likely to be important with osCommerce than with a blog. Far more people need both pieces of functionality. osCommerce actually has several contributions for this. Each does slightly different things. Taking a quick look at WP-MU, it looks like it allows for multiple blogs to run on the same software, with shared users but separate roles (i.e. you login the same at two blogs but can do different things at each). It's possible that osCommerce could implement one click installation of the various modules (payment, shipping, and order total). It's almost there now. Historically what people have had to do themselves has been to copy the files over. This could be automated to include the file download and putting them in the proper places. The upgrade system could also be improved (currently you may have to uninstall and reinstall). Also, according to the eShop forum, Google Checkout is not available for eShop, because eShop does not support SSL. This may not be the best example to establish your point... And does it have over six thousand contributions adding additional features? I think that what you'll find is that the eShop would give you most of what you want but when it fails, it will be difficult to add functionality. The impression that I get is that you can't add plugins to eShop. You can only get the eShop author to add new functionality. At least googling for eShop payment processors and eShop plugin did not find a list of payment processors that could be installed in eShop via one click plugin installation. This is also somewhat away from the point. There is a contribution to embed Wordpress in osCommerce. Do we credit osCommerce with every capability of Wordpress? In the customer table? So, for each product, you have to add a new *column* in the customer table? That doesn't seem scalable. Perhaps you meant that the currency preference should be stored in the customer's table? I'm not sure that there's enough information in a currency to justify a whole module. It's basically five pieces of information that you can enter into a single form. Or run one line of SQL. It would not be difficult to automate this into a plug in module. The function getPriceFormated (sic) outputs the actual price plus the special's price (if present) in the correct way (including HTML) for the customer's currency, including or not including tax as per the configuration. It is based on the product and will give the same result for the same product and different results for different products. It is not stored in a table but calculated from various pieces of data (product, specials, tax rate, currency, etc.). My point was that this should be split off from product, as people will want to override the default behavior. When they override, they should not have to change the product file, as they only want to change one function. Further, this function is display related and may change without any changes in the product row in the database (for example, specials are in their own table). I was agreeing with you here. This is a place where osCommerce could be more modular and therefore easier to override but isn't. However, contrast that with the ease of adding a textarea product attribute contribution. That would be a simple drop in of a single file. If there was an automated contribution loader, you could use it on most product attribute contributions (not on file upload attributes, because there is currently no place to automatically hook in the upload processing functionality). My major point is that it is easier for a blog to integrate plugins because a blog is an inherently more basic concept. A comment is linked to a post but comment behavior does not change from post to post. You can add a ratings system to your comments because it's easy to separate the ratings from any other information that you might want to attach to comments. Adding functionality is easy. The difficult part comes when you want to modify functionality. I suspect that Wordpress handles this well for the first modification but has trouble with the second modification. This may not impact you much, if you rarely need to make modifications in the same place twice. However, with a cart, modifications tend to cluster in certain places and shops have very individual needs. One store may never use specials, so that functionality can be hacked out (as many templates do). Another store may need specials and MSRP and Quantity Price Breaks. Here's a question, does the quantity price break apply to the special price? Or is it an either/or situation? Two different stores may answer that question differently. The big advantage of osCommerce is the ability to customize it. Two osCommerce stores can have very different behavior. We should not make changes that restrict this. We should make changes to make addon installation easier, especially for the common case, installing on a new store. We should work to make the team better aware of places where osCommerce should be more modular (like creating a FormattedPrice class that can be overridden separately from the product, currency, and tax rate classes). We will not always succeed in doing those things. For example, the File Upload contribution has always been more developer friendly than store owner friendly. However, would it have been better for me to have waited before contributing it? A contribution with a clumsy install is still better than no contribution at all. Contrast that with the case of a payment module that I wrote but never contributed. It was only minimally tested (worked on the store where it was installed) and needed some care and improvement. Apparently I never got around to contributing it (as I can't find it). Someone else has presumably written another version, when they could have just improved mine. If I had waited to contribute until the File Upload contribution was perfect, there might not have been an Options Types V2 contribution. At the very least, Zappo would have had to do more work to get it up and running.
  4. ecartz

    Modular means "Modular", right?

    It's worth noting that blogs and forums are simpler beasts than a shopping cart, a blog almost strictly so. A blog has posts; a cart has products. Equal. Products have prices; posts don't. Cart. Prices can be with tax or without tax. Cart. Both blogs and carts have categories. Equal. A blog has comments; a cart has reviews. Equal. Reviews have star ratings; comments don't. Cart. Both have search and browse. Equal. Both have registration and login. Equal. Users put products in their carts; no blog equivalent. Cart. Checkout. Cart. Interaction with external shippers and payment processors. Cart. Both are multilingual. Equal. Carts are multi-currency. Cart. No matter what system of contribution/addon/plugin install you have, I don't think that there is an automated solution for someone who wants to install all of Separate Price Per Customer, Quantity Price Break, Options Price Update, Actual Attribute Price, and MSRP. The fundamental problem is that they all want the same piece of real estate and they want to do incompatible things to it. For example, when you change the selected attribute, should the Options Price Update change the MSRP as well as the regular price? I'm not even sure that it's meaningful to mix Options Price Update with Actual Attribute Price. As a project, osCommerce could do a better job of internal modularity. It's easy to see that just contrasting 2.2 RC2a with 3.0a5. The latter is much improved, although it could be better. For example, getPriceFormated (sic) should not live in Product but outside it somewhere that is easily overridden. Otherwise, every one of the previous contributions will be in there modifying that single function in Product. Not to mention possible template issues. In terms of managing contributions, it's true that the addons area could be a lot better. Ratings for contribution (both functionally and for ease of install); tagging of contribution versions (rc2a compatible, code merge required, update package, specific solution, not multilingual); better handling of contribution forking and merging; so on and so forth. I don't favor mandates though; I favor increasing information. If people don't want to install contributions that don't come with step by step install instructions, then they shouldn't do so. I still prefer whole files, because it is easier for me to diff them than it is to diff an instruction from a text file.
  5. ecartz

    boolean is sql

    int(1) would be consistent with what the rest of osCommerce does.
  6. checkout_process.php (after buyer confirmation, before success).
  7. ecartz

    Product version add-on?

    If you want to choose the color from a drop down list, Product Attributes are part of the base install. If you want to show pictures of the colors (may appear differently to the customer because of monitor settings), you could look for the Options as Images contribution. If you need inventory tracking, check out QT Pro. An alternative option would be to install Master Products or one of the similar contributions. This would allow you to show multiple products on one product info page. It would offer images and track inventory.
  8. ecartz

    Easiest way to give shipping options

    I think that what you want to do is install flat rate shipping to implement Registered Post. Download and install a contribution for Customer Pickup. The link to contributions is in the Community menu at the top of the page. The customer will choose between Registered Post and Customer Pickup during checkout.
  9. Did you install a contribution related to attributes? Perhaps QT Pro? The error is saying that there is code that thinks that there is a column named options_values_model_no in the products_attributes table; however, the database says that the column does not exist. That is not the name of any of the standard osCommerce columns, so it is likely that this is something that you added later. The easiest fix would be to make the database changes that the contribution wants. However, that may not be practical. An alternative would be to undo the code changes from the contribution. That's more complicated though.
  10. ecartz

    Shipping Module In Shoping Cart?

    Yes. It's called something like ship in cart.
  11. ecartz

    New OScommerce User

    You need to run the .sql file in the root directory of the contribution in something like phpMyAdmin. If you continue to have problems, you may want to post in the contribution's support thread: http://forums.oscommerce.com/index.php?showtopic=338661
  12. ecartz

    mod_rewrite

    That's quite possible. It's also possible that they have AllowOverrides set to false. Have you tried going to admin >> Tools >> Server Info? It should tell you how Apache is configured. Look under apache >> Loaded Modules and see if mod_rewrite is listed. If your host has disabled phpinfo so that it doesn't show you this information, then it would be best to ask them how they have things configured and how to implement your rewrite rules.
  13. ecartz

    Where is Line 109

    Try searching for noscript in the file. The code that you want to replace is in a javascript block and is immediately followed by the section for people without javascript, which is in <noscript></noscript> tags. Also look to see if your product_info does an include or a require of a page to display the images. Perhaps you installed a contribution? If your product_info file is just a long series of defines that look like define('TEXT_PRODUCT_NOT_FOUND', 'Product not found!'); define('TEXT_CURRENT_REVIEWS', 'Current Reviews:'); define('TEXT_MORE_INFORMATION', 'For more information, please visit this products <a href="%s" target="_blank"><u>webpage</u></a>.'); define('TEXT_DATE_ADDED', 'This product was added to our catalog on %s.'); define('TEXT_DATE_AVAILABLE', '<font color="#ff0000">This product will be in stock on %s.</font>'); define('TEXT_ALSO_PURCHASED_PRODUCTS', 'Customers who bought this product also purchased'); define('TEXT_PRODUCT_OPTIONS', 'Available Options:'); define('TEXT_CLICK_TO_ENLARGE', 'Click to enlarge'); then you are looking at the wrong product_info file.
  14. Reported spammer

  15. ecartz

    [Development] Products Specifications

    It looks like should be PRIMARY KEY ( `specifications_filters_id` ) ,
  16. ecartz

    suggest a receipe

    Perhaps the Article Manager contribution would work for you?
  17. ecartz

    Shipping Costs

    Order Editor includes that.
  18. ecartz

    Cool Flash Carousel Menu

    Have you verified that the function flash_carousel_product_name() exists in includes/functions/flash_carousel.php? It looks like it is a newer function. Maybe you have an older version of the file?
  19. ecartz

    Cool Flash Carousel Menu

    I don't think that would matter (you did the right thing there). The error it is giving you suggests that you missed step 11, where you were supposed to end up with code like tep_expire_specials(); // auto expire flash carousel products require(DIR_WS_FUNCTIONS . 'flash_carousel.php'); tep_expire_flash_carousel(); in includes/application_top.php
  20. ecartz

    Fast and Easy Checkout

    Purchase without Account
  21. I would expect that that would break things and would not add pull downs where they aren't already. You absolutely should not add a </form> if it is not there already. You may have to do something similar to compensate. In particular, you should make sure that all forms have the session ID somewhere. If you find a </form>, you may need to add the session ID if is a GET form. In the POST forms, I think that the session ID would already be provided by the action URL.
  22. ecartz

    Better Product Preview with Lightbox 2

    document.write('<?php echo '<a href="' . DIR_WS_IMAGES . $review['products_image'] . '" rel="lightbox" title="' . addslashes($review['products_name']) . '">' . tep_image(DIR_WS_IMAGES . $review['products_image'], addslashes($review['products_name']), SMALL_IMAGE_WIDTH, SMALL_IMAGE_HEIGHT, 'hspace="5" vspace="5"') . '<br>' . TEXT_CLICK_TO_ENLARGE . '</a>'; ?>');
  23. ecartz

    Free shipping module and Coupon module

    I have the impression that the order of the order total modules matters. If you go into the order total section in admin and change the sort order so that coupons are before shipping, it might fix your problem.
  24. ecartz

    Better Product Preview with Lightbox 2

    Try changing (in the code I posted previously) '" rel="lightbox" title="' . $product_info['products_name'] . '">' to '" rel="lightbox" title="' . addslashes($product_info['products_name']) . '">' I think that this is a bug in the contribution and that everyone who has apostrophes in their titles will encounter it (not just your modified version).
  25. ecartz

    Header Tags SEO

    'categories_description_front' => tep_db_prepare_input ($categories_description_front_array[$language_id] ); // End Categories images box /*** Begin Header Tags SEO ***/ $sql_data_array = array('categories_name' => tep_db_prepare_input($categories_name_array[$language_id]), I think that the first line should be last, like this (also changed a semicolon to a comma): // End Categories images box /*** Begin Header Tags SEO ***/ $sql_data_array = array('categories_name' => tep_db_prepare_input($categories_name_array[$language_id]), 'categories_description_front' => tep_db_prepare_input($categories_description_front_array[$language_id] ), Don't forget to backup before you try it.
×