Jump to content
Latest News: (loading..)


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by altoid

  1. In thinking that over, and actually looking at what I do on site, it turns out my redirects for defunct items go to the category pages rather than another product for the vast majority of the time. On rare occasion, where there is virtually an identical product I may consider redirecting to that. So when redirecting to the category page, it seems very understandable and user friendly for the customer in and of itself. That coupled with the message stack, seems to be good. It's my understanding when using a 301 the search engine process that by removing the previous product from index when redirected to another by the 301. In webmaster tools I do not see any duplicate content other than product and product reviews dupes.
  2. Actually using Gergely's add on, my redirects from an defunct product are to the category of that product, with the message stack telling customer product is not available but here are similar items to consider. I think it's user friendly and effective.
  3. Back when Gergely was developing this we discussed that. He came up with a handy message stack that shows a nice clear message that after the redirect clearly alerts the customer such and such is not available but here is something you may wish to consider.
  4. Eventually yes over time as I understand it with a 301. I do that by choice to avoid a long term page or product not found. Once set up it stays there until you remove it. His mod let's you set whatever code you want too. By default the mod throws a 302, which you can review in a log and the change to 301, delete or whatever.
  5. @burt I have gergelys redirect installed and use it a lot. Mostly for discontinued items. When the last one sells of something I set up a redirect to an appropriate product or category. I also set up a 301 for SEO. I'm really interested in what you come up with especially with edge and PHP 7 in mind.
  6. As I see it the boot strapped version is what's keeping OSC above water.
  7. Only help I can offer would be installing on source tree and testing
  8. Installed and working. Thx for the update.
  9. I've been S L O W L Y upgrading to edge, I've been doing that via Github and installing commit by commit. I still have a way to go. My reasons for going to Edge is I want to run php 7* and folks are turning out addons that are meant for Edge.
  10. Slim Checkout for BS

    Can test but currently traveling. Couple of weeks...
  11. AJAX Attribute Manager support

    Hello, thanks for that info. Got it now. With that so updated, the values are showing in product_info neatly now. As you add them in the ajax portion, they will show in order of how you add them it appears. That's a plus. Also, I find by making and copying a template, when applying that template to a new product, the values show well as well. If a shop owner really needs to change the order, it is possible to do that manually withing the products_attributes table. Suggestion on instructions for AM... consider removing: 1) If you haven't installed the attribute sort order contrib then you should install that one first: http://addons.oscommerce.com/info/1822 Maybe some explanation of what I observed above would help a new user. Also, in the code to be replaced for this purpose I see $HTTP_GET_VARS I believe that has been modified when going to edge. Thanks
  12. AJAX Attribute Manager support

    Hello, I was looking over the install instructions and for the optional product attributes sort order add on.. https://apps.oscommerce.com/2K0SB looks like it was last updated there in 2012 which is pretty much pre bs and edge. So I'll presume the coding there would be outdated. Wondering if table definition code would be the only thing needing updated. TABLE_PRODUCTS_ATTRIBUTES example
  13. QTPro BS

    @raiwa, I installed QTPro in a test shop using edge and php 7+ that I already had ajax attribute manager installed. The Ajax attribute manager folder in the QTPro package looks like the files may need updated for edge and php 7. I ran into some errors initially but doing some updates as best as I could seemed to take care of those.
  14. AJAX Attribute Manager support

    @raiwa In a test shop with php 7.1.7 No errors displayed on shop or admin side. Once in stalled, had to go through and reset some settings to false because I didn't have the particular add on installed. but once done all's good.
  15. 2 Minute Testers Required

    Facebook and Google log in worked.
  16. PHP 7

    @@burt Gary, I lost track of where the php7 project is for Edge but in Github I managed to pull John's branch into my local branch (after dealing with a couple conflicts), the using the zip from that I ran a fresh install a "live" test shop using php 7.1. Hopefully what I have there is Edge up to the latest as of this date, then John's php7 work on top of that. Install went fine, no errors showing. A quick look around the test shop..no errors appeared but more looking needs done. FYI on that
  17. @@burt I can test, but it'll have to be on a uniserver test shop as my live shop is still way back from being caught up on Edge
  18. QTPro BS

    @@raiwa Found it admin/includes/header.php Got there from the original instructions it looks like.
  19. QTPro BS

    @altoid I am updated from Github. Regarding that duplicate message, I don't see anything in admin/includes/template_top.php Going through that again..when ordering a Value 8 MB card, where there is only one in inventory when completed over on the admin side when on the index.php page, I see just one notice: Warning: There are 1 sick products in the database. Please visit the QTPro doctor. It appears only with the catagories.php page, I see two notices now: Warning: There are 1 sick products in the database. Please visit the QTPro doctor Warning: There are 1 sick products in the database. Please visit the QTPro doctor. Seems something specific to categories.php?
  20. QTPro BS

    @@raiwa I'll update with what you advised and check things out on the test shop. Regarding my repo, I apologize, I got backed up and haven't kept that up to date. I'll do that with files from your repo which should get it up where it needs to be. Thanks for working on the QT Pro modification > BS. It'll surely help folks out.
  21. QTPro BS

    @@raiwa Using the files from the github, I completely wrote over existing files from new and modified files in qtpro-5.0-BS-master and then reinstalling, I see this happed during a trial purchase: Adding a Value Model with 8 mb to the cart Model Memory Price Qty. Value 4 mb $299.99 1 Value 8 mb $349.99 1 Noting there's just one of those in stock. On the shopping cart page when I update the quantity to 2 and refresh this message appears. Matrox G200 MMS*** - Memory 8 mb - Model Value Products marked with *** dont exist in desired quantity in our stock. You can buy them anyway and check the quantity we have in stock for immediate deliver in the checkout process. Continuing through the checkout process... checkout_shipping > checkout_payment > checkout_confirmation Showing: 2 x Matrox G200 MMS - Memory: 8 mb - Model: Value I get to checkout_success and done. In admin I see this message: Warning: There are 1 sick products in the database. Please visit the QTPro doctor. QT Pro Doctor says: You currently have 28 products in your store. 3 of them have options with tracked stock. In the database we currently have 0 trash rows. 1 of the producks with tracked stock is sick. Sick products in the database: Product with ID 1: The summary stock calculation is wrong. Please take a look at this products stock. Clicking products stock I see duplicate warnings at the top: Warning: There are 1 sick products in the database. Please visit the QTPro doctor Warning: There are 1 sick products in the database. Please visit the QTPro doctor. Noting stock for that Value 8 MB Value 8 mb -1 Below I click on: Automatic Solutions Avaliable: Set the summary stock to: 14 QT Pro Dr is happy now but in stock for that item stock shows: Model Memory Quantity Value 16 mb 5 Premium 16 mb 6 Value 4 mb 1 Premium 4 mb 2 Value 8 mb -1 That's it for now
  22. QTPro BS

    @@raiwa Are the most up to date files on the github repo?
  23. QTPro BS

    @@raiwa That languages issue was because I didn't uninstall that module before I updated the module file. An uninstall and reinstall fixed that. Testing adding product with options for Model Memory Price Qty. Value 4 mb $299.99 1 Matrox G200 MMS - Memory 4 mb - Model Value In shopping cart, when I change the number order to 4 and refresh.. I do not get a notice of ordering more than is in stock. I am able to click Checkout. Ran a test checkout, completed successfully with 4 x Matrox G200 MMS - Memory: 4 mb - Model: Value In admin stock shows -3
  24. QTPro BS

    update to beta 5 With these settings, Show Out of Stock Attributes True Mark Out of Stock Attributes Right Display Out of Stock Message Line True Prevent Adding Out of Stock to Cart True Use Actual Price Pull Downs False Here's what I see for the various displays for Product Info Attribute Display Plugin with memory of 8 mb out of stock for both models: Base: 8 mb shows, no out of stock message and I am able to add to cart multiple_dropdowns 8 mb shows, with out of stock message. When trying to add to cart this popup shows: The combination of options you have selected is currently out of stock. Please select another combination. sequenced_dropdowns 8 mb does not show single_dropdown 8 mb shows with out of stock message. Trying to add that to cart gives pop up notices. single_radioset 8 mb shows with out of stock message. Trying to add that to cart gives pop up notices. In the edit mode for qt pro options..looks like a language mix up: Admin Stock Warnning ENGLISH Definición de idioma usado en admin QT Pro Stock Out of the edit mode I see: Admin Stock Warnning ENGLISH Warning: There are %s sick products in the database. Please visit the QTPro doctor Clicking that link, I get a page with this error on it: Bad RequestYour browser sent a request that this server could not understand. That's it for now