The Dotnet Nuke blog is a collection of related modules which comprise of all the working parts of a blog. When the blog module is added to a page,all module are added
Blog Module
- Menu: List of blog related actions that a user can take, based on permissions (e.g. changing settings, adding a post, etc).
- Search: Utility for searching Blog content.
- Roll: List of blogs on the site (or in some logical grouping)
- Archive: Calendar indicating dates when blogs have been posted
- Posts: Display of the lists and content of the blogs.
You are in the process of setting up module and you do not want anyone to see it until you have completed it.
There are really four (4) different ways to think about giving access to Modules on your website. Who would you like to be able to see each module?
(1) Administrators: Only users who have the authority to "administer" your website can see these modules (so that means you)! This is a good setting to use for modules that you are in the process of setting up but don't want anyone to see until you are finished. You can use the Page Editors Only option of the Visibility selector when you add new modules to keep them private until you are ready.
(2) Unauthenticated Users: All visitors can view your Module anonymously. "Unauthenticated" means that the user has not logged in and may not even be registered as a user of your website. Think of this as "public" access... things that you want everyone to be able to see.When a Module is only visible to website Administrators a red border is applied to alert you of this. That way you won't forget that nobody can see them except you!
(3) Registered Users: Users that have filled out a Registration form on your website and now have a User Name and Password and have already logged in.
(4) Custom Group of Users: These are Registered Users that you have also placed into a special group or "Role" that you have created (e.g. "Family" or "Customers"). For more information on custom groups you'll want to read the tutorial: Manage Users.
Powered By DotNetNuke®
Microsoft Publishes Windows 7 Bugs List
Microsoft today published the full bug list for its Windows 7 operation system. For the first time ever, All known and reported bugs are to be made available to the public.Mr Hyan-Lee of Japan(photographed above) made the mistake of printing the whole list...
What is the first step in good programming?
The first step in good programming is to understand fully what the
program is supposed to do and the relationship between the inputs and the outputs.
The second step is to break down the process into its smallest component. This is
called modularity. A flowchart is very useful here. It is because of modularity
that you can use "libraries" of functions so that you don't have to reinvent the
wheel every time you program something.
The third step, implementation, is where you put together all the modules
according to the flowchart you designed.
What is the mark of good programming?
Actually, the first and most important rule of writing good code is to comment your code....In a past few days or months, you may need to go back and rewrite something. You need to be able to look at the code and know what it is doing. The most effective way of doing this is to comment your code as you write it.
Equally important, don't just start writing code. Sit down and write out a statement as to what you want your code to do before you ever start. That will help you stay focused on what it is you are trying to achieve.
