| Author |
Messages |
|
Adeptris
Posts:6
 |
| 05/24/2007 1:54 PM |
|
Hi everyone, I am not a DNN programmer but have started to look at it more, after being a plug and play user of DNN for a while now.
I have purchased the module builder and read the demo screens, but I was hoping for a pdf file, that would take me from A - Z, parent and child tables, and linked table values.
Why I purchased Module Builder is to add a price group list to the store module, as I take photographs as a hobby, if I wanted to sell them I would need a price list / matrix, as an image can be supplied in different sizes and materials, A2, A3, A4 - Gloss, Matte, Lustre and Canvas, as an example.
So any guidance would be most welcome, if there was a step by step tutorial that built the example on this site would be a good starting point.
I look forward to any replies!
David |
|
|
|
|
host
Posts:93
|
| 05/24/2007 4:58 PM |
|
There are resources under Community Resources --> Training
There are also some videos under screenshots.
The interface is numbered to provide a step-by-step process for module creation.
Hope that helps. |
|
|
|
|
Adeptris
Posts:6
|
| 05/24/2007 5:19 PM |
|
Posted By host on 05/24/2007 4:58 PM
There are resources under Community Resources --> Training
There are also some videos under screenshots.
The interface is numbered to provide a step-by-step process for module creation.
Hope that helps.
I have looked at these, but they are not detailed enough, just to say do this next is no help to someone new, an example in pdf download, step by step is really required.
I was looking at another post for the Parent Child example, I followed the example, creating new tables, but when i add a record to the parent I get {fldxxx} where the parent fields should be, there is no information as to where the {SelectLink}EmployeeName{/SeletLink} should go, and I get an error saying a quote is expected for a text field on the detail.
The Default Request.querystring("EmployeeID") is cut off from view, as it says RQV.Request.querystring("Empl, I am sure these are minor problems, but frustrating when you are starting out.
A document style step by Step build, Parent and Child would be a good starting point!
David |
|
|
|
|
host
Posts:93
|
| 05/24/2007 5:47 PM |
|
I understand.
Let's see if we can get you going.
{fldxxx} is a placeholder for you to replace with an actual field, like {fldLastName}
{SelectLink}EmployeeName{/SelectLink} would go in the Template as it gets repeated for every record that is returned. The Header and Footer are only processed once. So anything being affected by every record should be in the Template itself.
Not sure what you mean exactly by "I get an error saying a quote is expected for a text field on the detail." Is this a code crash? In the parent? or child?
My suggestion is to get the master module working the way you want, before you dive into relationships. Doing so will get you familiar with what's going on. |
|
|
|
|
Adeptris
Posts:6
|
| 05/25/2007 12:24 AM |
|
Many Thanks.
1. I have added the field Name in the Template, and that works really well now!
The Child / Linked Table is the problem now, it does not even load.
This is the Error I get when I add the Detail Module, I will try again tonight!
David
Error: PriceGroupLine is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: C:\DotNetNukeDev\DesktopModules\PriceGroupLine\ViewPriceGroupLine.ascx.vb(85): error BC30648: String constants must end with a double quote. ---> System.Web.HttpCompileException: C:\DotNetNukeDev\DesktopModules\PriceGroupLine\ViewPriceGroupLine.ascx.vb(85): error BC30648: String constants must end with a double quote. at System.Web.Compilation.BuildManager.CompileWebFile(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.UI.TemplateControl.LoadControl(VirtualPath virtualPath) at System.Web.UI.TemplateControl.LoadControl(String virtualPath) at DotNetNuke.UI.Skins.Skin.InjectModule(Control objPane, ModuleInfo objModule, PortalSettings PortalSettings) --- End of inner exception stack trace --- |
|
|
|
|
host
Posts:93
|
| 05/25/2007 5:56 AM |
|
| It sounds like something is off in the code of your module. Could you send the module to support@socani.org so that we can take a look at it? |
|
|
|
|
Adeptris
Posts:6
|
| 05/25/2007 2:33 PM |
|
Hi my mistake, sytax error, I have managed to compile the two modules, both are uploaded, but I select add on the child form, I get no errors, but I cannot view the lines, I will export and send the module, if you could correct any mistakes this time, I will use it as a guide going forward.
I have made more progress in a couple of hours than I have in a month! :~}
Many Thanks
David. |
|
|
|
|
Adeptris
Posts:6
|
| 05/29/2007 2:23 AM |
|
All Sorted now thanks to your quick and detailed replies.
I did follow your forum example in the "Applicate" thread, and the syntax error I made, PriceGroup instead of 'fldPriceGroup' is there in the thread as well, you may want to edit this so others do not make the same mistake .
http://www.socani.org/CommunityResources/Forums/tabid/53/forumid/2/postid/30/view/topic/Default.aspx
I would urge and suggest that you make a couple of module examples for download, for new people like me, the lack of examples is the only negative thing that would say if asked for my opinion of the module builder.
Any of your employee examples would have been helpful, as it covers a lot of area's, if you made it downloadable, this would mean that users like me that needed help, could find the answers in the examples, empowering the user to resolve any issues, rather than emailing support.
I have so far found it easy to use, well supported, and worth the subscription.
David :) |
|
|
|
|
host
Posts:93
|
| 05/29/2007 6:16 AM |
|
Glad you're making progress and finding it easy to use.
We did change the post, I see where the confusion was.
We are working on providing modules for download. |
|
|
|
|
|