Forum Replies Created
-
Posts
-
Hi Rikard,
thanks for your reply. Just to be perfectly clear (sorry to bother but I don’t want our client to get in trouble):It is no license infringement to “disassemble” Enfold’s code and reuse parts of it (especially styles, JavaScript and HTML structure) to build a static website or Hubspot theme for a client?
Best regards,
StefanI understand your position but to be honest, selling and promoting a theme that contains proprietary tech without ever communicating this and thus trapping site owners is really bad practice. Other theme devs make use of plugins like Slider Revolution, Visual Composer or Elementor without taking away the possibility to migrate sites.
And as a side note: this has nothing to do with “frustration” – your design and development choices as a theme development team cost us money (and lots of it) due to the fact that we will need to refactor more than 6.000 articles because you did not consider modern development practices and some common sense.
Thanks Mike,
as stated the site has already been moved / transitioned. Since the features are basically just shortcodes which get expanded, I’d say it should be possible to bring the image, slider and one or two other media-related functionalities over to the new theme or a separate plugin, don’t you think?
Apart from that I’d consider it a pretty bad business model to basically bind website owners to Enfold because they lose functionality / introduce major problems due to the fact that Enfold uses stuff under the hood that is basically proprietary. Don’t get me wrong, no accusations here but I’d expect you guys to not take site owners hostage by making large portions of sites unusable due to the framework…
Best,
Stefan
