dynambee

[deleted double post]

Regarding @Adik's original question about performance, Thirty Bees uses Cloudflare as a CDN which should result in faster load times. Have you tried using Cloudflare or a different CDN? Cloudflare has a free tier that is quite good. Excellent, considering the cost. 🙂

I'd double check the SPF record as small errors can make a huge difference in the meaning.

Just a thought, have you updated your SPF record to include the IP of your webserver as being allowed to send emails on behalf of your domain? I don't know how PHP-mailer works but there's a chance 365 is refusing your emails because they are coming from an unauthorized user. Your SPF record should look something like this: SPF v=spf1 ip4:<Webserver IP Address> include:spf.protection.outlook.com ~all

That is newer than the version that PS added to 1.6.1 to fix the STARTTLS issue. You should be able to test the included swiftmailer version with help from this page. You should also make sure you have openssl installed and available on your server, you can do that with the info in the link (this link) I provided a couple of replies ago. If you don't have openssl installed on the server then AFAIK you won't be able to connect securely to the remote SMTP server, something that is going to be required in today's world.

I checked the swiftmailer version included with TB 1.0.8 and it is 5.4.12. I'm not sure which version was in 1.0.7 but it is unlikely to be older than 5.4.9 which was released a number of months before TB 1.0.7 was released. You can check the version yourself though, it is located here: [your tb top folder] /vendor/swiftmailer/swiftmailer/VERSION Edit: These are both much newer than the version provided by PS that fixed the STARTTLS issues discussed in the thread you linked to so I don't think changes to the TB swiftmailer will be necessary. Also, TB has moved the location of swiftmailer so I suspect installing that extension would bork TB's ability to send mails at all.

According to this Microsoft support page Office 365 uses STARTTLS for SMTP access. However there are other pages like this one that say TLS is also okay. Other pages I have found say that TLS is okay but it must be version 1.2 or higher. You can probably use the first option on this page to check if your server supports TLS 1.2. This is another Microsoft page that looks like it might be useful. It explains how you can send messages directly to your Office 365 mailbox but your server must be able to send out on port 25. If you have shared hosting or some VPS services (like DO, or so I have heard) that block outbound connections on port 25 then direct send wouldn't work. However if you do have the ability to send out on port 25 then it might be a good solution for your particular problem. Hope some of this helps.

As part of a process of elimination, try setting up a mail client on your local PC with the SMTP settings you get from MS. Send some mails and see if it works. If the local setup works then double-check the credentials you have on your server to make sure they are correct. You also might find this page to be useful with setting up SMTP on Office 365. If it still isn't working then you may have to try a manual SMTP connection from the shell so you can see what the errors are.

Thirty Bees is just about perfect for my needs except for this problem with the shipping system. I haven't found any other cart that comes close to matching my needs as well as TB does so getting this fixed is quite a priority for me.

@haylau has explained it very well. It seems simple at first but it gets very complicated very quickly. Besides not really being effective (as explained by haylau) it rapidly becomes impractical if not impossible to manage per-item carrier assignments for a site with 5000, 10000 or more items. There is also a big problem because TB (and the origin project) do not handle things well if there are different items in the cart that have differing shipping options available. In fact it doesn't handle things at all in some cases and customers are just told that no shipping option is available, with no further explanation. This description is only scratching the surface of the problem. The way the TB shipping system is set up is flexible but it can result in multiple copies of the same carrier needing to be created for different zones or countries, resulting in dozens of "different" carriers. I'm sure it sounds absurd but I have been working on this problem for quite a while. The best & easiest workable solution by far is to limit low-cost (slower, maybe no tracking, perhaps no insurance, etc) shipping types to low total cart values. This avoids so many different problems and greatly reduces the complexity of the carrier & item setup. I actually decided to do this soon after my original post. It's really the ideal solution for my needs and would solve a lot of the problems I face with the shipping & carrier setup.

A while back I looked into just modifying the PHP myself, and adding a "max_cart_value" field to the carrier db table. It didn't seem like it should be all that difficult to do but I don't really want to monkey with the core files. I also don't know where else the carrier options might appear that might need to be changed too. Basically I hesitate to poke around in code that I don't really understand in any depth. Law of unintended consequences and all that... Maybe @Traumflug knows? If the code for the carrier options is changed and a field is added to the db table to facilitate this (assuming the field is manually set, nothing fancy...) would this be enough to make this limit work? Of course any upgrade would bork the new code so that would need to be manually managed. Or perhaps there is another way to accomplish this?

I just discovered the lack of TB on Cloudways. Very unfortunate change as it made setting up dev sites super easy. I hope Cloudways themselves continue to function okay as they are a great balance between a shared host and a bare VPS.

