Dolfijn

Updating from TB 1.1 to 1.5 I ran into trouble because in the old environment you can use non encrypted SMTP while, if you do so in TB1.5, you are using TLS anyways due to the default enabled AutoTLS function. So, if your email provider supports TLS, it will be selected in the negotiation process. So far so good. But my provider happened to have some config problem with its certificate. So, email using TLS doesn't work, while you are thinking that you are not using TLS. Was very confusing for me. Because it will take a while for my service provider to sort things out, I changed the default to : public $SMTPAutoTLS = false; in PHPMailer.php. Shouldn't it be an option, to facilitate these kind of situations?

I finally opened a file and wrote some php %variables to file. It works.. $file = fopen(_PS_ROOT_DIR_ . '/myLog1.txt', 'a'); $my_own_message = strval($idShop); fwrite($file, $my_own_message); fclose($file);

The picture explains it all. I solved it by overriding style in global.css. But should this not work out of the box? I added the following override to create some extra padding: /* Override padding-left*/ .col-xs-12 .col-sm-12, .col-xs-12 .col-sm-4, .blockcmsinfo-block .col-xs-12 col-sm-4 { position: relative; min-height: 1px; padding-left: 30px; padding-right: 15px; }

Ok, this one I could figure out by myself :-). You can adjust the aspect ratio under Preferences->Images by mutating a nice table. I discovered it by reading the PrestaShop 1.6 manual. As I don't now much of TB or PS. Is there one for TB? I searched for it first but couldn't find one?

I migrated from TB1.1 to 1.5. Now when I create a new product, its pictures have another size and aspect ratio. The old pictures all have a landscape aspect ratio and the new ones are 1:1 and bigger (higher). The two different sizes create a very chaotic visual view. I hope that I'm wrong because that would mean that I have to redo every product picture in the shop. What am I missing? BTW, I'm using the community theme.

I did that several times today but I'm glad you asked because now it helped: it works. Many thanks! At least one more issue done on my list 🙂

Yes, I see them installed and enabled. I also see the BO menu for the blog and they work ok too. I also see all the posts in the BO. Its the FO where nothing shows up.

Or has this something to do with the position page in the back office? I don't know where to start because nothing is shown.

Still looking for the cause of this problem. Which code is activated when I press the test email button in the back office? Maybe I can figure it out from there. I'm getting that desperate 🙂

I migrated from 1.1 to 1.5 and I'm using the community theme. The blog posts itself are there if you know there url's. But they aren't visible on my homepage as they where in TB1.1. I thought I used the 'Bees Blog Recent Posts plugin' for that. However, that changes nothing. What can I do? I don't see any other option in the BO.

It's a long time that I debugged PHP. I would like to do so to better understand what I'm doing wrong (as I often do 🙂). I'm running in production at a hosting provider. I will only use it to analyse backoffice code. I already switched debugging on and also did so in defines.inc.php. But a simple echo('Hello'); is never seen..? How can I do this in TB 1.5?

Yes, I'm aware, but I still don't get it going, pfff. I'm pretty sure I use correct credentials, server name, connection type and port number (I double checked it with the hosting provider). And I know the PHPmail module is flawless. I'm afraid that the problem is with what is stored in the database. There are multiple entries without shop-id. I'm using shop-id=2 (I have two shops but only use one actively). The info for shop-id=2 looks good though. I'll attach a screen shot. But those empty fields, would that be a problem? And one must be aware what shop is selected when configuring the outgoing email.

Turned out that the server name I used was not correct. Problem solved. Now I only have to fight he usual "Failed to send email: SMTP Error: Could not connect to SMTP". I used a multistore config and I noticed that in the database the shop instance specific credentials are old ones. It is not clear how that is possible but at least I know where to look 🙂

That really is helpful. I will start a chat with my hosting provider first. Thanks.

