If we have 5 pages in the site, this mean do we need 5 skin pages for the skin package? I've created an instruction on how you can copy Themler Sections to the DNN HTML Modules: > Themler works similar to Artisteer 3.x versions (before content editor and content export). It means that each Section, Image, Text or any other control is a part of the skin design. > As mentioned above and as mentioned in the documentation, Themler does not export content. Themler works similar to Artisteer 3.x versions (before content editor and content export). We really keen on your priduct and want it as a fully compatible product with DNN in standard way.Īs mentioned above and as mentioned in the documentation, Themler does not export content. If we have 5 pages in the site, this mean do we need 5 skin pages for the skin package? Please, advise us or this too. We need it like Artisteer 4.x and please give a good priority for this. I am using Themler only for DNN and there may be many more who is working only with DNN. I was an artisteer user from Artisteer 2.0 beta version where you introduced DNN to Artisteer. I think this is why you also moved from Artisteer 3.X from Artisteer 4.X The content is also a part of skin is not a standard way of a standard DNN skin development. Last edited 29 March 2016 by Support Team What are we doing wrong here? How can we convert the static theme to a dynamic editable DNN site? After importing the theme, all looks great, but users can't utilize the CMS "edit content" feature to edit text or alter a image, rendering the CMS useless and to nothing more than a static hosting platform for the themler site.
However, we use DNN to host the websites and have customers edit the sites content afterwards. He told us we should actualy use Themler, so he is now using that and created his first theme (compliments on the themler product).
We create websites for lots of customers and tried out Artisteer for one of our web developers.
0 kommentar(er)
