We've corrected a few more small things we've noticed, as well as added a few new features. Amongst other things - here are the notables -

1. Hopefully - corrected the DNN 3.3 issue which caused the Action menu to evaporate.
2. Extended the functionality of the System variables using Reflection. Now you can not only do things like the standard [TabID,System], but actually access deep properties of the runtime. For instance [Request.UserAgent,System] or [PortalSettings.ActiveTab.FullUrl,System]. This is a complete mirror of the provided properties, so there will be an extensive list in the release documentation.
3. Modified the ACTION tag to allow an additional parameter to generate only the javascript postback code, and not the complete href attribute. To do this, simple add a ,False to the end of the action tag (demonstrated in the Repository LP).
4. Added a new ascx control to meet the needs of our clients who need the ability to use a ListX control as a Skin control. This is handled throught the xListingSkin.ascx control and can be used in a skin by setting up the tag with the TabModuleID,ModuleID and TabID of the target skin element. Similar to this:

<%@ Register TagPrefix="b4" TagName="LISTX" Src="~/DesktopModules/ListX/xListingSkin.ascx" %>

<b4:LISTX runat="server" id="b4ListX" TabID="202" ModuleID="641" TabModuleID="333" />

This will use the configuration for the Tab/Module you initially created (and still manage), but now the ListX can appear as a skin control.

Finally, you will find in the following post a ListX Package (LP) which provides a brief repository handling interface, so you can roll back changes easily within your ListX controls. To install the LP, simply add a ListX module to a page. Click the Settings of that module, and select the file from the Installer interface (bottom of the Settings page). Once selected, press the Install link. The script and configuration will handle the rest.

Once installed - you will see two drop downs, Tab and Module. Select the Tab to filter the module for that tab, select the module to view the history of the updates (date of update). Click the row pertaining to the date/time you want to roll back to. A Confirmation link will appear to the right of the date. Click the confirmation date to roll back. The Settings will roll back to the requested version, and the cache will be cleared in order to experience the change immediately.

AS PROMISED - The Repository has been updated to work in DNN with and without objectQualifier utilization. Additionally, instructions have been added to the UI, and a few visual appearance things have been improved. Use this copy!

Hey - I've updated the download link above for Prerelease 8. The DNN 4 Serialization issue has been corrected thanks to alot of back and forth testing with TSchwingle! The problem actually was resolved using a post from Dotnetnuke's site (Charles Nurse) -

http://www.dotnetnuke.com/DotNetNukeProjects/ModuleContacts/tabid/832/EntryID/241/Default.aspx

Hi, I like the repository system! One question - I installed the repository through a module that already had a ListX application designed. Now it seems like that module is permanently assigned to being a repository manager. Is there a way to 'turn off' the repository manager and return it to being a standard ListX module?

Unfortunatly, this could be done, but isn't the case in this release of the repository. The reason is, while the repository DOES execute a backup of all the existing XML configurations for the ListX modules - it does this AFTER assigning the configuration for itself. I'll be sure to change the order of execution in the .install script for the repository. For this to be the case, all I would need to do is execute the script prior to the configuration change.

OK thanks

Kevin,

I applied our PortalSwitcher menu using the new xListingSkin.ascx and got a strange result - the [*TabID] and [TabID,System] are always returning the TabID of the portal where the referenced module is located. But, [*PortalID] and [PortalID,System] as well as [PortalSettings.PortalName,System] all return the current portal values, which is what I'm expecting. No matter where I navigate to, the tabID values are always that of the referenced module portal.

Any ideas?

Mike Crain

Another anomaly with regard to a listx skinobject. It doesn't evaluate a Message Action when clicked on, whether or not the skinobject listx is in the same portal as the source/referenced module. The Message Action only gets evaluated at the source module. And again, [*TabID] and [TabID,System] are always the TabID of the Tab that the source module resides, regardless of portal and tab.

Mike

Is the final release going to be free to current users or is there an upgrade path? Also, I am anxious to see the documentation that you all have feverishly been working on!

Current licensed users will have a free upgrade to the latest release of ListX.

Bi4ce

Can you please tell me how I can upgrade?

My upgrade just showed up this weekend at Snowcoverd.com. Go to YourAccount and then Patches/Hotfixes. It should be one of the top items on your list.

Thanks. Never noticed that link. I see I also have some updates for other modules!