I have this error, When i import .po file in drupal admin panel,
Configuration » Regional and language » Translate interface
Error: File upload error. Could not move uploaded file.
Error: File to import not found.
Anybody know how to rectify this error...
I found a way to do this using Drush and Localization Update.
Install Localization Update
Configure a local path for po-files (admin/config/regional/language/update)
Configure automatic updates from remote servers or just local sources
Now you can put your own po-files in a local path (for example sites/all/translations). If you have translations for your own module then you name it according to this naming convention:
modulename-version.language.po
So a Swedish po-file for 'my_module', version 7.x-1.1 would be named:
my_module-7.x-1.1.sv.po
Now you have everything setup and you can start updating your sites translation with Drush:
drush l10n-update-refresh // Looks for new po-files
drush l10n-update // Updates translations
Related
I am having an Android app that I developed in July 2019 using Eclipse (at least that is what the folder says).
Now I want to make some changes and tried to import and run the project with Eclipse.
But when trying to run the project, I get the following error messages:
These values are required!
userName - login information from codenameone.com
password - the password matching your login from codenameone.com
jarFile - the application jar file resulting from the build
ApplicationDisplayName - display name for the application in the UI
MainClassName - the name of the main class not including the package name
ApplicationPackageName - the package in which the main class resides, this will also be used to classify the application. It is recommended you give this some thought since package names are impossible to change later on some stores!
version - the version number for the application
There is some other strange behaviour, like the error:
The method getAllStyles() is undefined for the type Form
and no Simulator_Project.launch file ...
I have tried refreshing the libraries, but to no avail. Maybe there have changes been made to the build process ...
How can I run the project?
I am very new to Zeppelin/spark and couldn't get an accurate description of steps to configure new dependencies like that of NLP libraries.
Found similar issue here.
I was trying to use Johnsnowlabs NLP library in Zeppelin notebook (spark version2.2.1).
Setup included :
In Zeppelin's Interpreters configurations for Spark, include the following artifact:
com.johnsnowlabs.nlp:spark-nlp_2.11:2.5.4
Then, in conf/zeppelin-env.sh, setup SPARK_SUBMIT_OPTIONS.
export SPARK_SUBMIT_OPTIONS=” — packages JohnSnowLabs:spark-nlp:2.2.2". Then restarted Zeppelin.
But the below program gives the error :
%spark
import com.johnsnowlabs.nlp.base._
import com.johnsnowlabs.nlp.annotator._
<console>:26: error: object johnsnowlabs is not a member of package com
import com.johnsnowlabs.nlp.base._
^
<console>:27: error: object johnsnowlabs is not a member of package com
import com.johnsnowlabs.nlp.annotator._
Can someone please share how this can be done? I referred this link .
TIA
you don't need to edit the conf/zeppelin-env.sh (anyway you're using it incorrectly, as you're specifying completely different version), you can make all changes via Zeppelin UI. Go to the Spark interpreter configuration, and put com.johnsnowlabs.nlp:spark-nlp_2.11:2.5.4 into spark.jars.packages configuration property (or add it if it doesn't exist), and into the Dependencies at the end of configuration (for some reason, it isn't automatically pulled into driver classpath).
I'm trying to change locale in the plugin that is used as a theme.In my AppController I set the locale with:
I18n::locale('bs');
And in the plugin that is named 'Admin' I place the translation file in this location:
Admin
/src
/Locale
/bs
admin.po
Locale does seem to change, but it doesn't fetch the translations from the translation file. What could be the problem?
The problem was I wasn't using domain name while translating strings. You need to use __d() with the name of your plugin as the domain.
I am new to Go and AppEngine. I am trying to figure out how to create packages but I keep running into conflicts. My directory structure is below:
GOPATH
third-party-libs
app
app.yaml
controllers
default.go -- package controllers
models
models.go -- package models
templates
templates.go -- package templates
I am importing the templates package as follows import ("app/templates") inside default.go
When I do goapp serve I get this error:
Failed parsing input: app file templates.go conflicts with
same file imported from GOPATH
I have tried a bunch of things and nothing has worked so far. These are things I have tried:
Changed the templates directory to apptemplates and the corresponding file to apptemplates.go, changed package name to apptemplates. I imported it as app/apptemplates
I tried different combinations by changing the file name but not the package name, vice versa, etc. Either it does not find the file or has a conflict.
I am importing html/template in my templates.go file. So I commented out the entire file just keeping the package declaration but did not make the conflict go away
I thought may be another file is named templates.go but when I do this (at the GOPATH level) find . -name "*.go" | grep "templates.go" I only see the one file I have created.
I am confused as to how packages are created. I have changed the name to something generic so it does not look like a naming issue. Can someone please tell me how I can debug this error?
Thanks!
Rename the package to a non-conflicting name as in #1. Import the package using the path "apptemplates".
Packages inside of the application directory (the directory containing app.yaml) are imported with a path relative to the application directory. See Organizing Go Apps for the complete details.
Is there a way to get details about this error? I turned off custom errors:
It looks like I am missing a skin file. How do I get it back? I used the one from the default install of DNN 6.2.4.
You could look at your DotNetNuke log4net config settings and check where you are logging errors. The default location is {DotNetNuke_Root_Folder}/Portals/_default/Logs/.
The log level by default is set on error so you can change that to "Debug" if you want by changing the element in the following config file {DotNetNuke_Root_Folder}/DotNetNuke.log4net.config
You can copy the skin's folder in your DotNetNuke installation zip file to your installed DotNetNuke website. Path to skins (DotNetNuke_Community_07.00.05_Install.zip\Portals_default\Skins)
Hope this helps.
You can get all error detail from LogViewer module of DotNetNuke
Login as administrators then go to Admin-Event Viewer , here you can find the details about error.
I had this error also; on a local instance. After installing a DNN Template via the .visx file, IIS had set up a virtual directory for the desktopmodules folder. Removing the virtual directory cleared this right up in my case. Took a long time to troubleshoot, so hopefully this helps someone avoid the wild goose chase.