| Hi Prophet, Hope your very well. I'm sorry it's taken me so long to respond to your post. I did see and print this post a few weeks back and have made progress with your suggestions. I just wanted to finally address each of your points... 1) Manage Categories Screen: a) Move Up & Move Down button appears to work when first clicked, but it isn't actually updating the db, just the tree at that point. so as soon as you go back to the kb the menu looks the same. This was a problem within RC1. If you update your 1.3 data using the f[INSTALL]\DatabaseScripts\UpgradeScripts1.3_to_2.0.sql script provided with the either RC2 or the final release migrated categorie will sort correctly. You'll find the following snippet of SQL within the 1.3_to_2.0.sql upgrade script within the RC2 and final releases... ----------------------------------------------------
-- Update CAtegory Sort Orders
------------------------------------------------------ set sort order
DECLARE @intSortOrder int
SET @intSortOrder = 1 -- create cursor
DECLARE @intCategoryID int
DECLARE MSGCURSOR CURSOR FOR SELECT CategoryID FROM InstantKB_Categories OPEN MSGCURSOR
FETCH NEXT FROM MSGCURSOR
INTO @intCategoryID
WHILE @@FETCH_STATUS = 0
BEGIN -- ensure sort order is sequential
UPDATE InstantKB_Categories
SET CategorySortOrder = @intSortOrder
WHERE CategoryID = @intCategoryID -- increment
SET @intSortOrder = (@intSortOrder + 1) FETCH NEXT FROM MSGCURSOR
INTO @intCategoryID
END
-- tidy cursor
CLOSE MSGCURSOR
DEALLOCATE MSGCURSOR GO This will ensure the category sort orders are updated to allow sorting however it will clear any current sort order and categories will be displayed in the order they appear within the database until sorted. You should only use this script if you continue to have any problems with this. b) if you delete a parent category the child categories remain hidden in the db.
Eg I created a category Test. then a sub category Test 2. I deleted Test, and Test 2 can't be found using the program. But the records for it remains in the db.
This isn't a big issue. Actually isn't not one at all. I just thought I'd make the remark just incase. We didn't manage to address this for the final update however it's something we will be looking to ensure in the 2.1 update. It would be nice to keep the InstantKB_Categories table clean. I would actually like to improve this area to allow the option to delete content and child categories. Similar to when you delete a custom tab. It's noted prophet and will be addressed. c) Sort orders didn't seem to be copied over from 1.3 (not even sure if they are being used in 1.3) It won't unfortunately prophet. You will need to resort your categories again after updating to 2.0. This is due to the new way we allow for sorting of categories. Previously we used to ask users to enter a number to represent the category sort order. This caused some confusion and we've moved towards providing options to simply sort data by clicking move up or move down. Due to the way this works the sort order field within your database needs to auto-increment similar to a identity field. Due to the unstructured way categories could be sorted within 1.3 it was not possible to copy over the existing sort order value without breaking the sorting functionality within 2.0. Hopefully this won't cause to much pain as it's much quicker to work with your categories in 2.0 using the new ajax based tree control. 2) Admin Reports (/Admin/AdminReports1-2.aspx) If you change the All Categories drop down when "Include child categories" is ticked the % values don't change. This was not resolved in the final release however i will be posting a small update to 2.0 to resolve 5issues spotted since the 2.0 final release. I'll be popping a post here once the update is available and detailing the issues it resolves. 3) Article Types Great suggestion Prophet. You'll find this feature now available within the 1.3_to_20.sql upgrade script provided with the final release. We now copy over any custom article types from 1.3 into the InstantKB_Types table and map these correctly to your migrated articles. You'll find the following code within the upgrade script to import custom types... -- import any custom types from 1.3
DECLARE @strArticleType nvarchar(255)
DECLARE MSGCURSOR CURSOR FOR SELECT DISTINCT ArticleType FROM InstantKB_ArticlesOld WHERE ArticleType IS NOT NULL
OPEN MSGCURSOR
FETCH NEXT FROM MSGCURSOR
INTO @strArticleType
WHILE @@FETCH_STATUS = 0
BEGIN
SET @strArticleType = REPLACE(@strArticleType, ':','');
DECLARE @intSortOrder int
SET @intSortOrder = (SELECT TOP 1 TypeSortOrder FROM InstantKB_Types WHERE TypeTabID = 1 ORDER By TypeSortOrder DESC)
IF NOT EXISTS (SELECT TypeID FROM InstantKB_Types WHERE TypeName = @strArticleType)
BEGIN
INSERT INTO InstantKB_Types (TypeName,TypeIcon,TypeSortOrder,TypeTabID) VALUES(@strArticleType,'',@intSortOrder + 1,'1')
END
FETCH NEXT FROM MSGCURSOR
INTO @strArticleType
END
-- tidy cursor
CLOSE MSGCURSOR
DEALLOCATE MSGCURSOR
GO Providing the types appears within the InstantKB_Types table before the upgrade script starts migrating articles the types will map correctly to your articles. I hope this helps Prophet. Looking forward to any further feedback 
Kindest Regards,
Ryan Healey
Director / Developer
 Explore our products...
http://demos.instantasp.co.uk/
|