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.


Popular Content

Showing content with the highest reputation since 06/15/2020 in Posts

  1. 17 points
    Hi everyone We know it's now been a while since our first post. While we'd love to have new news to share, we're still waiting for some important documents to continue the negotiations. Someone here mentioned that buying a company can sometimes take months. Unfortunately we're seeing that this may be the case here too. We are eager to pick up the reigns and move TB forward, but will have to ask you all for your continued patience while we sort out all the details of purchasing TB. We're picking up that it could still take many weeks before this thing has been finalised. On the plus side, we do have some info to share: The Core Developer has essentially been finalised and has indicated that he is on board (subject to the sale of TB being concluded and other details, of course). We will reveal who, once everything is sorted. He will be full-time. And you will be more than happy 😉 We plan to move TB forward with continued maintenance and improvements and evolution. Making TB better, by building on its solid foundation and listening to the community. Not ripping it up and starting again. So no plans to change architecture or any crazy Prestashop 1.7 or Symfony ideas. There will be roadmaps, bug fixes, new features, enhancements, support and massive community involvement, feedback and participation. We look forward to finalising the negotiations and purchase of TB. We will provide feedback within the next few months. Hopefully sooner. In the meantime, please keep using and promoting TB. We promise an exciting future for TB ahead. Thanks for all your support 👍
  2. 6 points
    Hi all We understand that a lot of us have been wondering what has been going on and if Thirty Bees will continue. Everyone being quiet hasn't been helping, we know. Please see this post as assurance that we're on it 👍 We can't divulge much at the moment but suffice to say there is currently something in the works. We had hoped to say something to you all sooner. Unfortunately the negotiations has been taking a lot longer than initially expected. However, we feel pretty close and hope to have a proper announcement soon. One of the Core developers is involved so that should be reassuring. Can't say who just yet though. Either way, you'll be happy. For now, keep your fingers crossed, and please continue your contributions in the forum and keep using Thirty Bees. Also, please show your support by liking this post. There is a bright future for TB and we'd love to see your continued involvement, support and participation. More soon. Watch this space!
  3. 6 points
    I am not part of the new team. As the new team doesn't want to give recognition yet, I say something: Because I have private contact to all almost all big contributors of this project, I have quite a clear idea, who the new owner will be (ofc I won't reveal anything to anyone). The new team is not any mysterious investor, who is lacking of tb/ps expierence. If this deal will be done, all TB users will be better of... So please @all: relax 🙂
  4. 3 points
    Das "Sicherheitslücke" schreibe ich mal in Anführungszeichen, denn es geht um Git, das sowieso keine Sicherheitsmechanismen hat. Was nicht ist, kann auch keine Lücke haben. Es geht um das hier: Zehntausende Server deutscher Firmen von Sicherheitsproblem betroffen Es geht da offensichtlich um (zahlreiche) Server, die Git für die Versionierung des Inhalts verwenden und das Git-Repo direkt auf dem öffentlichen Server haben. Sperrt man dieses Repo nicht, ist es öffentlich zugänglich. Damit kann man das Repo auslesen, z.B. die rohen PHP-Dateien. Problem erkennen. Wie im Artikel schon steht, kann man einfach die passende URL versuchen auszulesen: https://meinedomain.de/.git/config Kommt da was anderes als 403 oder 404 zurück, ist das ein Problem. Abhilfe. 1. Das Verzeichnis /.git in Apache/Nginx sperren. 2. (besser) Das Git-Repo anderswo unterbringen und nach Änderungen den Inhalt der Webseite mit FTP oder Rsync hochladen. Natürlich ohne das Verzeichnis .git. Plesk/cPanel und einige andere haben ein Feature, mit dem man Git-Repos "live" machen kann. Jeder Commit in das Repo wird automatisch auf die öffentliche Seite hochgeladen. In wie weit diese Funktion betroffen ist, kann ich nicht sagen. Geheuer war mir das jedoch noch nie, denn beim committen in ein Repo sind Flüchtigkeitsfehler eigentlich an der Tagesordnung, das will man nicht ungeprüft öffentlich haben. Man kann das jedoch auch wie oben beschrieben heraus finden.
  5. 3 points
    Not sure how to answer this. Seen this 'Goodbye' thread, and perhaps some of these spontanously appearing chats? People talked about "plans", but actually meant their personal wishlist. A wishlist-festival! On top a couple of people who tried to switch a few simple knobs in order to pull developers in for their own favor. Working on tb means hearing complaints and unfulfillable wishes every day. "I want this!", "somebody should do that!", "why is this still not done!!1!!!" ... and all for free and yesterday, of course. Somewhere in the depths of Slack is a channel with lots of developers, most at least partially building their business on tb. Same experience there: "when will this be done?", "should do that!!", "why didn't do somebody XY already???" ... and zero contributions from them, not a single line of code. A quite daunting experience, one needs a thick skin to survive in such an environment. Ah. No hesitation to shell out money towards the old PS universe, but not even thinking about investing these bucks into the tb project. I better stay silent here. Perhaps the recent stirrup is a cleaning rain shower for the project. Because there are also these other merchants and developers. Those developers who don't complain, but show up with code. Those merchants who don't lament about free modules not working perfectly, but pay a developer to get these modules there. It's a joy and a satisfying experience to work with them and for them. Thanks to all of them, they move the project forward!
  6. 2 points
    Thanks @wakabayashi for this initiative. It will have to be thoroughly tested before it is integrated to the core, obviously. But hopefully there won't be any showstoppers. One thing that would be nice to implement together with this functionality would be an audit log, so merchants could see why, when, and by whom was the order modified
  7. 1 point
    did you empty the shop cache and the browser cache? i currently only see the maintenance mode. Your php version with 5.6.xxxx should also be updated - this gives more power. try a new update with template change. it can also be due to one or the other module. or change your settings before trying the performance again example and reload:
  8. 1 point
    You have probably enabled Advanced Parameters > Performance > Move JavaScript to the end option. If so, please file an issue in https://github.com/thirtybees/thirtybees/issues , as it would be a bug in core.
  9. 1 point
    No, it would not. It would be a huge step back - from seo perspective, from accessibility perspective,... Alt tags are very useful. If you really need them go away, you will have to edit your theme and remove them.
  10. 1 point
    SOLVED prestashop.com/forums/profile/1523298-jbw/ is working on a module to do this it says here prestashop.com/forums/topic/623011-17-save-customization-when-add-to-cart/?tab=comments#comment-3236236- ready for both Prestashops and Thirtybees. He sells finished modules for about €50 or $50 on https://addons.prestashop.com/en/2_community-developer?contributor=1035467 He might quote a price for a pre-release version, if there is nothing finished for sale yet or nothing on other download sites.
  11. 1 point
    yes, it´s like that. Maybe you find this useful (it is for other themes, but description is very good): https://answers.themler.io/articles/9064/how-to-use-google-fonts-locally
  12. 1 point
    Hi Wartin, thank you, I find it's working now, just because the difference of the mobile brower which makes the remove options become different. But now it's better than before.
  13. 1 point
  14. 1 point
    New versions 1.2.2 (free) and 2.2.2 (premium) has just been released: fixed PHP 7.4 deprecation warnings fixed database tables charset -- it's not possible to use smileys in review content fixed microdata in js code -- rich metadata were emitted only in .tpl templates. Now they are also in DOM nodes created by javascript
  15. 1 point
    Hello. Go to the product's price page. Down in the page there is an option called "Add specific price". You can choose to make a percentage discount or just a fixed discount. In frontpage you will see: new price old price
  16. 1 point
    panda is not ready for tb (1.1.x) bleeding edge only manual update im not sure if its work back update to 1.1.0 but you can try it on test store update to tb 1.1.0 -> update panda via st theme editor -> update bleeding edge
  17. 1 point
    I am on TB 1.1.0 I will do a backup before upgrading, but looks fine on my test shop.
  18. 1 point
    Some things would be easier to answer if there was more information on various questions. For example, which TB version, which template, etc. ..... Sometimes it also helps to search the forum ....... Example your question 2 see here:
  19. 1 point
    I fixed it. The install function needs to look like this, to circumvent the problem: public function install() { parent::updateTranslationsAfterInstall(false); return parent::install(); } Also submitted an issue on github: https://github.com/thirtybees/thirtybees/issues/1220
  20. 1 point
    Hello! I've just found out that the example file you can download to copy the headers for combination import is wrong. The second column should be 'Reference' and not 'Attribute'. The error was about group_type, that has to be of one of values: select, radio, color I read in a forum that Prestashop 1.6 has this problem too. I think it would be really great, to understand CSV, that the products listed to be the same that comes in TB as test products. Edit: I attached the same file, just added a new row (the second one). combinations_import.csv
  21. 1 point
    Your .htaccess seems to be fine. Robots.txt on the other way, does not cause 500 errors. Go to your Admin Panel Performance options and Enable debug mode. Then see what 500 hides from you.
  22. 1 point
    Genau. Die 19% von 2019 haben dann eben eine andere interne ID als die 19% von 2021, doch das interessiert bestenfalls Datenbank-Ästheten. Wichtig ist doch, dass der richtige Prozentsatz auf der Rechnung steht.
  23. 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.
  24. 1 point
    @Fernando In custom CSS I would go with: body.category-{id_category} .category-info { display: none;} .category-info will hide h1 and description .page-heading.product-listing would hide only h1
  25. 1 point
    Email templates don't have smarty tags. There are only placeholders that will be replaced with *static* content. This means that there can be no loops, no if/else, or other control blocks in the email templates. Which sucks. Replacement content is defined by php code. Usually it is retrieved from existing data (order reference code, customer name, etc...). In some special cases (like here), the content is generated by evaluating smarty template. Template returns static html markup, which is then replaced into the email template.
  26. 1 point
    In controllers/admin/AdminCustomCodeController.php, find the array definition starting with: Configuration::CUSTOMCODE_METAS => [ (probably line 29) To this array definition, add 'maxLines' => 100, This lets this field grow to up to 100 lines. Additional keywords: 'fontSize', 'minLines', 'showPrintMargin', 'enableBasicAutocompletion', 'enableSnippets' and 'enableLiveAutocompletion'. Same applies to the other fields defined in this controller ( = on this page) and to code input fields elsewhere.
  27. 1 point
    Thank you @yaniv14 ...that was the right solution ... great catch!!! 👍👍👍 @wakabayashiyou were very close, its me with so little code understanding not coming to the point ... thank you too! 🙏 So, if someone have a similar problem, this is the final code assembled to conditionally display my module in the right column on both cms categoriy and related cms page by given ID: {if $smarty.get.id_cms || $smarty.get.id_cms_category} {if in_array($id_cms, array(4,13,14,18,19,20,22)) || in_array($smarty.get.id_cms_category, array(2))} {$content|escape:nofilter} {/if} {/if}
  28. 1 point
    try: {if $smarty.get.id_cms_category} {if in_array($smarty.get.id_cms_category, array(2))} {$content|escape:nofilter} {/if} {/if}
  29. 1 point
    Oh nice! That reminds me on my own start with coding. Keep going 😉 I am not sure, what the variable $page_name is. Maybe this is working: {if $smarty.get.id_cms_category} {if in_array($id_cms_category, array(2))} {$content|escape:nofilter} {/if} {/if} I for myself would rather check CmsController and go for something like {if isset($cms_category) && in_array($cms_category->id, array(2))} {$content|escape:nofilter} {/if} But I haven't tested it... Just wrote it 😅 Just when rethinking it. Maybe this is not working, since it's another column. Maybe you have to use $smarty.get.cms_category. Please confirm if some of my lines are working ^^
  30. 1 point
    One more :) I had to change some things to make it work well. I'll send my files, maybe it's useful. 1) In Niara, as I said above, checkboxes didn't appear. Just after radio buttons there is always a <span> tag, unlike Community. If it's not there, the radio button is not shown. this is true in 'Accept terms', select delivery address and in carrier selection. 2) Instead of adding all the functions from order-carrier.js to order-address.js, I added those two files to the override override/controllers/front/OrderController.php public function setMedia() { parent::setMedia(); if ($this->step == 1) { $this->addJS(_THEME_JS_DIR_.'order-address.js'); $this->addJS(_THEME_JS_DIR_.'order-carrier.js'); } } 3) In Step 2, I had an error in js console with updateExtraCarrier (did't find it, as it's in cart-summary.js). I added that function at the end of order-carrier.js. It's really cleaner to have 3 steps, maybe these changes are useful for somebody using Niara. If you find something wrong, please tell me. To use it, just like parents', make backup of your files and uncompress the .zip file in your shops' / 3step-niara.zip
  31. 1 point
    moin zusammen. auf das Risiko, dass dieses Problem bereits lange gelöst ist. 🙂 Für mich sieht das nach ner Kleinigkeit im CSS-Code aus. Soll heissen: Das FAQ-Modul möchte einen breiteren Rahmen zur Anzeige nutzen, als das Theme an der Stelle vorsieht/erlaubt. Ich würde da mit den Webdevelopertools der meistren Browser mir mal den Bereich näher ansehen und feststellen, welcher Parameter, welche Abmessung da zu groß ist. die meisten Tools erlaubern auch das ausprobieren anderer Werte uns sagen Dir auch, in welcher Datei du die Ampassungen vornehmen muss. in diesem Sinne Viele Grüße Klaus / Lockesoft
  32. 1 point
    I don't think you have to worry for now. Such things just take time apparently.
  33. 1 point
    I have a fresh installation of TB that I want to use with an old db. The working installation I have has always had things wrong (ie blog not working) so I do not want the old code base. Im shifting domains completely, with a fresh code base. But I do want my old database. Whats the suggestion here?
  34. 1 point
    upload your picture use the custom code -> change background css
  35. 1 point
    Use the Core Updater module.
  36. 1 point
    There are (at least) two ways to format prices. One is the way you used. The other way can be found in back office ->Localization -> Currencies -> (edit currency). There one can turn off 'auto format' to get additional options. And even the ability to show one currency with decimals and another one without.
  37. 1 point
    As far as I know he is not. And the deal being worked out is no where around those numbers.
  38. 1 point
  39. 1 point
  40. 1 point
    It is normal tb/ps behavior because orders are tied to carrier_id and if you change carrier info (like tracking link) and want to look at old order than you can get the carrier info from that time. I really ate this behavior because I believe that the only thing matters in orders are the shipping price and this part already being saved in the order table.
  41. 1 point
    Earlier this week I was asked for advice on two vulnerabilities somebody assumed to exist on his site. Lo’ and behold, s/he was right both times. For one of them I wrote a blog post, showing how to detect this vulnerability and also a rough sketch on how to fix the server if needed. The Host Header Injection Booboo Detection is quite easy on the command line. Just run this, with <my host> replaced by your actual host: curl -v -H "Host: evil.com" https://<my host> 2>&1 | grep evil.com If the answer contains something with evil.com, the host is vulnerable. Testing should happen on all hosts in the public and with HTTP as well as HTTPS.
  42. 1 point
    If you're at fixing stuff, then one thing. Just one small thing I can't watch at... or 2 rather... Pretty please... it hurts me 😞
  43. 1 point
    Thanks a lot @datakick . I was aware about that module but even when i was adding there my copyright info, i couldn't see anything at the footer bottom . My issue was that i have had unhooked the module by accident from "Header" Hook position. Now it works perfect. Hope this will help also other users with the same issue.
  44. 1 point
    Ideally there were some standardized ERP connection protocol. Better to implement that than a connector for only a specific ERP suite. Still the idea goes into the right direction. Warehouse handling is a typical task one better outsources to a distinct software, even if it's a software developed by the same project.
  45. 1 point
    No. That's nothing critical, as its only related to "Advanced Parameters/Email/Email subject template" field, which is missing "[{shop_name}] {subject}". You have to add it manually. Now after upgrade, install core updater, update to latest bleeding edge. Apply fixes in Core Updater / Database schema (for developers) (second tab) Install Datakick consistency check module and check with that. Than you are ready to go. It's always good that you do all the upgrades and fixes on spare copy of your live shop, so you can check if everything works as it should.
  46. 1 point
    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! 😎
  47. 1 point
    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.
  48. 1 point
    Got the same issue, I got this for answer We have stopped supporting Thirtybees from Cloudways console. You can install it manually by creating a custom PHP application, then install Thirtybees in it.
  49. 1 point
  50. 1 point
    I would use the layout from the default theme as a base, then work from there. Starting from scratch is going to kill you because there is so much javascript and smarty you would need to learn to make a theme from scratch. I have a small article on how to compile with our theme, so you can make changes in the scss files and then compile them into your own css files. https://thirtybees.com/developer-blog/editing-theme-css-linux/
  • Create New...