Dear all,

I did a small test and the initial results is that HCC 3 works with DNN 9.1.1. I changed some code that upgrades HCC to version 3. HCC 3 builds fine with the latest DNN dll's. Furthermore, installing HCC 3 in DNN 9.1.1 gave no issues.

The upgrade file (HCC 3 Core, in github) needs some love. Furthermore, I reported, see github HCC Core page, some 'Exceptions' I got when running HCC 3 with DNN 9.1.1.

In summary, HCC 3 works with DNN 9.1.1. I hope that the community and maintainers of this project can reproduce my results.

Some additional information:
STEPS:
1. Download Hotcakes Core solution
2. Open solution in vs 2017 (core/Libraries/ is the single most important folder)
3. Build solution
4. Delete OLD 'dotnetnuke' references (6)
5. Add NEW 'dotnetnuke' references (6) -> Version 9.1.1
6. Remove second dnn/web project -> leave only ONE dnn/web project (I forget which one but I think it was 'Hotcakes.Modules.Core') that has the .dnn manifest file (basically all the files are c# library proj, only ONE folder needs some love ( has the .dnn manifest file)) + all the UI elements are really NOT important and can be easily DELETED (no effect)
7. Minor changes such as 1. Update MakeHccControlPanelDefault (Hotcakes.Modules.Core), 2. Remove <skinsrc>[G]Skins/Gravity/2-Col.ascx</skinsrc>
8. Build solution in release mode
9. You can see an install file that you can INSTALL in DNN 9.1.1

The only issue is the usage of TELERIK. Hope the dependency on TELERIK is minimal and will be removed soon.

Good stuff, Kurt. Thank you for your time and effort looking into this. I've seen reports from various people in the past about compatibility issues with CMS version 9.xx though. Hopefully, they were environmental. I've also not done my own testing against version 9.xx yet.

The only issue is the usage of TELERIK. Hope the dependency on TELERIK is minimal and will be removed soon.

It would be great to remove telerik, but I think we're going to need an Issue and pull request to make that happen soon.

The primary thing that's missing from this evaluation the fact that the administrative user experience paradigm has changed dramatically in version 9.xx of the CMS. It didn't account for comprehensive solutions like Hotcakes - where we have a back office administrative experience, and a completely different context for the people that use that area. They're generally not the same people that manage the CMS, nor do they have the same skill set. The persona bar and administrative experience need a good plan.

---

Will,

My experiences are positive, but you have to be an expert to do it right. Hopefully you can share the reports you mentioned. Would make our lives easier.

The problem is really the way if thinking. I think you think in an old fashoin way. No, the old controlepanel is not needed. It was only a MENU. In dnn9 you get a link to hcc admin and you dont need more than that. A menu referencing various hcc admin componenets is nice but not needed. Let us focus on removing telerik and stuff.

The problem is really the way if thinking. I think you think in an old fashoin way. No, the old controlepanel is not needed. It was only a MENU. In CMS9 you get a link to hcc admin and you dont need more than that. A menu referencing various hcc admin componenets is nice but not needed. Let us focus on removing telerik and stuff.

I'm afraid that there's much more than that. Since version 2.0, Hotcakes Commerce has it's own control panel that includes e-commerce-specific features that help store owners know the health of products and categories quickly, and it empowers them to be able to manage them immediately. It's been a great feature for anyone that's upgraded to version 2.xx. This is not something that we'd wish to throw away, and simply putting a link in the persona bar would be a huge step backwards.

---

The problem is really the way if thinking. I think you think in an old fashoin way. No, the old controlepanel is not needed. It was only a MENU. In CMS9 you get a link to hcc admin and you dont need more than that. A menu referencing various hcc admin componenets is nice but not needed. Let us focus on removing telerik and stuff.

I'm afraid that there's much more than that. Since version 2.0, Hotcakes Commerce has it's own control panel that includes e-commerce-specific features that help store owners know the health of products and categories quickly, and it empowers them to be able to manage them immediately. It's been a great feature for anyone that's upgraded to version 2.xx. This is not something that we'd wish to throw away, and simply putting a link in the persona bar would be a huge step backwards.

All of this helps a ton. I will be diving in at some point to get a better look at any UI changes we can assist on. Some food for thought could be having admin views to mimic the same old cms feel to maintain the current functionality by sharing the modules used throughout.

I know this provides a bit of complexity when it comes to any store navigation as a user vs admin, but it might get us there quicker.

Destroy admin panel to have just e-commerce is not good idea, I think that having a dashboard module for hcc is good solution, put on home page and show only for admins or some special roles, in main admin panel see a summary of commerce and some main functional button (shown as module) looks good.
And if admin want to manage shop, go to hcc own panel as before. I think putting a dashboard module is better than destroy standard menus .
Having a module as module instead of menu can be show to non admin roles too and can be implemented by more flexibility any where in template.

I've been thinking about the control panel features a bit more, and I think we could get the best of both worlds by integrating some of the administrative experience into the product & category views themselves. They'd only be available to certain roles, of course.

For example, in the event that the control panel is not available or in use, the header area of the product details page could have an expandable section that shows the same information that's in the control panel today. Most of the code already exists. It can be pulled from the control panel itself. Then, we'd also be able to reduce the code footprint a bit by removing the control panel entirely.

What do you think?

---

I've been thinking about the control panel features a bit more, and I think we could get the best of both worlds by integrating some of the administrative experience into the product & category views themselves. They'd only be available to certain roles, of course.

For example, in the event that the control panel is not available or in use, the header area of the product details page could have an expandable section that shows the same information that's in the control panel today. Most of the code already exists. It can be pulled from the control panel itself. Then, we'd also be able to reduce the code footprint a bit by removing the control panel entirely.

What do you think?

Love it! Can wait to use it!

And if there is any chance we an tap into the role in the view as well, I am sure I would use it for displaying other things as well.

Love it! Can wait to use it!

And if there is any chance we an tap into the role in the view as well, I am sure I would use it for displaying other things as well.

You can already work with roles in the viewset. The entire API of the CMS and Hotcakes is available to you there.

---

Love it! Can wait to use it!

And if there is any chance we an tap into the role in the view as well, I am sure I would use it for displaying other things as well.

You can already work with roles in the viewset. The entire API of the CMS and Hotcakes is available to you there.

That's right! Wasn't thikin, just got excited to reply.

For further discussion about the control panel:

https://github.com/HotcakesCommerce/core/issues/36 

---

Love it!

Actually, you can easily mimic the old controle panel in the new personabar. For the menu links, you'll have to change 3 tables, using the menulinkcontroller. I can provide a sql query to do this. Furthermore, if Arrow, Will or community post detailed information on the idea presented above by Will OR other ideas, including images or drawings (final results in mind), I can build these features in the personabar using react/redux.

Love it!

Actually, you can easily mimic the old controle panel in the new personabar. For the menu links, you'll have to change 3 tables, using the menulinkcontroller. I can provide a sql query to do this. Furthermore, if Arrow, Will or community post detailed information on the idea presented above by Will OR other ideas, including images or drawings (final results in mind), I can build these features in the personabar using react/redux.

I like the idea of having Hotcakes be natively included into the persona bar. I don't have enough experience with the persona bar yet to thoroughly determine how and what should be done.

With this being an open source project now, there's really no resources or funding to get you the UX, PRD, and other supporting materials we'd normally see in any funded project. If you're really looking to do this, I'd suggest beginning some proof of concept development, and sharing it openly in the community so we can collaborate on it together. We should probably do the collaboration in another forum post or in the GitHub issues though.

---

it Seems that most important job to do at this moment is release a HCC Package with exist Feature and D.N.N 9.1 capability ( just link to HCC Admin Panel), after that more people contribute to improve community .
improving admin panel in the feature Version .

FYI - All of the challenges mentioned above are about to be resolved in the pending Hotcakes Commerce 03.03.00 release.

https://github.com/Hotca...commerce-core/issues/226 

---