Jump to content

kru

Members
  • Content count

    143
  • Joined

  • Last visited

  • Days Won

    1

kru last won the day on December 24 2011

kru had the most liked content!

2 Followers

About kru

  • Rank
    Kru

Profile Information

Recent Profile Visitors

6,411 profile views
  1. kru

    View Counter

    Here's a screen shot showing access from Vietnam. (I cross-checked the IP using a popular site, which also showed it as Vietnam.) It's not always Vietnam. That's just the first example I came upon. I'm also including a screen shot from the Tools section, showing some countries we have blocked. I'm not saying something is broken. (We have discussed this previously and you explained how this situation can sometimes happen.) I would just like to make it easier to identify them when it does happen...
  2. kru

    View Counter

    Every so often I check View Counter to see what kind of activity we're getting and from what countries. Countries other than the US and Canada are not supposed to be allowed through, but some foreigners are gaining access. Their country flags are shown in the monitor next to the IP address and an IP lookup confirms they are from foreign countries. Anyway, it would be nice if the country flag was in it's own sortable column. That way we could quickly skip to the ones that do not show a US or Canada flag and potentially block them with the Ban or Block Range features. As it is now, if I want to get anal and see who all is slipping through, I have to go page by page. I may find one out of every 5 pages sometimes. That's pretty time-consuming, which means I don't do it as often as I'd like. Just something to think about next time you happen to be updating this add-on. Thanks.
  3. kru

    Automatically send data feed to Froogle

    What Jack is saying is, your first define statement says: define('OPTIONS_ENABLED', 0); However, if you're using any of the options at all, that first define should say: define('OPTIONS_ENABLED', 1); So you enable the options, then tell the program specifically which ones you want to use...
  4. kru

    Automatically send data feed to Froogle

    "Not Supported" is only appearing in the output file if the value is still set to NULL. If that field is empty, it is appearing as such instead. If we modified the record for any other field, the value in the UPC was being changed from NULL to empty, whether we updated the UPC field or not. So there was a weird mixture of values in the googlefeeder output file since we are constantly modifying product records. A lot of blanks, some "Not Supported" and a lot of UPCs. So I had to change the code whether "Not Supported" was a valid value or not. It didn't make sense to have a mixture of blanks and "Not Supported" for those records that did not have a UPC. FYI - The pickup-method attribute is the only one I could find that has a valid value of "not supported". I'm not complaining. I know Google is constantly making changes and it's incredibly hard, if not impossible, to keep up with them. I'm just pointing it out so you can incorporate it into the next version, assuming there is one. In the meantime, if others have problems with this and want to change it in the code, now they know how. (Line 501 in admin/googlefeeder.php)
  5. kru

    Automatically send data feed to Froogle

    Yes. I have been using that same page as a reference. It is my understanding you only use the 'identifier exists' attribute if you are missing both GTIN (UPC, in this case) and MPN. From the page you referenced: "In the rare situation where your product has neither a GTIN nor MPN (for example, made-to-order or handmade items), set ‘identifier exists’ to 'FALSE' to indicate that you have no identifier for the product." Regardless, that's really a separate issue. I was trying to figure out why the Google Base program is adding "Not Supported" in the UPC field of the txt file. It only happens if the products record has not been updated to include a UPC and, as a result, the UPC field is still set to NULL. (Which is a fair number of our OEM auto parts.) Wouldn't it be better for Google Base to populate a value of '' (empty) if the UPC field is either empty or still set to NULL? The help document you referenced says it is acceptable to provide no value for UPC as long as the Brand and MPN attributes are populated, which is the case with our feed. My goal is to create output that's ready to load into Google without manually tweaking any records, because that can lead to typos and/or formatting problems. (Not to mention delays.) If "Not Supported" is never supposed to appear in the UPC field, as far as Google is concerned, shouldn't the code which is adding it actually be removed from the Google Base program? I see where "Not Supported" is truly a valid value for another field, but not for UPC. Perhaps it was at one time and the code is still in the program? I can modify the code (@ line 501, if I recall) to keep it from happening in our file, but I thought I should bring it to your attention.
  6. kru

    Automatically send data feed to Froogle

    Jack, We added a products_upc field so we could pass UPC to Google. (Using your handy Add-A-Field add-on.) We have many products for which we do not have a UPC. (Most OEM replacement auto parts do not have a UPC and that is actually acknowledged by Google in the product feed specifications.) Anyway, in the generated txt file, I see a value of "Not Supported" for those products that do not have a UPC in our database. Is Google actually expecting to see "Not Supported" in that position if there is not a UPC? I can't find reference to that particular text string needing to be in that 'field'. (Or any 'field', for that matter.) Thanks. -Kevin
  7. kru

    Authorize.net SIM Configuration

    It is my understanding PCI compliance is about more than just storing credit card info. If they're entering it on your site at all, it must be transferred to a processor and the compliance folks take issue with that as well. Even if you're not storing it you have to send it somewhere and there are obviously security risks in that. I don't think that makes it impossible to pass the compliance 'test' but it seems to make it more difficult than solutions where the customer enters all their card-specific info somewhere other than your site. If your understanding is different, let me know.
  8. Nevermind. Not a bug at all. Just something that is not documented very well. There is a setting in Configuration>>Maximum Values. It is called New Reviews. This is evidently where you set the number of reviews you want considered for the total count. It was set at 6. I changed it to a higher number and the total displayed is now accurate.
  9. So I have a problem with this contribution... The count for the number of reviews is wrong in the Product Listing (where you see multiple different products in a category.) We have an item that has 9 reviews but, in the Product Listing, it only shows it as having 6 reviews. Once I click on the item to get into the details, it shows me there are 9 reviews. They appear on two pages. Page 1 has 6 reviews and page 2 has 3 reviews. Is it just coincidence that the total in the Product Listing matches the total number of reviews on the first page once I get into the item description? At any rate, it's been a while since I looked at this contribution. I was wondering if anyone has seen this bug and already made the appropriate code change and, if so, can you please share it? Thanks.
  10. Nevermind. It worked on the third try. I had some double quotes around a few words in the description. I took those out and the upload worked. I don't know if that was the issue or if they were just experiencing temporary problems. Either way, it's resolved now.
  11. I used 7zip too. Did you save it as a zip file or a 7z file? I saved it as zip because that was a file type in the list. 7z was not.
  12. I uploaded a new add-on package called Discontinue Product but it doesn't appear in the list of Add-Ons. It is a zip file and it is less than 3KB in size, so it doesn't even come close to the 3MB size noted as needing admin review. I uploaded it twice, actually. I thought maybe I did it wrong the first time. No dice. I'm wondering why it doesn't appear. Is there an Add-On approval process that isn't documented? Do I need to notify someone to get it approved? If someone can provide some guidance, it would be appreciated. Thanks.
  13. Thanks. I had found something else to suit my purposes not long before your post but I looked at the Sold Out add-on and it helped me discover an oversight in what I went with. I ended up modifying the Easy Call For Price add-on for my purposes. I just replaced the Contact link in that add-on with text that says 'DISCONTINUED.' I also had to modify the product_reviews and product_reviews_write files to get rid of the Add To Cart button. (That's the piece I discovered in the Sold Out add-on.) At any rate, I created a new add-on called 'Discontinue Product' if anyone is interested in doing this. I uploaded it to the Add-On page but it doesn't appear yet. I assume there is some sort of waiting period...even though it is not even close to the 3MB file size it says requires review...
  14. We need something like this. Does anyone have any idea if anything was ever developed? I searched the Add-Ons and didn't find anything. Basically, we want the product to continue to be displayed on the website if it was discontinued. We just want the Add To Cart button removed so they can't purchase it and maybe display a message of some sort, like "This product has been discontinued. Please contact us if you need help selecting a similar product." at the top of the page. Why do we need this? For many of the same reasons as MindTwist. Plus we sometimes have customers who we need to refer back to the original listing for warranty terms, return policy, compatibility notes, etc. If they were the last person to purchase it and we de-activated it because we can't get any more (and didn't want to risk someone else purchasing it), they can't see the listing at that point. We do not automatically hide products when the stock goes below zero, because, for most items, we can usually get more (or already have more on the way). But discontinued products are another story. We only want to display them if the customer can't actually purchase one. We don't want credit card fees for orders we already know we're going to have to cancel... The cleanest way to do this might involve adding a new field to the products table for a discontinued flag but, of course, that would involve adding the field to the product display page in Admin as well, so it could easily be updated. (Updating through mySQL is a pain.) A quick-and-dirty method would be to check the products_quantity value in the products table and, if quantity is set to -1000 or less, don't display the Add To Cart Button and also show the Discontinued message. Then it could be 'administered' from the existing products page in Admin by simply setting the quantity to a value of -1000. Any thoughts or direction?
  15. kru

    [Contribution] Database Manager

    He posted a link to a version specific to 2.3 one page back in this thread, I believe. Maybe you should check there. Perhaps there are additional changes for 2.3 that you will not find in the 2.2 thread...
×