MvvmCross MvxFragment issue - android-fragments

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

Related

removed MessageSelector in Symfony/Component/Translation

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

middleware_stack.js:31 Uncaught Error: Handler with name 'route' already exists. Iron router Meteor

My code was working fine until last night and suddenly I am getting this error and routes are not working at all.
middleware_stack.js:31Uncaught Error: Handler with name 'route' already exists.
for simple routes like this:
Router.route('/admin/dashboard', {
template:"adminDashboard"
});
Router.route('/admin/create/table', {
template:"create_table"
});
I cannot figure out the error, I have checked all the routes. Have anyone else faced this error?
This is a known issue. The problem occurs with recent versions of Google Chrome and Microsoft Edge (edit: also Firefox now).
It has been fixed by a recent iron router update, it should be fixed by meteor update iron:middleware-stack.
Edit: If the middleware-stack package rolls back when you restart the server, check #bigsan's comment
Edit: this issue was fixed in iron:middleware-stack 1.1.0 .
I have the same problem. Weirdly, I have this problem on Chrome 51 but not on Chrome 46. I guess this has to do with updates in the javascript engine, and I'll post here if I figure out what exactly.
In the meantime, the workaround I used was to explicitly add names to the routes. It doesn't matter what they are, they just have to be declared, otherwise iron-router think the name of the route is "route." So your code would become:
Router.route('/admin/dashboard', {
name: "Boaty_McBoatface",
template:"adminDashboard"
});
Router.route('/admin/create/table', {
name: "Guacamole",
template:"create_table"
});
First, have a look here and see when this error is thrown. So, actually I have not faced that error but I've read about it. Further have a look at the official guide and post. I see that you are trying to create a subdirectory to your route /admin. Usually, I do this by using this.render() function. Concerning the layout I use this.layout() so I think that if you use these functions and remove template:"adminDashboard". It will work.

InvalidConfigurationException: Unrecognized options "fallbacks" under "framework.translator"

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?

Why does EasyNewsletter for plone throw NameError on 'toLocalizedTime

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

simplehtmldom 500 error

I saw that there are a lot of topics on simplehtmldom, but no one's problem seems to be mine- specifically, that it just 500s, even on the examples provided. I've found that I can include the file without an error, but if I then try to use file_get_html, it 500s. The only thing I found in the manual about installation is a possible problem with allow_fopen_url, which I do.
Something I'm missing?
Seems like too long since you asked this question, but since I came across this trying to solve this problem myself, I thought I'd post what worked for me.
I solved this problem by changing file_get_html to file_get_contents. Since I wanted to use the 'find' feature in simple_html_dom, I had to then convert the string to an object:
$string = file_get_contents(http://thedeadfallproject.com/)
$object = new simple_html_dom();
$object->load($string); // Load HTML from a string

Resources