Obi

What is this "Warehouse theme" that you speak of? I'm always interested in looking through code that provides cool features to see how other developers implement those features - it is how I have taught myself to code in php, javascript, and smarty, primarily for prestashop and now thirtybees.

I use it so I can enter a location where products are physically stored - one site I manage has over 20k products - makes it much easier to find in the warehouse when picking. The inventory however has been set to local tracking as the warehouse tracking is quite complicated (and a pita) as you have stated. I have a site that will be going live next year that is tied to a brick and mortar store that also has a remote warehouse, so this feature will be instrumental in being able to tell a customer "yes we have it and it will be here tomorrow" or "yes we have it, and it is located on wall section A7 - let me show you".

I recently started using prestools... while it does not have all of the functionality of SM, I have found it to be quite useful in facilitating batch edits and various other needs. I currently use it for light category work and daily for products. I have the supplier plugin and plan on getting two more - so far so good.

^^^ What He Said ^^^

Yeah, bloated code stats don't impress me - at all - so we're just gonna have to disagree on this one... I just started working on an owl carousel plugin, not sure how far that will get before the end of the year as I have other obligations and projects, but hopefully I will have something far better than homeslider before the end of the year. I MIGHT even be convinced to give it away for free - we'll see. PS: If someone has already done owl carousel for TB1.4 - I would love to not have to reinvent the wheel so to speak!

