lesley

That is an option as well, a pretty easy one to be honest that I thought we already did.

What do you mean by a non standard license? The license they offer allows it to be re-licensed.

Did you upload it over the current theme?

We have actually looked at some of the choices. Like extending tinyMCE with a more feature rich version. But that is expensive to go with them. I haven't seen any other options that were as good given our budget.

Oh, interesting. I will reach out to them.

Have you tried contacting them for support? The should support it with thirty bees from the discussions I have had with them. Its just hard for us to diagnose / figure out the issue with not actually having the module or the source.

Is this module made by smart data soft?

I think that would be a viable solution at a point in the future. One thing that we are trying to guard against with not selling modules that we create is the idea that we leave features out, so we can charge for them. Basically like a freemium type software. That is something we are fighting against. I have seen other packages do that and it is not something I want us to get tangled in. If it means we make less money and grow slower, so be it.

I think that is fine, we just would not be able to do them through us. The whole point in the beginning was to make an open source module. Having paid or closed source modules is a conflict of interest with our companies principals.

Selling it would be against what we have said we are going to do as a company, I don't think that is something we are going to do. The module can be designed in such a way that it will be very difficult to ever make work in PrestaShop and that is how it will be designed. A simple break down of how we are going to use the funds is as follows, 80% of the goal for funding the module will go to the developer. The remaining 12% will be set aside for tax liability. Indiegogo takes 8%, so that is how the 20% is rounded out.

It would work, but you would have the same issue with the custom css.

Sounds like a plan to me. Like I said, it is something that needs to be looked at, but we have to pick and chose our battles accordingly.

That sounds like your php max execution time is too low. Try setting it at 300 or have your host set it at 300.

@ajensen27 I do as well. I think there is really a void in the market for affordable services to get banners designed from. I know most of my clients would pay a reasonable amount for a banner that looks good

What we thought was doing it like this, creating one project with a 2000 euro goal, then having the extended goals, like if we raise 3k we will do the search and the review module, if we raise 4k we will do the search, review, and blog module, ect.

This is what worried us, that is why we gave different options with different pricing options so we could make the best possible decision as to which one might be successful.

I hope everyone pays that, it will really get us moving and we can start looking into other modules too. :smiley_cat:

@ajensen27 As many articles as there are to back it up, I think most are written by non ecommerce people. I think they are mostly written by designers. I know that there are hot rivalries between some of the big American ecommerce sites, but I see all of them using sliders or hero images. I think people like to claim they are bad, but if they were bad for visitors or conversions then sites with huge ecommerce, marketing r and d, and design / development departments would not be using them.

Yeah, there is. The benefit of having the more semantic html was worth the change though, it should help with SEO.

You would need to create a new installer for the theme, but that could work. You can also cherry pick, like if you know you have edited the global.css file you can just grab the updates from it, there has not been too much added, https://github.com/thirtybees/community-theme-default/commits/1.0.x/css/global.css

Correct. You can always back your css files up and replace them after the upgrade. We included the css editor in the backend to solve some of these issues with updating themes.

That is correct.

We cannot afford the time to do that. You are taking a 4 hour project and converting it in to a 40 hour project that would serve a very small market of people. That would best be done in a mobile to see if it is a viable solution that people would actually want. I think there are a lot of higher priority items.

The featured work by products that are in the root category. I think your requests are to specific for the algorithm I think we need to have maybe a couple basic choice and then a setting where you associate products

It would not be a bad idea actually, it would just need some work figuring out how to best logically handle it in the back office ie where to put the controller so people could find it easily and not make the interface overly confusing.