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 01/09/2019 in all areas

  1. 11 points
    Hi everyone, I needed a way to log into my frontend as one of customers. Because I couldn't find any module that would work correctly on thirtybees, I've build my own. I have decided to release it as an open source / free module. So, if anyone need this functionality, you can download it on my store. url: https://store.getdatakick.com/en/modules/login-as-customer github: https://github.com/getdatakick/loginas
  2. 7 points
    It's long ago. I have been here. I have a lot of ToDos on my list. I have taken the most relevant out and post it here: E-Mail: Core function with core template, that just allows to put in some array with content. That way you need just one html file. Each email looks the same and modules can easily add email functionality. Images: Add a cover_2 image to getProducts function In general it sucks, the way one has to get Cover Image as a coder Customers: A way to merge two customer accounts Login as customer (there are modules, but it would be a nice core feature) -> also if there would be an easy way to use it for devs. Imagine you can send email links with default login… Addresses: Clear way to define required fields Sometimes a line more, would help a lot Combinations Allow them for bundles and probably digital products Allow different descriptions for different combinations Allow different gtin for different combinations No forcement of using default combination Products Add archive column -> merchants often don't want to delete product information, but they often have products, that they don't need for ever or at least a big time span. If you have multiple thousands products, it helps a lot for filtering. Same could be helpful for Suppliers. Remove Tags and only use Features Remove on_sale checkbox -> what is it good for? Automate this by checking special prices… Accesoirces groups -> Imagine you sell Digital Cameras. You might want to define USB Cables as accessoires. But I don't think you want to update every camera, always when you got a new USB Cable. Define a default text for available_now and available_later Allow extra fields Product Features: Multiple Features (done) Add Feature types with units or allow at least suffix and prefix value. That way filter modules can work without any issues. A filter module could than easily group values or work with ranges… Create Product Listing Pages from feature values. Imagine you sell books. It would be cool to have a product listing page for "Stephen King" with one click. Categories Allow extra fields or add at least a second description Voucher Allow to use it on product and shipping value. We sell vouchers and customer still need to pay for shipping even if his voucher value is bigger than product+shipping. That's not acceptable. Checkout: A clean checkout with ajax Adress saving Drop the two different checkout system. It's just a mess. Customer Service: Clean forms and handling in the BO. Nowdays you don't even know from where a message comes. Sometimes you get an email sometimes not. Have a good sync with email folder. My wish would be, that I can 100% handle customer cases in BO. Allow shortcodes on predefined messages and include attachments Handling returns Order Status: Remove some functionality and implement clean processes. Imagine you have a Status: "Service in progress". How could you say if the order ist paid or not? This should all be handled by order payments What is logable status good for? In my opinion an order should have two bools: paid and shipped. This should be handled auto by modules. Then you have a status canceled. The rest of status should just be for displaying infos to merchant/customer, no funcionality should be involved imo. Order Edit: Give more flexibility on invoice and delivery_slip generation. Why can't I edit an order after I genereated an order_slip. That makes no sense to me. A merchants knows best, when he needs to change/generate something. In my opion merchants should be able to generate as much invoices as they want per order. I don't see any need for invoice tables at all. I would just save a pdf. Maybe it's naive, please tell me. But I believe for us it would work perfectly. Allow to delete an order state. Sometimes you set it by mistake. Remove "tracking status" What is it good for? Remove "customer more" button. You can just click on the name… We have already too many buttons. Having to buttons to save address "Save as new Address" and "Override". Right now it's always saved as a new adress. In our case we want 90% of the times the "override". Either integrate a usable "return system" or remove it Allow to edit shipping costs (I have actually almost done it) Allow to edit payment method, allow to edit/delete payment lines (right now, you can only remove). On the otherhand the "details" can probably removed. Anybody really wanna save credit cart data on his server? Allow to add a cart rule by code. Order Add: Allow to select the real payment method. In fact you can just select the payment module… Use a real shipping free stuff. In fact it just adds an ugly voucher. Stock: Oh I better don't begin. It doesn't make sense as long as combinations and bundles aren't handled cleanly. Captcha: Simple Usage of Captcha for devs. So that not multiple captcha version are used. Backoffice List Allow better filtering (>=2) Allow better sorting (two columns) Allow custom display of columns -> every merchants wants a bit different columns. Modules: Right now you have to set controllers, where you don't wanna show a module output. In my opinion it would be better if you would set where to show. Why is Payments under modules but Carrier has it own menu in BO? What we don't need: Full Cache Page System -> TB is fast, if you aren't greedy on saving money for a good webspace.
  3. 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.
  4. 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
  5. 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
  6. 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.
  7. 5 points
    Hmm, why another fork? Wouldn't it be better to gather all forces and try make TB better instead of two different versions?
  8. 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.
  9. 5 points
    I did some investigation, and this area is pretty fuc*ed up. There is a column total_paid_real in order table that tracks how much money was actually paid. This column has been deprecated for a very long time, because this information is primarily stored inside tb_order_payment table. However, for backwards compatibility reasons, this column is still there, and thirtybees tries to keep it in sync with records in tb_order_payment table. Needless to say, it does this very poorly. The issue I've mentioned in my previous post is just one problem. There are others, for example currency issues. Some code expects this column to be in shop currency, other code expects it to be in order currency, and this can lead to totally wrong amounts (apples and oranges added together) We need to fix this. The first item is to remove all *read* usages of this column from core. Core code should always use data retrieved from tb_order_payment, and not use this deprecated column at all. Then, we should fix all *write* usages, so modules that depends on this column continues to work. Unfortunately, even with all of these, we will still have consistency issues, only not so frequently. It's just not really possible to keep things in sync. For this, we should have some scheduled task that automatically fix the data. https://github.com/thirtybees/thirtybees/issues/1161
  10. 5 points
    Here is some modifications you can do for Niara theme modify the "../themes/niara/css/global.css" file starting at line 1848 and replace all the content of the @media for mobiles by this @media screen and (max-width: 767px) { .table-responsive { width: 100%; margin-bottom: 15px; overflow-y: hidden; -ms-overflow-style: -ms-autohiding-scrollbar; } .table-responsive > .table { margin-bottom: 0; } .table-responsive table, .table-responsive thead, .table-responsive tbody, .table-responsive th, .table-responsive td, .table-responsive tr { display: block; } .table-responsive tfoot { display: inline; } .table-responsive > .table > thead > tr > th, .table-responsive > .table > thead > tr > td, .table-responsive > .table > tbody > tr > th, .table-responsive > .table > tbody > tr > td, .table-responsive > .table > tfoot > tr > th, .table-responsive > .table > tfoot > tr > td { white-space: nowrap; border-bottom: 0; } .table-responsive > .table-bordered { border: 0; } .table-responsive .unvisible, .table-responsive thead tr, .table-responsive #cart_summary .cart_total_price #cart_voucher { display: none; } .table-responsive .cart_total_price > td#total_product, .table-responsive .cart_total_price > td#total_price_container, .table-responsive .cart_total_delivery > td#total_shipping { border-top: 0; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_quantity { width: 50%; float: left; border-left: 0; border-right: 0; padding: 0; line-height: 34px; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_quantity > .cart_quantity_input { float: left; width: 55px; border: 0; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_quantity::before { content: "x"; float: left; left: 13px; line-height: 34px; position: relative; } .table-responsive .cart_quantity_button a.btn { border: 0; background-color: #eee; margin-top: 1px; } .table-responsive .cart_quantity_button a.button-minus { margin-right: 10px; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_unit { float: left; border-right: 0; } .table-responsive #cart_summary > tbody > tr.cart_item > td.cart_delete { position: relative; bottom: 109px; border: 0; float: right; margin-right: 15px; } .table-responsive #cart_summary > tbody > tr.cart_item:last-of-type { border-bottom: 1px solid #ddd; } } It will do the trick....
  11. 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
  12. 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.
  13. 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
  14. 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.
  15. 4 points
    New version (release candidate): SCA support Here's a pre-release candidate of stripe module that implements support for SCA - new European regulation coming into effect on September 14, 2019. If you are collecting payments from EU customers, you will need to upgrade stripe module, otherwise you will see a huge increase in card declines. The changes to the module are substantial -- 3 core checkout flows had to be rewritten from scratch using new Payment Intent API. Therefore, before I release this version officially, I would like to ask you all to test it thoroughly. If you find any bug or problem, please report to this thread. Download: stripe-v1.7.0.zip
  16. 4 points
    New release: 0.2.0 I'm happy to announce new version of this module. This version brings one important feature Ability to impact execution path Until now, conseqs rules were executed in parallel to the code that triggered it. It run in isolation and it could not impact execution path of the code that triggered it. Let's take Before email is sent trigger as an example. Regardless of what action was executed, the email was always sent, unchanged. We were able to create rule to log information about email, but it wasn't possible to create action to prevent email from being sent, or to modify email subject... That's not true anymore. This new version of module supports these kind of actions. New actions: Change Order Status you can create rules and change order status example use case is to automatically cancel old, unpaid orders Email: prevent sending email this action will block email from being sent for example, you can drop contact form notification emails or you can ignore emails to disposable addresses (for example mailinator) Email: change subject you can use this action to compose custom email subject ideal for email personalisation Email: add BCC recipient you can add new recipient to BCC great way to send yourself copy of all emails sent from your store Email: attach file you can dynamically attach file(s) to your emails for example, you can attach product manual to Order Confirmation email Email: change recipient you can use this action to change email recipient (to email address) Email: change email template this action will allow you to use different email template to render email You can use this feature to have different templates for different customer groups, for example I hope you will find these new features useful. If you have any feature requests or suggestions, please let me know. At the moment, I have the last big feature planned for this module -- Custom variables (as explained in previous post)
  17. 3 points
    Hi everyone, Elasticsearch module received some love lately. A lot of bugs were fixed. Module should now work on php7 version without issues, and ES versions 5.x, 6.x, 7.x should be supported. Before we release the module officially, I would like to ask community member to test it. You can download pre-release version here elasticsearch-v1.1.0-pre.zip For testing purposes you can start up elastic search in docker using command like this: docker run --rm -p 9200:9200 -p 9300:9300 -e "discovery.type=single-node" elasticsearch:7.11.2 Many thanks to @zen for his contribution. Most of this release is based on his work.
  18. 3 points
    Thanks for the support and contributios @zen Looking forward to an exciting future together 😀
  19. 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
  20. 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.
  21. 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
  22. 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
  23. 3 points
    Thanks for your post! Thats exactly how I think about it, too!
  24. 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
  25. 3 points
    I've just released new versions 1.1.0 and 2.1.0 (premium). The only change in these versions is integration with my new conseqs module. Module now offers 4 triggers that you can use to implement your automations. For example, you can reward customer with discount coupon for submitting a review
  26. 3 points
    I've just released first beta version of this module, you can download it here. There are still a lot of work to do, but I wanted to release it as soon as possible in order to collect your opinions and ideas. I hope there will be some 🙂 You can also test this module on my demo server - go to Advanced parameters > Conseqences. Please be careful and don't ruin my test account too much 🙂 Some information about the module: - this module allows you to create Rules - every Rule consists of three parts: trigger, conditions, and action - trigger is some event that can fire the action, for example new order created email is about to be sent page view order status change ... etc - conditions - optional settings that you can use to react only on some events. For example, you can use conditions to execute action only when new order is created for customer with id 123 - action - this is where you set what you want to do in reaction to trigger event. For example: send email redirect raise error change product quantity execute custom sql Some screenshots: 1) Rule builder: 2) Choose trigger 3) enter conditions: 4) define action
  27. 3 points
  28. 2 points
    I know this topic has already popped up multiple times. Still I believe it's very sad, that we have launched a crowdfunding project, which is almost not used. Who is using it on a live or teststore? Who wants to use it, but couldn't make it work? I followed the instructions on https://docs.thirtybees.com/native-modules/elastic-search/, but they are just too unclear to me. If I could make this work for myself, I would improve the docs and probably also the module.
  29. 2 points
    Well you won’t get help like that. This is a community support forum, main contributors are other sellers like you just trying to help in their spare time. You will not get instant answers, and sometimes no help at all. You need to have some patience Most visual things are in the modules section. Look there for sliders.
  30. 2 points
    Absolutely agree with you, @lesley. Core update needs to perform some additional checks. I will also make core updater work more autonomously, without the need for running store. This will allow us to revert to working version in case store is broken after upgrade. That shouldn't happen, but it will sometimes, I'm sure 🙂
  31. 2 points
    When someone wants to build a module from Prestools product-edit I would be happy to cooperate. The most popular mass edit module on Prestashop Addons (https://addons.prestashop.com/en/fast-mass-updates/19965-bulk-mass-editing-products.html) looks like it took quite a lot of inspiration from Prestools. If such a module was made both for Thirty Bees and Prestashop it could pay for itself. As I see it mass edit and cronjobs are areas that have a broad appeal and could help TB too. One of the latest additions to Prestools was image edit that allows you to add images by drag and drop. You need to generate thumbnails afterwards as otherwise it would take too much time. However, for Prestashop 1.7 that is not necessary as it generates its thumbnails on the fly. It might be a good things to have such a thing in Thirty Bees too. Also for mass import by csv. Many of the latest additions to Prestools concern maintainability: integrity checks and cleanup procedures. My main inspiration was that I had to deal with some old shops with quite a lot of decay. As I see it, such old shops should play some role in the discussion about stability.
  32. 2 points
    P.S.: ganz ohne Cookies wird es jedoch auch in Zukunft nicht gehen. Für Login und Warenkorb braucht man einen. Das lässt sich jedoch DSGVO-konform ohne Cookie-Consent lösen, da technisch notwendig.
  33. 2 points
    @Smile I can understand the feeling of @wakabayashi and I suppose some others. What we hope for (i talk only for me but I have the intuition is the same for some others), was not only to tell us if you would continue with TB name or another one new, but what was going to change and what we could we expect from this new path. People has been waiting for these news a lot of months. Now a communicate to tell, TB is going to continue but wait again up to 2 month more to know the details.... The feeling is: ok... I know plans take time, but the plan I suppose (i hope) has been developedduring this time. I suppose, most of the changes and roadmap were not going to be alterate because of the name... why not to communicate them to the people? What is going to be the revenue business model? What is the draft of the roadmap (even if it changes)? is the new image/website has been prepared? when is going to be released?, What about people concerns about 1.6 limited in time compatibility?....
  34. 2 points
    Thanks so much for this. It worked. pb4sc
  35. 2 points
    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.
  36. 2 points
    As far as I know he is not. And the deal being worked out is no where around those numbers.
  37. 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.
  38. 2 points
    https://github.com/seigieu/watermark/tree/thirtybees Here is version of PS 1.6 watermark module that also generates webp images. Also, thank @Smile for this 🙂
  39. 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.
  40. 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! 😎
  41. 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? 😢
  42. 2 points
    you need to go there, and turn on (green check) the left column on Index
  43. 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
  44. 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)
  45. 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.
  46. 2 points
    Bienvenido al foro. Soy nuevo tambien. Saludos
  47. 2 points
    I am going to be honest, there is no good way to display multiple products on the same page. There is however a hidden system for displaying parts on an image map, so people can mouse over a schematic and click on a part. We still haven't figured out how to handle that though. For the attributes, I fee that problem daily as well. Unfortunately changing that would break just about every module. If we shoehorned something in, it would be for lack of a better word stupid. It would maybe work, but it would not be stored in the right spots and would cause a ton of problems later on.
  48. 2 points
    I can also confirm that the fix works. I've picked this change into the next tb version https://github.com/thirtybees/thirtybees/commit/51ebfa051ebd330f0d35a873679ca28ff818e2d2
  49. 2 points
    Okay, I have actually worked out how to hide it in all three places that it appears. The following lines need to be added to the Add extra css to your pages section in the Preferences/Custom Code area of your TB back office: /* For desktop browser account creation, add this line: */ .account_creation .date-select { display: none; } /* For mobile browser account creation add this line: */ #opc_account_form .date-select { display: none; } /* For the user's "My account" page that they can see after they sign up, add this line: */ #identity .std .date-select { display: none; } The commented lines (/* ... */) do not need to be added, only the code lines that start with . or #. Copy & paste to avoid errors. I have tested the above on TB 1.0.8 with the standard community theme (obviously) and it is working without trouble.
  50. 2 points
    D'oh. Forgot the question about whether the old updater should get uninstalled. The answer is No. The old updater is still needed for updating not thirty bees core, but modules. Plan is to move code needed for updating modules back into core, so eventually the module becomes obsolete, but not for the time being.
×
×
  • Create New...