chajo10 wrote:
Yes, RouteProdiver.cs can be in plugins and quite a few have them. Is it needed, not necessarily. Arguing Views are not code is kind of pointless since Razor was built around making interjecting C# code into html easier. Look at your Html.Action. That is code made for Razor that is using some C#. So is it code? Seems like it, so rethink the statement you aren't changing code.
So I say you have not understood my point. In my case, it is necessary, because we are linking a to a new page (read: Action), and we want a nice route. Let me explain again in case you are lost:
1. We have the Public Info action, which will contain just a link to our Action in point 3.
2. We have a Configure action, which can provide a mean for you to manage (read: database CRUD) the FAQs
3. Then we have an Action that is, let say, named Faq, and a corresponding View that is named Faq. This is the place that the FAQs will be shown, not the Public Info action. And we can use RouteProvider to provide a nice link to this page, let say http://site.com/faqs. Clean solution. The Faq action will do the heavy lifting of pulling data from the DB.
4. Back to the Public Info action (or rather, the Widget itself). It will be added to, let say, the "header_menu_after" zone, then we have a link to the page in POINT 3.
chajo10 wrote:
Yes, his info is static. Should it be on the homepage, doubtful unless the FAQs are very, very short.
No. His info is DYNAMIC. Read his very first post:
krutal wrote:I want to add dynamically manageable FAQ page in my current Nop
chajo10 wrote:
Arguing Views are not code is kind of pointless since Razor was built around making interjecting C# code into html easier. Look at your Html.Action. That is code made for Razor that is using some C#. So is it code? Seems like it, so rethink the statement you aren't changing code.
You have a point here, criticism accepted. Anyway, just as I've explained, you can add a widget to ANY zone. You only need to change if there is no such zone defined. So yeah, WE ARE NOT CHANGING CODE! :)
chajo10 wrote:
In that case, it would be a page, that use, could use a widget. Why you would want to build a widget into a lone page, I don't know, but whatever makes you happy. Btw, his info could be edited on the backend as well for this if built out.
Read POINT 3 to learn how to attach a page to a plugin, and have other place of nopCommerce link to it.
chajo10 wrote: I've not run across where it can be edited on the backend for widgets thus far, so yeah, it's possible if it makes you happy.
Based on Point 2 in my explanation above, you should now learn how it can actually be done. Otherwise, you might want to learn at https://www.nopcommerce.com/docs/75/plugin-with-data-access.aspx
chajo10 wrote: Lol, so much trolling. Do you know for certain I haven't made plugins? You might be disappointed if so. But whatever makes you happy. :P
You may have made 1000 plugins, but the information you've provided that "a Widget can't do this or cant do that" just doesn't make sense.
chajo10 wrote: It's manners, not manner... As for mind your manners, you're a shining example. Thanks! :P
I did not personally attack you originally and simply said that is changing code after you said it was not. For you to fire back so harshly makes me wonder why you would be so infuriated by something that should not have mattered.
Btw, people do come up with different ideas on a subject and can/will criticise one another about said ideas. Learn to deal with that aspect of life.
The fact that you corrected on my typo means you have lost your sense. I am open to criticism, but please, give fact.
Plus
chajo10 wrote: *sighs while shaking head*
is very offensive, in case you need to know. :)