Jump to content
thirty bees forum

dynambee

Members
 View Profile  See their activity

  • Posts

    837

  • Joined

  • Last visited

  • Days Won

    5

 Content Type 

Posts posted by dynambee

    Direction question and thanks

    in English

    Posted

    9 minutes ago, Traumflug said:

    Yes, this was the idea. Actually working on improvements turned out that one can pretty much always provide a backwards compatibility path.

    That is absolutely fantastic news. Thank you!

    Search Index table getting massive

    in Technical help

    Posted

    I've been playing with the ES module on TB 1.0.8.

    My host (Cloudways) offers ES 5.4 and 6.5. I tried to get it working with 6.5 but even following the suggestions I found on this forum I was unable to get ES to index with 6.5. I think there have been too many changes between 6.0 (which the module is in theory compatible with) and 6.5/6.8/newer for it to work. Even with only the 8 or 10 sample products in the store the indexing didn't work.

    However when I rolled back to ES 5.4 the indexing worked perfectly & was nearly instant.

    Now I have a different problem, the front end parts of the ES module do not seem to function with TB 1.0.8 with Bleeding Edge upgrades. Later today I will do some more testing on this and see if I can narrow down exactly why.

    PHP encryption, stopped receiving emails via 365

    in Technical help

    Posted

    If the current IP gets re-blacklisted then a new IP will get blacklisted as well.

    The key thing is to fix the problems that caused the blacklisting the first time -- using PHP Mailer and not having the mail DNS SPF & DKIM records set up correctly. Once those issues are fixed it doesn't really matter if you get a new IP or go through the effort of getting the current IP unlisted. The only real difference is the amount of time & effort involved and as you have experienced getting unlisted is a PITA.

    • Like 1

    PHP encryption, stopped receiving emails via 365

    in Technical help

    Posted

    38 minutes ago, t4Chippy said:

     HI Ian, error is still coming up the same 😞 

    You could save yourself a lot of time by getting a new IP for your webserver.

    Before doing this edit your DNS to change the domain record TTL settings from their current 14400 (4 hours) to 300 (5 minutes). I would advise doing this 24 hours before you swap the IP but you could wait as little as 4 hours. Then swap the IP, and after a few hours increase the DNS TTL to 3600 (1 hour).

    Make sure all your DNS settings for email (SPF and DKIM in particular) are correct.

    This should solve your problem without having to deal with all the blacklist issues you face now.

    Trying to install Elasticsearch Module crashes back office

    in Technical help

    Posted

    I wanted to do some testing with the Elasticsearch module but I cannot seem to get the module to install.

    I downloaded the module from github as a zip file. Renamed the zip file to "elasticsearch.zip" and renamed the module folder inside the zip file to "elasticsearch". Then I uploaded the module in the back office. The file seems to have been unzipped into the correct elasticsearch folder but once this completes everything crashes (error below).

    I figured maybe I need to install it from the command line so I did that as well (manual unzipping, making sure permissions are set correctly) and then went back into the back office. When I try to open the Modules and Services it crashes. In both cases I get the following error message: 

    [PrestaShop] Fatal error in module file :/public_html/modules/elasticsearch/elasticsearch.php:
