lesley

We have looked over them, they are aimed at limiting it. Our goal is to fix it and expand it. I really feel like they are at a point where they are hiding issues they cannot fix instead of fixing them. So we have had to stop merging from them because they have introduced so many bugs and regressions.

I personally know that there are bugs in it and I would not recommend turning it on now. What we are going to end up doing is making it a project. We are going to get a few shop owners to set it up when we are ready and can devote the time, then we are going to provide on demand bug fixes for the system. That is going to be the best way to handle it in my opinion, but it is not something we can handle at the moment.

For me the templates are going to go in two parts. The first part is going to be more simple, it won't actually affect the looks of the templates at all. The micro data that we are going to add only works with a couple email systems like Gmail. Think of rich snippets on your site, they don't affect the layout, you never really know they are there, but they do things. The things they do though make life easier for android users. This is a image for my gmail, http://storage7.static.itmages.com/i/17/0630/h14988040451981990_55719ed11f.png on mobile it does a lot more than desktop, it send the information to your google cards. But this will be the first change we make in the emails.

Make the changes to the theme, the core ones might be updated soon in the future. I am planning at some point in the next month or two to try to start adding rich data actions that will work with Google. So in a core update in the next couple months they might get overwritten.

@dprophitjr I was actually talking about something different. Most of our clients do not like the stock generated pages for those two pages. They like creating categories where they can associate what they want seen on those pages. That is why we redirect them. Sometimes bestsellers are not really what sells best, it might be what a shop wants to move most. Same with the specials. That is why we do them that way normally.

We have talked to a couple of merchants about the ASM bugs. What we have come up with is that we need them to migrate to thirty bees and we need to monitor their shops and the errors. It makes it so much easier to have some shops that we work with in production to fix the bugs.

You would need to make a best sellers and a on sale category, then you can use the httaccess file to write a 301 redirect.

I redirect them to a category that has targeted products a lot, like a sale category that has better control.

Your only real option is to sell them as products. They are not an attribute of a product. As far as the amount, yes, it can handle it, that is not to say you can handle it on a 2 core vps server, but a setup can be made to handle it. I can show you how to bring back the scenes area which will allow for having schematics with links, but it is not responsive or zoomable, that would need to be custom written into the theme. As far as excluding the products from search, that would take something custom as well. A module would need to be developed that overrode the search and limited the categories that it would index. It is all possible though.

No worries. We are working on a deal with cart 2 cart right now, that should make a good platform to migrate people from any shop to thirty bees or back to PrestaShop if they choose.

It could be that your mail server is not set up correctly. Are you sending email from your shop using the same domain that your shop is on?

@DavidP We are planning on releasing a module soon that will handle json+ld data for shops. We just want it to integrate correctly with everything, so it is taking some time.

What our plan is, is to follow the dev style of more mature communities. We are going to always have what is called a long term support version. Right now 1.0.x is going the be the long term support branch. We will be stopping support for it around Aug 2019. We think it is very important to maintain support as long as possible, but also give a roadmap if possible as well. Likely 1.1.x will break some support for modules and themes. There are things that we want to change in those versions to make the experience better for merchants and developers. We are going to try our best to have compatibility patches that can be run that will make the experience not optimal, but work. Breaking compatibility is hard, but it is something that is going to have to happen at some point to move forward. As our community grows so will the offerings from the community. One thing we do believe in though is long beta's on new versions. We aren't going to stick you with broken software and make you either suffer or pay a developer to fix it.

My thoughts exactly. If you really need to roll back, you can do a fresh install and use cart 2 cart if needed.

The regressions in the 1.6 branch of PrestaShop are getting so bad it would be a time consuming module. They keep breaking things, so we would have to account for those breakages and it would take a signifigant amount of time away from what we want to do, write stable software.

There is an amp plugin for prestashop, I imagine it works with thirty bees.

I don't think amp will be around too much longer to be honest.

Likely what we will do is pick the winning module as the main goal, then the second place module will be a stretch goal, and so on. So in reality if it is popular enough they could all get funded.

Awesome, thanks. Likely what we are doing is ordering the modules. Like the winning module will be the goal, then the second place module will be a stretch goal. All depending on how the whole campaign goes.

You would have to edit that in the shopping-cart.tpl You would need to make a hard edit in the header.tpl for this as well.

The stat system needs a revamping too. One thing I have planned is to turn all 20 something modules into one module and just have a standard configuration where you can set whatever stats you want. I think this would be a lot less confusing than 26 or so different modules. It would also make it easier on us to keep up with as well.

I have just posted an article about crowdfunding modules, we are going to go ahead with it, but we want the community to be able to vote on which module we pick to test the waters out. You can read the article here, https://thirtybees.com/blog/crowdfunding-modules/

I have just posted a new blog post about the crowdfunding. You can see it here, https://thirtybees.com/blog/crowdfunding-modules/ The reason we went with options is because we are trying to gauge how successful the idea is and also try to cover the most amount of users.

In 1.1.x we are looking at changing the modules up a bit. We are going to be reducing the number of modules that are used in themes by combining several modules down into single modules. An example is the block my account and the block my account footer. There is no reason to have to maintain 2 modules for this. At the same time we are looking to introduce new front end modules as well. Things that theme developers can use to make shops prettier or more functional. What kind of new front end modules would you like to see?

@presto5 is there anything in your error log?