I've created my own theme using community theme as the starting point. I'm on my second round of revisions and while there is still much to do to get it up to the level that Panda used to be (I don't like the new version - too "glitchy" for me), I still use Panda's features and UI design as my foundational vision. I prefer a left column - blocked theme design as that is what I have found to be most appealing to my customers and new visitors. It seems to have some "sticky" to the site once a live person visits - I believe because navigation is easier and you can change left column options very easily, allowing you to experiment with "widgets" aka blocks that your customers find useful. Here is the first UI rendition of my theme: Here is the second theme derivative, based on the first theme effort (for various reasons this site is still in development): A shorter product listing that shows the various "status" details (drawn from keywords in the available_now/later variables): Out Of Stock (deny order), Out of Stock (allow order aka backorder), Available but Discontinued aka Out of Print, Coming Soon - essentially an Out of Stock (deny order) setting but keyed off of the available_later text. I was going to key this off of availability_date and allow_oosp, but opted for the keyword option instead because the available_later text can be overriden within the template file and that keyword can be seen in the back office as an indicator. Product Detail Page: I apply a "wrapper" class in an outer div at the head of the description to achieve this effect based on brand - not really fond of this particular one, but it is easily changeable in the custom.css file that gets loaded last (can't use autoload for this purpose) ensuring the custom theme at least has the chance to override most elements if you cannot get specificity on desired target elements.) I know others disagree with me on this approach, but it works well for me as the majority of what you see is because of the theme's custom.css file. Cart Pulldown: Checkout button turns to a lime racing green when hovered. Built in (but modified) One Page Checkout featuring stock status indicators: It is responsive and mobile "friendly", though there is still a bit of tweaking needed on some elements for mobile optimization, everything is functional on both an iPhone6 (very old phone) and a Motorola G 2024 (recently purchased) at this time. I haven't done a bunch of speed tests yet, but things are pretty snappy on a shared hosting account (used for development). I do plan to add a few other touches, like search results with icon image and some variation of the owl carousel (the homeslider module that ships with TB1.4 is atrocious). Side note: I also do not plan to port this to TB1.5 as that version is going off the rails from the original stated mission/purpose of the project (IMO) and I fear that it will ultimately be another Prestashop scenario for store owners and developers alike. My point in posting the visuals is so that folks can see the potential of the TB1.4 platform. It is substantially better than PS ever was but the same ills that befell PS seem to be creeping into TB - and while that is a sad situation - I cannot find a better open-source solution available at this time. Good Luck - I am open to helping others, provided you have a solid plan of what you want to achieve and at least some idea of how. PS: There is a security vulnerability in the header.tpl file of the 1.1.0 version of community theme - it has to do with the IE polyfill.io library. You can find more info here: polypill.io malware? - Technical help - thirty bees forum

So that was my first impression as well, but since I've been out of the "security" game for a while, I felt it best to ask. And that was prompted because I was researching SEO questions and was told by an SEO person that the method first described (TB subdirectory under WP at root) would provide better SEO "juice"... Now that I have confirmation that it is as bad an idea as I thought - I'm with you chaps! Isolated sub-domain is the correct answer! THANKS!!!

I have installed many Prestashop sites and am working on my 2nd ThirtyBees deployment. However, this one is a touch different in that the primary website is WordPress, and because of ticket sales from that installation, it MUST remain the primary site. My original intention was to deploy the TB "shop" site as a subdomain, primarily for security reasons, but after reading a bit more on recent(?) SEO "best practices", the recommendation seems to be that sub-directories are preferred over sub-domains. An ancillary question that I probably should ask is whether anyone else has information that confirms or contradicts this "recommendation". Note: My website management style does not hinge on every breath depending on google, or any other search engine edict, dictate, or notice - but I do want to at least work within the major framework. My philosophy has always been that PEOPLE spend money on website, not crawlers and bots, so using a "People First" approach has always served me well, but I don't want to miss something important because I'm looking past that something important. So the simple question is this: Is there a deployment best practices document anywhere on how one should install ThirtyBees in conjunction with a primary Wordpress site? Thanks All in advance, for any feedback or assistance.

I found something else that isn't in the free version, but cannot find a plugin for it - warehousing - does this exist as a plugin?

It's part of the core distribution - therefore it should be supported. That is my opinion, but that and a couple of dollars MIGHT get you a coffee at one of the carry-out gas stations or maybe a truck stop if you have a discount card. I also have a problem with it, I can't get it to display in the displayHomeTab/displayHomeTabContent hooks so that it will appear to the right of my left column and above the homepage "tab" content (I manually hooked via the database including the displayHomeTabContent hook but it still does not display). If you have any ideas that might reduce my effort (like where/how to rewrite the hooks) I would appreciate it. I'm trying to set time aside today to dig into the module code, in the hope to figure it out. But I really don't believe I should have to waste time like this on such an essential module and use scenario. But then that is my problem with all of the free stuff, many of the essentials are tossed to the side in favor of other efforts... and I cannot afford any of the paid solutions, even though they are only marginally better. Even the intros/trials for those solutions are too costly for me, plus the constant UI changes and "new module" costs that nickel and dime you to death aren't worth the frustration or the price! (IMO) The following is a depiction of what I want to do - this should have been easy-peasy right out of the box - but alas it is not...

I'll see what I can put together.

Looks like you got your answer 😞

Works like a charm!

Ok, purchased what I need for now... I'll let you know if any problems once I get around to using them.

I am looking for a basic product export with all the fields on the information tab, the price and wholesale price values, the 3 SEO fields on the SEO tab, the Associations tab fields, Shipping Tab fields, Quantity Tab fields, and Suppliers Tab information. Warehouse info would probably be too much to hope for - but mentioned here just in case. I could definitely live without being able to export sales/specials data, but maybe if the basics (default options available under a default install of TB1.4?) were available? I used the new version settings1.php file and only changed settings from within the new file since this installation is on a beta site at present. /* the following array determines which fields are shown in the search block of product-edit */ /* pack_stock_type was new in version 1.6.0.12. New fields in 1.7 are isbn, state, show_condition */ /* sosh_title and sosh_description (social_sharing) were present in the first 1.7 version but not later */ /* new in 1.7.3 were low_stock_threshold, additional_delivery_times, delivery_in_stock,delivery_out_stock, low_stock_alert */ /* new in 1.7.7 was mpn */ /* it is recommended that when you delete some of the fields you keep an outcommented copy of the original */ $productedit_fieldblock = Array( Array("name","VAT","priceVAT","reference","link_rewrite","description","description_short","meta_title","meta_keywords","meta_description"), Array("quantity","price","category","wholesaleprice","position","manufacturer","virtualp","availorder","on_sale","online_only"), Array("ean","image","date_upd","minimal_quantity","shipweight","shipheight","shipwidth","shipdepth","aShipCost","attachmnts"), Array("upc","active","date_add","visibility","condition","pack_stock_type","reserved","customizations","indexed","indexes"), Array("unity","unitPrice","unitPRatio","available_now","available_later","available_date","stockflags","warehousing","redirect","out_of_stock"), Array("isbn","state","show_condition","aDeliveryT", "deliInStock","deliOutStock","ls_threshold", "ls_alert","location","mpn"), Array("ecotax"), Array("tags","shopz","carrier","discount","accessories","combinations","supplier","featureEdit","features","statistics") ); I only removed "VAT","priceVAT", from the array string and I get the green error screen: duh... I feel stupid for not even clicking the button. "Some fields (supplier,image) are in demo mode. You can buy plugin(s) to use them at Prestools.com." I ASSumed that they were non-functional so what was the point. ¯\_(0.0)_/¯ Sooo... Whole enchilada or pay the individual prices. Had to ask. 🙂