Jump to content

Welcome, Guest!

By registering with us, you'll be able to discuss, share and private message with other members of our community.

Leaderboard


Popular Content

Showing content with the highest reputation since 07/13/2019 in Posts

  1. 7 points
    I uploaded a new Prestools version: 1.24n. It contains a new version of the image plugin too. The new version fixes a few issues with image edit: - you could not add an image to a product that didn't have any images. - when you marked a newly added image as cover it wasn't registered as such. As a consequence the product ended with no cover and you didn't see an image in the backoffice product list. - when you made the image field editable and the cover image was not the first one it displayed on the first position the cover image too. The editing is now more wysiwig as it makes that you to always have an active cover product. If you find any more problems please let me know.
  2. 6 points
    UPDATED May 10. Theme file added for download Github link with latest changes. https://github.com/toplakd/thirtybees-modifications community-theme-modded.zip
  3. 6 points
    @rubben1985 gave me access to his back office, so I had a look at the issue. Indeed there was some weird stuff going on. For example, cache was not flushed when you clicked on Clear cache in Performance tab. My investigation showed that this problem was caused by missing /cache/smarty/cache directory. Recreating this directory using ftp seems to fix the issue (pending confirmation from @rubben1985) Thirtybees codebase never checked existence of this directory, so this issue is hardly 1.1.x injection. But it's an issue nevertheless -- the system should recover from this situation. The fix is already committed in bleeding edge
  4. 6 points
    New: the Image Edit plugin. It enables you to add and remove images in the product-edit page. You can also change their order and choose the cover image. It looks like this: The "X" button allows you to delete. Right below is the field for the cover selection. You can add images both by clicking the add button and selecting a file and by drag-and-drop. Changing the order goes by drag-and-drop too. As usual in Prestools all changes are only implemented after you submit. When you add an image it is uploaded to a temp directory below your Prestools directory. When you submit it is moved below your /img directory. Image (re)generation of formats like 123-small_default.jpg does not take place. You will need to that separately in Prestools or the Thirty Bees backoffice. As usual with new modules this one will be free to download for a few days on this location. People who have bought the full Prestools package can just download the latest version. It is included there. Note that this will only work on Prestools 1.24l and newer.
  5. 5 points
    These recommendations were discussed many times on the forum, for example this flame from two years ago. Unfortunately, not much was done in the last two years, other than code implementation. Stable and nice codebase is important, of course, but it's not what will attract users. When I look at the last two years, I see a lot of wasted opportunities. There should have been massive campaign to attract ps16 merchants when support for their platform was ending. There was none. Third party developers with ps16 modules should have been contacted, and some incentive should have been offered to them in return for maintaining their modules compatible. For example, their modules could have been highlighted in the 'modules' page in your back offices. Again, this didn't happen. And since then, most of these developers either completely migrated to ps17 platform, or quit the presta-world completely. And there are so many other things that could have been done. Instead, the platform stagnated. The only area that was worked on was codebase. And that just not enough. Two years ago, I wrote: I wonder how accurate builtwith.com data are - they track ~576 sites Now, this web tool tells us there are 509 active thirtybees sites. These two years should have been the best time for attracting new users. Instead, we lost some. This inactivity is what drove my decision to quit. I have no problems working for free on an open source platform. I have problems seeing this work being wasted. If the situation changes I might revert my decision. But I don't see how it could change, unfortunately. Also - I don't want to 'take over', as some of you suggested. While I'm flattered, I don't want to do that. I would really hate doing all those things that I've just complained above. I'd be terrible at that, I'm sure.
  6. 5 points
    I've just released new version 0.2.0. Here are the main features: 1) you can now choose between unified block with both shipping and payment options, of have these two sections rendered separately. Unified block: Separate blocks: 2) There's an option to render logos for payment and carriers 3) Initial support for form extension. Third party modules can now extend checkout forms, and add their own fields (or even sections). For example, my premium version of revws module (in upcoming version) will render checkbox to ask user for consent to send review request. And of course, there were some bugs fixed. You can download the new version from my site
  7. 4 points
    I am generally very open about things with our community. Some people might not like the answers I have given at any given time, but I have always tried to be forthright with them. I am unsure where you recent hostility against me or thirty bees has come from. You contacted me last year about partnering on a project roll out. You asked several different questions / opinions and I told you what I thought. You mentioned you might want to invest in thirty bees, but never anything past that, until you contacted me a week or two ago just to tell me to fuck off basically. You were mad because your bug reports were not handled satisfactory. Here is the last conversation for the people reading and wondering. But yes, I am up for whatever works, as long as it works for our mission and our community. I am not up for scaling module prices based on how much business a shop is doing. I am not for selling code that thirty bees produces. From the start of this company / project those have been the values. I might not be capable of piloting the company or project much longer, but I am not going to turn it over to someone that will exploit the community. These people have been awesome to me and thirty bees over the last several years and I am trying my best to leave them in capable hands with my integrity intact.
  8. 4 points
    @datakick I was going to write you in private but I think this community deserves to give their opinion but also to know what others think too. I honestly think that you (and the rest of the actual actives contributors), should "take the the helm" and create the new staff. Without all of you (and specially you in the last months) there is not TB because community is great but we need someone more involved than standard merchants. Community growth around a solid core. I can understand Lesley is ill and we hope he will recover soon, but it is also true that we are in a professional environment and any project needs a leader. Why not you? You have been the leader anyway this last period. It can be at TB or a TB fork if necessary. I am not developer, but I am quite decent in management and marketing (that was always the biggest problem for TB growth). I would gladly give my inputs (there are so many easy things to fix in the communication and branding...), even collaborate with designers from my team for free. Not talking about intensive work, but more that testimonial, for sure. If you think about the possibility, I think could be an inflexion point in TB history
  9. 4 points
    I am not really part of this team. I don't have any shares and I am also not paid in any means. In fact I am a merchant that contributes more to this project than most others do. I have asked Lesley in private, how is it going and he didn't respond. So either he needs recovery time or he just doesn't want to talk about it. I understand, that you get a little nervous, when the initiator of the project is absent. On the other hand, you could use the time to improve your store or to contribute in some way. As I said in another thread: bleeding edge right now is stable like no other tb/ps software before. In general we (merchants) expect this project to go further. But we can not even find out together, what the most important todos are.
  10. 3 points
    Since about a year, these do get removed by the migration module. https://github.com/thirtybees/psonesixmigrator/blob/master/classes/AjaxProcessor.php#L878-L880
  11. 3 points
    Who cares if it is late a few weeks? It is a small, dedicated team. I would rather it be late than buggy. Worst comes to worst, you can always painlessly experiment with the 1.1.x version. We are getting more than I ever got under the old model. I can be patient. I would rather have something that works than a mountain of hidden bugs like we used to get... The team here has its heart in the right place. They are responsible and meticulous. I am willing to be patient. They will let us know when they are ready for prime time.
  12. 3 points
    It's not -- the format is hardcoded in smarty template. I managed to reproduce the display tax problem, and hopefully fixed it. Please download new version 0.6.1 and let me know if it works for you
  13. 3 points
    New version 0.4.0 has just been released New functionality - Persistent storage for entry form - customers can now leave checkout or refresh the page, and the data they have already entered will be recovered - Ability to remove products from cart, or edit their quantities Bugfixes - fixed problem with displaying payment name in collapsed mode - display placeholder when no shipping / payment is available
  14. 3 points
    Thanks for your post! Thats exactly how I think about it, too!
  15. 3 points
    Definitely not. I was just answering your question why this happens. It doesn't mean that this is correct behaviour 🙂 Moreover, the two installation methods -- installing from zip file and installing from remote repository -- should be unified and work in the same way. Right now they use different code with different results. For example, if you update module from thirtybees repository, its directory is deleted and then re-created from scratch. This means that *any* assets that module might store inside its directory are lost (for example uploaded files). I'll create new github issue for this EDIT: actually there is already an issue for this: https://github.com/thirtybees/thirtybees/issues/522
  16. 2 points
    Hi all, we have some news on the future of Thirty Bees! https://forum.thirtybees.com/topic/4194-thirty-bees-future-announcement/
  17. 2 points
    @datakick New Bug with TB 1.1.x and Panda: Got a strange new bug after I updated my 1.1.0 site with Panda to latest TB Bleeding edge: On Product list / Category page: For some reason the Left Column disappears when a Sub Category is selected. Main Categories are fine. I noticed that the var left_column_size is set to 0 instead of 3. Weird, as this worked before the update. Because I know the Left Column should always show on the Category page, I've created the following to 'fix' it, albeit temporarily. And obviously this isn't a real fix, as it doesn't address the cause. Just helps for now. <!-- /// No Left Column on Subcategory Fix /// --> {if $page_name == "category" && $left_column_size == 0} {assign var='left_column_size' value = 3} {/if} <!-- /// *** *** /// ---> Insert the code before: {if isset($left_column_size) && !empty($left_column_size)} Thought I'd point this out. I have notified @Jonny as well.
  18. 2 points
    @Traumflug There is also another thing. There are not many people wanting for TB to rise for one simple reason: Having to maintain compatibility for 2 shops. A lot of devs dream of 1.6 being put to rest (yes, they also hate Prestashop 1.6), as 1.7 takes over. Maintaining backward compatibility with 1.6 (and/or TB) is additional work. So basically it's not personally aimed at TB or you guys, it's aimed at lowering costs and maximizing income. Because of state of 1.7 I'm seriously thinking about changing my business model. I don't want to be held responsible by my clients for bugs in 1.7. Still, my clients I migrated to TB expect FROM ME modules for prestashop to work or fix them. Their mentality is like: "If I had Prestashop, it would surely work". So either I go on war with them or comply with their insane requests. It's a shame, but this brings a lot of regret to devs like you and me. PS: Also, when I recommend thirtybees and explain all differences, I'm being held responsible for recommending it to clients. Some people are insane, and blaming their decisions on others. And saying "Prestashop would be better". That's where "brand" part comes in.
  19. 2 points
    OK.. so since january 2nd we have NO news from Him.. what to do ? Where are you going Datakick.. may I follow you ? LOL more seriously.. let's start or continue with a fork of TB with people really motivated, why not ?
  20. 2 points
    @Chandra you are mixing two things. The settings on Order Statuses has impact on 'Order Status Changed' email only (ie. Awaiting bank wire email) What you are talking about is the 'Order confirmation' email, and that has nothing to do with order status. This email is always sent, and it contains all current information available. I guess we could change the current semantics, and attach invoice to 'Order confirmation' email only if current order status has the send invoice checkbox enabled. However, I'm sure there would be plenty of merchants that would not want this behaviour by default.
  21. 2 points
    For hunting down small bugs (or my mistakes) I always have 3 installation of thirty bees on the server. All latest bleeding edge One is live, one is exact copy of live shop for testing, and 3rd is always the clean stock thirty bees installation. So if something does not work on live but it works on stock install, i can compare testing shop with clean stock, and make adjustments or fixes until it works 100% like stock. Only after that, I apply it to the real live shop.
  22. 2 points
    Hi. Yeah, but you don't need Warehouse 😀 Thankfully, one of the best and insanely feature rich and customisable PS themes, Panda, has been updated for TB and is actively maintained by the Theme developer @Jonny Which is great and it gives you the "AAA" quality theme that you need for TB that is actively maintained and updated.
  23. 2 points
    So I finally got this sussed! Go to Positions ->Click Paypal Modules and this brings up all the hooks associated with. Under DisplayFooterProduct, which hooks modules to the front office product page and this is where you unhook the Paypal module and it removes it from the product page! 😎
  24. 2 points
    Hi, Another forum where a person arrives with his problem, asks for help, finds the solution on his own, deletes his question and asks to delete his Topic. Yet, this person comes to the forum to find answers to his questions, but if everyone asked to delete his Topic, what would become of a forum? 😢
  25. 2 points
    you need to go there, and turn on (green check) the left column on Index
  26. 2 points
    Hi As we needed dynamic URLs in the Menu, CMS pages and TB HTML Block, and TB doesn't have this functionality natively out the box, I've decided to write a little 'workaround' / solution to try and fix this issue (at least temporarily until TB one day does this natively). Solution: Static URLs to Dynamic URLs maker + Smarty Tags in CMS, Menu and TB HTML Block The problem with static URLs is that they are a pain to maintain especially if everything you added to the site in the CMS is saved as a Static URL... So if you need to move the site from Local -> Staging -> Live and to another domain, you're going to have a bit of a problem. I've had to 'fix' this for the Top Menu, CMS page and TB HTML Block This solution also allows you to 'call' Smarty variables in the Admin BO CMS, Top Menu and TB HTML Blocks. How does it work and how to use? Add the code to either blocktopmenu.tpl, blockcms.tpl in your template file or tbhtmlblock.tpl - replacing the content generator: either {$MENU} or {cms->content} or {$customblock} Specify on which page (Menu/CMS/TB HTMLBlock) the code needs to appear {$MENU} or {cms->content} or {$customblock} The code replaces the "content generation" for the target page / section You need to specify the Static URLs you want to replace (remember to do this wherever the script is added). Static URLs normally for Local, Staging or Old Live addresses (can add 3 more if required) If you know what the Staging and Live Locations are going to be beforehand, then you do not need to update this again after the site has been moved / re-deployed. You can call a predefined Smarty variable in the Menu, CMS or TB HTML Block using the Smarty tag identifier {$content_dir} for example. When you add a link, you can either just use the full static path (as previously specified), or use the Smarty variable {$content_dir}blog/link-to-page If you add an image via the CMS RTE or even a link to an image, it will identify the Static URL and replace it with the Dynamic URL as set by $content_dir. So if you move the site to another address, all your Static URLs (if specified in the Menu, CMS or TB HTML Block) will be automatically updated - with no maintenance required from your side. Credits: This would not be possible without FullCircles - who way back in 2014, came up with the base solution. I've just modified it a bit. https://www.prestashop.com/forums/topic/372976-global-smarty-variables-used-in-cms-content/?tab=comments#comment-1855331 https://www.prestashop.com/forums/profile/720051-fullcircles/ Datakick supplied the correct Smarty variable name to be used as "BaseUrl" $content_dir Hope it helps. Instructions: Insert the following code in either "nameoftemplate/" blocktopmenu.tpl or blockcms.tpl or modules/tbhtmlblock/views/templates/hook/tbhtmlblock.tpl And make sure that it replaces the "page content generator" {$MENU} or {cms->content} or {$customblock} Configure as mentioned previously I've included a 'tester' code you can add to a CMS page to test that it's working properly Main Script (for tpl files): {* /// STATIC TO DYNAMIC URL MAKER - with 'Dynamic Tags' / 'Fake' Smarty Variables Functionality /// * v1.1 - last updated: 11/10/19 * To be used on BO Admin pages where Dynamic URLs are required * Automagically Replaces Static URLs on Runtime with 'dynamic' URL based on $content_dir * So if your site is on Local, Staging, Live or has been moved, this script has you covered * If you know what the Staging and Live Locations are going to be beforehand, then you do not need to update this again after the * site has been moved / re-deployed. * Just remember to change the 'Static URL Sources' whereever you've included this script * * CAVEAT: This does not save the updated safe URLs, it just replaces them on run-time for the front-end. * CAVEAT: The links and images pointing to the old URLS will still be 'broken' in BO Admin CMS until manually updated. * * Allows for the use of limited Smarty variable 'printing' within the 'code location' (CMS,TB HTML Block,Menu,etc) * I.e. using {$content_dir} in a CMS page will now work (like in a TPL file) * This code should be placed on the Target location's TPL file like "blocktopmenu.tpl, blockcms.tpl" within your theme * or for the TB HTML Block: modules/tbhtmlblock/views/templates/hook/tbhtmlblock.tpl * The Code Location must be changed accordingly below * Extendable by adding more Smarty variables or code locations * Note: If you want to have 'BaseUrl in a TPL page, just use the normal Smarty var $content_dir as this script is built for BO Admin pages * ie. <a href="{$content_dir}info/link-to-cms-page">cms page link</a> * * Credit to FullCircles for initial 'BaseURL' solution back in 2014. Without you, we'd be f'ed. Thanks bro :D * https://www.prestashop.com/forums/topic/372976-global-smarty-variables-used-in-cms-content/?tab=comments#comment-1855331 * https://www.prestashop.com/forums/profile/720051-fullcircles/ * * Credit to Datakick for the Smarty variable for the correct site domain path: $content_dir * * // To use: * Adjust the settings (values) below and add Smarty variables etc if you require * Replace the page's content generator tag, i.e. $cms->content, with this entire script block. * Refresh Cache * Static URLs as specified should now be replaced and 'dynamic' tags should be displayed * Note: the URLs come with a trailing slash (pagename/) so keep that in mind * *} {* /// Initial build, do not modify this one - Creates 6 available Static URL slots if you need them /// *} {assign var=s2d_specifysourceurls value=['placeholder-donotchangethis0','placeholder-donotchangethis1','placeholder-donotchangethis2','placeholder-donotchangethis3','placeholder-donotchangethis4','placeholder-donotchangethis5','placeholder-donotchangethis6']} {* /// /// *} {* /// Set Static URL Sources (array with 3 values for now - supports up to 56): /// - Remember to include trailing slash (pagename/) - Example array currently set for Local, Staging, Live Old - Example: {$s2d_specifysourceurls[0] = 'http://localhost/siteaddress/'} *} {* /// Set Local Address Source - Change this /// *} {$s2d_specifysourceurls[0] = 'http://localhost/siteaddress/'} {* /// Set Staging Address Source /// *} {$s2d_specifysourceurls[1] = 'http://www.stagingaddress.com/'} {* /// Set Old Live Address Source /// *} {$s2d_specifysourceurls[2] = 'http://www.liveaddress-old.com/'} {* /// Extendable if required - up to 6 available slots: (0-5) //*} {* {$s2d_specifysourceurls[3] = 'http://www.emptyslot4.com'} {$s2d_specifysourceurls[4] = 'http://www.emptyslot5.com'} {$s2d_specifysourceurls[5] = 'http://www.emptyslot6.com'} *} {* /// Set Dynamic URL source, leave as $content_dir for dynamic URL. Only 1 URL required /// *} {assign var=s2d_url_maker_target value="{$content_dir}"} {* /// Set Code Location /// - Set the Code Location by changing the value below accordingly: - CMS page: {$cms->content} - TB HTML BLOCK: {$customblock} - MENU: {$MENU} *} {assign var=s2d_url_maker_code_location value="{$MENU}"} {* /// Generator that does the work: /// - You can add more variables to the beginning of the source and target arrays below if required - Default list of available Smarty variables: - $content_dir, $base_uri, $base_dir, $base_dir_ssl, $img_dir (template img dir bytw), - $page_name, $logo_url, $shop_name, $shop_phone *} {* /// Generator /// *} {str_replace( array('{$content_dir}','{$base_uri}','{$base_dir}','{$base_dir_ssl}','{$img_dir}','{$page_name}','{$logo_url}','{$shop_name}','{$shop_phone}',$s2d_specifysourceurls[0],$s2d_specifysourceurls[1],$s2d_specifysourceurls[2],$s2d_specifysourceurls[3],$s2d_specifysourceurls[4],$s2d_specifysourceurls[5]), array($content_dir,$base_uri, $base_dir, $base_dir_ssl, $img_dir, $page_name, $logo_url, $shop_name, $shop_phone, $s2d_url_maker_target,$s2d_url_maker_target,$s2d_url_maker_target,$s2d_url_maker_target,$s2d_url_maker_target,$s2d_url_maker_target), $s2d_url_maker_code_location )} {* /// *** *** /// *} Tester Code: <h2>Static 2 Dynamic URL Maker with Limited 'Smarty' Tags in CMS Tester</h2> <br/> <b>Static URL Locations to be updated:</b> <br/> <br/> <b>Local: </b> http://localhost/siteaddress/ <br/> <b>Staging: </b> http://www.stagingaddress.com/ <br/> <b>Live old/prev: </b> http://www.liveaddress-old.com/ <br/><br/> <b>Smarty variable print:</b> <br/> <br/> <b>$content_dir:</b> {$content_dir} <br/> <b>$base_uri:</b> {$base_uri} <br/> <b>$base_dir:</b> {$base_dir} <br/> <b>$base_dir_ssl:</b> {$base_dir_ssl} <br/> <b>$img_dir:</b> {$img_dir} <br/> <b>$page_name:</b> {$page_name} <br/> <b>$logo_url:</b> {$logo_url} <br/> <b>$shop_name:</b> {$shop_name} <br/> <b>$shop_phone:</b> {$shop_phone} Script not active yet: Script activated, Static URLs + Smarty Tags updated + Menu Links updated
  27. 2 points
    And now since I know that Petr has an adress in L.A. 😊 while doing tests I can tell you that our orders for Sep. and Oct. increased three times while the numer of open carts decreased by two times in comparission to last year. I am confident that this is mainly due to Petr's CHEX module. Thank you to all who tested and for Datakick's constant development of his modules.
  28. 2 points
    In general I rewrite quite a lot of functions, since I became a much better coder than I was back then. This is changed: Expiration of loyalty points (but not the history way) Stats for total value of outstanding loyalty points Functionality to hide players from leaderboard Functionality to show possible actions in FO I am thinking of: adding email support referral/affiliate functionality better handling of history (for example for product returns, cancelled orders)
  29. 2 points
    Haha very funny, that yesterday I tried this 😂 Search in your theme for product-sort.tpl and add: <option value="date_add:desc"{if $orderby eq 'date_add' AND $orderway eq 'desc'} selected="selected"{/if}>{l s='Newest first'}</option> Please respond, if this works out well for you.
  30. 2 points
    I have tried on my local installation running 1.1.0 to create many features: 356 features 201332 default feature values 604002 feature value lang This is much more features than you have (according your first post). The product page is indeed sluggish -- the readystatechange event handler run for 3 seconds, and the page is non-responsive until this finishes. Moreover, switching to Features tab takes 4 seconds, even after the page loads. This was on chrome. When I tested on Firefox, I got worse measurements - it took 8 seconds to open features tab. The same results are in 1.0.8. So (unfortunately), this is nothing new. It's indeed inherited limits of thirtybees platform. When I tried with the less features (180 features, 4800 default feature values) it worked quite fast, thought. There was some performance degradation, but it wasn't really noticeable. My initial investigation shows that the problem is in huge amount of DOM nodes. Basically, for every feature and every feature value, DOM nodes are created and inserted into the page. Browser can't handle so many of them on one page. There is no quick fix -- the product page needs to be reworked to use some data lazy-loading (Instead of displaying 200k DOM nodes upfront, we would only display 356 features and load feature value only when necessary via ajax). But, unfortunately, this is a big change. It's not realistic to expect it anytime soon. Sorry for the bad news
  31. 2 points
    @led24ee Assuming those modules files are on your server, and you just really have to have these modules, and cant wait for the developers to change it, you can do this.... All three of those modules have the same problem and need the same fix. edit the main .php of each module, for instance in the Tawk.To module you would edit tawkto.php, and look for something like: $this->tb_versions_compliancy = '1.0.x'; now replace that line with the following two lines: $this->tb_min_version = '1.0.0'; $this->tb_versions_compliancy = '> 1.0.0'; Do that in the main file of each of those modules, and it should let you install them. edit: I did a github pull request for all three of these modules, seems to work for me anyways....
  32. 2 points
    Here's the last chunk for the time being: beesblog Changed default image sizes. Removed Google+ support, this community vanished. Added support for updateFriendlyURL(). Code maintenance. blockbestsellers Actually two releases, 2.2.0 and 2.2.1. The latter restores compatibility with community-theme-default and themes derived from this. Support for the new hook displayHome. Shows just 4 products by default to appear more pleasing on theme Niara. Code maintenance. blockcontactinfos Preserve newlines in the contact address. Before one could enter them on the configuration page, but front office would show all in one line. blocknewproducts: same as with module blockbestsellers. blocksocial Pre-fill some fields on installation. Code maintenance. blockstore Code maintenance. blocksupplier Code maintenance. coreupdater (yet another release) Fix configuration page display on wide screens. homeslider (yet another release) Explain image sizes on the configuration page. statsmodule Additional section Stats for Groups. Fixed uninstallation. Code maintenance. And last, not least, a new module: HTML Block.
  33. 1 point
    Das ist kein Fehler, sondern völlig richtig so. Da braucht man auch nichts "reaktivieren". Steigt die Mehrwertsteuer wieder, wird der Steuersatz erneut kopiert, alles ist prima. Keinerlei Grund, in der Datenbank herum zu fummeln.
  34. 1 point
    Who is chasing? Who says you have to be?
  35. 1 point
    Hola a todos, después del "Prueba y Error" unas 5.000 veces logré resolverlo eliminando la mayoría de columnas y atributos, dejando solo las 4 o 5 proncipales u obligatorias y cargando el CSV guardado como excel, es una tontería pero me generaba error al usalro separado con comas, como lo sugirió Wartin, en este caso me funcionó el: menos es más!!!
  36. 1 point
    It's said to generate a couple of warnings, but work flawlessly.
  37. 1 point
    Problem solved. I have been trying to get all my sites to be compatible with php 7.3 as was still running on 7.1 which is no longer supported. I had to install ZipArchive on php 7.1 before I could migrate from PS to TB. Yesterday after testing everything locally I switched the live server to 7.3 and it didn't reinstall the zip archive. Now able to install modules again.
  38. 1 point
    Do you see Edit button on the right? Try clicking on it. 🙂
  39. 1 point
    Feel free to modify the email template to whatever you need.
  40. 1 point
    create a file "ContactController.php" and place it inside "override/controllers/front" folder. the file should look like this. <?php class ContactController extends ContactControllerCore { public function postProcess() { $email_address = Tools::convertEmailToIdn(trim(Tools::getValue('from'))); $emailParts = explode( '@', $email_address ); $emailDomain = end($emailParts); if ($emailDomain == 'qq.com') { header('HTTP/1.1 403 FORBIDDEN'); header('Status: 403 No China here!!!'); header("Location: https://www.qq.com/"); } return parent::postProcess(); } } i think it should work, don't have time to test it right now. you should delete cache/class_index.php as well
  41. 1 point
    The checkout page he is showing is what Niara does on mobile. It just uses the desktop checkout screen, and mobile users have to swipe back and forth to see anything or make any changes.
  42. 1 point
    Hello, There is a news from Stripe: Strong Customer Authentication is a new European regulation coming into effect on September 14, 2019, which will require additional authentication for many online payments. You can learn more about SCA and the latest regulatory requirements in our guide, or in our upcoming webinar on March 27, 2019. Read our guide to learn more about what to expect from SCA March 19, 2019 source: https://stripe.com/blog/strong-customer-authentication-mar-2019 https://stripe.com/guides/strong-customer-authentication similar thing is regards Paypal and other payment gateways: https://www.paypal.com/uk/webapps/mpp/psd2 added: Currently, the most common way of authenticating an online card payment relies on 3D Secure—an authentication standard supported by the vast majority of European cards. Applying 3D Secure typically adds an extra step after the checkout where the cardholder is prompted by their bank to provide additional information to complete a payment (e.g., a one-time code sent to their phone or fingerprint authentication through their mobile banking app). 3D Secure 2—the new version of the authentication protocol rolling out in 2019—will be the main method for authenticating online card payments and meeting the new SCA requirements. This new version introduces a better user experience that will help minimise some of the friction that authentication adds into the checkout flow. Other card-based payment methods such as Apple Pay or Google Pay already support payment flows with a built-in layer of authentication (biometric or password). These can be a great way for businesses to offer a frictionless checkout experience while meeting the new requirements. https://stripe.com/guides/strong-customer-authentication?utm_campaign=scamar2019&amp;utm_source=blog&amp;utm_medium=stub I don't see the modul support 3d secure 2. https://stripe.com/guides/3d-secure-2 Will you add support for 3d secure 2? Some more info: VISA and MasterCard will be mandating that the new version of 3D Secure (version 2.0) should be in place for issuers and merchants by April 2019 in preparation for the mass adoption in September 2019. https://www.barclaycard.co.uk/business/news-and-insights/guide-to-strong-customer-authentication
  43. 1 point
    Yes you can, in the customer tab, customer services. In customer / contact persons you can specify the to addresses
  44. 1 point
    Thank you very much @musicmaster, I solved, you gave me the opportunity to better understand the problem. I checked the ps_tab table and actually the tabs: - AdminAccess - AdminTabs - AdminEmployees for some strange reason they were no longer present. In this way I added them by hand via database and now they are again present in the menù and accessible through the control panel.
  45. 1 point
    New version 0.6.0 has just been released with following new actions you can use to create your rules: Remove customer from group Associate product with category Remove product from category You can now create rules like add product to Featured category when its price is > $100 remove product from category Featured when it is sold out When customer purchase product Club membership then add customer into group Premium,and remove customer from group Customer
  46. 1 point
    Hi Dan, We are creating orders in our backoffice, we use TB 1.08, the button is in the right top of the order overview screen. Also changing orders is no issue in our shops. Maybe it has something to do with user rights. Screenprint is in Dutch but you should see the same in any language.
  47. 1 point
    There are three important things about backups: They must be automatic. They must be regular. They must be stored away from the server you are backing up (offsite). Personally I do this with a custom script that dumps the database, compresses it, and downloads it to my local servers. The local server is backed up with Crashplan so my backups are stored in 3 places: On the source server (not in the public_html folder!), on a server in my offices, and on Crashplan. The entire site is backed somewhat less often (weekly generally) as backing up a complete site with all photos tends to eat through bandwidth. There are pre-made solutions that will do the same thing. Some of them back up to S3 as @Factor showed above. Others back up to Dropbox which can be a cheaper option if you are using Dropbox already. All the above solutions can be used together with your web host's backup system for even better protection.
  48. 1 point
    This is probably related to new version of smarty. Similar problem was in community theme / niara, and it was fixed by simply moving the block of code to the proper place. If you send me the module, I can fix it for you
  49. 1 point
    You have good speed on your site 🙂
  50. 1 point
    @datakick - your module says it will work with CSV files soon. Can you say when? Looking to import stock levels and prices only (in thirtybees and prestashop) and another prestashop instance that would also have lots of combinations
×
×
  • Create New...