Why IM:get.content.record Tag Does Not Honor The Current/Display Locale (But Always Using User Default Locale) For the Access(ContentUserVisit) Count?
Last updated on DECEMBER 09, 2015
Applies to:Oracle Knowledge - Version 8.2 and later
Information in this document applies to any platform.
The IM:get.content.record tag always uses the logged-in user's Default Locale for the access(ContentUserVisit) count despite that the current/display has already been switched to other non-default locale (that is configured/allowed for this particular IM user).
Older versions of the OOTB infocenter webapp do not allow the logged-in user to switch to other current/display locale (that is configured/allowed for this particular IM user). ie, The current/display locale will always be the same as the logged-in user's default locale. As customers has customized the OOTB infocenter webapp to allow switching to other current/display locale (that is configured/allowed for this particular IM user), then this defect will be visible when you inspect/compare the IM contents' expected access(ContentUserVisti) counts among different locales.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms