Jump to content

Obewanz

Members
  • Content count

    147
  • Joined

  • Last visited

4 Followers

About Obewanz

  • Birthday 04/15/1974

Profile Information

  • Real Name
    Ben Kenobi
  • Location
    United States
  1. Obewanz

    Bundled products

    The Problem/Error: Every time I try to add a bundle to a product, the bundled items would be added to the PRODUCTS_BUNDLES table but they would not show up when I went back into the product detail page to view or edit something else about the bundled (master) product. I don't know why this became an issue as this has been working for some time. The Fix: What I discovered was happening was the PRODUCTS table had the products_bundle field type set to tinyint. This in effect stored a '1' in the table for products with bundles and since that does not equal a "yes" the bundled items were never being pulled from the table to be displayed in the product detail page. The other side of this was that the website would not display or work with the bundles either as all tests on that side of the app require the string value "yes" as well and not a numeric value. It is possible that this began as in issue from a database restore, but since it took me about 5 hours to find this needle, I thought I would share - in case anyone else is having the same problem.
  2. Thanks, I'll give your suggestion a try... Hmmm, I've been using osCommerce since 2000!! and No, not CRE Loaded. I've also contributed much in the back side over these years without any recognition, but that does not affect my willingness to help others, and even still give bug fixes when I find them. I've just stopped suggesting new code additions or enhancements - but I really don't want to go there. Now, let's look at your suggestion for a moment as this is a contribution that is being pushed hard at many osC users and trickles to the other "forks" as well... If this is in-fact the solution, which it does seem to be at first glance, wouldn't it have been better coding practice to incorporate this? Or at least make a notation in the documentation that html special character codes are not included in the parsing functions of the contribution? Granted, maybe the better solution is to fix the special character use in the BTS template files, but without analyzing the entire contribution, you aren't going to catch that - I didn't. Please don't take offense to the comments above as they are not intended to offend anyone, just trying to provide resolution and discussion. Thanks for taking the time to offer your solution to the problem, it confirms my suspicions of the difficulties as well as my belief in the generosity of the users who support osC. I'll still have the issue with the sid being appended to the url, but haven't had to time to look into that either - any ideas?
  3. I didn't say it was HARD - quite the contrary - the installation was a BREEZE - JUST DIDN'T WORK! You know, it was because of comments like this that I went against better judgement and installed this contribution without doing my usual backup/etc. Against the fact that this support thread (which doesn't include other versions of this contribution) is over 2600 posts and 135 pages LONG!! I also read the installation docs BEFORE touching anything and thought that maybe my prior reluctance to install the code was sorely misplaced, given that the documentation seemed very comlpete and the updates somewhat innocuous given the fact that only four files were actually modified. It seemed like it would be a no-brainer to me given this scenario. Of course, this is what made backing out the contribution a relatively painless task - which was contemplated before as well. Having said all of this, I still think this is a good contribution - just not something that a new store owner should jump onto right away without some help - and certainly not until it is installed and tested with their specific osCommerce code. Also, the ramifications for malfunction of this contribution will do substantially more harm than good with the search engines if double redirects and other issues present themselves, not to mention the effects on the "customer experience". Enough said about the bad... My store resides in a catalog directory so my .htaccess was correct in that regards. [RewriteBase /catalog/] Because I really did want to use this contribution, I've included a copy of that file pasted in this reply - just in case there is something wrong with it. I'll also be happy to communicate via PM regarding details if you want to help debug/troubleshoot my installation. # $Id: .htaccess,v 1.2 2003/09/24 13:57:00 wilt Exp $ # # This is used with Apache WebServers # # For this to work, you must include the parameter 'Options' to # the AllowOverride configuration # # Example: # # <Directory "/usr/local/apache/htdocs"> # AllowOverride Options # </Directory> # # 'All' with also work. (This configuration is in the # apache/conf/httpd.conf file) # The following makes adjustments to the SSL protocol for Internet # Explorer browsers <IfModule mod_setenvif.c> <IfDefine SSL> SetEnvIf User-Agent ".*MSIE.*" \ nokeepalive ssl-unclean-shutdown \ downgrade-1.0 force-response-1.0 </IfDefine> </IfModule> # If Search Engine Friendly URLs do not work, try enabling the # following Apache configuration parameter # # AcceptPathInfo On # PHP configuration values <IfModule mod_php5.c> php_flag register_long_arrays On php_value register_globals On php_flag display_errors Off </IfModule> <IfModule mod_php4.c> php_value session.use_trans_sid 0 php_value register_globals 1 php_flag display_errors Off php_flag track_errors On </IfModule> # The following RewrtieRules have been added as additional # security enhancement. These are not required for the # normal operation of the cart and may optionally be turned off. Options +FollowSymLinks RewriteEngine On # seo-urls rewrites below RewriteBase /catalog/ RewriteRule ^(.*)-p-(.*).html$ product_info.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-c-(.*).html$ index.php?cPath=$2&%{QUERY_STRING} RewriteRule ^(.*)-m-([0-9]+).html$ index.php?manufacturers_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pi-([0-9]+).html$ popup_image.php?pID=$2&%{QUERY_STRING} RewriteRule ^(.*)-t-([0-9]+).html$ articles.php?tPath=$2&%{QUERY_STRING} RewriteRule ^(.*)-a-([0-9]+).html$ article_info.php?articles_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pr-([0-9]+).html$ product_reviews.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-pri-([0-9]+).html$ product_reviews_info.php?products_id=$2&%{QUERY_STRING} RewriteRule ^(.*)-i-([0-9]+).html$ information.php?info_id=$2&%{QUERY_STRING} I have a hunch the problem, or at least part of it, lies in my link strings from my product_listing.tpl.php page from which the following is a sample; $lc_text = '<a href="' . tep_href_link(FILENAME_PRODUCT_INFO, ($cPath ? 'cPath=' . $cPath . '&' : '') . 'products_id=' . $listing[$x]['products_id']) . '">' . $listing[$x]['products_name'] . '</a>'; The rest of the code changes came straight from the doc and was pasted where/how instructed using the ver 2.1d Updated download files. (I also looked at the 2.1d Updated 1_2 download files but didn't see any differences besides stuff being what appears to be innocuously shuffled around.) PS: I am not bashing Chemo or his code, this is some very good stuff, just not really "industrial strength" yet - then again - not really much meets those standards these days! ;)
  4. My Review and Take on this Contribution: My experience with the Ultimate SEO Urls v2.1d contribution; Not Good! Install went very smooth, even looked like everything was working perfectly --- until... Can't access products from the categories box on left (using categories2.php) - seems I'm also getting a malformed url - ie. xxx.html?product_info.php?&id=424 or something to that effect. (not going to go double check as I now only have my live site to work with - temporarily.) I still had the osCsid issue that others have had no matter what my settings, except I do not use force cookies as that limits some people from being able to even browse your site, let alone make a purchase. (I have this problem on occasion as well and just leave the site - as an example; I have wanted to order several times from Vista Print now for over a year and can't even send them an email - can't get to the site to get the address!! - Sooo, I just gave up and now use a local printer == no less than $500 in lost sales (so far) for Vista Print!!) Since the above issue also prevented from adding to the shopping cart I needed to back this out quickly and I didn't do the things that I should have BEFORE I worked on this contribution. (Also why I am sharing this evaluation with you.) To fix this FAST! (Yes I installed to my live site without FULLY testing!! - Very Stupid of Me - and I KNOW better!! :blush: ) I renamed the .htaccess file to dot.htaccess, comented out the function inserted into the /catalog/includes/functions/html_output.php file, turned off SEO in the admin panel, and reset the cache to clear things up. I won't be turning them back on until I get all of the stuff reinstalled (from scratch) on my dev server. (Had problems with Zend Optimizer on another project - hosed the system) Anyway, the above issue caused a "Product not Found" to be displayed when I clicked on a product link from the above referenced location or from some but not all of the product links in other parts of the site. (Now this is why I just said forget debugging until later.) Oh, and this isn't my first rodeo - I have over 100 modification/contributions installed on my site with no other known issues! (Same code is also running 3 other sites now with no known issues on any of them either.) Final Evaluation: If you are not really well versed with osC, don't have time to debug, and/or don't have a second site to get things working on - DO NOT INSTALL THIS CONTRIBUTION!! It REALLY isn't worth the pain if you are just beginning. The search engines will index your standard osC url's just fine and if you install the HEADER TAGS contribution - which is also probably not for the faint of heart - but less damaging - you'll get nearly the same benefit! Stock out of the box osC needs some help, but if I were to advise a client, I would suggest using the header tags over the SEO thing every day of the week at this point. PS: This is an EXCELLENT contribution as it can also hide the identifying features of the engine on your site to amateur hackers, and seems to have been well written overall. But, it is complex code that just isn't ready for prime time yet and has potentially devastating consequences to your site if something isn't working correctly within the contribution.
  5. Obewanz

    Secret Questions

    After having a second to read what I previously posted about how the contribution might be modified to accomodate your request, I realized that I stated the "check" field going into the customers table, that would be incorrect - it should go into the customers_info table as that table is updated with each login, thus reducing the overall number of queries. I would probably call this field something like "secret_check" and give it an integer field type with a length of 3 and a default of 0. That would force all new logins to deal with the password secrets. The next step would obviously be to write the random number generator and update the code in login.php as well as password_forgotten.php (call rnd generator and update "secret_check" since customer has just accessed the secrets) to handle the logic regarding when to present as well as decrementing the "secret_check" number and resetting the value once presented. Oh and the create_acccount.php page should probably be modified to dump the rnd number into "secret_check" as well since this is where the account would start off. This is probably not something that I would write anytime soon as I have other obligations at the mooment, but you can PM me if you want to discuss when/where, etc this might happen, if you really want it.
  6. Obewanz

    Secret Questions

    Leslie, I don't really see this providing much in the way of extra protection when you evaluate the impact on the customer. As for Citibank, well they are a bank and as such try to make things a bit inconvenient in the name of security. When I worked at NASA, we had systems that required you to change your password every week, you couldn't write the password down and it had to contain both alpha and numeric characters with a length no less than 7 characters. This was what I would call a secure system except that you could remove some of the data once you gained access - but this is not a viable security setup for an ecommerce site as NO ONE would ever be able to purchase from you - you would probably be better off using (Purchase Without Account) and just leave it at that. Now that I've had a rant - sorry :blush: - I'll get back to the original question; why would you want something to come up random like that on an ecommerce site? Seems to me the customers would be more annoyed as the login process would change periodically. If you REALLY wanted that feature, it would be easy to implement in the existing contribution by adding a "check" field in the customers table and writing a little random number generator (one may already be in the general functions library) to pop into that field an integer, each login decrements the value by 1 and when it hits 0, the "Secrets" get presented. Of course the login.php page would have to be where this happens, but that is another simple modification.
  7. Obewanz

    Secret Questions

    Leslie, You should not be asked for the secret question if you have the userid and password, unless the user's "Secrets" are blank in the database - at which point the user is notified via a "warning message" that they don't have any Password Secrets and should create them. In this situation, it also takes them to the password_forgotten.php page which sees that they are logged in, but need secrets, so it doesn't ask them for their email. (The first step in resetting) It actually just asks for the secret question and secret answer, the "Secrets", and then redirects to the index.php page when these are entered correctly. The contribution sets up a default min length and max length for the secrets which can be changed via the configuration menu in the Admin panel to whatever you like. (You would have to change the database fields in the customers table if you want to exceed the default maximum for these.) Hope this helps!
  8. Obewanz

    Secret Questions

    Has anybody even been interested in this contribution? Please let me know how the installation goes if you use it. That will help me for future contributions. ;)
  9. Obewanz

    Seperate Pricing Per Customer v3.5

    Did you get things worked out Niel? Tried to PM you but your PM is disabled... :(
  10. Obewanz

    Roman Numerals

    Ok, this contribution was very old, but still works with the current release and was never packaged up as a contribution. It's not really a template or theme, but since it is really only a cosmetic enhancement/change, it seemed like the best place to put it. If you're interested in changing your copyright footer from regular decimal notation to roman numerals for the copyright year, you can get this contribution here: http://addons.oscommerce.com/info/5764 It's actually only a 3 step installation and very easy to implement. I've subscribed to this thread as I think this is where support for the contribution is supposed to be done. :'(
  11. Obewanz

    PreOrder or Checkout Later Module?

    I am planning on checking out the method posted in this topic, but if it doesn't really work the way I need it to, then I will be writing a contribution to handle this need. Basically I need to have an item placed on the site and have customers "preorder" the item with maybe a countdown as to how many need to be ordered before the item will be produced. The countdown is not absolutely needed, but the store I need to do this with has close to 3K products and does not handle inventory online as they manufacture to order. If this sounds close to what you need cloudzero, let me know and I will see what I come up with...
  12. Obewanz

    Secret Question v2.4

    Ok, I think this post should have gone to a different forum so you can find the contrib location, etc in the following post: http://forums.oscommerce.com/index.php?showtopic=294603 (General Contributions - Secret Questions)
  13. Obewanz

    Syntax, error 1064

    Denise, It would appear to me that you need to run the following sql statement using phpMyAdmin or similar tool; CREATE TABLE categories_to_stores ( categories_id int NOT NULL, stores_id int NOT NULL, PRIMARY KEY (categories_id,stores_id) ); If the table already exists you will get an SQL error stating that it was unable to create the table. (#1050 - Table 'categories_to_stores' already exists) Hope this helps... :)
  14. Obewanz

    PreOrder or Checkout Later Module?

    I'd like to know more about the payment aspect of this option as you will either have to use an astronomical stock quantity or really track your inventory within oscommerce to prevent items running out of stock when they are not preorders. I may create a contribution for this in the near future if I discover that this really isn't too flexible or viable given some simple requirements. If you have the answer to the payment/total issue before I get a chance to check on it, or you want to talk more about this functionality, feel free to contact me. (see profile)
  15. Obewanz

    Secret Questions

    Just uploaded a new contribution that removes the password being sent via email and replaces that operation with new functionality. This contribution will use "Secrets" to allow the customer to reset their password via a secured page. (You should have this if you are running a live site and accepting payments without a third party processor - such as paypal.) Anyway, find the contribution and read the introduction here: http://addons.oscommerce.com/info/5781 (Secret Questions in Other) I'm interested in hearing feedback so let me know what you think. PS: I'm sure that I messed up on the first post regarding this contribution and I couldn't see a clear category to put it in as it wasn't a payment module, etc. :blush:
×