I migrated from TB 1.1 to 1.5, quite succesfully so far. I'm only lost in getting the outgoing email to work again. I configured the PHPMailer. But when sending a test email I get the following error message: Failed to send email: SMTP Error: Could not connect to SMTP host. Connection failed. stream_socket_enable_crypto(): Peer certificate CN=`*.exacthost.nl' did not match expected CN=`mail.gquipment.com' I also checked the email database settings but can't find a reference to 'exacthost.nl'. But to be honest, I don't understand what the problem is. What can I do?

Hi, I'm in the process of changing some names of blog posts. But I don't want to loose my link juice. So, how can I add a redirect to the old name / url? Must I put them manually in the .htaccess file? Thanks

I removed the plugin and re-installed it. And now it works great! Thanks for the suggestions!!

Unfortunately, i suddenly have a severe amount of spam. It makes the TB shop more or less useless. I receive several emails per minute. All by using the contact form. So, I tried installing the No CAPTCHA reCAPTCHA module. I can configure the keys and the other settings but when I hit 'save', I get the error message "public_html/override/override/controllers/front) not writable ". What I find suspicious is the double override/override directory structure. It (obviously?) doesn't exist. Also, all settings are persistent except the contact form setting. I discovered that the installer wants to write the file "ContactController.php" to this path (which is not there). If I create the missing directory, the installation error disappears, but the captcha procedure at the contact form is just ignored (but visible and also seems to work, but it just is not necessary - you can skip it while sending an email). But the recaptcha procedure is in working order at other places then the contact form (for example at customer login - also you can't skip it there). I'm running TB version 1.1.x I uploaded the module form this link: https://thirtybees.com/blog/recaptcha-and-spam/ Hope somebody can give me some hints!

Okay, and maybee, I shoulld also migrate to the latest theme anyways 🙂

It is a copy of the default theme that I used in Prestashop 1.6. After my migration to Thirtybees, I'm still using that same theme. Hopes this gives you any clue? If you need more info, please let me know.

Hi there, Last week I had a customer complaining about much higher product pricing during checkout then 'promised' in product view, caused by this problem. So, I decided to give it a try and I think I have solved it :-). Root cause is the construction of the product page which uses a table to display volume discount. In this table, some CSS attributes are used to store the volume discount prices and that values are (only) set on page creation (from the product.tpl code). And these CSS attributes are used to display the price (when in product view). That all works ok, until you add product attributes (combinations) that influence the price. Because, that influence is not reflected back in the mentioned DOM css attributes of the volume discount table. So, the effect is that you always use the price levels of the first product attribute, regardless of the actual attribute chosen by the user. What I did is add a new function (UpdateDOMdiscountPriceTable(newPrice)) that updates the table DOM elements that store the prices with the correct new price levels and call it from UpdateDisplay(). All changes are made in product.js. I attached the file for those interested. Final warning: I'm not an thirthybees expert and also not a seasoned JavaScript programmer. I also only tested it for my shop config (using attributes and volume discount using some percentage). product.js

Ok, I found it. The path for the BeesBlog module is a little different: it uses the format <my-theme>/css/modules/beesblog/views/css/beesblogstyle.css. So, my first attempt was close but not close enough. Thanks for showing the way. public function hookDisplayHeader() { $this->context->controller->addCSS($this->_path.'views/css/beesblogstyle.css', 'all'); }

Thanks for the pointer! I will start digging over the weekend :-)

I tried it: same result 😞 Can it not be that for the beesblog modules this construction of using theme related css is not implemented? Or is it some general construction that should always work? I'm not afraid to take a look at the code, just need a pointer where to start..

Link to the default css file: https://www.gquipment.com/modules/beesblog/views/css/beesblogstyle.css Link to the <my-theme> copy: https://www.gquipment.com/themes/Gquipment-theme/css/modules/beesblog/beesblogstyle.css And what the source actual blog post files uses (in its head section) and where I see that it is still using the default file: <link rel="stylesheet" href="/modules/beesblog/views/css/beesblogstyle.css" type="text/css" media="all" />