I have used Symfony '2.3.*' version in my project. after updating the composer. I am getting following error and not able to fix the issues.
Error is:
InvalidConfigurationException: Unrecognized options "fallbacks" under "framework.translator"
Kindly Help to fix this issue. Thanks in advance.
Please note the difference that was introduced in 2.3.25:
New in version 2.3.25: The fallbacks option was introduced in Symfony 2.3.25. Prior to Symfony 2.3.25, it was called fallback and only allowed one fallback language defined as a string. Please note that you can still use the old fallback option if you want define only one fallback.
Source: http://symfony.com/doc/2.3/reference/configuration/framework.html#translator
Does this help?
Related
I just tried to upgrade to Symfony 5.0, however, I get the following error:
You have requested a non-existent service "translator.selector".
In my code in services.yaml I have
Symfony\Component\Translation\MessageSelector: '#translator.selector'
https://github.com/symfony/symfony/blob/master/src/Symfony/Component/Translation/CHANGELOG.md I saw that it was removed. How should I continue? Thanks in advance!
Best way is to check the Changelog https://github.com/symfony/symfony/blob/master/UPGRADE-5.0.md
The MessageSelector, Interval and PluralizationRules classes have been removed, use IdentityTranslator instead
we upgraded from HV 4.x to HV 5.4.2 and now when we have interface like following
#NotNull
List<AccountInfo> getMultiClientAccountBalances(#NotNull ClientContext clientContext, #NotNull Optional<AccountFilter> accountFilter);
I'm getting error:
javax.validation.UnexpectedTypeException: HV000186: The constraint of type 'javax.validation.constraints.NotNull' defined on 'getMultiClientAccountBalances.arg1' has multiple matching constraint validators which is due to an additional value handler of type 'org.hibernate.validator.internal.engine.valuehandling.OptionalValueUnwrapper'. It is unclear which value needs validating. Clarify configuration via #UnwrapValidatedValue.
I know it can be fixed by adding #UnwrapValidatedValue to the field, but this must be added to every method what is a lot of work for me. Is there any simpler solution (besides upgrade to HV6.x)
Unfortunately I don't see how we could change this behavior in 5.4 without breaking other use cases.
And there is no easy way to disable the optional value handler as it's added unconditionally.
So I would say you have two solutions:
a search and replace of all #Constraint Optional to add the UnwrapValidatedValue option
or move to HV 6, where we totally reworked this feature and where, I think, it should work as you expect it. I know you didn't want this answer but it is what it is...
The issue with 1. is that we removed this annotation from HV (it was experimental) in favor of a standard feature included in Bean Validation so you will have to remove it when moving to 6.
I don't know your exact environment but HV 6 is highly compatible with the previous versions so it might work very well. Just be careful about the dependencies as we changed the groupId of the artifact from org.hibernate to org.hibernate.validator. Also be aware that you need to update the validation-api from 1.1 to 2.0.
6 is already very stable and if you have any issues with it, we will fix them right away.
I cant find
using MvvmCross.Droid.Support.V7.Fragging.Fragments;
for MvxFragment and when I use
MvvmCross.Droid.FullFragging.Fragments;
or
MvvmCross.Droid.Support.V4
I get this error
IllegalArgumentException: already added:
Landroid/support/v4/accessibilityservice/AccessibilityServiceInfoCompat;
I have seen this post:
IllegalArgumentException: already added: Landroid/support/v4/accessibilityservice/AccessibilityServiceInfoCompat$AccessibilityServiceInfoIcsImpl;
but didn't helped me solve my issue.
Any suggestions?
MvvmCross.Droid.Support.V7.Fragging and MvvmCross.Droid.Support.V4 are deprecated. Use the new MvvmCross.Droid.Support.Fragment. Also see the upgrade documentation on this: https://www.mvvmcross.com/documentation/upgrading/upgrade-to-mvvmcross-50
In roboelectric when you write your test class you have declare the #RunWith annotation of which there is RobolectricGradleTestRunner and RobolectricTestRunner.class. What is the difference and which one should we use ? Why is there 2 in the first place. If I use RobolectricTestRunner then it does not work for me it says some weird error like :
"java.lang.IllegalStateException: You need to use a Theme.AppCompat theme (or descendant) with this activity."
However this seems to go away if I use RobolectricGradleTestRunner.
RobolectricTestRunner was first and is for maven based projects.
RobolectricGradleTestRunner was for gradle based projects because some paths have changed.
Since robolectric 3.1.1 this is not more necessary and is now deprecated.
For more details see also http://robolectric.org/getting-started/
I have installed EasyNewsletter, but whenever I add an issue, I get a traceback claiming:
NameError: name 'toLocalizedTime' is not defined
How should I solve this issue?
The issue is filed and fixed:
https://github.com/collective/Products.EasyNewsletter/commit/9d756f22c3117aa239c60283a8249edb56b9bf8f
Contact the authors to ask for a new release or apply the fix yourself, according to the link above.
The reason lies in the 'no more global definitions'-changement from Plone-3 to Plone-4, see further explanations on:
http://plone.org/documentation/manual/upgrade-guide/version/upgrading-plone-3-x-to-4.0/updating-add-on-products-for-plone-4.0/no-more-global-definitions-in-templates