Forums

Yes, we are all anxiously awaiting this release--it's really the big missing feature.

Have you thought about releasing this in stages?

1. add tokenization for articles & support it in the "custom view"
2. add template selection of user-entered HTML article rendering, but no UI
3. add tokenization for category lists
4. add template selection of user-entered HTML category list rendering, but no UI
5. add ui for creating the template

In other words, don't put it all into one big release, because it never gets released and we keep waiting and waiting for--sooner or later we're going to give up hope and jump to another product...

I am very interested to hear too.

After reviewing the road map, we've moved things around slightly, so that our next release is what was previously called 5.5.5, now 5.6, the known bugs are planned to be fixed in 5.7, we may or may not address some pending enhancements in 5.8, and then we're still planning on templating being the main or only feature in version 6.

That being said, we're planning to have some more internal discussions on where Publish needs to go, what we need to work on , emphasize, deemphasize, how it fits in with DNN Pro's workflow, etc.  This could have an effect on when we feel we need to address templating as a feature.

Let us know if you have any feedback on the directions that you would like to see Publish taken.

Hope that helps,

I agree with this last statement. Publish is almost unusable without templating (unless it's only being used on single-portal DNN installation). I purchased Publish a few months ago and am implementing it on 2 portals for 2 different clients currently (with many more potential implementations to come) and their layout needs are entirely different. I had to make a lot of changes to the CustomDisplay.ascx file to satisfy the needs of the first client. Now that I'm working on the second one, their needs are very different and I seem to have no options to give them and risk losing their business if I can't come up with a workable solution for them. So, which client do I make happy and which do I potentially lose (along with tens of thousands of dollars) because I can't meet their very basic layout requirements?

I've been planning on migrating all my portals off of DNNMasters Content Builder Pro 2 (which has supported templating for several years)  to get some of the features found in Publish. Now that I'm learning Publish, I'm discovering it's lacking in some pretty fundamental capabilities that even basic article management solutions typically provide. The cost may be too high to use Publish as it doesn't have even the most basic of features like templating (i.e. it supports user ratings but you can't sort articles based on ratings - half baked). Also, in the few months since I purchased Publish, they haven't come out with a single update and this makes me think the vendor is stretched too thin trying to support too many modules given their resources. I can't risk my business on a vendor that can't meet the ongoing needs of my clients. Any insights here would be appreciated.

DNNMasters is coming out with version 3 of their article publisher soon (in beta now). I may be forced to use Publish for only one site (which makes it really expensive) and use Content Builder for all the others. Any other options anyone can suggest to allow me to recover my investment in Publish?

Thanks, John