Currently the available shipping types can be limited by the total weight of the items in the cart. I would like to add the ability to also limit the available shipping types by the total value of the items in the cart. So, for example: Shipping Type 1: Max 2kg, Max Cart Value $50 Shipping Type 2: Max 2kg, Max Cart Value $100 Shipping Type 3: Max 30kg, No Upper Value Limit (or an unrealistically high limit, say $20k) Does anyone know how to add this functionality, or perhaps know of an existing (& compatible) PS 1.6 module that does this? All help appreciated!

I believe they were probably linking to the thread that contained this comment. Just in case this link at some point gets broken too, here is what it suggested: > alwayspaws if i recall right you are using transformer theme you can actually just use CSS to hide the fields 🙂 > Go to Modules >> Theme editor >> Custom Codes >> And add this below to Custom CSS Code > .account_creation .date-select { display: none; } > Since DOB is not required field this should not give any issues at all. Credit to @bzndk for the great solution. Edit: Full solution for TB 1.0.8 (may work on other versions too) is here:

Interesting, it was disabled on my profile as well. I haven't been around much lately so I only noticed it now. New forum looks great @lesley! Still working on the automation to get my first store launched. If only I didn't have so many day to day things to take care of.

Also worth noting is that PrestoChangeo has a $75 module to fix this, and it been tested for compatibility with thirty bees. The PrestoChangeo solution is certainly more complete than the free solution and is probably worth the $75 for most people.

This is also something that concerns me as I will be making heavy use of attributes. I found this post on the PS forums which has a link to a free module that claims to solve this problem. The caveat is that it only works for attributes contained within drop-down lists. Still, it's free instead of 60 Euros... Hopefully it works with thirty bees.

@violinparts said in Setting up elasticsearch module: It's clear to me you are the one without common sense. We took a vote, you lost. You're also the one who screwed up the free help you were getting. I guess you can work it out on your own or you can pay someone.

@doclucas It would seem so. Some people really have no common sense.

@violinparts said in Setting up elasticsearch module: What manners? It does not make any sense. Did your parents not teach you basic manners when you were a child? Someone has taken time out of their day to help you solve a problem. The very least you can do is to say thank you when they reply and upvote their helpful messages. Instead of just replying "Ok" you should say something like, "Thanks, I'll check into it." or "Thanks for your time. I'm still not sure about...." or "I appreciate your help" or anything else that shows a little graciousness.

@violinparts said in Setting up elasticsearch module: wonder what you are talking about now Manners. When someone is helping you it’s nice to upvote their comments and to say “thank you” as you go along. Alternatively you can always pay someone to help you but even then employees tend to do better work if they feel appreciated.

@violinparts said in Setting up elasticsearch module: How to replace the word "manufacturer" with "brand" in elasticsearch filter? Didn't find in translations. Future version Must never use the word "manufacturer." Manufacturers of one product line can be one, two, several or more. They can be in China, Poland, Vietnam, etc - anywhere in the world. It's impossible to know. What matters is brand - again Brand. Who, where a product is manufactured, no one gives a shit. This is a long running issue with Prestashop that has been inherited by thirty bees. There is nowhere to add "Brand" info for items but they have "Manufacturer" info. You can change the terms in the translation files. One PS discussion about this is here.

@doclucas said in Setting up elasticsearch module: Thanks @violinparts @dosbiner I have installed Elasticsearch version: 5.6.10 and it now indexes fine in the BO. I think it's extremely important to write that it is only compatible with ES v5 and is not compatible with v6, both on the module download page and inside the module page itself (in the BO). I believe the PS module was written to work with ES 5.4 (used by Cloudways) and ES 6.0 as those were the two commonly available versions at the time. At one point I had an ES 6.0 server set up for testing purposes and it worked okay. I don't have it running at the moment though so I can't test further. Maybe @lesley can comment on the expected compatibility?

@doclucas said in Is thirty bees dead?: I could find 3, all paid (yeah, not cheap), but at least one of them seems pretty impressive to me, with cron options and additional features: https://addons.prestashop.com/en/search?search_query=elasticsearch Why do you think none of them is as good? There was a lot of discussion about this while the ES module was being developed but I don't have the time to dig through a year of forum posts to find the relevant ones. :( From memory there were a few issues: One was that the available modules do not offer faceted search which is the ability to filter search results by selecting options listed down the side of the page. Maybe you only want blue items, or maybe in a certain price range. You may have used this on sites like Amazon before. The free PS module, BRAD does have faceted search but BRAD isn't really supported and there are quite a few bugs. It's fast but not perfect. Another issue was the way the queries were sent to the ES server and then how the results were managed. From memory there is an easy way to do this that is slower and a somewhat more complicated way to do this that is much faster. The thirty bees module uses the faster way. There was more that was discussed as well, if you dig through the various Elasticsearch threads on this forum you will find the original discussions. Unfortunately @mdekker is on a leave of absence right now or he would be able to come in and explain things in detail. (You're missed @mdekker, I hope all is well and that you return soon!)

There are PS1.6 modules available for elasticsearch. One is free and one is very expensive. Neither is as good as what @mdekker created for thirty bees.