WPMU DEV in your language
Translations
Translation of Shipper: Danish
| Prio | Original string | Translation | — |
|---|---|---|---|
| 4. If none of the above works, you can ask your hosting support to turn off the open_basedir restriction for you. | 4. Hvis intet af ovenstående virker, kan du bede din hostingsupport om at slå open_basedir-begrænsningen fra for dig. | Details | |
|
4. If none of the above works, you can ask your hosting support to turn off the open_basedir restriction for you. 4. Hvis intet af ovenstående virker, kan du bede din hostingsupport om at slå open_basedir-begrænsningen fra for dig.
Login to your account for contributing to translations.
|
|||
| 3. You can also edit the Apache configuration file to disable the PHP open_basedir restriction. Open the httpd.conf file. Add the following line of code at the end, and restart your web server. | 3. Du kan også redigere Apache-konfigurationsfilen for at deaktivere PHP open_basedir-begrænsningen. Åbn filen httpd.conf. Tilføj følgende kodelinje til sidst, og genstart din webserver. | Details | |
|
3. You can also edit the Apache configuration file to disable the PHP open_basedir restriction. Open the httpd.conf file. Add the following line of code at the end, and restart your web server. 3. Du kan også redigere Apache-konfigurationsfilen for at deaktivere PHP open_basedir-begrænsningen. Åbn filen httpd.conf. Tilføj følgende kodelinje til sidst, og genstart din webserver.
Login to your account for contributing to translations.
|
|||
| 2. Open your php.ini file, comment the open_basedir rule, and restart your server. To comment a line of code in the php.ini file, you need to suffixit with a semicolon. So, to comment the open_basedir rule, add a semicolon in the beginning as in: “; open_basedir true”. Commenting is preferred to deleting the rule, in case you want to reactivate it after the migration. | 2. Åbn din php.ini-fil, kommenter open_basedir-reglen, og genstart din server. For at kommentere en kodelinje i php.ini-filen skal du slutte den med et semikolon. Så for at kommentere open_basedir-reglen skal du tilføje et semikolon i begyndelsen som i: "; open_basedir true". At kommentere er at foretrække frem for at slette reglen, hvis du vil genaktivere den efter migreringen. | Details | |
|
2. Open your php.ini file, comment the open_basedir rule, and restart your server. To comment a line of code in the php.ini file, you need to suffixit with a semicolon. So, to comment the open_basedir rule, add a semicolon in the beginning as in: “; open_basedir true”. Commenting is preferred to deleting the rule, in case you want to reactivate it after the migration. 2. Åbn din php.ini-fil, kommenter open_basedir-reglen, og genstart din server. For at kommentere en kodelinje i php.ini-filen skal du slutte den med et semikolon. Så for at kommentere open_basedir-reglen skal du tilføje et semikolon i begyndelsen som i: "; open_basedir true". At kommentere er at foretrække frem for at slette reglen, hvis du vil genaktivere den efter migreringen.
Login to your account for contributing to translations.
|
|||
| 1. Go to your cPanel > Select PHP Version, and click on Switch to PHP Options link to see the default values of PHP options. Update the value of open_basedir to an empty value, and click on Apply and then Save. | 1. Gå til din cPanel > Vælg PHP-version, og klik på linket Skift til PHP-indstillinger for at se standardværdierne for PHP-indstillinger. Opdater værdien af open_basedir til en tom værdi, og klik på Apply og derefter Save. | Details | |
|
1. Go to your cPanel > Select PHP Version, and click on Switch to PHP Options link to see the default values of PHP options. Update the value of open_basedir to an empty value, and click on Apply and then Save. 1. Gå til din cPanel > Vælg PHP-version, og klik på linket Skift til PHP-indstillinger for at se standardværdierne for PHP-indstillinger. Opdater værdien af open_basedir til en tom værdi, og klik på Apply og derefter Save.
Login to your account for contributing to translations.
|
|||
| We recommend disabling the <b>open_basedir</b> restriction during migrations to ensure things go smoothly. | Vi anbefaler at deaktivere <b>open_basedir-begrænsningen</b> under migreringer for at sikre, at tingene går glat. | Details | |
|
We recommend disabling the <b>open_basedir</b> restriction during migrations to ensure things go smoothly. Vi anbefaler at deaktivere <b>open_basedir-begrænsningen</b> under migreringer for at sikre, at tingene går glat.
Login to your account for contributing to translations.
|
|||
| Open_basedir restriction is in effect on <b>%s</b>. | Open_basedir-begrænsningen er i kraft på <b>%s</b>. | Details | |
|
Open_basedir restriction is in effect on <b>%s</b>. Open_basedir-begrænsningen er i kraft på <b>%s</b>.
Login to your account for contributing to translations.
|
|||
| PHP has a security measure called <b>open_basedir</b> which limits which files can be accessed by a PHP script. Usually, it’s set to your root directory or a couple of specific directories. Shipper needs to be able to write in the working directory, storage directory, temp directory, and log directory to work properly. Having open_basedir active is likely to cause migration failures. | PHP har en sikkerhedsforanstaltning kaldet <b>open_basedir</b>, som begrænser, hvilke filer der kan tilgås af et PHP-script. Normalt er det indstillet til din rodmappe eller et par specifikke mapper. Shipper skal kunne skrive i arbejdsmappen, lagermappen, temp-mappen og log-mappen for at fungere korrekt. Hvis open_basedir er aktiv, vil det sandsynligvis forårsage migreringsfejl. | Details | |
|
PHP has a security measure called <b>open_basedir</b> which limits which files can be accessed by a PHP script. Usually, it’s set to your root directory or a couple of specific directories. Shipper needs to be able to write in the working directory, storage directory, temp directory, and log directory to work properly. Having open_basedir active is likely to cause migration failures. PHP har en sikkerhedsforanstaltning kaldet <b>open_basedir</b>, som begrænser, hvilke filer der kan tilgås af et PHP-script. Normalt er det indstillet til din rodmappe eller et par specifikke mapper. Shipper skal kunne skrive i arbejdsmappen, lagermappen, temp-mappen og log-mappen for at fungere korrekt. Hvis open_basedir er aktiv, vil det sandsynligvis forårsage migreringsfejl.
Login to your account for contributing to translations.
|
|||
| <b>%1$s</b> is on MySQL v%2$s whereas <b>%3$s</b> is on MySQL v%4$s. | <b>%1$s</b> er på MySQL v%2$s, mens <b>%3$s</b> er på MySQL v%4$s. | Details | |
|
<b>%1$s</b> is on MySQL v%2$s whereas <b>%3$s</b> is on MySQL v%4$s. <b>%1$s</b> er på MySQL v%2$s, mens <b>%3$s</b> er på MySQL v%4$s.
Login to your account for contributing to translations.
|
|||
| WordPress uses MySQL database to store your data, including posts, pages, users, and plugins data. Migrating from one server to another with a significant difference in the MySQL versions can cause issues in your destination site. | WordPress bruger MySQL-databasen til at gemme dine data, herunder indlæg, sider, brugere og plugins-data. Migrering fra en server til en anden med en betydelig forskel i MySQL-versionerne kan forårsage problemer på din destinationsside. | Details | |
|
WordPress uses MySQL database to store your data, including posts, pages, users, and plugins data. Migrating from one server to another with a significant difference in the MySQL versions can cause issues in your destination site. WordPress bruger MySQL-databasen til at gemme dine data, herunder indlæg, sider, brugere og plugins-data. Migrering fra en server til en anden med en betydelig forskel i MySQL-versionerne kan forårsage problemer på din destinationsside.
Login to your account for contributing to translations.
|
|||
| Unfortunately, Shipper cannot yet migrate between sites with different WordPress installation type. We're working on adding features which will allow you to extract a single site from a network and move it to a standalone installation, or migrate a single site into a network as a subsite. Meanwhile, you can use another plugin which supports this type of migration. | Desværre kan Shipper endnu ikke migrere mellem sider med forskellige WordPress-installationstyper. Vi arbejder på at tilføje funktioner, så du kan udtrække et enkelt site fra et netværk og flytte det til en selvstændig installation, eller migrere et enkelt site til et netværk som et subsite. I mellemtiden kan du bruge et andet plugin, der understøtter denne type migrering. | Details | |
|
Unfortunately, Shipper cannot yet migrate between sites with different WordPress installation type. We're working on adding features which will allow you to extract a single site from a network and move it to a standalone installation, or migrate a single site into a network as a subsite. Meanwhile, you can use another plugin which supports this type of migration. Desværre kan Shipper endnu ikke migrere mellem sider med forskellige WordPress-installationstyper. Vi arbejder på at tilføje funktioner, så du kan udtrække et enkelt site fra et netværk og flytte det til en selvstændig installation, eller migrere et enkelt site til et netværk som et subsite. I mellemtiden kan du bruge et andet plugin, der understøtter denne type migrering.
Login to your account for contributing to translations.
|
|||
| %1$s but %2$s installation. | %1$s men %2$s installation. | Details | |
|
%1$s but %2$s installation. %1$s men %2$s installation.
Login to your account for contributing to translations.
|
|||
| Shipper can only migrate between the same WordPress installation types, i.e. from one single site to another single site or from one multisite network to another multisite network. It is necessary for your source and destination sites to have the same WordPress installation. | Shipper kan kun migrere mellem de samme WordPress-installationstyper, dvs. fra et enkelt site til et andet enkelt site eller fra et multisite-netværk til et andet multisite-netværk. Det er nødvendigt, at dine kilde- og destinationssider har den samme WordPress-installation. | Details | |
|
Shipper can only migrate between the same WordPress installation types, i.e. from one single site to another single site or from one multisite network to another multisite network. It is necessary for your source and destination sites to have the same WordPress installation. Shipper kan kun migrere mellem de samme WordPress-installationstyper, dvs. fra et enkelt site til et andet enkelt site eller fra et multisite-netværk til et andet multisite-netværk. Det er nødvendigt, at dine kilde- og destinationssider har den samme WordPress-installation.
Login to your account for contributing to translations.
|
|||
| <b>%s</b> is a multisite | <b>%s</b> er en multisite | Details | |
|
<b>%s</b> is a multisite <b>%s</b> er en multisite
Login to your account for contributing to translations.
|
|||
| <b>%s</b> is a single site | <b>%s</b> er et enkelt sted | Details | |
|
<b>%s</b> is a single site <b>%s</b> er et enkelt sted
Login to your account for contributing to translations.
|
|||
| Log directory is not writable on %1$s. Please fix this and check again. | Log-biblioteket kan ikke skrives på %1$s. Ret venligst dette og tjek igen. | Details | |
|
Log directory is not writable on %1$s. Please fix this and check again. Log-biblioteket kan ikke skrives på %1$s. Ret venligst dette og tjek igen.
Login to your account for contributing to translations.
|
|||
Export as •