|
|
I just finished ditching all the other navigation modules and moved to use solely the DDRMenu on all my websites (man I love that control). I also took opportunity to learn and write it all in Razor (C#). Amongst the last things I need to move is NBStore
category navigation. I'm still in process of learning how to correctly implement INodeManipulator to feed DDRMenu with correct category links :/, meanwhile wouldn't it be great if NBStore natively moved to this perfect and unified solution? This would allow
to use any template made for DDRmenu be it xsl, cshtml, vbhtml or html with tokens. It can support everything including options to enable product counts, thumbnails, images and what not. And would offload work trying to improve this area :).
If I happen to make it in timely, redistributable manner I can share my work later on with anyone interested.
What are your thoughts on this?
|
|
|
Coordinator
Jan 3, 2012 at 7:03 AM
|
Hi,
I'll let Mark know how much you like his menu, next time I see him :-).
But yes, it is a great solution, we tend only to use the xsl solutions, but if you can create a solution that links into NB_Store, that would be great. In v3 of the store I'm planning on changing the categories tables to a grouped based, multiple use
structure. But this should not effect the actual table too much, so any work you do on this should be easily adapted to the v3 of the store.
Regards,
Dave.
|
|
|
|
|
Hi
I need this feature, is it ready for use?
thank you both for your perfect modules.
best regards,
Behnam Emamian
|
|
|
Aug 1, 2012 at 4:54 PM
Edited Aug 1, 2012 at 4:55 PM
|
Hi bemamian,
You can download my version from
DDRMenu NBStore Provider
Just extract it in the bin folder of your website and then add DDRMenu module to a page, hit its settings and set
Node manipulator type to DDRMenu.Providers.NB_Store,DotNetNuke.Web.DDRMenu.NB_Store
Let me know how it works.
|
|
|
Coordinator
Aug 2, 2012 at 10:02 AM
|
Hi Xeevis,
Any chance you can donate the source code to the NB_Store project?....I'm sure other people will be interested in this!
If so contact me.
Thx
Dave.
|
|
|
|
|
Hi Dave, not sure you got my message. So I'm pasting it here for anyone to download
DDRMenu NBStore Provider Source.
|
|
|
Coordinator
Aug 6, 2012 at 2:03 PM
|
Thx Xeevis, I didn;t get your email..or at least I missed it. Thx for the link I'll download it and see if I can find a sensible place to put it for download on codeplex.
Dave
|
|
|
|
|
i put the DDRMenu NBStore Provider in the bin folder and my site has been down.
this error appeared:
Error 1 Could not load file or assembly 'DotNetNuke.Web.DDRMenu.NB_Store' or one of its dependencies. This assembly is built by a runtime newer than the currently loaded runtime and cannot be loaded.
|
|
|
Coordinator
Aug 12, 2012 at 8:40 AM
|
This sounds like the Menu provider was compiles against .Net4. You seem to be running you IIS app pool on .Net3.5. I think you need to either change your app pool to .Net4 or recompile the menu provider against .Net3.5.
Also I've heared that there is a problem with DNN 6.2 on the social login, where if running with an app pool of .Net3.5 the CPU usage gets stuck at 100% and causes a time out. I've had this on a test machine and heared a simular story about this from
others...but I have no facts about this bug, and I've been told upgrading to .Net4 seems to solve it.
I've not upgraded anything to DNN6.2 because of this, and if it is true then it's going to cause a lot of headaches for a lot of people. So either DNN corps should fix this or have a statement that DNN6.2 only works on .Net4 app pool (Again,
a headache to update app pools for those people hosting a lot of site, as the upgrade to .Net4 may be a problem for older sites!)
Anyway @Xeevis, I currently still compile against .Net3.5 as this makes you dll compatible aginst everything. I'll have to switch to .Net4 at some point, but at the moment with DNN "offically" working against .Net3.5 I think compiling agsint .Net4
will stop people using the assembly.
Dave.
|
|
|
Aug 12, 2012 at 10:29 PM
Edited Aug 12, 2012 at 10:30 PM
|
Yep assembly is compiled against .NET 4 ... sorry for that, 3.5 package coming right up
Binary (3.5) or
Source (3.5).
leedavi yeah thats possible, newer framework not just adds new functionality, but improves and fixes problems from previous. I'm pretty sure most of the DNN devs are already running 4.0 for quite some time and just backpedal for releases which can have some
issues.
I'm using .NET 4.0 for over 2 years and even now I consider it outdated as I'm about to move to 4.5 ... It has a lot better performance which is I'd say critical for web presentation. I also use Razor quite extensively, especially for DDRMenu as these templates
are some much easier to manage than XLS ... I don't see why would anyone dangle around "minimum requirements" which are about to get raised to .NET 4 soon anyway (possibly 4 months down the road till DNN7). Also newer frameworks are backwards compatible
(except for 1.1 which no one is using anymore), there shouldn't be a problem transitioning any kind of website to it without any significant edits (DNN does all the necessary edits to config by itself).
At any rate I can provide both versions.
|
|
|
Editor
Aug 14, 2012 at 12:06 PM
|
Hi Xeevis,
Nice addon!
A question for you, might be a obious answer but..
I want to set the menu to a sub category which has also sub cats, can you tell me how to do this.
Thanks,
Geoff
|
|
|
|
|
Hi Geoff,
There is actually a bit of a problem. Normally you'd have to set category ID in the node selector .. But from what I've tested these settings are being run prior to NodeManipulator which adds NB_Store category nodes. Therefore there is no way to do this
other than either modifying source of my NodeManipulator to only include nodes you need or of course edit source of DDRMenu to do NodeManipulator first and NodeSelector/IncludeNodes/ExcludeNodes afterwards ... I'll try to open a ticket and resolve this, because
its clearly a bug, there is no reason for it to work this way, but with my experience with DNN bug tracker it won't be fixed before DNN 7.2 if ever ... I'll post a link to the ticket once i write it :(
|
|
|
Editor
Aug 15, 2012 at 6:20 AM
|
Hi Xeeivs,
Thanks for the reply.
It's a shame that the DDr menu doesn't allow for this or it would have been the perfect solution for us!
1 thing we didn't want to do is to change the code to set the catID, this would been us creating a new dll per shop and also it would not allow for catID changes dynamically for the client.
But, saying that I have found a work-around by re-designing the category structure to allow for the use of your add-on solution!
Again, thanks for the module and addon.
Geoff
|
|
|
|
|
I've got this working using dnn7, the dll above, a razor template and a jquery plugin.
I've got it to produce an accordion style menu that works just fine, except i cant figure out how to set a default or selected category in the menu?
Is there a way to do that?
Currently i have 4 pages, each with a ddrmenu and productlist module on.
the productlist modules all have different a default category
and i would like to be able to do the same with the menu effectivly
so when the page is opened both the menu and the productlist are on the same category.
i dont mean integrate the two modules, more set a hardcoded default in the menu...
is this what the nodeselector is for and if so what would i put in to default the menu to a category named=example1 or categoryid=123?
Thanks
|
|
|
|
|
Yes its what nodeselector is normally for. When used in conjunction with NodeManipulator however it doesn't work as one would hope it to. Basically all the settings take effect before the manipulator, therefore they have effect only on default DNN nodes and not the custom NB_Store ones. This functionality would have to be either fixed in DDRMenu or reimplemented in manipulator/razor templates. But considering they are not even being passed these settings this would be quite complicated matter.
Personally I've had enough with DotNetNuke, they are no longer capable of fixing or improving anything (hell they broke razor templates for DDRMenu in DNN7 and wasn't fixed for half a year). They went all out with professional edition and acquiring stuff for them and unless you pay them thousands of $$$ they ignore you and your bug reports get through in like 1-2 years. Instead of fixing and maintaining everything myself I chose to move to MVC platform (Orchard CMS with NopCommerce). Not gonna spend any more time on DNN as I'll never use it again, sorry. If anyone else feels like they can pull this off, It would be cool.
|
|
|
|
|
Sadly I'm seeing evidence of this same feeling more and more recently.
Significant members of dnn's blogging scene and the company itself are leaving or have left already and the general attitude of the few that remain is all so negative that they no longer post, The documentation is so out of date as to be silly and Most seem to feel that dnn corp is now so focused on the commercial aspect that the community no longer matters.
With regard to their bug tracker, I agree, it's a joke!
However I'm stuck, I can't just drop what I've already got and start over so ill have to come up with a plan b
But yes, I won't be making this mistake again, I'll never choose dnn again for a commercial/business site and will be joining the growing crowd of people who advise against dnn for anything but a noddy hobby site.
It's such a shame but they are killing the one thing that made it great, the community.
|
|
|
Coordinator
Apr 29 at 1:32 PM
|
Hi,
I've not given up on DNN yet, there is time to turn it around and DNN corps are starting to making an effort to bring the community back to them. I do hope that they are successful, so try and hang in a little bit longer and let's hope the turn around we all need is around the corner.
I've just got back from DNN Europe meeting where people are wanting to use DNN and I've had offers of help in creating NB_Store v3, which I hope should now be not far away. While DNN corps do need to make a profit and do need to focus on sales, I do think the community version of DNN can survive along side the Pro version and give a quality product for our clients!
I think the orchard project is probably still at the moment a step behind what we have in DNN and if DNN can drag back the quality control, give some focus to small things that do matter and some solutions to upgrade issues causing problems across portals and modules, it can get the trust back again and hopefully stop the sad trend of the last couple of years.
The DNN Europe community does have ideas on how to help with this and I do hope DNN corps support is total when asked for!
Dave.
|
|
|
|
|
Hi Dave,
You are right that DNN Corp needs to profit, but they twisted "community project" into completely different meaning. I've been using DNN for years (since 2007) and now its a deal breaker. The original idea was to add premium support like Vivo Social or NopCommerce or any number of community projects do, but not to develop frikkin standalone commercial product out of it. They took thousands of hours of work from people who reported, fixed, contributed, made possible and just sold it. They turned us into free labor for their business. But all that money they earned from it, isn't channeled back. Nothing they did for those paying ever made it into the community, while everything made by community goes to the commercial. I've seen no new employees or indication they'll ever care about community again. They smelled the big buck and that's practically end of it. At least that's how I feel it, but everyone is entitled to their own opinion :).
I'm not saying Orchard is perfect alternative for everyone, its mostly for developers and hobbyists (for now). But its perfectly designed with dreamy modularity, ANYTHING anywhere can be replaced, inserted, removed. Any view markup can be changed without touching the original files (and razor is awesome and easy to work with even for non-developers). Its extremely fast, concise, clean, well documented. And its true community project, not a single thing is enforced on user. The steering committee sets capabilities of the framework, modules tell how everything works and themes how everything looks. Yes, when it comes to raw functionality DNN has upper hand, but due to nature of the framework I'm actually more productive with Orchard when it comes to custom solutions. When Orchard becomes more popular it will quickly pick up the pace.
|
|
|
Coordinator
Apr 30 at 7:42 AM
|
Hi,
I don't think this is the right place for this conversation, if you want to continue to discussion options please PM me.
However in conclusion, I would just say that DNN community is alive, most of the people that helped create the DNN core and CE are either in DNN corps or still in the community.
I think it's wrong to expect anything from DNN corps other than a stable CE framework, something that needs work at the moment for small things that should never be a problem if QA was focused towards both CE and PE. I do hope this will change in the next few months.
Also there is new stuff out there that can be used to speed projects up and still get great results. here's a link to a great tool for this...
http://2sexycontentinstalle.codeplex.com/
I also have a in-house module that we've been using for a year now, which is very similar to this, it tries to solve the same problems but from a different direction. The results and solution are much the same....I do hope to release a free version of our tool soon.
I'm not going to try and convince you to stay with DNN, you must do what is right for your client base. At the moment I believe DNN is still the right platform for our clients. If my thoughts on this change I have no ties to DNN other than the commitment I've made over the years, so I will always pick what I think is best for my clients.
I wish you the best of luck and hope we meet again, hopefully in DNN community.....or Orchard if things go wrong in DNN :-)
But I do intend to commit myself to DNN for v3 of NB_Store so I am in it for the long duration!
Regards,
Dave.
|
|