Jump to content

techjp

Members
  • Posts

    13
  • Joined

  • Last visited

Profile Information

  • Location
    Osaka, Japan
  • Activity
    Developer

Recent Profile Visitors

3,029,208 profile views

techjp's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. I'm setting up a site on a Cloudways VULTR server using the fork you mentioned and it is certainly very fast. I have turned on Redis on Cloudways, do I have to configure anything within the app itself for Redis to be effective?
  2. Of course it is your product and you can price it at what you think is most reasonable. I was just certain it had been 5500yen earlier today but is now 8500yen. Unfortunately at 8500yen it is beyond what I am able to pay, at least with our need to standardize the modules used for multiple sites.
  3. > we took other ecommerce best practices, and made it better. This module is 'amazing', 5 months of work/testing....very happy with result. Am I misremembering the price or did it jump by about $30 in the past few hours? I could've sworn it was quite a bit cheaper when I looked earlier. > I think it's possible you were looking at my module shop, please click front off demo tab where shipping costs and carrier selector are visible in widget. Yes, this seems to have been what was happening. uBlock Origin was stopping some elements on your page from loading properly. After I whitelisted your site the link to the demo shop comes up. Took me a bit to figure out that I had to manually select the shipping country, and that it was not within the cart pop-up itself, or the "added to cart" confirmation. I think a lot of users will miss the country selection it if it's not right in front of them when they add items to the cart. Would it be possible to use GeoIP as a way to set a default country for each visitor, which they could then change if needed? > the module issues various messages, cannot deliver to address. We have new dev prod level that will provide prod level carrier select, including msg prod cannot be shipped to your country. I wanted an all inclusive carrier high level and product level but decided to do two separate module works. I'm not sure I understand. Will you be adding these features to the existing module, or are you creating another module that has them? My current plan is to launch multiple stores targeted at specific product lines and/or at specific countries, using a high degree of automation to make management possible. If it was just one store then buying a bunch of modules isn't such a huge issue, but buying a bunch of modules for 10 stores, 20 stores, 50 stores, etc, gets very expensive very quickly. So I'm looking for solutions that are both functional and reasonably priced.
  4. > the area you are in is well, barbaric, not very good. PrestaShop's shipping system is definitely messy, one that is ripe for a good module to fix a lot of the problems, IMO. I looked at your "PrestaShop Shipping Commander" module and the features are very slick indeed. I have a couple of questions: 1. The Front Office demo doesn't show any shipping costs though, everything is set to "Instant Download". Any chance that the demo could have some shipping costs to display? 2. Does the widget also display the name of the country the shipping costs are being calculated for? We have customers in many countries who have us ship through a US address, it would be helpful if they knew the shipping estimate was likely high because it was being calculated for Brazil rather than their shipping destination of the USA (for example). 3. Finally, what happens if an item is added to the cart that has no carrier available to the user's country?
  5. I have taken another crack at finding ways to make this work, but unfortunately am still at the same place. I tried setting up 3 different sets of carriers: Set 1: Slow Free Fast Upgrade Set 2: Slow Full Shipping Cost Billed Fast Full Shipping Cost Billed Set 3: Fast Free Slow Downgrade (free) I made sure that the names for the fast & slow carriers in each set were exactly the same, that they had the same transit time, and that they had the same speed grade set. So inside PrestaShop I see the following: Slow / Speed Grade 4 / Transit Time 7 to 14 days Slow / Speed Grade 4 / Transit Time 7 to 14 days Slow / Speed Grade 4 / Transit Time 7 to 14 days Fast / Speed Grade 6 / Transit Time 3 to 5 days Fast / Speed Grade 6 / Transit Time 3 to 5 days Fast / Speed Grade 6 / Transit Time 3 to 5 days I was hoping that with exactly the same names, speed grades, and transit times set that PrestaShop would at least display the name properly on the Shipping section of the checkout process. No dice though, it doesn't give any information about the carriers, only the price and a radio button to select: Beside the top radio button it should say "Fast" and beside the bottom one it should say "slow". I am going to work on a little code to see if there is a way to make this work. If I get it going I will be happy to share it here. Cheers, -techjp
  6. Update: I think the problem I was having was caused by having multiple items in the cart and having no carriers that were shared between all items. The reason for this is that some items had "free" shipping and other items had regularly billed shipping. To facilitate this I had five carriers set up: Carrier 1. Airmail Carrier 2. Airmail Free Shipping Carrier 3. Express Mail Upgrade from Airmail Free Shipping Carrier 4. Express Mail Carrier 5. Express Mail Free Shipping From a human perspective we can of course see that really there are only two actual ways to ship items, Express Mail and Airmail. PrestaShop however views them as five individual carriers. So, imagine the following three items in the cart: Item 1. Widget ABC (Carriers #2 and #3 assigned) Item 2. Widget OPQ (Carriers #1 and #4 assigned) Item 3. Widget XYZ (Carrier #5 assigned) In this situation PrestaShop doesn't see any shared carriers that can be presented as a shipping option even though in reality the items are either going to be shipped by Airmail or Express Mail. I never tested this with more than two carriers set for a single item so I am not sure what would happen in that case. However for my scenario with either 1 or 2 carriers set for each item PrestaShop combined the "cheap" options and "expensive" options together and presented two choices for shipping to the customer. The problem was that it didn't give any explanation as to what carrier (or carriers) would be used for a given shipping price. The result was the image in my original post: I ended up "fixing" this problem by either offering "free" shipping for all items or offering "paid" shipping for all items. This way there were only two carriers set for every item (Airmail and Express Mail) which results in tidy options presented by PrestaShop. If anyone does wish to proceed with having free & non-free shipping options on the same website you will run into another problem as well: When someone buys an item with "free" shipping and another with non-free shipping in the same order PrestaShop will split this order into two separate entries because from PrestaShop's viewpoint they are using two different carriers (one free, one not free). This is confusing for customers and a PITA for store managers, so ideally items that will be shipped in one box should be presented as shipping in one box. David Garcia faced this problem and fixed it by editing one of the core files to prevent this split from happening. Unfortunately there is a problem with doing this and that is that in some cases you may want (or need) to ship the items separately! For example if the items are dramatically different sizes or shapes it may not be practical to ship them together, and in this case having separate orders within PrestaShop is necessary. So overall it is a very complicated problem and different stores will need to approach it in different ways.
  7. There should be no "No Carrier Available" errors as long as you have carriers properly set up, properly assigned to products, valid for your shipping address, and valid for each item in the cart. The most common problems are: 1. The weight of the item(s) for a given carrier exceed the maximum weight set for that carrier, or the item weight ranges are not properly set up in the carrier. 2. The item's weights are not properly assigned (wrong values) 3. If you have your carrier settings based on the cart's total price then you may not have a range set that covers your cart's total value. 4. The selected shipping address is not covered by any carriers. 5. No carrier assigned to one or more items (or no carrier that is valid for that item/address) 6. If you are using warehouses then no carrier assigned to one or more warehouses (or no carrier that is valid for that item/address) You might want to have a look at this page that goes over proper carrier setup: http://alvinjiang.blogspot.jp/2011/05/prestashop-tip-no-carrier-available-to.html
  8. I had super slow load times on my 1.6.x panel as well (multiple versions, including the latest 1.6.1.7). In my case "demo mode" was still enabled due to site development ongoing. "Demo mode" wants to pull data (?) from gamification.prestashop.com and I think this was timing out. It's probably the same firewall issue that other users reported in earlier versions. If something in the admin panel is trying to access an outside site the timeouts are extraordinarily long which leads to ridiculous load times. It would be very helpful if Prestashop gave an actual error about these timeouts, it would make tracking down the source of the problem much easier.
  9. I'm setting up a store with a few different carriers. Sometimes a product can be shipped by 2 or 3 different carriers, depending on the user's preference. Other times a product can only be shipped with one carrier (oversize items, for example). Our customers tend to purchase more than one item at a time and there will often be cases where items from one order must be shipped separately. However, when more than one carrier is required for the items being purchased, no shipping carrier descriptions are shown during the cart checkout process. Difference prices are shown for different combinations of carrier, and the prices are accurate, but there is no indication of which carriers will be used if a given combination is selected. Here is a screenshot of what we see: *** Note: For testing purposes I am using a completely unmodified Bitnami PrestaShop 1.6.1.4 VMware image, the default theme, and no modules have been added. Carriers have been defined using weight ranges and the carriers have been assigned to separate warehouses. Items that can be shipped with a particular group of carriers have then been assigned to belong to that warehouse. The shipping calculation is working perfectly as far as getting the correct total shipping cost is concerned. So, my question is: How can we get a list of carrier names to be included with each price? It doesn't need to show which items will be shipped with which carrier, only which carriers will be used. Edit: I'd be happy to edit a bit of code to make this work, or use an override if that is possible. I'd sooner avoid using a shipping module as our shipping needs are quite unique. We have the shipping cost calculations working perfectly and just wish to display the carrier names.
  10. Just a short note to say that this issue still exists and is unchanged in PrestaShop 1.6.1.4
  11. I am working on adding carrier, price range, and weight range support to the PrestaSharp C# .NET client library for the PrestaShop web service. The short form of this question is: I need to send NULL values to the Web Service but sending NULL (tried many ways!) results in the value 0 (zero) being stored in the ps_deliveries table. How can I send NULL values to the Web Service within an XML file? For development and testing I am using PrestaShop 1.6.1.1 in a Bitnami VM. Edit: This issue still exists & is unchanged in PrestaShop 1.6.1.4 Longer with lots of details: Here is an image of the ps_deliveries table data. This data was entered through the web administration interface. The administration interface has not been modified in any way: As you can see, the id_shop, id_shop_group, and id_range_price values are NULL. This test store does not have Multistore enabled. I checked the ps_shop and ps_shop_group tables and the only value available for id_shop is 1, and likewise the only value for id_shop_group is 1. However if I set id_shop or id_shop_group to any value besides NULL the shipping prices no longer appear in the web administration interface. Here is what the web admin interface looks like with NULL in the id_shop and id_shop_group columns: However if I change id_shop and/or id_shop_group to any value besides NULL (0, 1, etc) I get the following results in the web admin interface: To eliminate any possible issues with the PrestaSharp XML serializer and my own coding I have used the "Advanced Rest Client" Chrome Extension to send various XML requests to the PrestaShop Web Service. The requests complete successfully but the stored values in the ps_deliveries table do not reflect the requested NULL values. I have tried doing the following: 1. Send NULL values as NULL within XML tags for id_range_price, id_shop, and id_shop_group as follows: <?xml version="1.0" encoding="utf-8"?> <prestashop> <delivery> <id xmlns="">26</id> <id_carrier xmlns="">4</id_carrier> <id_range_price>NULL</id_range_price> <id_range_weight xmlns="">3</id_range_weight> <id_zone xmlns="">227</id_zone> <id_shop xmlns="">NULL</id_shop> <id_shop_group xmlns="">NULL</id_shop_group> <price xmlns="">22.000000</price> </delivery> </prestashop> This results in a "400 Bad Request" return. The reason for this is that even though the web admin interface stores NULL in the id_range_price field (we only use weight ranges) the Web Service requires a value be set for id_range_price and will fail if it is set to NULL. 2. Send NULL values as NULL within XML tags as follows, except set 0 (zero) for id_range_price: <?xml version="1.0" encoding="utf-8"?> <prestashop> <delivery> <id xmlns="">26</id> <id_carrier xmlns="">4</id_carrier> <id_range_price>0</id_range_price> <id_range_weight xmlns="">3</id_range_weight> <id_zone xmlns="">227</id_zone> <id_shop xmlns="">NULL</id_shop> <id_shop_group xmlns="">NULL</id_shop_group> <price xmlns="">22.000000</price> </delivery> </prestashop> This results in a "200 OK" response with the following data returned: <?xml version="1.0" encoding="UTF-8"?> <prestashop xmlns:xlink="http://www.w3.org/1999/xlink"> <delivery> <id><![CDATA[26]]></id> <id_carrier xlink:href="https://192.168.10.105/prestashop/api/carriers/4"><![CDATA[4]]></id_carrier> <id_range_price><![CDATA[0]]></id_range_price> <id_range_weight xlink:href="https://192.168.10.105/prestashop/api/weight_ranges/3"><![CDATA[3]]></id_range_weight> <id_zone xlink:href="https://192.168.10.105/prestashop/api/zones/227"><![CDATA[227]]></id_zone> <id_shop><![CDATA[NULL]]></id_shop> <id_shop_group><![CDATA[NULL]]></id_shop_group> <price><![CDATA[22.000000]]></price> </delivery> </prestashop> Looks great! Except when I check the table I can see that id_shop and id_shop_group have both been set to 0 (zero) and not to NULL! Also, id_range_price is (of course) set to 0 (zero) as well when it really should be NULL based on how the web admin interface saves data. 3. We have tried sending NULL formatted in different ways as well. Empty tags, for example: <?xml version="1.0" encoding="utf-8"?> <prestashop> <delivery> <id xmlns="">26</id> <id_carrier xmlns="">4</id_carrier> <id_range_price>0</id_range_price> <id_range_weight xmlns="">3</id_range_weight> <id_zone xmlns="">227</id_zone> <id_shop xmlns=""></id_shop> <id_shop_group xmlns=""></id_shop_group> <price xmlns="">22.000000</price> </delivery> </prestashop> Returns "200 OK" with the following: <?xml version="1.0" encoding="UTF-8" ?> <prestashop> <delivery> <id> <![CDATA[ 26 ]]> </id> <id_carrier xlink:href="https://192.168.10.105/prestashop/api/carriers/4"> <![CDATA[ 4 ]]> </id_carrier> <id_range_price> <![CDATA[ 0 ]]> </id_range_price> <id_range_weight xlink:href="https://192.168.10.105/prestashop/api/weight_ranges/3"> <![CDATA[ 3 ]]> </id_range_weight> <id_zone xlink:href="https://192.168.10.105/prestashop/api/zones/227"> <![CDATA[ 227 ]]> </id_zone> <id_shop /> <id_shop_group /> <price> <![CDATA[ 22.000000 ]]> </price> </delivery> </prestashop> Once again however the values are stored as 0 (zero) and not NULL. 4. Other ways we have tried include the "<id_shop />" empty tag format (same 0 value stored) as well as specifying NULL as "<id_shop xsi:nil="true"/>" (results in a "500 Internal Server Error" return). We have also tried just excluding the NULL tags completely but this also results in a 0 (zero) value being stored. So, as far as I can tell, I have tried everything. Of course there's always a chance I have missed something! From my side however it looks like the PrestaShop Web Service doesn't support sending NULL values but we definitely need to send NULL values to support adding & updating data in the ps_deliveries table. Help? Edit: This issue still exists & is unchanged in PrestaShop 1.6.1.4
  12. If you wish to use the web service from C# you should definitely check out PrestaSharp, you can find it on Github.
  13. Hi everyone, I am in the early stages of building multiple web stores using PrestaShop. I have been selling online for 10 years but never with my own stores, always through 3rd party sites. I have a background in IT & programming. We would like to have all stores use proper identifying SSL certificates. Is this possible with a MultiStore setup? Do special multi domain certs need to be used or can I install multiple separate SSL certificates into a PrestaShop multistore installation? We have customers all over the world so would like to use a CDN together with our stores. In particular we are considering CloudFlare due to their reasonable prices, good API automation, and apparently very good SSL support. Are there any issues with using CloudFlare together with PrestShop multistore setups? (For that matter, any big issues using CloudFlare with PrestaShop in general?) As best I can tell the benefits I can see for a multistore setup would be a single point of administration, a shared product catalog, and in many cases the ability to share expensive plugins across all stores in one installation. Are there other benefits that I am not seeing? Finally, are there any big limitations, "gotchas", or other issues with using a multistore setup? Thank you very much in advance for any insight and assistance!
×
×
  • Create New...