Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TECHNICAL SUPPORT] LPS-45278 Search portlet shows some web content in Asset Publisher #11

wants to merge 113 commits into from


None yet
Copy link

commented Mar 21, 2014

No description provided.

vilmospapp and others added some commits Mar 5, 2014

LPS-45237 Same as BackgroundTaskConstants. We need to obtain a human …
…name for the relations to display them to the user when configuring the mentions settings.
LPS-45262 This should not be needed anymore.
Callers should compose resourceBundles appropriately when calling _get

Pablo Pinheiro and others added some commits Feb 11, 2014

LPS-33161 We don't create ddmField when we're translating a content a…
…nd the field is set to be not localizable. Journal article XML also don't need to have that dynamic-content element
LPS-45232 The NullCacheModel from UserPersistenceImpl is not a real U…
…serCacheModel, can not unconditional do the cast
LPS-44944 Move methods in WikiUtil to WikiSettings. @brian: note that…
… the _fallbackKeys map in WikiSettings is formatted differently from the one in MBSettings. This is intentional because this map represents the chaining to follow when searching for properties. Thus, for example, when getting the property "emailFromAddress", the fallback mechanism will look in PropsKeys.WIKI_EMAIL_FROM_ADDRESS if the former is not found. If it still not found, it will jump again from PropsKeys.WIKI_EMAIL_FROM_ADDRESS to PropsKeys.ADMIN_EMAIL_FROM_ADDRESS (as declared in the second line of the map). Then there's an empty line to denote a new chain start and so on. If you still don't like this formatting, we can try to abstract the chaining concept in a specific class to make this relation more evident.
LPS-44944 Avoid hardcoding "magic" default values in WikiSettings.
We assume that the default must *always* be set in

This comment has been minimized.

Copy link

commented Mar 21, 2014

OK, I should think twice if it as an issue at all,.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.