App Store showing blank pages in Yosemite

Question

After my update to Yosemite the AppStore behaves severely crippled.
The main "Featured" , "Top Charts", "Updates" and "Purchases" page work normal,
however the "Categories" page only shows the category titles, and worse: going into any detail page for an App gives me a completely blank page.
I already tried to restarted to system, but no change.
When starting AppStore from the iTerm the following error is included on startup (not sure if it's an expected message):
2014-12-02 10:50:01.130 App Store[9040:43093] Unknown class 'FRPageController', using 'NSObject' instead. Encountered in Interface Builder file at path /System/Library/PrivateFrameworks/StoreUI.framework/Resources/Base.lproj/FRStor eViewController.nib.
2014-12-02 10:50:01.131 App Store[9040:43093] Failed to connect (delegate) outlet from (NSObject) to (FRNavigationController): missing setter or instance variable
2014-12-02 10:50:01.132 App Store[9040:43093] Failed to connect (view) outlet from (NSObject) to (FRWindowBackgroundView): missing setter or instance variable
2014-12-02 10:50:01.132 App Store[9040:43093] Failed to connect (pageController) outlet from (FRNavigationController) to (NSObject): missing setter or instance variable
2014-12-02 10:50:01.171 App Store[9040:43093] NSWindow warning: adding an unknown subview: <_NSThemeCloseWidget: 0x7fae91f23430>
2014-12-02 10:50:01.173 App Store[9040:43093] Call stack:
  0   AppKit                              0x00007fff95b5ba9c -[NSThemeFrame addSubview:] + 107
  1   AppKit                              0x00007fff9554aa3f -[NSView addSubview:positioned:relativeTo:] + 208
  2   StoreUI                             0x0000000100a1e10a -[FRWindow handleToolbarViewChangedNotification:] + 1085
  3   CoreFoundation                      0x00007fff976e8cbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
  4   CoreFoundation                      0x00007fff975da1b4 _CFXNotificationPost + 3140
  5   AppKit                              0x00007fff954c6989 -[NSView _postFrameChangeNotification] + 422
  6   AppKit                              0x00007fff954c5996 -[NSView setFrameOrigin:] + 862
  7   StoreUI                             0x0000000100a1df90 -[FRWindow handleToolbarViewChangedNotification:] + 707
  8   StoreUI                             0x0000000100a1db24 -[FRWindow setToolbar:] + 183
  9   App Store                           0x00000001009f214f App Store + 8527
  10  AppKit                              0x00007fff956dc4e7 -[NSWindowController _windowDidLoad] + 586
  11  AppKit                              0x00007fff956c36a2 -[NSWindowController window] + 110
  12  App Store                           0x00000001009f19c8 App Store + 6600
  13  CoreFoundation                      0x00007fff976e8cbc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
  14  CoreFoundation                      0x00007fff975da1b4 _CFXNotificationPost + 3140
  15  Foundation                          0x00007fff97963ea1 -[NSNotificationCenter postNotificationName:object:userInfo:] + 66
  16  AppKit                              0x00007fff9548e187 -[NSApplication finishLaunching] + 440
  17  AppKit                              0x00007fff9548dc51 -[NSApplication run] + 128
  18  AppKit                              0x00007fff954792d4 NSApplicationMain + 1832
  19  libdyld.dylib                       0x00007fff908dc5c9 start + 1
  20  ???                                 0x0000000000000001 0x0 + 1
2014-12-02 10:50:03.094 App Store[9040:43093] addOperation <ISProcessPropertyListOperation: 0x7fae91c9a8f0>{name = '(null)'}
I've also performed a "Linc Davis system analysis", the results of which can be found here in Pastebin:
http://pastebin.com/1J2cXYZx
Any suggestions?
Thanks,
Martijn

Answer 1

Please read this whole message before doing anything.
This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
Step 1
The purpose of this step is to determine whether the problem is localized to your user account.
Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”
While logged in as Guest, you won’t have access to any of your documents or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this behavior; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.
Test while logged in as Guest. Same problem?
After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.
*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.
Step 2
The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of the file system or of certain system caches.
Please take this step regardless of the results of Step 1.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards, if applicable. Start up in safe mode and log in to the account with the problem. You must hold down the shift key twice: once when you turn on the computer, and again when you log in.
Note: If FileVault is enabled in OS X 10.9 or earlier, or if a firmware password is set, or if the startup volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to start up and run than normal, with limited graphics performance, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal startup may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
Test while in safe mode. Same problem?
After testing, restart as usual (not in safe mode) and verify that you still have the problem. Post the results of Steps 1 and 2.