Tasting a little dogfood, part 1 of...

I'm not going to make any attempts to wordsmith or be elegant in this series of posts.  Simply too busy for that at the moment.  But I did want to get a little information out there about my experiences in upgrading directly from 3.2.2 ==> 4.3.1.

All in all... this is a very good trip!  I think it's important to state that upfront as the remainder of this will all be about "what's broke" and "what's behaving oddly", etc.  You have to remember that we're still in stabilization mode on the 4.3 series... and by the time it's completely final it's going to be stupendous!

In no particular order... here's a few things I've encountered so far.  Some are core related, and some are module related.

• When upgrading the HTML/Text module, if you have an "empty" module ( an instance to which no text has been added ) it will throw an error to a non-admin user.  So, for example, on the site here there is an HTML/Text module on each project page which identifies "Team Members" ( left column, middle of page ).  I've left one of the pages in error so that you can see what that looks like, here.  If you're logged in as admin, you get the nice message "Click Here To Enter Your Content".
  
  By the way... the edit in place on both the content and the module title is AWESOME!  However, be advised that there is some caching strangeness going on with it still.
  
  
• Let's talk files & folders.  When I first attempted the upgrade... it left all the entries in the folders table with a trailing slash ( e.g. "subfolder/subfolder//" ).  This can cause a little confusion for all the modules ( and the core ) which reference files... so there's probably a LOT of additional problems with this at the root of them ( pun intended *grin* ).  So you'll see the entries with the double slash in the standard file picker... and if you are silly enough to try to synchronize files... you'll get double entries ( ones with double slashes and ones without ) which won't fix the issue.  It will just cause duplicate entries in the folders table which will then need to be deleted.  You need to FIX the double slashes first, and THEN resynch.  Here's a little SQL to update your folder table:
  
  UPDATE Folders
  SET FolderPath = REPLACE( FolderPath, '//', '/' )
  WHERE PATINDEX( '%//%', FolderPath ) > 0
  
  But that's not the WHOLE deal... Only run your file synch on the Portal Root.  Because if you run it against a subfolder it will INJECT the double slash in the middle instead of the original error at the end *grin*.  So you'd end up with something that looks more like this "subfolder//subfolder/"... by the way, the correct format for entries in the folders table is "subfolder/subfolder/".
  

This post was originally started on 6/23.  More to come...