Jump to content

derenyi

Members
  • Posts

    12
  • Joined

  • Last visited

Profile Information

  • Location
    hungary
  • Activity
    User/Merchant

derenyi's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. Hi, a know nothing about JavaScript, but regarding the url, instead of this: https://maglet.pswebshop.com/api/&ws_key=DRYZ21C3HNZJA1264GQER3DZU2ZAVV3L9/products?schema=blank use this: (http, not https) http://maglet.pswebshop.com/api/products?schema=blank&ws_key=DRYZ21C3HNZJA1264GQER3DZU2ZAVV3L9 Also, if you use multishop, several times it is necessary to narrow it to a certain shop: http://maglet.pswebshop.com/api/products?id_shop=1&schema=blank&ws_key=DRYZ21C3HNZJA1264GQER3DZU2ZAVV3L9 All shops: http://maglet.pswebshop.com/api/products?id_group_shop=0&schema=blank&ws_key=DRYZ21C3HNZJA1264GQER3DZU2ZAVV3L9 bye,
  2. Hello cowboyGeek! The solution is: http://teszt.diaper.hu/api&ws_key=xyzpasskey I think the documentation is simply erroneous with that. (If you use just http://teszt.diaper.hu/api instead of http://[email protected]/api/ (as the documentation suggests), the result is the same) bye,
  3. Hi all, It seems strange, but as far as I see there is no way to set the carrier availability restriction for a product via web service of PS 1.6 (I am talking about what is stored in the ps_product_carrier table) It is not under api/products, not under api/carriers Any idea? Thank you,
  4. Hello, The problem is: I am trying to use Presta's WebService, by sending url requests programatically, using WinHttpRequest. I use PS1.6, I configured what I had to in BO, if I type this url into a browser, everything works fine: http://[email protected]/api/ But when I try it using WinHttpRequest, the answer is: "401 Unauthorized" It is obviously so, because Presta prompts me for user password, as it is written in the developer's documentation: http://doc.prestashop.com/display/PS16/Chapter+2+-+Discovery+-+Testing+your+access+to+the+web+service+with+the+browser "The shop should prompt you for a username and a password to enter" I just can't figure out, how to get around this problem. (Actually, I do not really see why Presta prompts me again for the authentication key, which is already in the url?) Any suggestion would be really appreciated! Thank you, bye, Istvan
  5. Hello, The general question: Is it normal behavior that if I link (for example, from the top horizontal menu) to a category that is not the subcategory of the shop's root category, but of an other root, I get an 404 error? The whole problem: I want to create a special category for products that ar "on-sale". So I can display them for example in homepagetab, or I can have a menu item in top horizontal menu that links to them. On the other hand, I dont want this category to show up among the normal product categories. So, I created a second root category, and the special ("on-sale") category as the subcategory of this. But, if a place this category in the top menu, I get that 404 error. (Here is a test page: teszt2.diaper.hu, second menu item (AKCIÓK) is that.) Maybe that's the normal way, how it should work, but if so, the interesting thing is that this setup already worked a couple of days ago, also with a fresh test install, I just cant figure out, how? (Also, if really that's the way it should behave, could anyone give me a hint, how to solve some other way my problem?) Thank you,
  6. Thanks for your reply. It actually gave me a hint, and it seems that I solved the problem: It had nothing to do with Presta itself (or at least, it is working now): I imported back the whole database from a backup with phpmyadmin, and I forgot to uncheck the default option: "Don't use AUTO INCREMENT for 0 values". As my customer table was empty, maybe that is why it did not work. But, on the other hand, only logging in did not work, the newly created user was there in the database. And both creation and logging in worked fine with the base domain (localhost, in this case). So, the bottom line is: I am still not shure, why it is working now. (but the only difference is that AUTO INCREMENT setting.) Thank you anyway,
  7. Now it's an interesting problem: I have an absolutely fresh, local install (xampp) of PS 1.6.1 Steps I made: - Clean default user data - Switch on multishop, create a second shop group, and one shop in both groups. Their domains are: localhost and localhost/xy I can register new user at FO of the basic one (localhost), but when I try to do this with the second shop (localhost/xy), login does not work (the registered user actually shows up in BO, but he can not log in at FO) Any idea what's going on here? (It seems as if it happened only with local install.) Thank you very much, Bye, Istvan
  8. Hello, I am using PS 1.6, and what I want to achieve basically is to have two customer groups, and I want to be able to set "available for order", visibility, and prices of products independently for the two groups. I tried already a couple of things: - with customer group specific price, it is easy to solve the different price issue, but only that. - I know that I could duplicate each product categories, and then one of them would be available for one customer group, the other to the other one, but as far as I know, in this case what happens only is that a customer will not have direct link to a product, which does not belong to his customer group. But what if he still somehow gets the link? He will be able to order that product, I think. - With PS 1.6, there is multistore, but I have a couple of problems with that too. I declared two shop groups, one shop in each. My first problem is that I do not see, how can I change in back office, to which shop is the customer related. The other problem: each shop has to have its own URL, but I want only one domain for my shop. (When I changed the shop_id of the customer in the database, that customer was not able to log in any more under the original domain.) So, in brief: how to have different availability, visibility (and price) of the same product for different customer groups? Thank you very much,
  9. Dear Paul, dear Dave! Thank you both, both suggestions work. I like Paul's suggestion better, because in that case, one product still remains one product, with the possibility for the costumer to chosse the unit, meanwhile with Dave's solution, the two units became two products, which ruins a little the logic behind the category tree. (The costumer sees the product two times in the product list.) However, with Paul's suggestion, I do not know how to integrate an other pricing rule, that we use regurarly. Namely: the product is cheaper if the costumer buys more than a certain pieces. (For example, one box is 15USD, but if (s)he buys more than 10 pieces, then the price is 14USD a piece.) As far as I see, the pricing rules do not care about the combinations at all. Do you happen to know some solution to this problem too? Thank you again, Bye, Istvan Derenyi
  10. Hello! It seems as if no one talked about this issue, though it seems for me quite general. At least, I was not able to find any answer even close to it, so I am trying this forum. (If this should have been posted somewhere else, please, let me know.) So, the question: I am a wholesaler, and I want to sell the same product by different units, and corresponding unit prices. An example: I have a product, it is sold by the bag. Let's say, it's price is 10 USD. This product is packed 20 bags in one box. I also want to sell the product by the box, where the price would be let's say 1900 USD. So, same product, sold by the bag, 100 USD / bag, also by the box (where 20 bags are in one box), 1900 USD / box. Any idea? Thanks a lot, Istvan Derenyi
  11. Hello Gonebdg, I also failed with it (fresh install of 1.5.4), so let me ask very specific questions: - I added the line to the settings.inc.php file - In my override/classes diretory there was not those files, that you mentioned (Customer.php, Tools.php), so I just simply copied the files that you posted into that folder - Same with override/controllers/front folder (I copied your AuthController.php file there too) - From within phpMyAdmin (from the old, 1.4 presta install) I exported a few rows of the ps_customer table, into a .csv file - In the new install, I csv imported the previous file (as Customer entity) Still, the old password does not work. Where did I go wrong? Thank a lot, Istvan Derenyi
×
×
  • Create New...