require_once(): Failed opening required '/public_html/modules/elasticsearch/vendor/autoload.php' 
(include_path='/public_html/vendor/pear/archive_tar:/public_html/vendor/pear/console_getopt:
/public_html/vendor/pear/pear-core-minimal/src:/public_html/vendor/pear/pear_exception:.:/usr/share/php')

    I removed the directory path before /public_html as it was the same for every folder and just made the error harder to read. I've also inserted a few line breaks to make the error easier to read.

    I'm on a Cloudways VULTR server with 2 cores, 4GB memory, PHP 7.1, Elasticsearch 5.4 (tried 6.5 too, same error), and MySQL 5.7. Redis is installed too, which should be unrelated.

    I have tried disabling non-TB modules and disabling overrides, same problem happens. I have all caching on the server disabled. All forms of CCC are disabled. 

    I'm sure that I am just missing something simple here but for the life of me I can't figure out what it is.

    Help?

     

    Direction question and thanks

    in English

    Posted

    4 hours ago, Traumflug said:

    As mentioned many times, compatibility with PS 1.6.x won't go away.

    This is very interesting and relieving to hear.

    My memory from the earlier days of TB is that the plan was to maintain PS 1.6.x compatibility for the 1.0.x release of TB but that compatibility would start to break with the 1.1.x releases.

    I am very happy to hear that either my memory is wrong or that TB's planned path forward has shifted.

    PHP encryption, stopped receiving emails via 365

    in Technical help

    Posted

    At this point it has been definitively shown that MS is blocking SMTP requests from @t4Chippy's webserver. We don't know why the IP is being blocked but the test script runs perfectly from a server on a different IP using @t4Chippy's email account credentials.

    So, in final summary, the swiftmailer implementation included with TB supports STARTTLS and connects just fine to MS Office 365 SMTP server. The issue here was specific to the webserver in question.

    The solution will either be to get MS to take the IP off the blacklist (difficult IMO) or to change webserver IPs. Also, DNS settings regarding email authentication need to be fully set up to hopefully avoid this problem happening again on a new IP.

    • Like 1

    Search Index table getting massive

    in Technical help

    Posted

    8 minutes ago, movieseals said:

    I reinstalled 6.8 because that was the only one that had some sign of life in that stupid module.  5 will not connect at all, even after wiping everything.  This is clearly not a workable solution.  I tried about half a dozen times. It just won't do anything with 5. Elasticsearch, as promising as it sounds, is clearly not ready for primetime in Thirtybees!

    The Thirtybees module is not compatible with Elasticsearch 5. It is compatible with Elasticsearch 5.4. These are very different things. It should also work with 6.0 but I don't know of anyone who has tried it with a version as new as 6.8 and there is no way to know if it will run. It is best to get it working with a version that is known to work before trying anything else.

    I understand it gets very frustrating when a whole ton of time is spent trying to get something to work. Sometimes it is best to step away for a bit and then try again with rested mind & eyes. It is very much worth it to get the module working but as I mentioned in my original reply, it will probably take some effort.

    Search Index table getting massive

    in Technical help

    Posted

    1 hour ago, movieseals said:
    And the CURL command gets me this:
     
    Jun 09 16:37:50 odedi54851.mywhc.ca systemd[1]: Started Elasticsearch.
    [root@odedi54851 ~]# curl -XGET http://127.0.0.1:9200
    {
      "name" : "2ZwYVKY",
      "cluster_name" : "elasticsearch",
      "cluster_uuid" : "OTZDSTDgQieIL1C7AL4rZw",
      "version" : {
        "number" : "6.8.0",
        "build_flavor" : "default",
        "build_type" : "rpm",
        "build_hash" : "65b6179",
        "build_date" : "2019-05-15T20:06:13.172855Z",
        "build_snapshot" : false,
        "lucene_version" : "7.7.0",
        "minimum_wire_compatibility_version" : "5.6.0",
        "minimum_index_compatibility_version" : "5.0.0"
      },
      "tagline" : "You Know, for Search"
    So everything is running fine on the server!

    A bunch of messages back you mentioned that you installed ES 5. Hopefully by that you meant 5.4? That is the earliest version supported by the plugin. In any case, based on the CURL results you posted above, port 9200 still has ES 6.8 running on it. Not sure where ES 5.4 is but it won't be on 9200.

    I'm actually not even sure that it is supported to run two ES servers on one system but having never tried it I can't say for sure. Either way, I would remove both the installed ES servers and start fresh with ES 5.4 and see how that goes.

    PHP encryption, stopped receiving emails via 365

    in Technical help

    Posted

    Based on further discussion by PM and further testing by myself it would seem somewhat likely that @t4Chippy's webserver IP has been blacklisted by MS or by a 3rd party blacklist provider used by MS.

    This could be as a result of the regular connections by PHP Mailer or it might be because the DNS records for the domain did not show the webserver IP as being a valid IP to send mail from. Without the DNS records showing the webserver IP as an approved mail server for the domain it makes that IP appear to be sending spam.

    The exact reasons are speculation, but what does seem to be true is that the swiftmailer version included with TB is able to connect to smtp.office365.com using TLS.

    At this point @t4Chippy should check if his IP has been blacklisted and use something like this to see if his entire domain is on a blacklist.

    If the IP is blacklisted then getting a new IP for the webserver would be a good idea. If the domain itself is blacklisted, that is a much bigger problem. Getting a domain removed from public blacklists is just about impossible. The usual suggestion is to abandon the domain and start over with a new one.

    If neither the IP nor the domain appear on public blacklists then (assuming it is a blacklist issue) it is probably just the MS SMTP server blacklisting the IP. In this case a new IP for the webserver would be the solution, combined with proper DNS records of course.

    What is in the progress?

    in English

    Posted

    12 minutes ago, lesley said:

    When you create a new product, it just adds to you site like a normal product. It could be the main product your site is designed about, but the page looks the same as any other product on you site. Why? Why do we not have different templates for different types of products? We (and most of our competitors) just have one product page template. Why not have several to choose from?

    Something I would personally find extremely useful would be the ability to display multiple products on one page. This could be used for selling spare parts for a machine, for example. All the parts for one machine listed on one page with a price & "Add to Cart" button beside each one.

    It would also be very useful to be able to associate products to other products. Continuing the example from above, it would be very good to be able to associate all the spare parts for a given machine to the machine's own listing. From a different angle it would be great to be able to associate common or compatible accessories with a product. Customers are more likely to buy things together that way, or at least be aware of the options they might have. Spare batteries, cases, straps, etc, etc.

    Another thing that I have noticed is that when a product has variations (different sizes, different colors, etc) there is no way to set different physical weights or dimensions for the variations. Only the parent product has dimensions and weight set. Sometimes variations can be quite different in size & weight and not being able to set them individually makes the variation system a lot less useful.

    Just some random thoughts.

    • Like 1

    Search Index table getting massive

    in Technical help

    Posted

    6 hours ago, movieseals said:

    My feeling is that the connection is just not happening somehow.

    Try connecting from the command line with CURL: 

    curl -GET http://127.0.0.1:9200
or
curl -XGET http://127.0.0.1:9200
or
curl -IGET http://127.0.0.1:9200

    You can also try something like this to make sure your ES server is running: 

    sudo /etc/init.d/elasticsearch status

    There should also be a logs directory just below your main elasticsearch directory, or it could be /var/log/elasticsearch. You can also check the system logs, sometimes they will have helpful info.

    Search Index table getting massive

    in Technical help

    Posted

    The Elastic Search module will probably take some effort to get working properly but once you do get it working the search on your site will become incredibly fast. At least as fast and probably faster than any site you have visited.

    I’m working on a site now that will have ~100k items and eventually probably 200k items and will definitely be implementing the ES module on it. Unfortunately I’m not yet ready to start work on that part of the site.

    Shopping Cart shows "Free Shipping!" when weight has been exceeded for all available carriers

    in Bug Reports

    Posted

    SUMMARY

    I think I can summarize this with a few points:

    1. I was not able to completely replicate my results from yesterday. I am not sure exactly why this is but I did get "Free Shipping!" shown in more than one way yesterday, and I took the screenshots shown in the first comment.
       
    2. Even though "Free Shipping!" isn't always displayed there are still problems with how the shopping cart handles out-of-range shipping before the checkout process begins.
       
    3. The results are sometimes different depending on if a user is logged in or if there is no user logged in.
       
    4. Besides just the "Free Shipping!" display issue sometimes no shipping costs at all are displayed or the maximum weight range value is displayed, even though no shipping is available.
       
    5. When no shipping is available the cart should display a message about this to the customer. Something as simple as "No shipping available" would be fine.
       
    6. The checkout process itself (step 4 where the shipping carrier is chosen) does work fine so this isn't an issue where people can choose carriers that they should not be able to choose. Instead this is an issue where incorrect information (or no information) is shown to customers before they start the full checkout process.
       
    7. I did not run all of today's tests on PS 1.6.1.24 but as best I can tell it does operate in the same way. Therefore this is likely a problem that was inherited from the PS code.

     

    • Like 1
    • Thanks 1
×
×
  • Create New...