254 shaares
29 results
tagged
module
I want to set up a simple listing of cards (with a heading, a picture, some text, and a link) and when the user clicks on the link of a card, it brings them to a full "details" view that has a friendly URL. Very similar to a news module but considerably simpler.
So I would have https://mywebsite.com/careers and then a listing. When a user clicks on a career, they would be taken to https://mywebsite.com/careers/dairy-farmer
The URL would be the title of the career. On the details page, there would be a lot more content as well, that the content editor could manage.
Is this video still relevant? https://youtu.be/RtmOYvaeJpo
Or is there a newer, simpler way of doing things? Also, is this something I can set up in the Content module as opposed to the App module?
So I would have https://mywebsite.com/careers and then a listing. When a user clicks on a career, they would be taken to https://mywebsite.com/careers/dairy-farmer
The URL would be the title of the career. On the details page, there would be a lot more content as well, that the content editor could manage.
Is this video still relevant? https://youtu.be/RtmOYvaeJpo
Or is there a newer, simpler way of doing things? Also, is this something I can set up in the Content module as opposed to the App module?
What is the difference between DNN module control types Edit and View
Turn-key white papers are how we share some of our best advice to the public. We take pride in ensuring that best practices are followed by all, even those that are not our current customers.
ASP.NET Ajax allows developers to add Ajax functionality to quickly introduce Ajax features without extra development, however, usage of this within DNN is met with some challenges.
Many extension developers rely on the internal DotNetNuke Text Editor to provide rich-text editing experiences to users, however, Visual Studio may not always make this process straightforward.
DotNetNuke provides its own internal data access strategy for accessing SQL Server, this process works well for most standard situations. However, complex items such as the ability to call using Table-Valued Parameters can be less straightforward to implement.
Working with custom solutions it is commonplace to need multiple extensions, it is possible with small modifications to package those extensions all at once.
Over the past 6 months, I have been pushing to establish a set of NuGet packages for DotNetNuke extension development, these have finally been released!
Developers will often need to add custom functionality that ties into, or consumes data from, existing DNN tables. There are many ways that one can do this, and this post explores one of the best ways to do this without impacting DNN.
DNN provides methods for encrypting and decrypting parameter information, however, there are a few gotchas that can impact the usability of this feature.
Module developers have many choices as they create their extensions. One of which is around the level of emphasis placed on performance, a few simple things can set your module apart from others with these performance tweaks.
Installing multiple DotNetNuke extensions at the same time can be tedious and result in unexpected downtime. Thankfully there is an easy way to install multiple extensions at once.
Now that we have a good structure in place, how do we deploy to different environments and test our DotNetNuke solutions?
In the final installation of my Enterprise Extension Development blog series we look at the actual project file structure and focus on reusability.
Enterprise extension development is a mindset and a technology set. The prior blog post looked at the mindset, now we look at the technology.
There is a difference when developing enterprise-grade solutions vs those quick-hit type items that are more bespoke. This post explores some of the differences in structure and process for the enterprise developer.
Customizing the latest DNNModule Development Project Templates