Last post Jun 16, 2006 11:21 AM by baycom
Apr 26, 2006 11:43 AM|baycom|LINK
We are working on a DNN Module that replaces the Admin/Pages core module, Page Settings and Module settings, without touching the core framework.
This implementation displays a dhtml tree view of all pages with all the panels contained and inside each panel, the modules.
Throgh simple drag and drop, the admin can then move pages and modules around, and the changes will be saved immediately through ajax calls.
Right clicking on any page or any module, will show a context menu, that will allow the admin to select between creating new pages/modules or editing the settings of pages/modules. All settings can be changed (only a few are not implemented yet for beta
testing purposes), but it is 90% complete.
The advantage of this module is that for medium/large sites, it avoids the need to be posting back and refreshing on every page click, and also, having to navigate to each page in order to change page/module settings/permissions etc. Time savings can be
We are looking for 3-5 beta testers, that would give us feedback on the module. If interested, please contact us through the forum, and we will respond with an email and the PA.
Apr 26, 2006 08:26 PM|lou|LINK
Apr 26, 2006 09:03 PM|locopon|LINK
Apr 26, 2006 09:22 PM|SamTanner|LINK
Andreas, I'd like to test this as well.
Thank you -
Apr 27, 2006 05:08 AM|baycom|LINK
thank you for your interest.
I have sent an email to each one of you with my direction, so that I may send you the PA.
Apr 27, 2006 09:51 AM|dharmesh|LINK
Would love to try it out. Count me in (dshah at onstartups.com)
Apr 28, 2006 12:27 AM|SamTanner|LINK
Andreas, I finally had time to install this module tonight, and it's not working on my machine...
The installation gave no errors and reported positive results.
The module shows up on the drop-down list, but on placing the module I get a messagebox with "Parent node not found!!" (with two exclamation points) - I press OK and the module shows up with an empty left pane titled 'Pages and Modules' and Settings information in
the right pane.
Each time the page loads the same messagebox comes up.
I see no settings or controls that I can access.
I'm running DNN v3.2.2 on localHost, .NET Framework v1.1.4322.2032, SQL Server 2005, WinXPPro, AMD Turion 64 (notebook) w/1 Gig RAM.
Don't tell me this module is for DNN v4 only...
Apr 28, 2006 05:25 AM|baycom|LINK
The PA has been tested on DNN 3.1.1 and 3.2.2. Armand has also tested it on DNN4.0.3.
I think your version and CPU setup are not a factor here. Can you tell me a bit more about your DNN setup?
These are the things that I can think of that might affect the results.
Has naybody else had the same issue?
Apr 28, 2006 07:17 AM|SamTanner|LINK
A fresh install with no mods, only the default modules, but quite a few skins installed. So many that I didn't even think to install this module on a default skin. I did reset to the default DNN blue this morning and it made one small difference. I now have
a small blue pencil icon in the lower left, with no tooltip and another (un-named) option in the module action menu, normally like "edit". On clicking I'm taken to an empty page with address
The installation is at c:\dotnetnuke and the HTTPAlias is localhost/dotnetnuke.
Apr 28, 2006 07:45 AM|baycom|LINK
Good Morning Sam,
I have created a new download zone, and you should have received an email with details.
The new download removes the "edit" link that does not apply as well as adding some functionality and resolving a few bugs.
However, I do not think that it will resolve the main issue: parent node not found. From what you tell me, it should work on your installation, so something else must be going on.
On my machine, I have a DNN3.2.2 version installed with a Catalook trial module, and standard skins, and it is working fine.
I am thinking about sending you a separate js script that may give some insight as to what parent node does not exist, instead of giving you a generic message.
Have you tried on any other version of DNN?
Apr 28, 2006 07:55 AM|SamTanner|LINK
I just receied the email /update, installed (deleted the module from the page first) and still have the error. The edit link is gone and now I have a small 'gear' icon in the upper-left but it only responds with the same error message.
Too bad I have to go to the day job now.
Send the js and I'll toy with it tonight & over the weekend. I only have this version installed on the machine.
Hey - that's why they call it testing!
Apr 28, 2006 08:04 AM|baycom|LINK
No doubt :)
I have sent you the script.
Apr 28, 2006 06:53 PM|SamTanner|LINK
Ok, I installed the script and logged in as host, went to the test page and first got the original error message, upon clicking OK, got this long one:
ID=62|345 prn= capt= Links url= ic= /DotNetNuke/DeskTopModules/XepientSolutions.XSPagesAdmin/images/dnn_module.gif exp=true chk=false extra=LeftPane
I may have crossed up some capitalizations and spacing above, but that's the essence. I looked in the listed subdirectory and found the dnn_module.gif mentioned...
Apr 28, 2006 11:47 PM|codegalaxy|LINK
Apr 29, 2006 03:49 AM|baycom|LINK
the second pop-up you got is a debugging message I put in in the modified js I sent you.
the message can be interpreted as the following:
in tabid 62, there is a LeftPane, and to that pane, it was associating moduleid 345. However even though LeftPane is being reported as the parent node for that module, it was not added to the tree (prn=[empty]).
So, there must be something going on with the routine that adds the panes as parents. I am not sure why this happens (I am not having that problem on various installation tests and Nokiko did not report it either), and will need to take a deeper look. Unfortunately
I will not be able to do so until tuesday, but it is a good start.
As a starting point I would go to TabId 62, and see what modules are installed in the left pane. This is probably the home page. I would try to move that module around, and refresh the Open-PagesAdmin page to see if it changes anything.
Apr 29, 2006 04:01 AM|baycom|LINK
I have sent you an email with instructions on how to get a preview.
While we have exceeded the max number of testers that we were looking for, we are still interested in feedback.
Apr 29, 2006 10:25 AM|SamTanner|LINK
TabID 62 has a 'store-bought' skin applied, I won't mention the name. It's left pane held a core Survey Module that was set to 'display on all pages' from the home page. First I deleted TabID 62, and the PagesAdmin started working. I went to the recycle
bid and reinstated TabID 62, and PagesAdmin errored with the same code. Then I went to TabID 62 and moved the Survey Module over to the right pane, and PagesAdmin errored again with a similar message except now saying xtra=RightPane. I went back to TabID 62
and deleted the offending module, and PagesAdmin worked again.
The only thing unusual I saw at the time was a difference in capitalization between the skin and the js error message. The skin is using all lower-case, like leftpane, rightpane and the js error messages use CamelCase like LeftPane, RightPane. I modified the
skin .ascx to be id="LeftPane" vs. id="leftpane", but when I went to recycle the module back out to the page to test again, it didn't show up in the recycle bin! I went to the home page Survey Module's settings and re-set it to display on all pages. Now the
AdminPages module works no matter which pane the Survey module sits in, or what id the pane has.
It seems to me there must have been a problem in the particular instance of the survey module on TabID 62 only. The PagesAdmin Module is working fine now...
Apr 30, 2006 10:21 PM|lou|LINK
Can I have some intsructions too?
Apr 30, 2006 10:43 PM|codegalaxy|LINK
Okay this is a test machine that I put it on - ASP.NET 2.0 but running 3.2.2 clean install with only two other modules installed
THe functions seem to work but the update never finishes - functionality seems like a good idea but I dont know if it works
May 01, 2006 10:28 AM|baycom|LINK
you should have received instructions with the first version of the control that I sent you through email. Additionally, there is a readme.txt in the .zip download that explains how to set-up the module. Once installed, the right pane in the module also
shows instructions on how to operate the drag and drop as well as the context menu options.
Let me know if you have more specific needs.
May 01, 2006 10:32 AM|baycom|LINK
From what you are describing, I suspect that you have not modified the web.config to add the required Ajax entries. The readme.txt file in the .zip you downloaded has specific steps to follow in order to setup ajax. Without ajax, the module will install
but never finish updating.
If you did follow the setup instructions, and you are still having problems, let me know all information you can think of so that I may reproduce the issue on my machine.
May 01, 2006 10:34 AM|baycom|LINK
thanks a lot for the detailed report. I will be back in the office tomorrow and take a look at the code. I believe it is an issue with the Pane Names, and easily corrected by adding a ToLower or ToUpper when doing pane name comparisons.
Great Cactch. I will let you know.
May 01, 2006 05:14 PM|idumlupinar|LINK
May 01, 2006 06:23 PM|ikamiksok|LINK
I'm going to chime in here with some other feature suggestions. While you are doing this, it would be nice if you could customize the admin interfaces that a new admin role has access to. So, for instance, if I have some very novice admins and don't want
to confuse them with the full admin functionality, I could select what items to allow them access to.
For instance, I don't want to give a user access to site settings (as they could break things there) but I do want them access to edit pages and move modules around.
It would be nice if this interface was very intuitive and easy to use with great documentation and designed for a beginner. So I could give someone admin access to edit their homepage and they would have no problems figuring it out.
May 05, 2006 02:56 PM|baycom|LINK
I have made quite a few changes and additions to the module since the last post, and mostly following your suggestions and feedback.
1. I fixed all bugs reported so far.
2. The module no longer uses Ajax.Net as the ajax provider and replaced it with another provider that is quite robust (some say more robust). The requirement for using the Ajax.Net .dll was that <trust> be set to Full (because it uses reflection). This
is not an insormountable problem when running on localhost, but when in a Hosting environment, some ISP's may set it to medium in the machine.config with no possibility to override it. This restriction was not acceptable. The new Ajax provider does not need
full trust. As an added bonus, it does not need any web.config changes, so the module can be installed seamlessly. (I had implemented an automatic web.config modification routine, but now it is no longer needed).
3. There is a new feature: the ability to manage deleted pages and modules. (In DNN, these are found in the recycle bin tab). Now these modules can be managed, and reinstated directly from the tree menu, seamlessly. (thanks for the suggestion Mauricio).
4. Another feature is that from the page context menu, now you can navigate directly to the page you are interested in.
5. Hovering over a module with the mouse, and pressing the control key will now expand the node. This is useful when dragging and dropping pages and/or modules on nodes that have not been previously expanded.
6. Many other small changes.
The new module is available for download on the beta site. The readme.txt file is gone. Just install the zip as any other module.
As a last note, I would like to thank the people that have taken the time to offer their feedback so far. If you have not done so yet, I incourage you to do it as soon as you can. There are only 5 testers and I look forward to everybody's feedback. If
you are not able to, please let me know quickly, and we'll make room for others that are interested as well.
Last Last note: It would be nice to have a test site where non testers could see the module in action. Unfortunately, the only DNN site I am running is 3.0.13 which is incompatible due to the sweeping changes between that version and 3.1.x and up. If
you do have a test site where the module could be installed, I would be grateful if we could install the module there for everybody to see it.
Have a nice weekend.
May 06, 2006 02:47 AM|bluebirdzx|LINK
May 06, 2006 07:29 AM|SamTanner|LINK
May 06, 2006 12:02 PM|baycom|LINK
I immagine that you are using the same configuration as the last time: DNN3.2.2 with some pages with a custom skin?
If so, I'd like to test the module reproducing your setup. If you can, please send the skin at my personal email, and I'll try to go through a debug and see what is happening. I did add some code for camel case vs. lower case skins, but the fact that nothing
is showing up in the tree, means that it does not even get that far.
May 06, 2006 12:05 PM|baycom|LINK
I wanted to thank all the people that are volunteering to test. We purpusefully wanted to keep the number of testers to 3-5 to keep it manageable, and we reached that number the first day we started this thread.
For everybody else that is interested in seeing the module at work, I will set-up a test site in the next week or so, so that you may see it in action.
May 06, 2006 12:13 PM|SamTanner|LINK
When I removed the previous version, I restored my original, default web.config file with only the connection string changed - should there be any changes to the web.config at all?
May 06, 2006 01:05 PM|baycom|LINK
no web.config modifications are necessary for the new version.
May 06, 2006 01:28 PM|SamTanner|LINK
Looking back at the error, I see there is an extra space between the words 'node' and 'not'.
May 06, 2006 02:26 PM|baycom|LINK
Can you look at the skin you have and see if it has some lower case pane names? If everything else fails, I would try changing the entire site's skin with another standard DNN skin, such as the yellow or gray one.
I thought this issue had been resolved, but on monday I will do more tests, changing pane names and case.
May 06, 2006 03:29 PM|SamTanner|LINK
It's a pop-up, like the previous. Using the default dnn blue, fixed-width horizontal menu, here's the content area code:
<TABLE cellspacing="3" cellpadding="3" width="100%" border="0">
<TD class="toppane" colspan="3" id="TopPane" runat="server" valign="top" align="center"></TD>
<TD class="leftpane" id="LeftPane" runat="server" valign="top" align="center"></TD>
<TD class="contentpane" id="ContentPane" runat="server" valign="top" align="center"></TD>
<TD class="rightpane" id="RightPane" runat="server" valign="top" align="center"></TD>
<TD class="bottompane" colspan="3" id="BottomPane" runat="server" valign="top" align="center"></TD>
May 06, 2006 03:46 PM|baycom|LINK
It seems that this skin is not a factor. There is nothing different about it.
Do you use any other skin throughout the site? If you do have a custom skin on any other page, that could be the cause. I would try to apply the same standard skin to the whole site, and then once the module is working, start adding different skins. If
the module breaks after adding a particular skin, please post its html or send it to me, so that I may make the appropriate code changes.
May 06, 2006 05:06 PM|SamTanner|LINK
There are only two pages now, 'Home' and 'Test'. Both are using the default dnn blue skin. Home has only one module, the text/html. Test has the Admin module, and this page is set to Administrators only. The error remains.
May 06, 2006 05:30 PM|baycom|LINK
I tested on 3.1.1 and 3.2.2 on different installations on different machines, and have not had this issue.
Is anybody else having the problem reported by Sam?
May 06, 2006 09:43 PM|brian_c|LINK
Jun 02, 2006 04:51 PM|SamTanner|LINK
Jun 06, 2006 11:34 AM|baycom|LINK
I had to delegate the completion of a part of the functionality to a team member, and it will take a while before I can review the changes and re-post the latest version.
The project is still advancing (as a matter of fact in our new site
www.opendnn.com we used this module exclusively to administer pages), but it just not a high priority.
Since we have updated to DNN 3.2.2 I can now create a sub-portal to use as a demo. If we see that interest is high, then we may increase the priority and dedicate more resources to its development.
Jun 06, 2006 12:39 PM|SamTanner|LINK
It's a great module, please keep the community informed on it's development.
I'd also like to know if the problems I encountered during testing were ever solved.
Jun 06, 2006 04:41 PM|brian_c|LINK
typical.. announce module, ask and get beta testers.. then leave everybody in the dark... and then weeks later.. well.. maybe we can do this another time..
Jun 15, 2006 07:09 AM|baycom|LINK
I created a demo site so that everybody can see the module in action and download it.
Since access to the module means full administration rights, you will need to register in order to access it. So when you access the site, please do not delete pre-existing pages/modules that serve for the correct functioning of the site.
There is also a download section where you will be able to download the PA.
the site is: www.opendnn.com/pagesadmin
Jun 16, 2006 09:55 AM|simonduz1|LINK
Jun 16, 2006 10:11 AM|rodneyjoyce|LINK
Jun 16, 2006 11:21 AM|baycom|LINK
The module does not require any configuration. If you installed it, and added it to a page, thaen that should be it.
This beta version still has some issues with non standard skins, and it has not been tested on all versions of DNN. So far only on DNN3.1.1 and DNN3.2.2. One of our betat testers tested it on DNN4.0.2 and reported it working correctly as well.