Jump to content

Druid6900

Members
  • Content count

    332
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Druid6900

  1. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    @greasemonkey You think it might work better if it was set up to disallow everything as default and then add the ones you want to use?
  2. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    Well, I'm in Hamilton, and I was one of the people that helped keep this going, way back when. but 2.2 is a long time ago. You might be better upgrading your database through a number of versions (there are scripts) to something like 2.3.3.4 BS reactive and install GreaseMonkey's latest iteration. That's what I'm running on my shop and I started with 2.2 and cranked it up through the versions just as I mentioned above.
  3. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    Yeah, I'll do that. I'm just playing with Phoenix in (what little) spare time I have. I haven't decided if it's going to be worth the trouble, but, I suppose this will be a good first test....
  4. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    @greasemonkey Here we go again....Do we know if this package will work in Phoenix (1.0.3.0)?
  5. Druid6900

    Ebay manager

    @14steve14 I need something like this in that it would make life a little easier, but, it's not something that I can't live without. I hadn't even thought about it until I was browsing through add-ons. Should it become absolutely necessary, I will contract someone to write something and then release it into the wild. I'm guessing that not a lot of people would use an add-on like this just because it's as easy to post it on eBay directly and, for stuff already on a site, cut and paste would suffice. I'm further guessing that, anyone that is doing OsC to eBay would be doing it that way.
  6. Druid6900

    Ebay manager

    I'd guess, seeing as there doesn't seem to be another contribution like this, that either people are using something else to achieve this (which I can't find for 2.3.3.4 Gold BS) or that not enough people want to do this for someone to want to sit down and write it from scratch.
  7. Druid6900

    Ebay manager

    Yeah, I noticed it was a little heavy on the code, but, I suppose with dealing with APIs, it bulks up pretty quickly. I need a module that does this and this one sounded good. I'm looking for something that will work with 2.3.3.4 Gold BS responsive and there isn't a lot of choices, it seems.
  8. Druid6900

    Ebay manager

    @greasemonkey Hey GM, As bad as the Canada Post REST code when we sort of inherited that? Too bad. It sounded good and ALMOST works, but, I'll take your word for it since I've seen you pull off, what I considered, miracles, in the past. I guess I'll have to rip out the files and write it off. Anyone know what people use when they find out that this just isn't gonna cut it? Thanks
  9. Druid6900

    Ebay manager

    I'm getting the following error in Admin on almost all the functions for this add-on Notice: Undefined variable: SID in /hermes/bosnaweb15a/b152/ywh.xxxxxxx/catalog/admin/includes/functions/html_output.php on line 48 I'm sure it's a quick fix, and probably has something to do with some other addin. Any help would be appreciated, but, it looks like this add-on has been abandoned
  10. Druid6900

    consignment sales?

    Yes, a form is a given for security reasons. It would have to allow for photos, shipping dimensions and weight and all the fields that we use. In addition, a couple of extra fields would have to inserted into the database to hold the Zip/Postal code it will ship from and the shipping carrier to calculate the shipping options since the site is set up to only calculate Canada Post from the company postal code. I can see this getting mildly complicated for a non-programmer.....
  11. Druid6900

    consignment sales?

    Actually, I have become interested in this of late. My site is doing well and enjoys a good reputation, so, I'd like to be able to have people list their item(s), in line with what we sell, and be able to set the shipping point and shipping method for their items. It would be a flow-through system that we would take a small percentage of the sale of the item from. It gets them a better platform to sell on and we get a better reputation for providing the things that people are looking for. What I don't want to do is become a FeeBay type operation. Anything out there that would accomplish this for OsC 234BS? TIA
  12. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    Too bad we didn't think of it a month ago, eh? I removed all that packaging stuff a while bad, but, tomorrow, I'll put it back in and show you what it does. We can go from there....
  13. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    @greasemonkey I found this in includes/classes/packing; if ((float)$weight < 1.0) { $weight = 1; } else { $weight = round($weight, 3); } I removed it and the module, in ready to ship mode, works right, regardless of the weight.. I guess you can remove that for the next version of the package and now it's just a matter of fixing setting up the admin tools box sizes part of it and it will finally ALL work right. Thanks for all the help, Scott, and, as I said, I owe you one.....
  14. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    OK, here's a good one for you. If I select No to the question "Do you use the additional dimensions support?" in the admin configuration setup for this module, I get the right weight (.2 KG) and the right shipping price, but all my greater than 1 KG prices are wrong. So, something in the module is forcing a minimum weight of 1 KG.....
  15. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    @greasemonkey Well, I guess it must be some else because my code looks identical to yours. //******************************************** function _addItem($length, $width, $height, $weight, $price = 0 ) { $index = $this->items_qty; $this->item_length[$index] = ($length ? (string)round((float)$length,1) : '0' ); $this->item_width[$index] = ($width ? (string)round((float)$width,1) : '0' ); $this->item_height[$index] = ($height ? (string)round((float)$height,1) : '0' ); $this->item_weight[$index] = ($weight ? (string)round((float)$weight,1) : '0' ); $this->item_price[$index] = $price; $this->items_qty++; } //********************************************************************************************* I have no idea what could be causing it unless there is some statement in there that prohibits the use of anything less that 1 on the left of the decimal place and I haven't seen it. I have noticed, though, that, if you put in a weight of .15 and save it, when you look again, it's been padded with a 0 to the left of the decimal place when you look again. The weight and dimensions all seem to be handled in that file, so, it has to be somewhere in that canadapost.php file. I have a LOT of items that are sub-kilo in weight, so, this is affecting a lot of my inventory.
  16. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    @greasemonkey I agree that both sets of code SHOULD not be necessary and that the $weight should be whatever is in the table for that item. However, the comment for this function states "// Add box or item to shipment list. Round weights to 1 decimal places." So, what would happen if you have a weight of 0.150? It would be rounded to 1.0 or, possibly 1.1 (I don't know the structure of the rounding operation). Both useful values, but, hardly interchangeable with .150 I have done as you suggested and removed that code and it still does exactly the same thing. I understand that not everyone is a coder, but, I also understand that, if you are going to offer a package with multiple options, it would be nice if one checked that they all work, not just the one the author uses. Would you like me to repair your computer just to the point that it does the stuff that I use but not the stuff you need to work because I don't use it? As for not being broken, do you recall that the above code had the width statement equaling the weight statement, so the width was always 1 (which you found). I'd call that broken. How about all the things that you've found and repaired? They must have been broken when the package was released. I'm not saying that the author OWED us the package or that someone, even you, are required to spend your time making it work, the best you can, but, if you're going to write a contribution, why not get it right and/or give it a little support. "See what I wrote? Pretty cool, eh? It works 66% too. You're on your own." Why offer a package with dimensional support if it's not going to work right? Yes, I'm sure that I can find someone to fix it so that it actually does dimensional support correctly, and I may just have to do that and, if I figure it out or pay someone to fix it, should I share it with the rest of the community or just say "Screw you"? No, I would share the fix so that everyone that downloaded it and expected it to do what it says it's supposed to do actually was pleasantly surprised that it did. I was just saying that it would be nice if someone with the right skill set took a bit of time and fixed it and , like me, was able to take something broken and know the satisfaction that it is now repaired and working right and people who don't have skill set can install it and use it and not find out that, after all the work THEY put into getting it installed, that they are screwed because they put in all those dimensions for all those items (maybe during the previous versions of a Canada Post shipping module that DID work correctly) but they sure as hell aren't going to selling anything under a kilo or a pound because of faulty coding. I repair and rebuild a lot of more current computers and donate them to places to get them to kids whose parent(s) can't afford to buy their kid(s) computers because they are poor. It usually costs me a fair amount in time and parts but it helps people. It also makes me feel good to have the skill set to be ABLE to help people. I guess I'm just strange. GM, don't get me wrong. I appreciate all the work you've done fixing this package and all the time that it's taken you more than I could tell you, even to get to this point. If there is ever anything on the hardware side of this that I can do for you, just let me know. I guess our definition of "community" differs from that of other people.
  17. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    @greasemonkey The code above, which was not previously in your V1.2 rendition, was something that I slightly modified from your post showing that you took it out. I know enough about PHP to have figured out that this should do what I want it to do and allow sub-1KG values to exist, and be passed to CPC but, the problem I am having is that I don't know where about to insert it into the existing code in canadapost.php for it to work and not give me errors in the code. BTW, if you are going to put out another version, there is some SEO code in the admin/categories.php file that should be taken out and the packaging code comes out a mess for box creation/editing. There must be someone in Canada that is using this package that IS a coder that could clean up this code so that it could be used however a store owner needs to implement it. How about it, guys? Even when we were all using CrashnBurn's pre-sellonline package, I figured out and shared how to have a selected handling percentage added to the information returned and displayed from the CPC server. Someone with talent could put this package together right in now time. This package looks a lot better, but, in places, it is seriously broken and, as you know from all the great changes you've made to it, it always has been. Maybe someone will step up to the plate since the original author seems to have abandoned it. I mean, there is no law that says he has to, but, I've always been taught that, if you are going to do something, you do it right.
  18. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    OK, I have been trying to work out some code in an effort to pass on to this module the fact that weights less than 1 KG are valid and pass that to the CPC servers. No matter what I try, $weight will not accept a value less than 1 The piece of code above, obviously, doesn't do it. I'm not a coder, so, it's probably a really simple task that eludes me completely. Can anyone here help me work this out? Thanks
  19. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    I was looking at the first bit of code 2 messages up, and maybe we are going about this the wrong way.... What if we changed it like this if ((float)$weight < 0.0001) { $weight = 1; } else { $weight = round($weight, 3); And inserted it into the code? Would that work to pick up items less than 1 KG (seeing as dimensional likes to pad things out to 3 decimal places)?
  20. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    @greasemonkeyI missed one of your questions; I'm using Gold BS. OK, putting I in by hand explains a lot. LOL. I don't have that first set of code in my canadapost.php file, so, I can't remove it and commenting out the second set of code had no affect.
  21. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    @greasemonkey No, there was no tare in the shipping config. I made the change and there was no difference and the xml request still shows the weight as 1, I'm afraid. The only other example of rounding the weight is on line 420 when it changes lbs to kgs, but since my stuff is already in kgs, I don't see that affecting it. When you posted the XML request to the CPC Dev site, all your parameters were correct. What difference is there in the file between yours and mine?
  22. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    OK, well, the control for metric/imperial is in the Admin/configuration shipping module and is set to KGS/CM. The tests I have run on the packages over 1 KG agree with the prices on the CPC Find-a Rate function perfectly when the values input are metric. With that one particular package that was rated at 0.150 KGS, when I upped it to 1.15 KG, gave the right prices, but not if it was at less than 1 KG. It seems that the minimum it will accept as a weight is 1 (in the case of metric. I haven't tried it in imperial. I did notice, at line 185 in canadapost.php, that the code is trying to do some rounding function on the dimensions and weight, but I couldn't figure out how to change it with regards to the weight. Thanks for helping get the stuff above 1 KG working right. It was so obvious, once it was pointed out :-)
  23. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    OK, if this helps any, it seems to pick up weights of 2 KGs and 15.5 KGs correctly, so, there must be some cut-off point below where it doesn't get the weights right and I'm guessing it's below 1 KG.
  24. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    I made that weight to width change on line 414 and, as you would expect, it now picks up all the dimensions in the XML request :-)
  25. Druid6900

    canada.post.rest.rate.service.oscommerce.V2.3

    The items are all in Kgs and Cms and all weights and sizes are packages and ready-to-ship. Should I make that width change in canadapost.php? The file is unmodified from v 1.2
×