msgid ""
msgstr ""
"Project-Id-Version: WP Hide & Security Enhancer\n"
"POT-Creation-Date: 2025-11-11 16:26+0200\n"
"PO-Revision-Date: 2025-11-11 18:59+0200\n"
"Last-Translator: NspCode <contact@nsp-code.com>\n"
"Language-Team: contact@wp-hide.com\n"
"Language: no\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"X-Generator: Poedit 3.5\n"
"X-Poedit-KeywordsList: _;gettext;gettext_noop;__;_e;esc_html_e;esc_html__;esc_attr_e;esc_attr__\n"
"X-Poedit-Basepath: ..\n"
"X-Poedit-SourceCharset: UTF-8\n"
"X-Poedit-SearchPath-0: .\n"

#: compatibility/wp-simple-firewall.php:86
msgid "<b>Conflict notice</b>: <b>Shield Security</b> - Login Protection -> Hide Login -> use similar functionality as to WP Hide plugin - Admin Login Url change.  "
msgstr "<b>Konfliktvarsel</b>: <b>Shield Security</b> - Innloggingsbeskyttelse -> Skjul innlogging -> bruker lignende funksjonalitet som WP Hide-plugin - Endring av admin-innloggingsadresse.  "

#: include/admin-interface.class.php:107
msgid "Are you sure to reset the current page settings? All options will be changed to default. An Save is still required for the page."
msgstr "Er du sikker på at du vil tilbakestille innstillingene for denne siden? Alle alternativer vil bli endret til standard. En lagring er fortsatt nødvendig for siden."

#: include/admin-interface.class.php:108
msgid "Are you sure to reset all settings? All options will be removed. Manual removal of rewrite lines is required if no access from PHP."
msgstr "Er du sikker på at du vil tilbakestille alle innstillinger? Alle alternativer vil bli fjernet. Manuell fjerning av omskrivingslinjer er nødvendig hvis det ikke er tilgang fra PHP."

#: include/admin-interface.class.php:109
msgid "This creates a sample setup for Headers. That will overwrite any Headers settings previously created through the plugin options. Are you sure?"
msgstr "Dette oppretter en eksempeloppsett for Headers. Dette vil overskrive alle Headers-innstillinger som tidligere er opprettet gjennom plugin-alternativene. Er du sikker?"

#: include/admin-interface.class.php:363 include/admin-interface.class.php:423 include/admin-interface.class.php:438 modules/components/security-check_headers.php:264
msgid "Value"
msgstr "Verdi"

#: include/admin-interface.class.php:363 include/admin-interface.class.php:395 include/admin-interface.class.php:406 include/admin-interface.class.php:423 include/admin-interface.class.php:438
msgid "set for"
msgstr "satt for"

#: include/admin-interface.class.php:363
msgid "already in use for another option."
msgstr "allerede i bruk for et annet alternativ."

#: include/admin-interface.class.php:395 include/admin-interface.class.php:406
msgid "The value"
msgstr "Verdien"

#: include/admin-interface.class.php:395 include/admin-interface.class.php:406
#, php-format
msgid "must be a minimum of %s characters or longer."
msgstr "må være minst %s tegn eller lengre."

#: include/admin-interface.class.php:423
msgid "use the same base slug "
msgstr "bruker samme base-slug "

#: include/admin-interface.class.php:423
msgid "used for another option."
msgstr "brukt for et annet alternativ."

#: include/admin-interface.class.php:438
msgid " include a system reserved word."
msgstr " inkluderer et system-reservert ord."

#: include/admin-interface.class.php:757
msgid "The following settings are used as default, for other sites in the network"
msgstr "Følgende innstillinger brukes som standard for andre nettsteder i nettverket"

#: include/admin-interface.class.php:850 include/admin-interfaces/_licence.php:24
msgid "Save"
msgstr "Lagre"

#: include/admin-interface.class.php:877
msgid "Reset Page Settings"
msgstr "Tilbakestill sideinnstillinger"

#: include/admin-interface.class.php:904
msgid "Reset All Settings"
msgstr "Tilbakestill alle innstillinger"

#: include/admin-interface.class.php:1231
msgid "Unable to launch WP Hide through mu-plugins/wp-hide-loader.php<br /> Please make sure this location is writable so the plugin create the required file, or manually copy the wp-hide-security-enhancer-pro/mu-loader/wp-hide-loader.php to mu-plugins/wp-hide-loader.php."
msgstr "Kan ikke starte WP Hide via mu-plugins/wp-hide-loader.php<br /> Vennligst sørg for at denne plasseringen er skrivbar slik at pluginen kan opprette den nødvendige filen, eller kopier manuelt wp-hide-security-enhancer-pro/mu-loader/wp-hide-loader.php til mu-plugins/wp-hide-loader.php."

#: include/admin-interface.class.php:1236 include/admin-interface.class.php:1537
msgid "Unable to add required data to wp-config.php<br /> Please make sure this location is writable so the plugin append required data, or manually deploy the data specified withint Setup interface."
msgstr "Kan ikke legge til nødvendige data i wp-config.php<br /> Vennligst sørg for at denne plasseringen er skrivbar slik at pluginen kan tilføye nødvendige data, eller manuelt deployere dataene spesifisert i Oppsett-grensesnittet."

#: include/admin-interface.class.php:1266
msgid "Permalink is required to be turned ON for WP Hide & Security Enhancer PRO to work"
msgstr "Permalenke må være slått PÅ for at WP Hide & Security Enhancer PRO skal fungere"

#: include/admin-interface.class.php:1272 include/admin-interface.class.php:1532
msgid "Unable to identify server type!"
msgstr "Kan ikke identifisere servertype!"

#: include/admin-interface.class.php:1272 include/admin-interface.class.php:1532
msgid "No rewrite is being applied."
msgstr "Ingen omskriving blir brukt."

#: include/admin-interface.class.php:1278
msgid "All Settings where restored to default"
msgstr "Alle innstillinger ble gjenopprettet til standard"

#: include/admin-interface.class.php:1306 include/admin-interface.class.php:1561
msgid "Headers Sample Setup deployed successfully."
msgstr "Headers-eksempeloppsett deployert vellykket."

#: include/admin-interface.class.php:1317
msgid "The PHP DOMDocument is required for the CSS / JavaScript PostProcessing. Contact your server support to install the DOMDocument module."
msgstr "PHP DOMDocument er nødvendig for CSS / JavaScript PostProcessing. Kontakt serverstøtten din for å installere DOMDocument-modulen."

#: include/admin-interface.class.php:1340 include/admin-interface.class.php:1580
msgid "Settings saved"
msgstr "Innstillinger lagret"

#: include/admin-interface.class.php:1460
msgid "Unable to write custom rules to your .htaccess. Is this file writable?"
msgstr "Kan ikke skrive egendefinerte regler til .htaccess. Er denne filen skrivbar?"

#: include/admin-interface.class.php:1462
msgid "Unable to write custom rules to your web.config. Is this file writable? <br />No mod is being applied."
msgstr "Kan ikke skrive egendefinerte regler til web.config. Er denne filen skrivbar? <br />Ingen mod blir brukt."

#: include/admin-interface.class.php:1468
msgid "Self set-up is turned on, there will be no automated attempt to write data."
msgstr "Selvoppsett er slått på, det vil ikke være noe automatisk forsøk på å skrive data."

#: include/admin-interface.class.php:1476
msgid "Check Network Setup menu item for manual rewrite data deploy."
msgstr "Sjekk Nettverksoppsett-menyvalget for manuell deploy av omskrivingsdata."

#: include/admin-interface.class.php:1478
msgid "Network Admin has been notified. He will manually deploy the rewrite data."
msgstr "Nettverksadministrator er varslet. Han vil manuelt deployere omskrivingsdataene."

#: include/admin-interface.class.php:1482
msgid "Check Setup menu for instructions on how to deploy the rewrite rules on your server."
msgstr "Sjekk Oppsett-menyen for instruksjoner om hvordan du deployerer omskrivingsreglene på serveren din."

#: include/admin-interface.class.php:1503
msgid "<b>Your server operates on Nginx!</b><br /> Automatic deployment of the rewrite rules is not possible, manual action is required. Refer to the Setup menu for guidelines on adding the rewrite rules to your server."
msgstr "<b>Serveren din kjører på Nginx!</b><br /> Automatisk deployering av omskrivingsreglene er ikke mulig, manuell handling er nødvendig. Se til Oppsett-menyen for retningslinjer om å legge til omskrivingsreglene på serveren din."

#: include/admin-interface.class.php:1619 include/admin-interface.class.php:1624
msgid "WP Hide & Security Enhancer PRO plugin is inactive, please enter your"
msgstr "WP Hide & Security Enhancer PRO-plugin er inaktiv, vennligst skriv inn din"

#: include/admin-interface.class.php:1619 include/admin-interface.class.php:1624
msgid "Licence Key"
msgstr "Lisensnøkkel"

#: include/admin-interface.class.php:1619 include/admin-interface.class.php:1624
msgid "Specific functionality and updates are not available."
msgstr "Spesifikk funksjonalitet og oppdateringer er ikke tilgjengelige."

#: include/admin-interfaces/_licence.php:16 include/admin-interfaces/_licence_deactivate.php:20
msgid "License Key"
msgstr "Lisensnøkkel"

#: include/admin-interfaces/_licence.php:21
msgid "Enter the Licence Key you received when purchased this product. If you lost the key, you can always retrieve it from"
msgstr "Skriv inn lisensnøkkelen du mottok da du kjøpte dette produktet. Hvis du mistet nøkkelen, kan du alltid hente den fra"

#: include/admin-interfaces/_licence.php:21 include/admin-interfaces/_licence_deactivate.php:25
msgid "My Account"
msgstr "Min konto"

#: include/admin-interfaces/_licence_deactivate.php:23
msgid "Deactivate"
msgstr "Deaktiver"

#: include/admin-interfaces/_licence_deactivate.php:25
msgid "You can generate more keys at "
msgstr "Du kan generere flere nøkler på "

#: include/admin-interfaces/_licence_deactivate.php:32
msgid "License Status"
msgstr "Lisensstatus"

#: include/admin-interfaces/_licence_deactivate.php:37
msgid "License Expiration"
msgstr "Lisensutløp"

#: include/admin-interfaces/_licence_deactivate.php:41
msgid "Licence is expired, plugin <b>Updates</b> and <b>Support</b> are not available"
msgstr "Lisensen er utløpt, plugin-<b>oppdateringer</b> og <b>støtte</b> er ikke tilgjengelige"

#: include/admin-interfaces/_licence_deactivate.php:57
msgid "New plugin version available"
msgstr "Ny plugin-versjon tilgjengelig"

#: include/admin-interfaces/_settings.class.php:27
msgid "License"
msgstr "Lisens"

#: include/admin-interfaces/_settings.class.php:31
msgid "General"
msgstr "Generelt"

#: include/admin-interfaces/_settings.class.php:42 include/admin-interfaces/_settings.class.php:677
msgid "Import / Export"
msgstr "Importer / Eksporter"

#: include/admin-interfaces/_settings.class.php:46 include/admin-interfaces/_settings.class.php:734 include/functions.class.php:2466 include/functions.class.php:2473 include/functions.class.php:2554 modules/components/security-check_headers.php:139
msgid "Recovery"
msgstr "Gjenoppretting"

#: include/admin-interfaces/_settings.class.php:50
msgid "Data Collection"
msgstr "Datainnsamling"

#: include/admin-interfaces/_settings.class.php:155 modules/components/admin-login_php.php:464
msgid "Hello"
msgstr "Hallo"

#: include/admin-interfaces/_settings.class.php:156
msgid "This is an automated notification to let you know that your recovery URL has been successfully changed."
msgstr "Dette er en automatisk varsling for å informere deg om at gjenopprettings-URL-en din er blitt endret."

#: include/admin-interfaces/_settings.class.php:157
msgid "You can access your recovery page using the following link: "
msgstr "Du kan få tilgang til gjenopprettingssiden din ved å bruke følgende lenke: "

#: include/admin-interfaces/_settings.class.php:159
msgid "Have a great day!."
msgstr "Ha en fin dag!."

#: include/admin-interfaces/_settings.class.php:169
msgid "Recovery Code Successfully Reset."
msgstr "Gjenopprettingskode tilbakestilt."

#: include/admin-interfaces/_settings.class.php:228 include/admin-interfaces/_settings.class.php:318
msgid "There was a problem connecting to "
msgstr "Det oppstod et problem med å koble til "

#: include/admin-interfaces/_settings.class.php:271
msgid "There was a problem deactivating the licence: "
msgstr "Det oppstod et problem med å deaktivere lisensen: "

#: include/admin-interfaces/_settings.class.php:281 include/admin-interfaces/_settings.class.php:373
msgid "There was a problem with the data block received from "
msgstr "Det oppstod et problem med datablokken mottatt fra "

#: include/admin-interfaces/_settings.class.php:298
msgid "Licence Key can't be empty"
msgstr "Lisensnøkkel kan ikke være tom"

#: include/admin-interfaces/_settings.class.php:362
msgid "There was a problem activating the licence: "
msgstr "Det oppstod et problem med å aktivere lisensen: "

#: include/admin-interfaces/_settings.class.php:409 include/admin-interfaces/_settings.class.php:422
msgid "Invalid import data."
msgstr "Ugyldige importdata."

#: include/admin-interfaces/_settings.class.php:459
msgid "Import data sucesfully processed."
msgstr "Importdata behandlet."

#: include/admin-interfaces/_settings.class.php:476
msgid "Network Settings"
msgstr "Nettverksinnstillinger"

#: include/admin-interfaces/_settings.class.php:478
msgid "Settings"
msgstr "Innstillinger"

#: include/admin-interfaces/_settings.class.php:549
msgid "General Settings"
msgstr "Generelle innstillinger"

#: include/admin-interfaces/_settings.class.php:560 include/admin-interfaces/_settings.class.php:576 include/admin-interfaces/_settings.class.php:590 include/admin-interfaces/_settings.class.php:605 include/admin-interfaces/_settings.class.php:619 modules/components/admin-admin_ajax_php.php:90 modules/components/admin-admin_url.php:78 modules/components/admin-login_php.php:133 modules/components/admin-login_php.php:152 modules/components/cdn-setup.php:100 modules/components/cdn-setup.php:119 modules/components/firewall-query-string.php:79 modules/components/firewall-request-uri.php:77 modules/components/firewall-user-agent.php:69 modules/components/general-admin-bar.php:101 modules/components/general-block-detectors.php:58 modules/components/general-core.php:67 modules/components/general-core.php:89 modules/components/general-css-combine.php:144 modules/components/general-css-combine.php:165 modules/components/general-css-combine.php:184 modules/components/general-emulate.php:58 modules/components/general-feed.php:62 modules/components/general-feed.php:80 modules/components/general-headers.php:100 modules/components/general-headers.php:119 modules/components/general-headers.php:137 modules/components/general-headers.php:172 modules/components/general-html.php:120 modules/components/general-html.php:144 modules/components/general-html.php:167 modules/components/general-html.php:188 modules/components/general-html.php:207 modules/components/general-html.php:225 modules/components/general-html.php:244 modules/components/general-js-combine.php:155 modules/components/general-js-combine.php:178 modules/components/general-js-combine.php:200 modules/components/general-meta.php:169
#: modules/components/general-meta.php:189 modules/components/general-meta.php:207 modules/components/general-meta.php:225 modules/components/general-meta.php:245 modules/components/general-meta.php:263 modules/components/general-meta.php:283 modules/components/general-meta.php:303 modules/components/general-meta.php:324 modules/components/general-meta.php:344 modules/components/general-meta.php:364 modules/components/general-oembed.php:40 modules/components/general-scripts.php:53 modules/components/general-scripts.php:69 modules/components/general-styles.php:50 modules/components/general-styles.php:68 modules/components/general-tobots-txt.php:18 modules/components/general-user-interactions.php:200 modules/components/general-user-interactions.php:219 modules/components/general-user-interactions.php:237 modules/components/general-user-interactions.php:255 modules/components/general-user-interactions.php:273 modules/components/general-user-interactions.php:291 modules/components/general-user-interactions.php:310 modules/components/general-user-interactions.php:329 modules/components/general-user-interactions.php:347 modules/components/general-user-interactions.php:365 modules/components/general-wp_die.php:53 modules/components/general-wpemoji.php:50 modules/components/general-wpemoji.php:66 modules/components/login_2fa_app.php:70 modules/components/login_2fa_defaults.php:116 modules/components/login_2fa_defaults.php:153 modules/components/login_2fa_defaults.php:201 modules/components/login_2fa_email.php:62 modules/components/login_2fa_recovery_codes.php:62 modules/components/rewrite-author.php:89 modules/components/rewrite-author.php:105 modules/components/rewrite-comments.php:69
#: modules/components/rewrite-json-rest.php:157 modules/components/rewrite-json-rest.php:194 modules/components/rewrite-json-rest.php:215 modules/components/rewrite-json-rest.php:236 modules/components/rewrite-json-rest.php:254 modules/components/rewrite-json-rest.php:272 modules/components/rewrite-json-rest.php:290 modules/components/rewrite-mu-plugins.php:42 modules/components/rewrite-plugin_path.php:143 modules/components/rewrite-registration.php:88 modules/components/rewrite-registration.php:120 modules/components/rewrite-root-files.php:127 modules/components/rewrite-root-files.php:145 modules/components/rewrite-root-files.php:164 modules/components/rewrite-root-files.php:195 modules/components/rewrite-root-files.php:213 modules/components/rewrite-root-files.php:231 modules/components/rewrite-root-files.php:249 modules/components/rewrite-search.php:60 modules/components/rewrite-theme_path.php:136 modules/components/rewrite-upload_path.php:74 modules/components/rewrite-upload_path.php:90 modules/components/rewrite-wp_content_path.php:80 modules/components/rewrite-wp_includes_path.php:66 modules/components/rewrite-xml-rpc-path.php:94 modules/components/rewrite-xml-rpc-path.php:112 modules/components/rewrite-xml-rpc-path.php:136 modules/components/rewrite-xml-rpc-path.php:152
msgid "No"
msgstr "Nei"

#: include/admin-interfaces/_settings.class.php:561 include/admin-interfaces/_settings.class.php:577 include/admin-interfaces/_settings.class.php:591 include/admin-interfaces/_settings.class.php:606 include/admin-interfaces/_settings.class.php:620 modules/components/admin-admin_ajax_php.php:91 modules/components/admin-admin_url.php:79 modules/components/admin-login_php.php:134 modules/components/admin-login_php.php:153 modules/components/cdn-setup.php:101 modules/components/cdn-setup.php:120 modules/components/firewall-query-string.php:80 modules/components/firewall-request-uri.php:78 modules/components/firewall-user-agent.php:70 modules/components/general-admin-bar.php:102 modules/components/general-block-detectors.php:59 modules/components/general-core.php:68 modules/components/general-core.php:90 modules/components/general-css-combine.php:166 modules/components/general-css-combine.php:185 modules/components/general-feed.php:63 modules/components/general-feed.php:81 modules/components/general-headers.php:101 modules/components/general-headers.php:120 modules/components/general-headers.php:138 modules/components/general-headers.php:173 modules/components/general-html.php:121 modules/components/general-html.php:168 modules/components/general-html.php:189 modules/components/general-html.php:208 modules/components/general-html.php:226 modules/components/general-html.php:245 modules/components/general-js-combine.php:179 modules/components/general-js-combine.php:201 modules/components/general-meta.php:170 modules/components/general-meta.php:190 modules/components/general-meta.php:208 modules/components/general-meta.php:226 modules/components/general-meta.php:246 modules/components/general-meta.php:264
#: modules/components/general-meta.php:284 modules/components/general-meta.php:304 modules/components/general-meta.php:325 modules/components/general-meta.php:345 modules/components/general-meta.php:365 modules/components/general-oembed.php:41 modules/components/general-scripts.php:54 modules/components/general-scripts.php:70 modules/components/general-styles.php:51 modules/components/general-styles.php:69 modules/components/general-tobots-txt.php:19 modules/components/general-user-interactions.php:201 modules/components/general-user-interactions.php:220 modules/components/general-user-interactions.php:238 modules/components/general-user-interactions.php:256 modules/components/general-user-interactions.php:274 modules/components/general-user-interactions.php:292 modules/components/general-user-interactions.php:311 modules/components/general-user-interactions.php:330 modules/components/general-user-interactions.php:348 modules/components/general-user-interactions.php:366 modules/components/general-wp_die.php:54 modules/components/general-wpemoji.php:51 modules/components/general-wpemoji.php:67 modules/components/login_2fa_app.php:71 modules/components/login_2fa_defaults.php:117 modules/components/login_2fa_defaults.php:154 modules/components/login_2fa_defaults.php:202 modules/components/login_2fa_email.php:63 modules/components/login_2fa_recovery_codes.php:63 modules/components/rewrite-author.php:90 modules/components/rewrite-author.php:106 modules/components/rewrite-comments.php:70 modules/components/rewrite-json-rest.php:158 modules/components/rewrite-json-rest.php:216 modules/components/rewrite-json-rest.php:237 modules/components/rewrite-json-rest.php:255 modules/components/rewrite-json-rest.php:273
#: modules/components/rewrite-json-rest.php:291 modules/components/rewrite-mu-plugins.php:43 modules/components/rewrite-plugin_path.php:144 modules/components/rewrite-registration.php:89 modules/components/rewrite-registration.php:121 modules/components/rewrite-root-files.php:128 modules/components/rewrite-root-files.php:146 modules/components/rewrite-root-files.php:165 modules/components/rewrite-root-files.php:196 modules/components/rewrite-root-files.php:214 modules/components/rewrite-root-files.php:232 modules/components/rewrite-root-files.php:250 modules/components/rewrite-search.php:61 modules/components/rewrite-theme_path.php:137 modules/components/rewrite-upload_path.php:75 modules/components/rewrite-upload_path.php:91 modules/components/rewrite-wp_content_path.php:81 modules/components/rewrite-wp_includes_path.php:67 modules/components/rewrite-xml-rpc-path.php:95 modules/components/rewrite-xml-rpc-path.php:113 modules/components/rewrite-xml-rpc-path.php:137 modules/components/rewrite-xml-rpc-path.php:153 modules/components/security-header-content-security-policy-report-only.php:377 modules/components/security-header-content-security-policy-report-only.php:385 modules/components/security-header-content-security-policy.php:378 modules/components/security-header-content-security-policy.php:386
msgid "Yes"
msgstr "Ja"

#: include/admin-interfaces/_settings.class.php:565
msgid "Generate simple Rewrite Rules for Nginx."
msgstr "Generer enkle omskrivingsregler for Nginx."

#: include/admin-interfaces/_settings.class.php:566
msgid "Not all Nginx servers are configured to handle the full complexity of rewrite rules recommended by developers, as outlined in the guide at "
msgstr "Ikke alle Nginx-servere er konfigurert til å håndtere den fulle kompleksiteten av omskrivingsregler anbefalt av utviklere, som beskrevet i veiledningen på "

#: include/admin-interfaces/_settings.class.php:566
msgid "NGINX blog"
msgstr "NGINX-blogg"

#: include/admin-interfaces/_settings.class.php:566
msgid "In scenarios where servers have limitations or custom configurations, this option enables the generation of a simplified version of rewrite rules."
msgstr "I scenarier hvor servere har begrensninger eller egendefinerte konfigurasjoner, muliggjør dette alternativet generering av en forenklet versjon av omskrivingsregler."

#: include/admin-interfaces/_settings.class.php:567
msgid "These simplified rules are less resource-intensive and easier to process, ensuring compatibility across a broader range of server environments. It's important to note that few servers usually support full rewrite format. This option is ideal for maintaining performance on lightweight or restricted servers."
msgstr "Disse forenklede reglene er mindre ressurskrevende og enklere å prosessere, noe som sikrer kompatibilitet på et bredere spekter av servermiljøer. Det er viktig å merke seg at få servere vanligvis støtter fullt omskrivingsformat. Dette alternativet er ideelt for å opprettholde ytelse på lette eller begrensede servere."

#: include/admin-interfaces/_settings.class.php:581
msgid "Save the Nginx Rewrites to local configuration files."
msgstr "Lagre Nginx-omskrivingene til lokale konfigurasjonsfiler."

#: include/admin-interfaces/_settings.class.php:582
msgid "This option allows you to automatically save the dynamically generated Nginx rewrite rules into two dedicated files: <code>wphide-nginx.conf</code> and <code>wphide-firewall-nginx.conf</code>. These files will be stored directly inside the site's root directory, specifically designed to handle URL rewriting and firewall rule management."
msgstr "Dette alternativet lar deg automatisk lagre de dynamisk genererte Nginx-omskrivingsreglene i to dedikerte filer: <code>wphide-nginx.conf</code> og <code>wphide-firewall-nginx.conf</code>. Disse filene vil bli lagret direkte i nettstedets rotkatalog, spesielt designet for å håndtere URL-omskriving og brannmurregelbehandling."

#: include/admin-interfaces/_settings.class.php:583
msgid "By enabling this, the Nginx configuration process becomes streamlined and more organized, as the rules are neatly encapsulated in separate files. This setup enhances security by ensuring firewall rules are properly managed and also allows for easier troubleshooting and maintenance of Nginx server configurations."
msgstr "Ved å aktivere dette, blir Nginx-konfigurasjonsprosessen strømlinjeformet og mer organisert, ettersom reglene er pent innkapslet i separate filer. Denne oppsettet forbedrer sikkerheten ved å sikre at brannmurregler blir riktig administrert og gir også enklere feilsøking og vedlikehold av Nginx-serverkonfigurasjoner."

#: include/admin-interfaces/_settings.class.php:595
msgid "Save the Nginx Rewrite Headers to a wphide-nginx-headers.conf file inside the site root ( Nginx )."
msgstr "Lagre Nginx-omskrivingshoder til en wphide-nginx-headers.conf-fil innenfor nettstedets rot (Nginx)."

#: include/admin-interfaces/_settings.class.php:596
msgid "When enabled, dynamically generated Nginx rewrite headers will be automatically inserted into a file named wphide-nginx-headers.conf located in the root directory of the site. If this option is disabled, the rewrite rules will instead be incorporated into the default wphide-nginx.conf file."
msgstr "Når aktivert, vil dynamisk genererte Nginx-omskrivingshoder automatisk bli satt inn i en fil kalt wphide-nginx-headers.conf som ligger i rotkatalogen til nettstedet. Hvis dette alternativet er deaktivert, vil omskrivingsreglene i stedet bli inkorporert i standard wphide-nginx.conf-filen."

#: include/admin-interfaces/_settings.class.php:610
msgid "I'll set-up the rewrite data myself ( Apache )."
msgstr "Jeg setter opp omskrivingsdataene selv (Apache)."

#: include/admin-interfaces/_settings.class.php:611
msgid "This option allows you full control over the rewrite rules by configuring them manually on your Apache server. Selecting this option prevents the application from making any automatic changes to your server's rewrite rules. This is ideal if you have a custom server configuration or specific rewrite rules you want to manage yourself."
msgstr "Dette alternativet gir deg full kontroll over omskrivingsreglene ved å konfigurere dem manuelt på Apache-serveren din. Ved å velge dette alternativet forhindrer du applikasjonen i å gjøre automatiske endringer i serverens omskrivingsregler. Dette er ideelt hvis du har en tilpasset serverkonfigurasjon eller spesifikke omskrivingsregler du ønsker å administrere selv."

#: include/admin-interfaces/_settings.class.php:612
msgid "Typically, the plugin will attempt to handle rewrite rules automatically when using mod_rewrite for Apache or IIS rewrite for Windows servers, but this option is for advanced users who prefer manual intervention. Make sure you have experience managing server configurations before proceeding."
msgstr "Vanligvis vil pluginen forsøke å håndtere omskrivingsregler automatisk når du bruker mod_rewrite for Apache eller IIS rewrite for Windows-servere, men dette alternativet er for avanserte brukere som foretrekker manuell intervensjon. Forsikre deg om at du har erfaring med å administrere serverkonfigurasjoner før du fortsetter."

#: include/admin-interfaces/_settings.class.php:624
msgid "Convert Relative URLs to Absolute URLs."
msgstr "Konverter relative URLer til absolutte URLer."

#: include/admin-interfaces/_settings.class.php:625
msgid "Enabling this option converts all relative URLs within your site to absolute URLs. Relative URLs, which are often used to reference files or pages relative to the current domain or path, may sometimes lead to inconsistencies in URL changes or conflicts with plugins and redirects. By converting them to absolute URLs, you ensure that all references are fully qualified and consistent, which can help avoid potential issues with link structure and content delivery."
msgstr "Ved å aktivere dette alternativet konverteres alle relative URLer på nettstedet ditt til absolutte URLer. Relative URLer, som ofte brukes til å referere til filer eller sider i forhold til gjeldende domene eller sti, kan noen ganger føre til uoverensstemmelser i URL-endringer eller konflikter med plugins og omdirigeringer. Ved å konvertere dem til absolutte URLer sikrer du at alle referanser er fullstendig kvalifiserte og konsistente, noe som kan bidra til å unngå potensielle problemer med lenkestruktur og innlevering av innhold."

#: include/admin-interfaces/_settings.class.php:626
msgid "However, if your site is functioning properly with relative URLs, it's recommended to leave this option off to avoid unnecessary changes. This option should be used if you're encountering URL-related issues, otherwise, it's best to keep it disabled."
msgstr "Imidlertid, hvis nettstedet ditt fungerer skikkelig med relative URLer, anbefales det å la dette alternativet være av for å unngå unødvendige endringer. Dette alternativet bør brukes hvis du opplever URL-relaterte problemer, ellers er det best å holde det deaktivert."

#: include/admin-interfaces/_settings.class.php:634 include/admin-interfaces/_settings.class.php:662
msgid "Save Settings"
msgstr "Lagre innstillinger"

#: include/admin-interfaces/_settings.class.php:649 modules/components/security-check_headers.php:142
msgid "Sample Setup"
msgstr "Eksempeloppsett"

#: include/admin-interfaces/_settings.class.php:684
msgid "Export Settings"
msgstr "Eksporter innstillinger"

#: include/admin-interfaces/_settings.class.php:687
msgid "Export current settings"
msgstr "Eksporter gjeldende innstillinger"

#: include/admin-interfaces/_settings.class.php:688
msgid "This option allows you to export your current configuration settings. By selecting this, you can generate and copy to save on a local file, all the customized settings and preferences. This is useful for backing up your settings or transferring them to another installation."
msgstr "Dette alternativet lar deg eksportere dine gjeldende konfigurasjonsinnstillinger. Ved å velge dette, kan du generere og kopiere for å lagre på en lokal fil, alle de tilpassede innstillingene og preferansene. Dette er nyttig for sikkerhetskopiering av innstillingene dine eller overføring til en annen installasjon."

#: include/admin-interfaces/_settings.class.php:703 include/admin-interfaces/_settings.class.php:714
msgid "Import Settings"
msgstr "Importer innstillinger"

#: include/admin-interfaces/_settings.class.php:706
msgid "Import previously saved settings"
msgstr "Importer tidligere lagrede innstillinger"

#: include/admin-interfaces/_settings.class.php:707
msgid "Use this option to import the data of a previously saved setup. Simply paste the data content, and it will restore the configuration as per the exported settings. This feature is especially handy when migrating to a new setup or recovering from a previous configuration backup."
msgstr "Bruk dette alternativet for å importere dataene fra et tidligere lagret oppsett. Lim inn dataene, og den vil gjenopprette konfigurasjonen i henhold til de eksporterte innstillingene. Denne funksjonen er spesielt nyttig når du migrerer til et nytt oppsett eller gjenoppretter fra en tidligere konfigurasjonssikkerhetskopi."

#: include/admin-interfaces/_settings.class.php:736
msgid "To ensure you can restore your plugin settings if something goes wrong, make sure to copy the following link and store it in a secure location. This link provides a way to reset all plugin options to their default state. It's a crucial safety measure to prevent loss of configuration and to facilitate troubleshooting."
msgstr "For å sikre at du kan gjenopprette plugin-innstillingene dine hvis noe går galt, sørg for å kopiere følgende lenke og lagre den på et sikkert sted. Denne lenken gir en måte å tilbakestille alle plugin-alternativer til standardtilstanden. Det er en avgjørende sikkerhetstiltak for å forhindre tap av konfigurasjon og for å lette feilsøking."

#: include/admin-interfaces/_settings.class.php:737
msgid "Keeping this link safe ensures that you can easily revert to the original settings without manual intervention. This recovery link is your backup plan, providing peace of mind and quick restoration in case of any issues with the plugin's functionality."
msgstr "Å holde denne lenken trygg sikrer at du enkelt kan gå tilbake til de opprinnelige innstillingene uten manuell intervensjon. Denne gjenopprettingslenken er sikkerhetskopien din, gir ro i sinnet og rask gjenoppretting i tilfelle problemer med pluginens funksjonalitet."

#: include/admin-interfaces/_settings.class.php:744
msgid "Reset Recovery Code"
msgstr "Tilbakestill gjenopprettingskode"

#: include/admin-interfaces/_settings.class.php:749
msgid "Are you sure you want to reset the recovery code? A new code will be generated, and the previous link will no longer be valid."
msgstr "Er du sikker på at du vil tilbakestille gjenopprettingskoden? En ny kode vil bli generert, og den forrige lenken vil ikke lenger være gyldig."

#: include/admin-interfaces/_settings.class.php:771
msgid "Data Collection Status"
msgstr "Status for datainnsamling"

#: include/admin-interfaces/_settings.class.php:774
msgid "The Data Collection represents a compilation of post-processed assets that are utilized internally within your system. These assets are generated when you enable CSS and/or JavaScript Post-Processing options."
msgstr "Datainnsamlingen representerer en samling av etterbehandlede ressurser som brukes internt i systemet ditt. Disse ressursene genereres når du aktiverer CSS og/eller JavaScript-etterbehandlingsalternativer."

#: include/admin-interfaces/_settings.class.php:775
msgid "The purpose of Data Collection is to optimize and enhance performance by storing processed assets, which helps in speeding up subsequent loading times and ensuring consistent behavior of your site's styling and functionality."
msgstr "Hensikten med datainnsamling er å optimalisere og forbedre ytelsen ved å lagre behandlede ressurser, noe som bidrar til å fremskynde påfølgende lastingstider og sikre konsistent atferd for nettstedets stil og funksjonalitet."

#: include/admin-interfaces/_settings.class.php:776
msgid "Important Note:"
msgstr "Viktig merknad:"

#: include/admin-interfaces/_settings.class.php:780
msgid "<b>Clearing Data Collection:</b> It is generally not necessary to clear the Data Collection. However, if you encounter any issues such as layout inconsistencies or broken design elements on your site, clearing this data might resolve such problems."
msgstr "<b>Tømming av datainnsamling:</b> Det er vanligvis ikke nødvendig å tømme datainnsamlingen. Imidlertid, hvis du opplever problemer som layoutuoverensstemmelser eller ødelagte designelementer på nettstedet ditt, kan det å tømme disse dataene løse slike problemer."

#: include/admin-interfaces/_settings.class.php:782
msgid "<b>Action Steps:</b> If you suspect that outdated or corrupted assets are affecting your site's appearance or functionality, you can clear the Data Collection from this panel. After clearing, the system will regenerate the necessary assets, which might resolve any issues related to layout or performance."
msgstr "<b>Handlingstrinn:</b> Hvis du mistenker at utdaterte eller korrupte ressurser påvirker nettstedets utseende eller funksjonalitet, kan du tømme datainnsamlingen fra dette panelet. Etter tømming vil systemet regenerere de nødvendige ressursene, noe som kan løse eventuelle problemer knyttet til layout eller ytelse."

#: include/admin-interfaces/_settings.class.php:784
msgid "For ongoing maintenance or troubleshooting, refer to our documentation."
msgstr "For løpende vedlikehold eller feilsøking, se vår dokumentasjon."

#: include/admin-interfaces/_settings.class.php:787
msgid "Data Collection size is"
msgstr "Datainnsamlingsstørrelse er"

#: include/admin-interfaces/_settings.class.php:788
msgid "Data Collection Clear"
msgstr "Tøm datainnsamling"

#: include/admin-interfaces/_setup.class.php:43
msgid "Setup"
msgstr "Oppsett"

#: include/admin-interfaces/_setup.class.php:56
msgid "ReWrite"
msgstr "Omskriv"

#: include/admin-interfaces/_setup.class.php:66 include/admin-interfaces/_setup.class.php:74
msgid "Add the following to your"
msgstr "Legg til følgende i din"

#: include/admin-interfaces/_setup.class.php:66 include/admin-interfaces/_setup.class.php:74
msgid "file in"
msgstr "fil i"

#: include/admin-interfaces/_setup.class.php:66
msgid "<strong>above</strong> all other code"
msgstr "<strong>over</strong> all annen kode"

#: include/admin-interfaces/_setup.class.php:67
msgid "Remove any existing rewrite rules within"
msgstr "Fjern alle eksisterende omskrivingsregler innenfor"

#: include/admin-interfaces/_setup.class.php:67 include/admin-interfaces/_setup.class.php:111 include/functions.class.php:2512 include/functions.class.php:2600 modules/components/general-html-css-js-replacements.php:62
msgid "and"
msgstr "og"

#: include/admin-interfaces/_setup.class.php:75
msgid "Remove any existing rewrite rules named <b>wph</b>, then add the following into &#x3C;rules&#x3E;, above any other rule."
msgstr "Fjern alle eksisterende omskrivingsregler med navn <b>wph</b>, og legg deretter til følgende i &#x3C;rules&#x3E;, over enhver annen regel."

#: include/admin-interfaces/_setup.class.php:86
msgid "Your site use WPEngine! You need to get in touch with live support and forward the following details:"
msgstr "Nettstedet ditt bruker WPEngine! Du må ta kontakt med kundestøtte og videresende følgende detaljer:"

#: include/admin-interfaces/_setup.class.php:87
msgid "Ask the support representative to add the following Nginx rewrites to your account at \"before\" (not \"before-in-location\") spot! This can be for Staging or Production, depends on which the current site is deployed."
msgstr "Be støtterepresentanten om å legge til følgende Nginx-omskrivinger til kontoen din på \"before\" (ikke \"before-in-location\")-stedet! Dette kan være for Staging eller Production, avhengig av hvilket nettsted som er deployert."

#: include/admin-interfaces/_setup.class.php:88 include/admin-interfaces/_setup.class.php:96
msgid "Explicitly specify the code lines must be used as is, they are not redirects but rewrite rules."
msgstr "Spesifiser uttrykkelig at kodelinjene må brukes som de er, de er ikke omdirigeringer men omskrivingsregler."

#: include/admin-interfaces/_setup.class.php:94
msgid "Your site use Kinsta! You need to get in touch with live support and forward the following details:"
msgstr "Nettstedet ditt bruker Kinsta! Du må ta kontakt med kundestøtte og videresende følgende detaljer:"

#: include/admin-interfaces/_setup.class.php:95
msgid "Ask the support representative to add the following Nginx rewrites to your account! This can be for Staging or Production, depends on which the current site is deployed."
msgstr "Be støtterepresentanten om å legge til følgende Nginx-omskrivinger til kontoen din! Dette kan være for Staging eller Production, avhengig av hvilket nettsted som er deployert."

#: include/admin-interfaces/_setup.class.php:107
msgid "There are two ways to deply the custom nginx rewrites:"
msgstr "Det er to måter å deployere de egendefinerte nginx-omskrivingene på:"

#: include/admin-interfaces/_setup.class.php:110
msgid "Add the following lines to your Nginx config file located usually at"
msgstr "Legg til følgende linjer i Nginx-konfigurasjonsfilen din som vanligvis ligger på"

#: include/admin-interfaces/_setup.class.php:111
msgid "Replace any existing rewrite rules within"
msgstr "Erstatt alle eksisterende omskrivingsregler innenfor"

#: include/admin-interfaces/_setup.class.php:112 include/functions.class.php:2513
msgid "After config file updated"
msgstr "Etter at konfigurasjonsfilen er oppdatert"

#: include/admin-interfaces/_setup.class.php:112 include/functions.class.php:2513 include/functions.class.php:2601
msgid "Test"
msgstr "Test"

#: include/admin-interfaces/_setup.class.php:112 include/functions.class.php:2513 include/functions.class.php:2601
msgid "the new data using "
msgstr "de nye dataene ved hjelp av "

#: include/admin-interfaces/_setup.class.php:112 include/admin-interfaces/_setup.class.php:118
msgid "If successfully compile, restart the Nginx service."
msgstr "Hvis den kompileres, restart Nginx-tjenesten."

#: include/admin-interfaces/_setup.class.php:112 include/admin-interfaces/_setup.class.php:118
msgid "read more.."
msgstr "les mer.."

#: include/admin-interfaces/_setup.class.php:116
msgid "Caution: The system encountered an issue while attempting to write the custom rewrites to wphide-nginx.conf. Resolve the problem or follow the steps above.  "
msgstr "Advarsel: Systemet opplevde et problem under forsøket på å skrive de tilpassede omskrivningene til wphide-nginx.conf. Løs problemet eller følg trinnene ovenfor. "

#: include/admin-interfaces/_setup.class.php:117
msgid "Correspondingly, with the option \"Save the Nginx Rewrites to a wphide-nginx.conf file,\" the following lines have been added to a file named wphide-nginx.conf located on site root. You can incorporate this file into your nginx.config using the following line:"
msgstr "Tilsvarende, med alternativet \"Lagre Nginx-omskrivingene til en wphide-nginx.conf-fil,\" er følgende linjer lagt til i en fil kalt wphide-nginx.conf som ligger på nettstedets rot. Du kan inkorporere denne filen i nginx.config ved å bruke følgende linje:"

#: include/admin-interfaces/_setup.class.php:118
msgid "After the update, test the new data using "
msgstr "Etter oppdateringen, test de nye dataene ved hjelp av "

#: include/admin-interfaces/_setup.class.php:127
msgid "There is no change in rewrite data, no additional action is necessary."
msgstr "Det er ingen endring i omskrivingsdata, ingen ytterligere handling er nødvendig."

#: include/admin-interfaces/_setup.class.php:162 include/admin-interfaces/_setup.class.php:171 include/admin-interfaces/_setup.class.php:194
msgid "The following code need to be placed before"
msgstr "Følgende kode må plasseres før"

#: include/admin-interfaces/_setup.class.php:162 include/admin-interfaces/_setup.class.php:171
msgid "block, which is the http { .. } section."
msgstr "blokk, som er http { .. }-seksjonen."

#: include/admin-interfaces/_setup.class.php:173 include/admin-interfaces/_setup.class.php:194
msgid "Or use an include for the file "
msgstr "Eller bruk en include for filen "

#: include/admin-interfaces/_setup.class.php:194
msgid "block."
msgstr "blokk."

#: include/admin-interfaces/_setup.class.php:212
msgid "Once all above steps completed, confirm throught the following button."
msgstr "Når alle trinnene ovenfor er fullført, bekreft gjennom følgende knapp."

#: include/admin-interfaces/_setup.class.php:302
msgid "Environment File"
msgstr "Miljøfil"

#: include/admin-interfaces/_setup.class.php:320
msgid "Add the following to "
msgstr "Legg til følgende i "

#: include/admin-interfaces/_setup.class.php:320
msgid "<strong>Replacing</strong> anything inside the file"
msgstr "<strong>Erstatt</strong> alt inni filen"

#: include/admin-interfaces/_setup.class.php:326
msgid "The environment file contain correct data, no additional action is necessary."
msgstr "Miljøfilen inneholder riktige data, ingen ytterligere handling er nødvendig."

#: include/admin-interfaces/_setup.class.php:340
msgid "Wp-config.php"
msgstr "Wp-config.php"

#: include/admin-interfaces/_setup.class.php:350
msgid "Add the following code to "
msgstr "Legg til følgende kode i "

#: include/admin-interfaces/_setup.class.php:350
msgid " at top, right after &#60;?php tag. If exists, <strong>Replace</strong> any existing lines betwen <strong># START WP Hide & Security Enhancer</strong> and <strong># END WP Hide & Security Enhancer</strong>"
msgstr " på toppen, rett etter &#60;?php-taggen. Hvis den finnes, <strong>erstatt</strong> alle eksisterende linjer mellom <strong># START WP Hide & Security Enhancer</strong> og <strong># END WP Hide & Security Enhancer</strong>"

#: include/admin-interfaces/_setup.class.php:356
msgid "The wp-config.php file contain correct data, no additional action is necessary."
msgstr "Filen wp-config.php inneholder korrekte data, ingen ytterligere tiltak er nødvendig."

#: include/admin-interfaces/security-scan.class.php:198 include/admin-interfaces/security-scan.class.php:203 include/admin-interfaces/security-scan.class.php:537 include/widgets.class.php:56
msgid "Security Scan"
msgstr "Sikkerhetsskanning"

#: include/admin-interfaces/security-scan.class.php:230
msgid "Unknow - Start a new Scan"
msgstr "Ukjent - Start en ny skanning"

#: include/admin-interfaces/security-scan.class.php:291
msgid "Unknown"
msgstr "Ukjent"

#: include/admin-interfaces/security-scan.class.php:294 include/admin-interfaces/security-scan.class.php:339
msgid "Running first Scan.. Please wait!"
msgstr "Kjører første skanning.. Vennligst vent!"

#: include/admin-interfaces/security-scan.class.php:311 include/widgets.class.php:46
msgid "Your current estimated protection is"
msgstr "Din nåværende estimerte beskyttelse er"

#: include/admin-interfaces/security-scan.class.php:335
msgid "Start First Scan"
msgstr "Start første skanning"

#: include/admin-interfaces/security-scan.class.php:337 include/admin-interfaces/security-scan.class.php:372
msgid "Working"
msgstr "Arbeider"

#: include/admin-interfaces/security-scan.class.php:337 include/admin-interfaces/security-scan.class.php:372
msgid "of"
msgstr "av"

#: include/admin-interfaces/security-scan.class.php:337 include/admin-interfaces/security-scan.class.php:372
msgid "total tests"
msgstr "totale tester"

#: include/admin-interfaces/security-scan.class.php:340 include/admin-interfaces/security-scan.class.php:402
msgid "Last Scan"
msgstr "Siste skanning"

#: include/admin-interfaces/security-scan.class.php:340
msgid "Unavailable"
msgstr "Utilgjengelig"

#: include/admin-interfaces/security-scan.class.php:351 include/admin-interfaces/security-scan.class.php:393
msgid "Another Scan instance in progress. Refresh the page in a minute."
msgstr "En annen skanningsinstans er i gang. Oppdater siden om et øyeblikk."

#: include/admin-interfaces/security-scan.class.php:360
msgid "Passed"
msgstr "Bestått"

#: include/admin-interfaces/security-scan.class.php:364
msgid "Failed"
msgstr "Feilet"

#: include/admin-interfaces/security-scan.class.php:370
msgid "Start New Scan"
msgstr "Start ny skanning"

#: include/admin-interfaces/security-scan.class.php:398
msgid "Found new Items, a new Security Scann is recommended."
msgstr "Fant nye elementer, en ny sikkerhetsskanning anbefales."

#: include/admin-interfaces/security-scan.class.php:453
msgid "Very Poor"
msgstr "Veldig dårlig"

#: include/admin-interfaces/security-scan.class.php:455
msgid "Poor"
msgstr "Dårlig"

#: include/admin-interfaces/security-scan.class.php:457
msgid "Fair"
msgstr "Middels"

#: include/admin-interfaces/security-scan.class.php:459
msgid "Good"
msgstr "God"

#: include/admin-interfaces/security-scan.class.php:461
msgid "Great"
msgstr "Flott"

#: include/admin-interfaces/security-scan.class.php:463
msgid "Excellent"
msgstr "Utmerket"

#: include/admin-interfaces/security-scan.class.php:465
msgid "Perfect"
msgstr "Perfekt"

#: include/admin-interfaces/security-scan.class.php:524 include/admin-interfaces/security-scan.class.php:527
msgid "unsatisfactory"
msgstr "utilfredsstillende"

#: include/admin-interfaces/security-scan.class.php:530
msgid "dangerously low, an imminent security breach is highly likely."
msgstr "farlig lav, en overhengende sikkerhetsbrudd er svært sannsynlig."

#: include/admin-interfaces/security-scan.class.php:534
msgid "The current protection level is "
msgstr "Nåværende beskyttelsesnivå er "

#: include/admin-interfaces/security-scan.class.php:534
msgid "Consider improving the overall security by fixing the issues reported by the Scan"
msgstr "Vurder å forbedre den generelle sikkerheten ved å fikse problemene rapportert av skanningen"

#: include/admin-interfaces/security-scan.class.php:552
msgid "Ignore"
msgstr "Ignorer"

#: include/admin-interfaces/security-scan.class.php:555
msgid "Restore"
msgstr "Gjenopprett"

#: include/admin-interfaces/security-scan.class.php:581
msgid "Another Scan instance in progress. Please wait until completed."
msgstr "En annen skanningsinstans er i gang. Vennligst vent til den er fullført."

#: include/admin-interfaces/security-scan.class.php:611
msgid "Scan completed."
msgstr "Skanning fullført."

#: include/admin-interfaces/security-scan.class.php:794
msgid "The wp_remote_get() returns a Not Found page."
msgstr "wp_remote_get() returnerer en Ikke Funnet-side."

#: include/admin-interfaces/security-scan.class.php:800
msgid "The wp_remote_get() returns a 401 error code, the request could not be authenticated. Does the site use an httpd password?"
msgstr "wp_remote_get() returnerer en 401-feilkode, forespørselen kunne ikke autentiseres. Bruker nettstedet et httpd-passord?"

#: include/admin-interfaces/security-scan.class.php:806
msgid "The wp_remote_get() returns a"
msgstr "wp_remote_get() returnerer en"

#: include/admin-interfaces/security-scan.class.php:806
msgid "error code"
msgstr "feilkode"

#: include/admin-interfaces/security-scan.class.php:810
msgid "Unespected error code for wp_remote_get() call."
msgstr "Uventet feilkode for wp_remote_get()-kall."

#: include/admin-interfaces/security-scan/scan_item_database_prefix.php:32
msgid ""
"WordPress security is a serious matter and you can improve it by changing the WordPress database prefix. A WordPress database contains all of the information for your website, which makes it a prime target for hackers. \n"
"                                                                By default, the WordPress database prefix is “wp_” and is quite easy to locate and target."
msgstr ""
"WordPress-sikkerhet er en alvorlig sak, og du kan forbedre den ved å endre WordPress-databasetabellprefikset. En WordPress-database inneholder all informasjon for nettstedet ditt, noe som gjør den til et hovedmål for hackere. \n"
"                                                                Som standard er WordPress-databasetabellprefikset \"wp_\" og er ganske enkelt å lokalisere og målrette."

#: include/admin-interfaces/security-scan/scan_item_database_prefix.php:46 include/admin-interfaces/security-scan/scan_item_db_debug.php:48 include/admin-interfaces/security-scan/scan_item_disable_file_edit.php:44 include/admin-interfaces/security-scan/scan_item_wp_debug.php:46
msgid "Current value: "
msgstr "Nåværende verdi: "

#: include/admin-interfaces/security-scan/scan_item_database_prefix.php:51
msgid "<span class=\"dashicons dashicons-no\"></span>The database prefix use the default wp_ prefix."
msgstr "<span class=\"dashicons dashicons-no\"></span>Databasetabellprefikset bruker standard wp_-prefikset."

#: include/admin-interfaces/security-scan/scan_item_database_prefix.php:61
msgid "<span class=\"dashicons dashicons-yes\"></span>The database prefix use a custom name."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Databasetabellprefikset bruker et egendefinert navn."

#: include/admin-interfaces/security-scan/scan_item_db_debug.php:32 include/admin-interfaces/security-scan/scan_item_wp_debug.php:32
msgid ""
"Debugging PHP code is part of any project, but WordPress comes with specific debug systems designed to simplify the process as well as standardize code across the core, plugins and themes.\n"
"                                                                On production sites, the debug should be disabled to avoid exposing paths and other pieces of information related to the site. "
msgstr ""
"Feilsøking av PHP-kode er en del av ethvert prosjekt, men WordPress kommer med spesifikke feilsøkingssystemer designet for å forenkle prosessen samt standardisere kode på tvers av kjerne, plugins og temaer.\n"
"                                                                På produksjonsnettsteder bør feilsøking deaktiveres for å unngå å eksponere stier og andre informasjonsdeler relatert til nettstedet."

#: include/admin-interfaces/security-scan/scan_item_db_debug.php:53
msgid "<span class=\"dashicons dashicons-no\"></span>The database debug is active. Check your site wp-config.php and comment the WP_DEBUG and  WP_DEBUG_DISPLAY ( if exists ) constants declaration."
msgstr "<span class=\"dashicons dashicons-no\"></span>Databasefeilsøking er aktiv. Sjekk din wp-config.php og kommenter ut WP_DEBUG og WP_DEBUG_DISPLAY (hvis de finnes) konstantdeklarasjoner."

#: include/admin-interfaces/security-scan/scan_item_db_debug.php:62
msgid "<span class=\"dashicons dashicons-yes\"></span>The database debug is disabled."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Databasefeilsøking er deaktivert."

#: include/admin-interfaces/security-scan/scan_item_disable_file_edit.php:32
msgid ""
"The WordPress theme/plugin file editor lets you open files from the site. It displays the file content on the text editor allowing changes to the code, directly on the dashboard.\n"
"                                                                <br />Unless this is a development instance, it should be disabled."
msgstr ""
"WordPress tema/plugin-filredigering lar deg åpne filer fra nettstedet. Den viser filinnholdet i teksteditoren og tillater endringer i koden, direkte på dashbordet.\n"
"                                                                <br />Med mindre dette er en utviklingsinstans, bør den deaktiveres."

#: include/admin-interfaces/security-scan/scan_item_disable_file_edit.php:49
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The file editor is enabled. \n"
"                                                                        <br />To fix this security issue, add/change the wp-config.php:\n"
"                                                                        <br /><code>define ( 'DISALLOW_FILE_EDIT', TRUE );</code>."
msgstr ""
"<span class=\"dashicons dashicons-no\"></span>Filredigering er aktivert. \n"
"                                                                        <br />For å fikse dette sikkerhetsproblemet, legg til/endre wp-config.php:\n"
"                                                                        <br /><code>define ( 'DISALLOW_FILE_EDIT', TRUE );</code>."

#: include/admin-interfaces/security-scan/scan_item_disable_file_edit.php:60
msgid "<span class=\"dashicons dashicons-yes\"></span>The file editor is disabled."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Filredigering er deaktivert."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:29
msgid "Firewall"
msgstr "Brannmur"

#: include/admin-interfaces/security-scan/scan_item_firewall.php:32
msgid ""
"A Firewall is a security piece of software that adds a layer of protection to your site. A firewall works as a rules-based filter for all incoming traffic to a website, it ensures only the secure traffic is reaching the server, all malicious attempts will be blocked and logged.\n"
"                                                                <br />A Firewall works as Proactive ratter reactive security solution, so it helps to protect a website before the malicious and malware actually reach it. This is a huge improvement for security, as preventing any harm and damages to a site, spare the administrators of incalculable losses which the malware can do."
msgstr ""
"En brannmur er et sikkerhetsprogram som legger til et beskyttelseslag for nettstedet ditt. En brannmur fungerer som en regelbasert filter for all innkommende trafikk til et nettsted, den sikrer at kun sikker trafikk når serveren, alle ondsinnede forsøk blir blokkert og loggført.\n"
"                                                                <br />En brannmur fungerer som en proaktiv snarere enn reaktiv sikkerhetsløsning, så den hjelper til med å beskytte et nettsted før skadelig kode og malware faktisk når det. Dette er en stor forbedring for sikkerheten, ettersom å forhindre skade og ødeleggelser på et nettsted, sparer administratorer for uoverkommelige tap som malware kan forårsake."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:49
msgid "Failed to block requests using malicious header calls."
msgstr "Klarte ikke å blokkere forespørsler som bruker ondsinnede header-kall."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:53
msgid "Failed to block requests using malicious set-cookie calls."
msgstr "Klarte ikke å blokkere forespørsler som bruker ondsinnede set-cookie-kall."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:57
msgid "Failed to block requests using malicious MySQL code."
msgstr "Klarte ikke å blokkere forespørsler som bruker ondsinnet MySQL-kode."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:61
msgid "Failed to block requests using malicious globals calls."
msgstr "Klarte ikke å blokkere forespørsler som bruker ondsinnede globals-kall."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:65
msgid "Failed to block requests using malicious request calls."
msgstr "Klarte ikke å blokkere forespørsler som bruker ondsinnede forespørsel-kall."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:92
msgid "No valid respons for the call."
msgstr "Ingen gyldig respons for kallet."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:108
msgid "<span class=\"dashicons dashicons-no\"></span>Your site does not appear to use a Firewall or fails to block specific hacks."
msgstr "<span class=\"dashicons dashicons-no\"></span>Nettstedet ditt ser ikke ut til å bruke en brannmur eller klarer ikke å blokkere spesifikke angrep."

#: include/admin-interfaces/security-scan/scan_item_firewall.php:115 include/admin-interfaces/security-scan/scan_item_hide_replacements.php:138
msgid "Found"
msgstr "Funnet"

#: include/admin-interfaces/security-scan/scan_item_firewall.php:129
msgid "<span class=\"dashicons dashicons-yes\"></span>Your site use a Firewall."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Nettstedet ditt bruker en brannmur."

#: include/admin-interfaces/security-scan/scan_item_headers.php:29
msgid "HTTP Response Security Headers"
msgstr "HTTP-respons-sikkerhetsheadere"

#: include/admin-interfaces/security-scan/scan_item_headers.php:32
msgid ""
"HTTP Response Headers are a powerful tool to Harden Your Website.\n"
"                                                                The Hypertext Transfer Protocol (HTTP) is based on a client-server architecture, in which the client ( typically a web browser application ) establishes a connection with the server through a destination URL and waits for a response.\n"
"                                                                The HTTP Headers allow the client and the server send additional pieces of information with the HTTP request or response.\n"
"                                                                The HTTP Headers are categorised by their purpose: Authentication, Caching, Client hints, Conditionals, Connection management, Content negotiation, Controls, Cookies, CORS, Downloads, Message body information, Proxies, Redirects, Request context, Response context, Range requests, Security, Server-sent events, Transfer coding, WebSockets, Other\n"
"                                                                This area provides support for the <a href='https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#security' target='_blank'>Security Headers</a> type. Those are the ones responsible for the security implementation for any page."
msgstr ""
"HTTP-respons-headere er et kraftig verktøy for å styrke nettstedet ditt.\n"
"                                                                Hypertext Transfer Protocol (HTTP) er basert på en klient-server-arkitektur, der klienten (vanligvis en nettleserapplikasjon) etablerer en tilkobling med serveren gjennom en destinasjons-URL og venter på et svar.\n"
"                                                                HTTP-headere tillater klienten og serveren å sende ekstra informasjonsbiter med HTTP-forespørselen eller responsen.\n"
"                                                                HTTP-headere kategoriseres etter deres formål: Autentisering, Hurtiglager, Klienthints, Betingelser, Tilkoblingshåndtering, Innholdsforhandling, Kontroller, Informasjonskapsler, CORS, Nedlastinger, Meldingstekstinformasjon, Proxies, Omdirigeringer, Forespørselskontekst, Responskontekst, Rekkeviddeforespørsler, Sikkerhet, Server-sendte hendelser, Overføringskoding, WebSockets, Annet\n"
"                                                                Dette området gir støtte for <a href='https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers#security' target='_blank'>Sikkerhetsheadere</a>-typen. Disse er ansvarlige for sikkerhetsimplementeringen for enhver side."

#: include/admin-interfaces/security-scan/scan_item_headers.php:86
msgid "<span class=\"dashicons dashicons-no\"></span>Your site is missing some security headers."
msgstr "<span class=\"dashicons dashicons-no\"></span>Nettstedet ditt mangler noen sikkerhetsheadere."

#: include/admin-interfaces/security-scan/scan_item_headers.php:98 include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:81 include/admin-interfaces/security-scan/scan_item_hide_replacements.php:144
msgid "Unable to complete this security task as an error occoured"
msgstr "Kan ikke fullføre denne sikkerhetsoppgaven da en feil oppstod"

#: include/admin-interfaces/security-scan/scan_item_headers.php:109 include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:92
msgid "<span class=\"dashicons dashicons-yes\"></span>There are no headers containing valuable pieces of information regarding your environment."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Det er ingen headere som inneholder verdifull informasjon om miljøet ditt."

#: include/admin-interfaces/security-scan/scan_item_hide_admin_ajax.php:29
msgid "New admin-ajax.php"
msgstr "Ny admin-ajax.php"

#: include/admin-interfaces/security-scan/scan_item_hide_admin_ajax.php:32
msgid "The admin-ajax.php is being used by WordPress core and many plugins to initiate AJAX calls from dashboard and front side. This is specific to WordPress, a site using such slug is an easy target to hack attempts."
msgstr "admin-ajax.php brukes av WordPress-kjernen og mange plugins for å initiere AJAX-kall fra dashbord og frontside. Dette er spesifikt for WordPress, et nettsted som bruker en slik slug er et enkelt mål for hack-forsøk."

#: include/admin-interfaces/security-scan/scan_item_hide_admin_ajax.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>Rewriting the admin-ajax.php to another slug to increase overall security for a WordPress site."
msgstr "<span class=\"dashicons dashicons-no\"></span>Omskriving av admin-ajax.php til en annen slug for å øke den generelle sikkerheten for et WordPress-nettsted."

#: include/admin-interfaces/security-scan/scan_item_hide_admin_ajax.php:65 include/admin-interfaces/security-scan/scan_item_hide_admin_url.php:66 include/admin-interfaces/security-scan/scan_item_hide_emulate.php:66 include/admin-interfaces/security-scan/scan_item_hide_json.php:69 include/admin-interfaces/security-scan/scan_item_hide_json_clean_api.php:66 include/admin-interfaces/security-scan/scan_item_hide_license_txt.php:65 include/admin-interfaces/security-scan/scan_item_hide_new_wp_login.php:66 include/admin-interfaces/security-scan/scan_item_hide_other_generator.php:65 include/admin-interfaces/security-scan/scan_item_hide_postprocessing.php:74 include/admin-interfaces/security-scan/scan_item_hide_readme_html.php:65 include/admin-interfaces/security-scan/scan_item_hide_registration.php:70 include/admin-interfaces/security-scan/scan_item_hide_remove_header_link.php:65 include/admin-interfaces/security-scan/scan_item_hide_remove_html_comments.php:65 include/admin-interfaces/security-scan/scan_item_hide_robots.php:66 include/admin-interfaces/security-scan/scan_item_hide_wlwmanifest.php:65 include/admin-interfaces/security-scan/scan_item_hide_wordpress_generator.php:65 include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:65
msgid "<span class=\"dashicons dashicons-yes\"></span>The option appears properly configured."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Alternativet ser ut til å være riktig konfigurert."

#: include/admin-interfaces/security-scan/scan_item_hide_admin_url.php:29 modules/components/admin-admin_url.php:51 modules/components/admin-admin_url.php:57
msgid "New Admin Url"
msgstr "Ny admin-URL"

#: include/admin-interfaces/security-scan/scan_item_hide_admin_url.php:32
msgid ""
"Despite the flexibility of WordPress framework, there are few ways to configure the admin login url customization for making a bit safer against unauthorized access and brute force attempts. All methods are not provided out of the box through WordPress core but require custom code to make it happen.\n"
"                                                                <br />This feature provide an easy way to change the default /wp-admin/ to a different slug."
msgstr ""
"Til tross for fleksibiliteten i WordPress-rammeverket, er det få måter å konfigurere tilpasning av admin-innloggings-URL for å gjøre det litt sikrere mot uautorisert tilgang og brute force-forsøk. Alle metoder er ikke tilgjengelige umiddelbart gjennom WordPress-kjernen, men krever egendefinert kode for å gjennomføre det.\n"
"                                                                <br />Denne funksjonen gir en enkel måte å endre standard /wp-admin/ til en annen slug."

#: include/admin-interfaces/security-scan/scan_item_hide_admin_url.php:55
msgid "<span class=\"dashicons dashicons-no\"></span>Map a new admin url instead default prevent hackers boot to attempt to brute force a site login."
msgstr "<span class=\"dashicons dashicons-no\"></span>Kartlegg en ny admin-URL i stedet for standard for å forhindre hackere i å forsøke brute force på en nettstedinnlogging."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:29
msgid "New Child Theme Path"
msgstr "Ny barne-tema-sti"

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:32 include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:32
msgid "This option helps to change the theme url to a custom one. As default all theme assets ( styles, JavaScript etc ) are loaded using the theme url and appear on front side HTML source code."
msgstr "Dette alternativet hjelper til med å endre tema-URL til en egendefinert. Som standard lastes alle tema-ressurser (stiler, JavaScript etc) ved hjelp av tema-URL og vises i frontside HTML-kildekode."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:47 include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:50
msgid "<span class=\"dashicons dashicons-yes\"></span>On the last scan, you are not using a Child Theme."
msgstr "<span class=\"dashicons dashicons-yes\"></span>På siste skanning brukte du ikke et barne-tema."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:77 include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:67
msgid "<span class=\"dashicons dashicons-no\"></span>The default theme url has not been customised."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard tema-URL er ikke tilpasset."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:81 include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:71
msgid "<span class=\"dashicons dashicons-no\"></span>The default theme url is still found within the source HTML."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard tema-URL finnes fortsatt i kilde-HTML."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:83 include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:80 include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:73 include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:74 include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:73 include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:73 include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:73 include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:73
msgid "<br />Ensure you cleared the site cache, then check again."
msgstr "<br />Forsikre deg om at du har tømt nettstedets hurtiglager, og sjekk deretter igjen."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme.php:95 include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:85
msgid "<span class=\"dashicons dashicons-yes\"></span>The default theme url cannot be found anymore through the site source."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Standard tema-URL kan ikke lenger finnes gjennom nettstedskilden."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:29
msgid "New Child Theme Style File Path"
msgstr "Ny barne-tema-stil-fil-sti"

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:32 include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:32
msgid "This allow to change the default style.css filename to something else e.g. template-style.css. Per this example, on front side the main style link change from /style.css to /template-style.css "
msgstr "Dette tillater å endre standard style.css-filnavnet til noe annet f.eks. template-style.css. I følge dette eksemplet, på frontsiden endres hovedstilenken fra /style.css til /template-style.css"

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:74 include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:67
msgid "<span class=\"dashicons dashicons-no\"></span>The default theme style url has not been customised."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard tema-stil-URL er ikke tilpasset."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:78 include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:71
msgid "<span class=\"dashicons dashicons-no\"></span>The default theme style url is still found within the source HTML."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard tema-stil-URL finnes fortsatt i kilde-HTML."

#: include/admin-interfaces/security-scan/scan_item_hide_check_child_theme_style.php:92 include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:85
msgid "<span class=\"dashicons dashicons-yes\"></span>The default theme style url cannot be found anymore through the site source."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Standard tema-stil-URL kan ikke lenger finnes gjennom nettstedskilden."

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:29 modules/components/rewrite-comments.php:48
msgid "New wp-comments-post.php"
msgstr "Ny wp-comments-post.php"

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:32
msgid ""
"To avoid boots to create smap comments, the default wp-comments-post.php should be changed to a custom one.\n"
"                                                            <br />This makes it easy to recognise as WordPress form. Boots always search for such file ( wp-comments-post.php ) and automatically submit spam messages.Though this option a new file slug can replace the default."
msgstr ""
"For å unngå at boter lager spam-kommentarer, bør standard wp-comments-post.php endres til en egendefinert.\n"
"                                                            <br />Dette gjør det enkelt å gjenkjenne som et WordPress-skjema. Boter søker alltid etter en slik fil (wp-comments-post.php) og sender automatisk spam-meldinger. Gjennom dette alternativet kan en ny fil-slug erstatte standard."

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:67
msgid "<span class=\"dashicons dashicons-no\"></span>The default wp-comments-post.php has not been customised."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard wp-comments-post.php er ikke tilpasset."

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:71
msgid "<span class=\"dashicons dashicons-no\"></span>The default wp-comments-post.php is still found within the source HTML."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard wp-comments-post.php finnes fortsatt i kilde-HTML."

#: include/admin-interfaces/security-scan/scan_item_hide_check_comments.php:85
msgid "<span class=\"dashicons dashicons-yes\"></span>The default wp-comments-post.php cannot be found anymore through the site source."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Standard wp-comments-post.php kan ikke lenger finnes gjennom nettstedskilden."

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:29 modules/components/rewrite-plugin_path.php:117 modules/components/rewrite-plugin_path.php:121
msgid "New Plugins Path"
msgstr "Ny plugin-sti"

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:32
msgid ""
"In WordPress, a plugin is a small software application that extends the features and functions of a WordPress website.\n"
"                                                                <br />Plugins play a major role in building great websites using WordPress. They make it easier for users to add features to their website without knowing a single line of code."
msgstr ""
"I WordPress er en plugin en liten programvareapplikasjon som utvider funksjonene og egenskapene til et WordPress-nettsted.\n"
"                                                                <br />Plugins spiller en stor rolle i å bygge flotte nettsteder med WordPress. De gjør det enklere for brukere å legge til funksjoner på nettstedet sitt uten å kunne en eneste kodelinje."

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:68
msgid "<span class=\"dashicons dashicons-no\"></span>The default plugins path has not been customised."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard plugin-sti er ikke tilpasset."

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:72
msgid "<span class=\"dashicons dashicons-no\"></span>The default plugins path is still found within the source HTML."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard plugin-sti finnes fortsatt i kilde-HTML."

#: include/admin-interfaces/security-scan/scan_item_hide_check_plugins.php:86
msgid "<span class=\"dashicons dashicons-yes\"></span>The default plugins path cannot be found anymore through the site source."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Standard plugin-sti kan ikke lenger finnes gjennom nettstedskilden."

#: include/admin-interfaces/security-scan/scan_item_hide_check_theme.php:29 modules/components/rewrite-theme_path.php:68 modules/components/rewrite-theme_path.php:72
msgid "New Theme Path"
msgstr "Ny tema-sti"

#: include/admin-interfaces/security-scan/scan_item_hide_check_theme_style.php:29
msgid "New Theme Style File Path"
msgstr "Ny tema-stil-fil-sti"

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:29
msgid "Hide default /wp-content/ "
msgstr "Skjul standard /wp-content/"

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:32 modules/components/rewrite-wp_content_path.php:57
msgid "As default a WordPress installation contain a wp-content folder which store files and resources used by themes and plugin. The wp-content is a common fingerprint, which makes easily to anyone to identify the site as being created on WordPress."
msgstr "Som standard inneholder en WordPress-installasjon en wp-content-mappe som lagrer filer og ressurser brukt av temaer og plugins. wp-content er et vanlig fingeravtrykk, som gjør det enkelt for alle å identifisere nettstedet som opprettet på WordPress."

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:67
msgid "<span class=\"dashicons dashicons-no\"></span>The default /wp-content/ has not been customised."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard /wp-content/ er ikke tilpasset."

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:71
msgid "<span class=\"dashicons dashicons-no\"></span>The default /wp-content/ is still found within the source HTML."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard /wp-content/ finnes fortsatt i kilde-HTML."

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_content.php:85
msgid "<span class=\"dashicons dashicons-yes\"></span>The default /wp-content/ cannot be found anymore through the site source."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Standard /wp-content/ kan ikke lenger finnes gjennom nettstedskilden."

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:29
msgid "Hide default /wp-includes/ "
msgstr "Skjul standard /wp-includes/"

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:32 modules/components/rewrite-wp_includes_path.php:46
msgid "As default a WordPress installation contain a wp-include folder which store files and resources used by WordPress core, themes and plugin. The wp-includes is a common fingerprint, which makes easily to anyone to identify the site as being created on WordPress."
msgstr "Som standard inneholder en WordPress-installasjon en wp-include-mappe som lagrer filer og ressurser brukt av WordPress-kjernen, temaer og plugins. wp-includes er et vanlig fingeravtrykk, som gjør det enkelt for alle å identifisere nettstedet som opprettet på WordPress."

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:67
msgid "<span class=\"dashicons dashicons-no\"></span>The default /wp-includes/ has not been customised."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard /wp-includes/ er ikke tilpasset."

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:71
msgid "<span class=\"dashicons dashicons-no\"></span>The default /wp-includes/ is still found within the source HTML."
msgstr "<span class=\"dashicons dashicons-no\"></span>Standard /wp-includes/ finnes fortsatt i kilde-HTML."

#: include/admin-interfaces/security-scan/scan_item_hide_check_wp_includes.php:85
msgid "<span class=\"dashicons dashicons-yes\"></span>The default /wp-includes/ cannot be found anymore through the site source."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Standard /wp-includes/ kan ikke lenger finnes gjennom nettstedskilden."

#: include/admin-interfaces/security-scan/scan_item_hide_emulate.php:29 modules/components/general-emulate.php:40 modules/components/general-emulate.php:44
msgid "Emulate CMS"
msgstr "Etterligne CMS"

#: include/admin-interfaces/security-scan/scan_item_hide_emulate.php:32
msgid ""
"Using the option the system try to misguide the used WordPress by outputting the wrong traces, of the selected CMS.\n"
"                                                                <br />Misleading and making a false lead provides an extra security, as the attacker search and attempt to hack something which not exist."
msgstr ""
"Ved å bruke alternativet prøver systemet å villede den brukte WordPress ved å sende ut feil spor, fra den valgte CMS-en.\n"
"                                                                <br />Villedende og å lage en falsk ledetråd gir ekstra sikkerhet, ettersom angriperen søker og prøver å hacke noe som ikke eksisterer."

#: include/admin-interfaces/security-scan/scan_item_hide_emulate.php:55
msgid "<span class=\"dashicons dashicons-no\"></span>It's recommended to use the option to output specific CMSs HTML traces to mislead any peculiar check."
msgstr "<span class=\"dashicons dashicons-no\"></span>Det anbefales å bruke alternativet for å sende ut spesifikke CMS HTML-spor for å villede enhver spesiell sjekk."

#: include/admin-interfaces/security-scan/scan_item_hide_json.php:29
msgid "JSON REST"
msgstr "JSON REST"

#: include/admin-interfaces/security-scan/scan_item_hide_json.php:32
msgid ""
"The WordPress REST API is an easy-to-use set of HTTP endpoints which allows access a site data in simple JSON format. That including users, posts, taxonomies and more. Retrieving or updating is as simple as sending a HTTP request.\n"
"                                                                <br />A REST API can be consumed everywhere. On mobile applications, on front-end (web apps) or any other devices that have access on the net, practically everything can connect from anywhere to your site and interact though JSON REST API service."
msgstr ""
"WordPress REST API er et enkelt å bruke sett med HTTP-endepunkter som gir tilgang til nettstedsdata i enkelt JSON-format. Det inkluderer brukere, innlegg, taksonomier og mer. Henting eller oppdatering er like enkelt som å sende en HTTP-forespørsel.\n"
"                                                                <br />En REST API kan konsumeres overalt. På mobilapplikasjoner, på front-end (web-apper) eller enhver annen enhet som har tilgang til nettet, kan praktisk talt alt koble til fra hvor som helst til nettstedet ditt og samhandle gjennom JSON REST API-tjeneste."

#: include/admin-interfaces/security-scan/scan_item_hide_json.php:58
msgid "<span class=\"dashicons dashicons-no\"></span>The JSON endpoint should be customised. If not used, should be disabled."
msgstr "<span class=\"dashicons dashicons-no\"></span>JSON-endepunktet bør tilpasses. Hvis det ikke brukes, bør det deaktiveres."

#: include/admin-interfaces/security-scan/scan_item_hide_json_clean_api.php:29 modules/components/rewrite-json-rest.php:146 modules/components/rewrite-json-rest.php:150
msgid "Clean the REST API response"
msgstr "Rens REST API-responsen"

#: include/admin-interfaces/security-scan/scan_item_hide_json_clean_api.php:32
msgid ""
"When calling the site REST API base route ( e.g. /wp-json/ or ?rest_route=/ ) the service outputs all available namespaces and routes for current site. This can be a breach for the system, as outputs important information regarding certain used theme and plugins.\n"
"                                                                <br />Recommended selection for this option is Yes, to ensure no inside data is being exposed. "
msgstr ""
"Når du kaller nettstedets REST API-baserute (f.eks. /wp-json/ eller ?rest_route=/) sender tjenesten ut alle tilgjengelige navnerom og ruter for gjeldende nettsted. Dette kan være et brudd for systemet, ettersom det sender ut viktig informasjon om visse brukte temaer og plugins.\n"
"                                                                <br />Anbefalt valg for dette alternativet er Ja, for å sikre at ingen interne data eksponeres."

#: include/admin-interfaces/security-scan/scan_item_hide_json_clean_api.php:55
msgid "<span class=\"dashicons dashicons-no\"></span>The \"Clean the REST API response\" should be active."
msgstr "<span class=\"dashicons dashicons-no\"></span>\"Rens REST API-responsen\" bør være aktiv."

#: include/admin-interfaces/security-scan/scan_item_hide_license_txt.php:29 modules/components/rewrite-root-files.php:117 modules/components/rewrite-root-files.php:121
msgid "Block license.txt"
msgstr "Blokker license.txt"

#: include/admin-interfaces/security-scan/scan_item_hide_license_txt.php:32 modules/components/rewrite-root-files.php:122
msgid "This is a text file which contain the licensing terms for WordPress framework. Obviously you don't want that visible as every site containing such file must be a WordPress."
msgstr "Dette er en tekstfil som inneholder lisensvilkårene for WordPress-rammeverket. Åpenbart vil du ikke at dette skal være synlig, ettersom hvert nettsted som inneholder en slik fil må være en WordPress."

#: include/admin-interfaces/security-scan/scan_item_hide_license_txt.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>The license.txt file is still accessible."
msgstr "<span class=\"dashicons dashicons-no\"></span>license.txt-filen er fortsatt tilgjengelig."

#: include/admin-interfaces/security-scan/scan_item_hide_new_wp_login.php:29 modules/components/admin-login_php.php:98 modules/components/admin-login_php.php:102
msgid "New wp-login.php"
msgstr "Ny wp-login.php"

#: include/admin-interfaces/security-scan/scan_item_hide_new_wp_login.php:32
msgid ""
"There are a lot of security issues that come from having your login page open to the public. Most specifically, brute force attacks. Because of the ubiquity of WordPress, these kinds of attacks are becoming more and more common.\n"
"                                                                <br />Map a new wp-login.php instead default prevent hackers boot to attempt to brute force a site login. Being known only by the site owner, the url itself becomes private."
msgstr ""
"Det er mange sikkerhetsproblemer som kommer av å ha innloggingssiden din åpen for offentligheten. Mest spesifikt, brute force-angrep. På grunn av WordPress's utbredelse, blir slike angrep mer og mer vanlige.\n"
"                                                                <br />Kartlegg en ny wp-login.php i stedet for standard for å forhindre hackere i å forsøke brute force på en nettstedinnlogging. Ved å være kjent kun av nettstedeieren, blir URL-en selv privat."

#: include/admin-interfaces/security-scan/scan_item_hide_new_wp_login.php:55
msgid "<span class=\"dashicons dashicons-no\"></span>Map a new wp-login.php instead default prevent hackers boot to attempt to brute force a site login. Being known only by the site owner, the url itself becomes private."
msgstr "<span class=\"dashicons dashicons-no\"></span>Kartlegg en ny wp-login.php i stedet for standard for å forhindre hackere i å forsøke brute force på en nettstedinnlogging. Ved å være kjent kun av nettstedeieren, blir URL-en selv privat."

#: include/admin-interfaces/security-scan/scan_item_hide_other_generator.php:29 modules/components/general-meta.php:177 modules/components/general-meta.php:181
msgid "Remove Other Generator Meta"
msgstr "Fjern annen generator-meta"

#: include/admin-interfaces/security-scan/scan_item_hide_other_generator.php:32 modules/components/general-meta.php:178 modules/components/general-meta.php:182
msgid "Remove other meta generated tags within head (eg Theme Name, Theme Version)."
msgstr "Fjern andre meta-genererte tagger innenfor head (f.eks. Tema-navn, Tema-versjon)."

#: include/admin-interfaces/security-scan/scan_item_hide_other_generator.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>The Other Generator Meta is still visible through the HTML code."
msgstr "<span class=\"dashicons dashicons-no\"></span>Den andre generator-metaen er fortsatt synlig gjennom HTML-koden."

#: include/admin-interfaces/security-scan/scan_item_hide_postprocessing.php:29
msgid "Post-Processing"
msgstr "Etterbehandling"

#: include/admin-interfaces/security-scan/scan_item_hide_postprocessing.php:32
msgid ""
"The feature provides a post-processing engine for all site assets ( CSS /  JavaScript ). That encodes the CSS  and JavaScript, which makes it unable to read. Also, ensure perfect URLs disguise, as even if changing the plugin's name, most of the URLs still contain traces within. \n"
"                                                                    This is also a great tool for making optimisation of the site assets by combining, minifying, comment removal etc. \n"
"                                                                    Perfectly functional and integration in conjunction with other SEO/Optimisation plugins.\n"
"                                                                    <p>&nbsp;</p>\n"
"                                                                    <p>There are 4 types of processing options:\n"
"                                                                    <b>Combine</b>: Merge all code in (usually) 2 files, one in the header and another in the footer.\n"
"                                                                    <b>Combine & Encode Inline</b>: Merge all code in (usually) 2 files, one in the header and another in the footer. Additionally, the Inline code will be base64 encoded and placed in the same spot.\n"
"                                                                    <b>In Place</b>: All JavaScript code will be processed and the results will be placed in the same spot. Any InLine code will be processed and saved into a data-collection directory for later usage.\n"
"                                                                    <b>In Place & Encode Inline</b>: All code will be processed and the results will be placed in the same spot. Additionally, the Inline code will be base64 encoded.</p>"
msgstr ""
"Funksjonen tilbyr en etterbehandlingsmotor for alle nettstedsressurser (CSS / JavaScript). Den koder CSS og JavaScript, noe som gjør dem uleselige. Den sikrer også perfekt URL-forsøpling, ettersom selv om du endrer plugin-navnet, inneholder de fleste URL-ene fortsatt spor inni. \n"
"                                                                    Dette er også et flott verktøy for å optimalisere nettstedsressurser ved å kombinere, minimere, fjerne kommentarer etc. \n"
"                                                                    Fullt funksjonell og integrerer perfekt sammen med andre SEO/Optimaliseringsplugins.\n"
"                                                                    <p>&nbsp;</p>\n"
"                                                                    <p>Det er 4 typer behandlingsalternativer:\n"
"                                                                    <b>Kombiner</b>: Slå sammen all kode i (vanligvis) 2 filer, en i headeren og en annen i footeren.\n"
"                                                                    <b>Kombiner & Koder inline</b>: Slå sammen all kode i (vanligvis) 2 filer, en i headeren og en annen i footeren. I tillegg vil inline-koden bli base64-kodet og plassert på samme sted.\n"
"                                                                    <b>På stedet</b>: All JavaScript-kode vil bli behandlet og resultatene vil bli plassert på samme sted. Enhver inline-kode vil bli behandlet og lagret i en datainnsamlingskatalog for senere bruk.\n"
"                                                                    <b>På stedet & Koder inline</b>: All kode vil bli behandlet og resultatene vil bli plassert på samme sted. I tillegg vil inline-koden bli base64-kodet.</p>"

#: include/admin-interfaces/security-scan/scan_item_hide_postprocessing.php:63
msgid "<span class=\"dashicons dashicons-no\"></span>Your site assets still contain traceable data within CSS / JavaScript"
msgstr "<span class=\"dashicons dashicons-no\"></span>Nettstedets ressurser inneholder fortsatt sporbar data inni CSS / JavaScript"

#: include/admin-interfaces/security-scan/scan_item_hide_readme_html.php:29 modules/components/rewrite-root-files.php:135 modules/components/rewrite-root-files.php:139
msgid "Block readme.html"
msgstr "Blokker readme.html"

#: include/admin-interfaces/security-scan/scan_item_hide_readme_html.php:32 modules/components/rewrite-root-files.php:140
msgid "A Hypertext Markup Language file with general information about installed WordPress, version, instalation steps, updating, requirements, resources etc."
msgstr "En Hypertext Markup Language-fil med generell informasjon om installert WordPress, versjon, installasjonstrinn, oppdatering, krav, ressurser etc."

#: include/admin-interfaces/security-scan/scan_item_hide_readme_html.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>The readme.html file is still accessible."
msgstr "<span class=\"dashicons dashicons-no\"></span>readme.html-filen er fortsatt tilgjengelig."

#: include/admin-interfaces/security-scan/scan_item_hide_registration.php:29
msgid "User Registration"
msgstr "Brukerregistrering"

#: include/admin-interfaces/security-scan/scan_item_hide_registration.php:32
msgid "Through your site, if the WordPress Membership option is active, anyone can register."
msgstr "Gjennom nettstedet ditt, hvis WordPress-medlemskapsalternativet er aktivt, kan hvem som helst registrere seg."

#: include/admin-interfaces/security-scan/scan_item_hide_registration.php:59
msgid "<span class=\"dashicons dashicons-no\"></span>The Registration should be customised or disabled through Dashboard > Settings."
msgstr "<span class=\"dashicons dashicons-no\"></span>Registreringen bør tilpasses eller deaktiveres gjennom Dashbord > Innstillinger."

#: include/admin-interfaces/security-scan/scan_item_hide_remove_header_link.php:29 modules/components/general-headers.php:88 modules/components/general-headers.php:92
msgid "Remove Link Header"
msgstr "Fjern Link-header"

#: include/admin-interfaces/security-scan/scan_item_hide_remove_header_link.php:32
msgid "Remove Link Header being set as default by WordPress which outputs the site JSON URL."
msgstr "Fjern Link-header som er satt som standard av WordPress som sender ut nettstedets JSON-URL."

#: include/admin-interfaces/security-scan/scan_item_hide_remove_header_link.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>The site pages header still contain the site JSON url."
msgstr "<span class=\"dashicons dashicons-no\"></span>Nettstedets sideheadere inneholder fortsatt nettstedets JSON-URL."

#: include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:29
msgid "Remove Environment Headers"
msgstr "Fjern miljøheadere"

#: include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:32
msgid "Remove the X-Powered-By and Server Headers if set. This type of header information discloses important details regarding your server environment."
msgstr "Fjern X-Powered-By og Server-headere hvis de er satt. Denne typen header-informasjon avslører viktige detaljer om servermiljøet ditt."

#: include/admin-interfaces/security-scan/scan_item_hide_remove_headers.php:69
msgid "<span class=\"dashicons dashicons-no\"></span>Your site headers still contain some valuable pieces of information regarding your environment."
msgstr "<span class=\"dashicons dashicons-no\"></span>Nettstedets headere inneholder fortsatt noen verdifulle informasjonsbiter om miljøet ditt."

#: include/admin-interfaces/security-scan/scan_item_hide_remove_html_comments.php:29 modules/components/general-css-combine.php:154 modules/components/general-css-combine.php:158 modules/components/general-html.php:110 modules/components/general-html.php:114 modules/components/general-js-combine.php:166 modules/components/general-js-combine.php:170
msgid "Remove Comments"
msgstr "Fjern kommentarer"

#: include/admin-interfaces/security-scan/scan_item_hide_remove_html_comments.php:32 modules/components/general-html.php:115
msgid "The HTML source code usually contain many comment lines, however there is no use for that, unless debugging. Remove all HTML Comments, which usually specify Plugins Name and Version. Any Internet Explorer conditional tags are preserved."
msgstr "HTML-kildekoden inneholder vanligvis mange kommentarlinjer, men det er ingen nytte av det, med mindre det er for feilsøking. Fjern alle HTML-kommentarer, som vanligvis spesifiserer plugin-navn og versjon. Eventuelle Internet Explorer-betingede tagger bevares."

#: include/admin-interfaces/security-scan/scan_item_hide_remove_html_comments.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>The site pages still contain HTML comments which may provide essential pieces of information regarding the active plugins and themes."
msgstr "<span class=\"dashicons dashicons-no\"></span>Nettstedets sider inneholder fortsatt HTML-kommentarer som kan gi essensielle informasjonsbiter om de aktive pluginsene og temaene."

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:30
msgid "Replacements"
msgstr "Erstatninger"

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:33
msgid ""
"The module implements a post-processing engine, which allows arbitrary words to be replaced with custom ones. This works for all site data as HTML, Css, JavaScript assets.\n"
"                                                                This is the perfect tool to white-label any plugins or active code on a site, by replacing the specific words (classes, tags, JavaScript variables etc).\n"
"                                                                Examples can be found at <a href='https://wp-hide.com/how-to-easily-hide-elementor-page-builder/' target='_blank'>How to white label Elementor</a> also <a href='https://wp-hide.com/hide-your-avada-theme-avada-builder-and-fusion-core/' target='_blank'>HowHide your Avada Theme, Avada Builder and Fusion core</a> this makes the plugins totally unrecognizable for anonymous users.\n"
"                                                                <p>&nbsp;</p>\n"
"                                                                <p>This feature integrates perfectly with any site environment, regardles of the used plugins and themes. Changing any fingerprint does not break the site layout or disable any existing functionality.</p>"
msgstr ""
"Modulen implementerer en etterbehandlingsmotor, som tillater vilkårlige ord å bli erstattet med egendefinerte. Dette fungerer for all nettstedsdata som HTML, CSS, JavaScript-ressurser.\n"
"                                                                Dette er det perfekte verktøyet for å hvitmerke plugins eller aktiv kode på et nettsted, ved å erstatte de spesifikke ordene (klasser, tagger, JavaScript-variabler etc).\n"
"                                                                Eksempler finnes på <a href='https://wp-hide.com/how-to-easily-hide-elementor-page-builder/' target='_blank'>How to white label Elementor</a> også <a href='https://wp-hide.com/hide-your-avada-theme-avada-builder-and-fusion-core/' target='_blank'>HowHide your Avada Theme, Avada Builder and Fusion core</a> dette gjør plugins helt ugjenkjennelige for anonyme brukere.\n"
"                                                                <p>&nbsp;</p>\n"
"                                                                <p>Denne funksjonen integrerer perfekt med ethvert nettstedmiljø, uavhengig av brukte plugins og temaer. Endring av ethvert fingeravtrykk ødelegger ikke nettstedets layout eller deaktiverer eksisterende funksjonalitet.</p>"

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:131
msgid "<span class=\"dashicons dashicons-no\"></span>Your site assets still contain traceable data within HTML / CSS / JavaScript. Those can be removed using the Replacements functionality."
msgstr "<span class=\"dashicons dashicons-no\"></span>Nettstedets ressurser inneholder fortsatt sporbar data inni HTML / CSS / JavaScript. Disse kan fjernes ved hjelp av Erstatningsfunksjonaliteten."

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:138
msgid "Add replacements for <code>"
msgstr "Legg til erstatninger for <code>"

#: include/admin-interfaces/security-scan/scan_item_hide_replacements.php:155
msgid "<span class=\"dashicons dashicons-yes\"></span>There are no obvious fingerprints."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Det er ingen åpenbare fingeravtrykk."

#: include/admin-interfaces/security-scan/scan_item_hide_robots.php:29
msgid "Process robots.txt"
msgstr "Behandle robots.txt"

#: include/admin-interfaces/security-scan/scan_item_hide_robots.php:32
msgid ""
"The robots.txt file plays a major role in search engine ranking. It blocks search engine bots and helps index and crawl important parts of your site.\n"
"                                                                <br />As default the robots.txt also includes an allow clause to admin URL and admin-ajax.php url. Once customized those areas, the new slugs might not want to be show to anyone. Turn this option to Yes removed any reference to new wp-admin and admin-ajax.php."
msgstr ""
"robots.txt-filen spiller en stor rolle i søkemotorrangering. Den blokkerer søkemotorboter og hjelper til med å indeksere og crawl viktige deler av nettstedet ditt.\n"
"                                                                <br />Som standard inkluderer robots.txt også en allow-klausul for admin-URL og admin-ajax.php-URL. Når disse områdene er tilpasset, vil du kanskje ikke vise de nye slug-ene til noen. Sett dette alternativet til Ja for å fjerne alle referanser til ny wp-admin og admin-ajax.php."

#: include/admin-interfaces/security-scan/scan_item_hide_robots.php:55
msgid "<span class=\"dashicons dashicons-no\"></span>The robots.txt should be processed to ensure none of the default URLs is still used."
msgstr "<span class=\"dashicons dashicons-no\"></span>robots.txt bør behandles for å sikre at ingen av standard-URL-ene fortsatt brukes."

#: include/admin-interfaces/security-scan/scan_item_hide_wlwmanifest.php:29 modules/components/general-meta.php:233 modules/components/general-meta.php:237
msgid "Remove wlwmanifest Meta"
msgstr "Fjern wlwmanifest-meta"

#: include/admin-interfaces/security-scan/scan_item_hide_wlwmanifest.php:32
msgid "The wlwmanifest link is actually used by Windows Live Writer. If you don't te application, this is just unnecessary code."
msgstr "wlwmanifest-lenken brukes faktisk av Windows Live Writer. Hvis du ikke bruker applikasjonen, er dette bare unødvendig kode."

#: include/admin-interfaces/security-scan/scan_item_hide_wlwmanifest.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>Unless using the Windows Live Writer, the file have no usage so should be disabled."
msgstr "<span class=\"dashicons dashicons-no\"></span>Med mindre du bruker Windows Live Writer, har filen ingen bruk og bør deaktiveres."

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_generator.php:29 modules/components/general-meta.php:157 modules/components/general-meta.php:161
msgid "Remove WordPress Generator Meta"
msgstr "Fjern WordPress-generator-meta"

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_generator.php:32 modules/components/general-meta.php:158 modules/components/general-meta.php:162
msgid "Remove the autogenerated meta generator tag within head (WordPress Version)."
msgstr "Fjern den autogenererte meta generator-taggen innenfor head (WordPress-versjon)."

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_generator.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>The WordPress Generator is still visible through the HTML code."
msgstr "<span class=\"dashicons dashicons-no\"></span>WordPress-generatoren er fortsatt synlig gjennom HTML-koden."

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:29
msgid "Change WordPress TagLine"
msgstr "Endre WordPress-tagline"

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:32
msgid "The WordPress tagline is a short description of your website.  The WordPress tagline can be modified by accessing the Dasboard > Settings > General"
msgstr "WordPress-taglinen er en kort beskrivelse av nettstedet ditt. WordPress-taglinen kan endres ved å gå til Dashbord > Innstillinger > Generelt"

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:47
msgid "Just another WordPress site"
msgstr "Bare et annet WordPress-nettsted"

#: include/admin-interfaces/security-scan/scan_item_hide_wordpress_tagline.php:54
msgid "<span class=\"dashicons dashicons-no\"></span>The tagline still uses the default WordPress sample, and should be customised."
msgstr "<span class=\"dashicons dashicons-no\"></span>Taglinen bruker fortsatt standard WordPress-eksempelet, og bør tilpasses."

#: include/admin-interfaces/security-scan/scan_item_hide_xml_rpc.php:29
msgid "XML-RPC"
msgstr "XML-RPC"

#: include/admin-interfaces/security-scan/scan_item_hide_xml_rpc.php:32
msgid "XML-RPC is a remote procedure call (RPC) protocol which uses XML to encode its calls and HTTP as a transport mechanism. This service allow other applications to talk to your WordPress site."
msgstr "XML-RPC er en ekstern prosedyrekall (RPC)-protokoll som bruker XML for å kode sine kall og HTTP som en transportmekanisme. Denne tjenesten tillater andre applikasjoner å kommunisere med WordPress-nettstedet ditt."

#: include/admin-interfaces/security-scan/scan_item_hide_xml_rpc.php:56
msgid "<span class=\"dashicons dashicons-no\"></span>The XML-RPC module has not been customised."
msgstr "<span class=\"dashicons dashicons-no\"></span>XML-RPC-modulen er ikke tilpasset."

#: include/admin-interfaces/security-scan/scan_item_hide_xml_rpc.php:67
msgid "<span class=\"dashicons dashicons-yes\"></span>The XML-RPC appears properly configured."
msgstr "<span class=\"dashicons dashicons-yes\"></span>XML-RPC ser ut til å være riktig konfigurert."

#: include/admin-interfaces/security-scan/scan_item_keys_and_salts.php:32
msgid ""
"WordPress security authentication or secret key or SALT keys, are the encrypted code that protects your login information. \n"
"                                                                Salt keys are cryptographic elements used to 'hash' data in order to secure it. In fact, most serious platforms and systems use similar mechanisms to protect sensitive data."
msgstr ""
"WordPress-sikkerhetsautentisering eller hemmelig nøkkel eller SALT-nøkler, er den krypterte koden som beskytter din påloggingsinformasjon. \n"
"                                                                Salt-nøkler er kryptografiske elementer brukt til å 'hashe' data for å sikre den. Faktisk bruker de fleste seriøse plattformer og systemer lignende mekanismer for å beskytte sensitive data."

#: include/admin-interfaces/security-scan/scan_item_keys_and_salts.php:69
msgid "<span class=\"dashicons dashicons-no\"></span>The Authentication unique keys and salts are empty or invalid."
msgstr "<span class=\"dashicons dashicons-no\"></span>Autentiserings-unike nøkler og salter er tomme eller ugyldige."

#: include/admin-interfaces/security-scan/scan_item_keys_and_salts.php:79
msgid "<span class=\"dashicons dashicons-yes\"></span>The Authentication unique keys and salts are correctly set-up."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Autentiserings-unike nøkler og salter er riktig satt opp."

#: include/admin-interfaces/security-scan/scan_item_mysql_version.php:32
msgid "Using a higher MySQL version ensures better capability for your system. Older versions are often exploitable making the system unstable and predisposing to security breaches."
msgstr "Bruk av en høyere MySQL-versjon sikrer bedre kapabilitet for systemet ditt. Eldre versjoner er ofte utnyttbare og gjør systemet ustabilt og utsatt for sikkerhetsbrudd."

#: include/admin-interfaces/security-scan/scan_item_mysql_version.php:47 include/admin-interfaces/security-scan/scan_item_php_version.php:47 include/admin-interfaces/security-scan/scan_item_wp_version.php:50 include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:49
msgid "Using Version: "
msgstr "Bruker versjon: "

#: include/admin-interfaces/security-scan/scan_item_mysql_version.php:52 include/admin-interfaces/security-scan/scan_item_php_version.php:53
msgid "<span class=\"dashicons dashicons-yes\"></span> You are using at least the minimum recommended PHP version."
msgstr "<span class=\"dashicons dashicons-yes\"></span> Du bruker minst den anbefalte minimumsversjonen av PHP."

#: include/admin-interfaces/security-scan/scan_item_mysql_version.php:57 include/admin-interfaces/security-scan/scan_item_php_version.php:58
msgid "<span class=\"dashicons dashicons-no\"></span> You are using an older PHP version that the minimum recommended."
msgstr "<span class=\"dashicons dashicons-no\"></span> Du bruker en eldre PHP-versjon enn den anbefalte minimumsversjonen."

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:32
msgid ""
"Old WordPress plugins can do damage to your website. Vulnerabilities are found within plugins all the time. Unmaintained code drastically increase the risk, as there are no patches for known issues. \n"
"                                                                Inconsistent updates can lead to serious security issues and compatibility problems, and land you in technical debt.\n"
"                                                                This will check for plugins with more than a year since their last update."
msgstr ""
"Gamle WordPress-plugins kan skade nettstedet ditt. Sårbarheter blir funnet i plugins hele tiden. Uvedlikeholdt kode øker risikoen dramatisk, ettersom det ikke finnes patcher for kjente problemer. \n"
"                                                                Inkonsistente oppdateringer kan føre til alvorlige sikkerhetsproblemer og kompatibilitetsproblemer, og sette deg i teknisk gjeld.\n"
"                                                                Dette vil sjekke etter plugins med mer enn et år siden siste oppdatering."

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:81
msgid "Found old plugins: "
msgstr "Fant gamle plugins: "

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:86
msgid "<span class=\"dashicons dashicons-no\"></span>The following plugins are very old and appear unmaintained:"
msgstr "<span class=\"dashicons dashicons-no\"></span>Følgende plugins er svært gamle og ser ut til å være uvedlikeholdte:"

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:95
msgid " Last updated on "
msgstr " Sist oppdatert "

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:101
msgid "<br /><p class=\"description\">We strongly suggest finding replacements for the above plugins and remove from your site.</p>"
msgstr "<br /><p class=\"description\">Vi anbefaler på det sterkeste å finne erstatninger for pluginsene ovenfor og fjerne dem fra nettstedet ditt.</p>"

#: include/admin-interfaces/security-scan/scan_item_old_plugins.php:112
msgid "<span class=\"dashicons dashicons-yes\"></span>There are no Old Plugins."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Det er ingen gamle plugins."

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:32
msgid ""
"Keeping your plugins up to date is important for the stability and security of your WordPress site. It also lets you take advantage of any new features the plugin's developers have added.\n"
"                                                                A key concept of updating WordPress core, themes, and plugins is to protect your site from the possible vulnerabilities that allow a hacker to compromise your site. "
msgstr ""
"Å holde plugins oppdatert er viktig for stabiliteten og sikkerheten til WordPress-nettstedet ditt. Det lar deg også dra nytte av nye funksjoner plugin-utviklerne har lagt til.\n"
"                                                                Et nøkkelkonsept med å oppdatere WordPress-kjernen, temaer og plugins er å beskytte nettstedet ditt mot mulige sårbarheter som tillater en hacker å kompromittere nettstedet ditt."

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:55
msgid "Found outdated plugins: "
msgstr "Fant utdaterte plugins: "

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:60 include/admin-interfaces/security-scan/scan_item_outdated_themes.php:60
msgid "<span class=\"dashicons dashicons-no\"></span>The following plugins are found outdated on your site:"
msgstr "<span class=\"dashicons dashicons-no\"></span>Følgende plugins er funnet utdaterte på nettstedet ditt:"

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:75 include/admin-interfaces/security-scan/scan_item_outdated_themes.php:70
msgid " Upgrade from "
msgstr " Oppgrader fra "

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:75 include/admin-interfaces/security-scan/scan_item_outdated_themes.php:70
msgid " to "
msgstr " til "

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:81
msgid "<br /><p class=\"description\">The inactive plugins require updating as well, as may contain harmful vulnerabilities, exploaitable even if the code is not active.</p>"
msgstr "<br /><p class=\"description\">De inaktive pluginsene krever også oppdatering, ettersom de kan inneholde skadelige sårbarheter, utnyttbare selv om koden ikke er aktiv.</p>"

#: include/admin-interfaces/security-scan/scan_item_outdated_plugins.php:92
msgid "<span class=\"dashicons dashicons-yes\"></span>All plugins are Up to Date."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Alle plugins er oppdaterte."

#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:32
msgid ""
"The biggest reason to keep your WordPress website up to date is Security. When you do not update your WordPress themes, you create a security risk and expose your site to existing vulnerabilities and imminent attacks. \n"
"                                                        The WordPress developers are constantly fixing security breaches or improving security."
msgstr ""
"Den største grunnen til å holde WordPress-nettstedet oppdatert er sikkerhet. Når du ikke oppdaterer WordPress-temaene dine, skaper du en sikkerhetsrisiko og utsetter nettstedet for eksisterende sårbarheter og overhengende angrep. \n"
"                                                        WordPress-utviklere kontinuerlig fikser sikkerhetsbrudd eller forbedrer sikkerheten."

#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:55
msgid "Found outdated themes: "
msgstr "Fant utdaterte temaer: "

#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:76
msgid "<br /><p class=\"description\">The  inactive themes require updating as well, as may contain harmful vulnerabilities, exploaitable even if the code is not active.</p>"
msgstr "<br /><p class=\"description\">De inaktive temaene krever også oppdatering, ettersom de kan inneholde skadelige sårbarheter, utnyttbare selv om koden ikke er aktiv.</p>"

#: include/admin-interfaces/security-scan/scan_item_outdated_themes.php:87
msgid "<span class=\"dashicons dashicons-yes\"></span>All themes are Up to Date."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Alle temaer er oppdaterte."

#: include/admin-interfaces/security-scan/scan_item_php_allow_url_include.php:32
msgid ""
"The allow_url_include allows a developer to include a remote file using a URL rather than a local file path. This technique is used to reduce the load on the server. \n"
"                                                                There are many servers with PHP configuration directive allow_url_include as enabled. When this setting is enabled, the server’s directory allows data retrieval from remote locations."
msgstr ""
"allow_url_include tillater en utvikler å inkludere en ekstern fil ved å bruke en URL i stedet for en lokal filsti. Denne teknikken brukes for å redusere belastningen på serveren. \n"
"                                                                Det er mange servere med PHP-konfigurasjonsdirektiv allow_url_include aktivert. Når denne innstillingen er aktivert, tillater serverens katalog datahenting fra eksterne steder."

#: include/admin-interfaces/security-scan/scan_item_php_allow_url_include.php:49
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The allow_url_include is ON. \n"
"                                                                        To fix this security issue, change the php.ini:\n"
"\n"
"                                                                        <br /><code>allow_url_include = \"off\"</code>\n"
"\n"
"                                                                        <br />or within .htaccess:\n"
"\n"
"                                                                        <br /><code>php_flag allow_url_include off</code>\n"
"                                                                        <br />or within wp-config.php:\n"
"                                                                        <br /><code>ini_set(\"allow_url_include\", \"0\");</code>."
msgstr ""
"<span class=\"dashicons dashicons-no\"></span>allow_url_include er PÅ. \n"
"                                                                        For å fikse dette sikkerhetsproblemet, endre php.ini:\n"
"\n"
"                                                                        <br /><code>allow_url_include = \"off\"</code>\n"
"\n"
"                                                                        <br />eller innenfor .htaccess:\n"
"\n"
"                                                                        <br /><code>php_flag allow_url_include off</code>\n"
"                                                                        <br />eller innenfor wp-config.php:\n"
"                                                                        <br /><code>ini_set(\"allow_url_include\", \"0\");</code>."

#: include/admin-interfaces/security-scan/scan_item_php_allow_url_include.php:67
msgid "<span class=\"dashicons dashicons-yes\"></span>The allow_url_include is Off."
msgstr "<span class=\"dashicons dashicons-yes\"></span>allow_url_include er AV."

#: include/admin-interfaces/security-scan/scan_item_php_display_errors.php:32
msgid "The display_error setting in PHP is used to determine whether errors should be printed to the screen or not."
msgstr "display_error-innstillingen i PHP brukes for å avgjøre om feil skal skrives til skjermen eller ikke."

#: include/admin-interfaces/security-scan/scan_item_php_display_errors.php:48
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The display_errors is ON. \n"
"                                                                        <br />To fix this security issue, change the php.ini:\n"
"                                                                        <br /><code>display_errors = \"off\"</code>\n"
"                                                                        <br />or within .htaccess:\n"
"                                                                        <br /><code>php_flag display_errors off</code>\n"
"                                                                        <br />or within wp-config.php:\n"
"                                                                        <br /><code>ini_set(\"display_errors\", \"0\");</code>."
msgstr ""
"<span class=\"dashicons dashicons-no\"></span>display_errors er PÅ. \n"
"                                                                        <br />For å fikse dette sikkerhetsproblemet, endre php.ini:\n"
"                                                                        <br /><code>display_errors = \"off\"</code>\n"
"                                                                        <br />eller innenfor .htaccess:\n"
"                                                                        <br /><code>php_flag display_errors off</code>\n"
"                                                                        <br />eller innenfor wp-config.php:\n"
"                                                                        <br /><code>ini_set(\"display_errors\", \"0\");</code>."

#: include/admin-interfaces/security-scan/scan_item_php_display_errors.php:63
msgid "<span class=\"dashicons dashicons-yes\"></span>The display_errors is Off."
msgstr "<span class=\"dashicons dashicons-yes\"></span>display_errors er AV."

#: include/admin-interfaces/security-scan/scan_item_php_expose.php:32
msgid "When the expose_php directive is enabled, PHP includes critical pieces of information within the HTTP response X-Powered-By header when a page is requested."
msgstr "Når expose_php-direktivet er aktivert, inkluderer PHP kritiske informasjonsbiter i HTTP-respons X-Powered-By-headeren når en side forespørres."

#: include/admin-interfaces/security-scan/scan_item_php_expose.php:48
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The expose_php is ON. \n"
"                                                                        To fix this security issue, change the php.ini:\n"
"\n"
"                                                                        <br /><code>expose_php = \"off\"</code>\n"
"\n"
"                                                                        <br />or within .htaccess:\n"
"\n"
"                                                                        <br /><code>php_flag expose_php off</code>."
msgstr ""
"<span class=\"dashicons dashicons-no\"></span>expose_php er PÅ. \n"
"                                                                        For å fikse dette sikkerhetsproblemet, endre php.ini:\n"
"\n"
"                                                                        <br /><code>expose_php = \"off\"</code>\n"
"\n"
"                                                                        <br />eller innenfor .htaccess:\n"
"\n"
"                                                                        <br /><code>php_flag expose_php off</code>."

#: include/admin-interfaces/security-scan/scan_item_php_expose.php:64
msgid "<span class=\"dashicons dashicons-yes\"></span>The expose_php is Off."
msgstr "<span class=\"dashicons dashicons-yes\"></span>expose_php er AV."

#: include/admin-interfaces/security-scan/scan_item_php_register_globals.php:32
msgid "When register_globals is enabled, PHP will automatically create variables in the global scope for any value passed in GET, POST or COOKIE. This, combined with the use of variables without initialization, has led to numerous security vulnerabilities."
msgstr "Når register_globals er aktivert, vil PHP automatisk opprette variabler i det globale scope for enhver verdi sendt i GET, POST eller COOKIE. Dette, kombinert med bruk av variabler uten initialisering, har ført til mange sikkerhetssårbarheter."

#: include/admin-interfaces/security-scan/scan_item_php_register_globals.php:48
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The register_globals is ON. \n"
"                                                                        To fix this security issue, change the php.ini:\n"
"\n"
"                                                                        <br /><code>register_globals = \"off\"</code>\n"
"\n"
"                                                                        <br />or within .htaccess:\n"
"\n"
"                                                                        <br /><code>php_flag register_globals off</code>."
msgstr ""
"<span class=\"dashicons dashicons-no\"></span>register_globals er PÅ. \n"
"                                                                        For å fikse dette sikkerhetsproblemet, endre php.ini:\n"
"\n"
"                                                                        <br /><code>register_globals = \"off\"</code>\n"
"\n"
"                                                                        <br />eller innenfor .htaccess:\n"
"\n"
"                                                                        <br /><code>php_flag register_globals off</code>."

#: include/admin-interfaces/security-scan/scan_item_php_register_globals.php:64
msgid "<span class=\"dashicons dashicons-yes\"></span>The register_globals is Off."
msgstr "<span class=\"dashicons dashicons-yes\"></span>register_globals er AV."

#: include/admin-interfaces/security-scan/scan_item_php_safe_mode.php:32
msgid "The PHP safe mode is an attempt to solve the shared-server security problem. It is architecturally incorrect to try to solve this problem at the PHP level, but since the alternatives at the web server and OS levels aren't very realistic, many people, especially ISP's, use safe mode for now."
msgstr "PHP safe mode er et forsøk på å løse delt server-sikkerhetsproblemet. Det er arkitektonisk feil å prøve å løse dette problemet på PHP-nivå, men siden alternativene på web-server og OS-nivåer ikke er veldig realistiske, bruker mange, spesielt ISP'er, safe mode for øyeblikket."

#: include/admin-interfaces/security-scan/scan_item_php_safe_mode.php:48
msgid ""
"<span class=\"dashicons dashicons-no\"></span>The register_globals is ON. \n"
"                                                                        To fix this security issue, change the php.ini:\n"
"\n"
"                                                                        <br /><code>safe_mode = \"off\"</code>\n"
"\n"
"                                                                        <br />or within .htaccess:\n"
"\n"
"                                                                        <br /><code>php_flag safe_mode off</code>."
msgstr ""
"<span class=\"dashicons dashicons-no\"></span>register_globals er PÅ. \n"
"                                                                        For å fikse dette sikkerhetsproblemet, endre php.ini:\n"
"\n"
"                                                                        <br /><code>safe_mode = \"off\"</code>\n"
"\n"
"                                                                        <br />eller innenfor .htaccess:\n"
"\n"
"                                                                        <br /><code>php_flag safe_mode off</code>."

#: include/admin-interfaces/security-scan/scan_item_php_safe_mode.php:64
msgid "<span class=\"dashicons dashicons-yes\"></span>The safe_mode is Off."
msgstr "<span class=\"dashicons dashicons-yes\"></span>safe_mode er AV."

#: include/admin-interfaces/security-scan/scan_item_php_version.php:29
msgid "PHP Version"
msgstr "PHP-versjon"

#: include/admin-interfaces/security-scan/scan_item_php_version.php:32
msgid "Using the latest PHP version ensures the longevity of security updates. While older versions of PHP offer security updates for a time past “end of life,” the most secure option is the version that is actively maintained."
msgstr "Bruk av den nyeste PHP-versjonen sikrer lang levetid for sikkerhetsoppdateringer. Mens eldre versjoner av PHP tilbyr sikkerhetsoppdateringer en tid etter \"end of life\", er den sikreste muligheten versjonen som aktivt vedlikeholdes."

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:29
msgid "Dangerous Files"
msgstr "Farlige filer"

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:32
msgid "This security test checks for any dangerous files on your WordPress root. You should avoid keeping any unnecessary files on domain root."
msgstr "Denne sikkerhetstesten sjekker etter farlige filer på WordPress-roten. Du bør unngå å ha unødvendige filer på domenerot."

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:110
msgid "<span class=\"dashicons dashicons-no\"></span> Your WordPress root still includes dangerous files which may contain valuable pieces of information regarding your environment."
msgstr "<span class=\"dashicons dashicons-no\"></span> WordPress-roten din inkluderer fortsatt farlige filer som kan inneholde verdifulle informasjonsbiter om miljøet ditt."

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:111
msgid "Consider re-locating the followng files from your site root:"
msgstr "Vurder å flytte følgende filer fra nettstedets rot:"

#: include/admin-interfaces/security-scan/scan_item_unwanted_files.php:132
msgid "<span class=\"dashicons dashicons-yes\"></span> Your WordPress root still includes dangerous files which may contain valuable pieces of information regarding your environment."
msgstr "<span class=\"dashicons dashicons-yes\"></span> WordPress-roten din inkluderer fortsatt farlige filer som kan inneholde verdifulle informasjonsbiter om miljøet ditt."

#: include/admin-interfaces/security-scan/scan_item_use_admin_user.php:32
msgid ""
"When setting up a new WordPress site, many users create the default administrator account using the username `admin`.\n"
"                                                                Considering entering the dashboard requires a username and a password, using the login `admin` makes the hackers have an easier time trying to brute force in. "
msgstr ""
"Når du setter opp et nytt WordPress-nettsted, oppretter mange brukere standard administrator-konto med brukernavnet `admin`.\n"
"                                                                Med tanke på at tilgang til dashbordet krever et brukernavn og et passord, gjør bruk av pålogging `admin` at hackere har enklere for å forsøke brute force."

#: include/admin-interfaces/security-scan/scan_item_use_admin_user.php:51
msgid "Found users: "
msgstr "Fant brukere: "

#: include/admin-interfaces/security-scan/scan_item_use_admin_user.php:56
msgid "<span class=\"dashicons dashicons-no\"></span>The admin or administrator usernames were found on your system!"
msgstr "<span class=\"dashicons dashicons-no\"></span>Admin- eller administrator-brukernavn ble funnet på systemet ditt!"

#: include/admin-interfaces/security-scan/scan_item_use_admin_user.php:66
msgid "<span class=\"dashicons dashicons-yes\"></span>There are no admin or administrator usernames."
msgstr "<span class=\"dashicons dashicons-yes\"></span>Det er ingen admin- eller administrator-brukernavn."

#: include/admin-interfaces/security-scan/scan_item_wp_debug.php:51
msgid "<span class=\"dashicons dashicons-no\"></span>The WP_DEBUG is active. Check your site wp-config.php and comment the constant declaration."
msgstr "<span class=\"dashicons dashicons-no\"></span>WP_DEBUG er aktiv. Sjekk din wp-config.php og kommenter ut konstantdeklarasjonen."

#: include/admin-interfaces/security-scan/scan_item_wp_debug.php:60
msgid "<span class=\"dashicons dashicons-yes\"></span>The WP_DEBUG is disabled."
msgstr "<span class=\"dashicons dashicons-yes\"></span>WP_DEBUG er deaktivert."

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:32
msgid ""
"WordPress is a permanent evolving software with regularly released security fixes. The core updates ensure the safety and efficiency of the WordPress system.\n"
"                                                            WordPress updates often include security fixes. It’s an ongoing battle since hackers find vulnerabilities all the time. It’s important to keep WordPress up to date to get the latest protections from new types of attacks."
msgstr ""
"WordPress er en permanent utviklende programvare med regelmessig utgivelse av sikkerhetsoppdateringer. Kjerneoppdateringene sikrer sikkerheten og effektiviteten til WordPress-systemet.\n"
"                                                            WordPress-oppdateringer inkluderer ofte sikkerhetsoppdateringer. Det er en pågående kamp siden hackere finner sårbarheter hele tiden. Det er viktig å holde WordPress oppdatert for å få de nyeste beskyttelsene mot nye typer angrep."

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:61 include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:60
msgid "<span class=\"dashicons dashicons-no\"></span> Unable to connect with WordPress API. Try again later."
msgstr "<span class=\"dashicons dashicons-no\"></span> Kan ikke koble til WordPress API. Prøv igjen senere."

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:83
msgid "<span class=\"dashicons dashicons-yes\"></span> You are up to date with the latest Wordpress version."
msgstr "<span class=\"dashicons dashicons-yes\"></span> Du er oppdatert med den nyeste WordPress-versjonen."

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:88
msgid "<span class=\"dashicons dashicons-no\"></span> An updated version "
msgstr "<span class=\"dashicons dashicons-no\"></span> En oppdatert versjon "

#: include/admin-interfaces/security-scan/scan_item_wp_version.php:88
msgid " of WordPress is available."
msgstr " av WordPress er tilgjengelig."

#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:32
msgid "Over time, security breaches are found within the WordPress core. This option checks whenever the WordPress version deployed on your site is succeptible to a known vulenrability. "
msgstr "Over tid blir sikkerhetsbrudd funnet i WordPress-kjernen. Dette alternativet sjekker om WordPress-versjonen deployert på nettstedet ditt er mottakelig for en kjent sårbarhet."

#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:81
msgid "<span class=\"dashicons dashicons-yes\"></span> The current Wordpress version stability tag is "
msgstr "<span class=\"dashicons dashicons-yes\"></span> Den nåværende WordPress-versjonens stabilitetsmerke er "

#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:88 include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:91
msgid "<span class=\"dashicons dashicons-no\"></span>  The current Wordpress version stability tag is "
msgstr "<span class=\"dashicons dashicons-no\"></span> Den nåværende WordPress-versjonens stabilitetsmerke er "

#: include/admin-interfaces/security-scan/scan_item_wp_version_stability.php:91
msgid ". This is critical and require urgent WordPress update."
msgstr ". Dette er kritisk og krever en presserende WordPress-oppdatering."

#: include/class.custom-admin-bar.php:218
msgid "The menu ID should not be empty."
msgstr "Meny-ID skal ikke være tom."

#: include/class.custom-admin-bar.php:511
msgid "Skip to toolbar"
msgstr "Hopp til verktøylinje"

#: include/class.custom-admin-bar.php:513
msgid "Toolbar"
msgstr "Verktøylinje"

#: include/class.custom-admin-bar.php:519
msgid "Log Out"
msgstr "Logg ut"

#: include/class.environment.php:182
msgid "<b>WP Hide</b> - Unable to create environment static file. The system returned the following error: "
msgstr "<b>WP Hide</b> - Kan ikke opprette statisk miljøfil. Systemet returnerte følgende feil: "

#: include/class.environment.php:193
msgid "Unable to create environment data at "
msgstr "Kan ikke opprette miljødata på "

#: include/class.environment.php:193
msgid "Is file writable"
msgstr "Er filen skrivbar"

#: include/class.environment.php:193
msgid "Check with Setup menu item or contact server administrator."
msgstr "Sjekk med Oppsett-menyvalg eller kontakt serveradministrator."

#: include/class.environment.php:200
msgid "will not work correctly, so where turned off."
msgstr "vil ikke fungere korrekt, så de ble slått av."

#: include/class.plugin-updater.php:136
msgid "An error occour when try to identify the pluguin."
msgstr "En feil oppstod under forsøk på å identifisere pluginen."

#: include/class.plugin-updater.php:136 include/class.plugin-updater.php:156
msgid "Try again"
msgstr "Prøv igjen"

#: include/class.plugin-updater.php:156
msgid "An Unexpected HTTP Error occurred during the API request."
msgstr "En uventet HTTP-feil oppstod under API-forespørselen."

#: include/functions.class.php:258
msgid "W3 Total Cache Plugin is active, make sure you clear the cache for new changes to apply"
msgstr "W3 Total Cache-plugin er aktiv, sørg for å tømme hurtiglageret for at nye endringer skal tre i kraft"

#: include/functions.class.php:262
msgid "WP Super Cache Plugin is active, make sure you clear the cache for new changes to apply"
msgstr "WP Super Cache-plugin er aktiv, sørg for å tømme hurtiglageret for at nye endringer skal tre i kraft"

#: include/functions.class.php:267
msgid "WP Fastest Cache Plugin is active, make sure you clear the cache for new changes to apply"
msgstr "WP Fastest Cache-plugin er aktiv, sørg for å tømme hurtiglageret for at nye endringer skal tre i kraft"

#: include/functions.class.php:2474
msgid "The plugin options have been reset successfully."
msgstr "Plugin-alternativene har blitt tilbakestilt."

#: include/functions.class.php:2481
msgid "Ensure the .htaccess file does not contain any WP-Hide rewrite lines. The plugin already attempts to clear the lines, if the operation fails, they are required to be removed manually. "
msgstr "Forsikre deg om at .htaccess-filen ikke inneholder noen WP-Hide-omskrivingslinjer. Pluginen prøver allerede å fjerne linjene, hvis operasjonen mislykkes, må de fjernes manuelt."

#: include/functions.class.php:2488
msgid "Ensure the web.config file does not contain any WP-Hide rewrite lines. The plugin already attempts to clear the lines, if the operation fails, they are required to be removed manually. "
msgstr "Forsikre deg om at web.config-filen ikke inneholder noen WP-Hide-omskrivingslinjer. Pluginen prøver allerede å fjerne linjene, hvis operasjonen mislykkes, må de fjernes manuelt."

#: include/functions.class.php:2499
msgid "Your site use WPEngine! You need to get in touch with live support and ask to remove the custom Nginx rewrite code from your account."
msgstr "Nettstedet ditt bruker WPEngine! Du må ta kontakt med kundestøtte og be om å fjerne den egendefinerte Nginx-omskrivingskoden fra kontoen din."

#: include/functions.class.php:2505
msgid "Your site use Kinsta! You need to get in touch with live support and ask to remove the custom Nginx rewrite code from your account."
msgstr "Nettstedet ditt bruker Kinsta! Du må ta kontakt med kundestøtte og be om å fjerne den egendefinerte Nginx-omskrivingskoden fra kontoen din."

#: include/functions.class.php:2512 include/functions.class.php:2600
msgid "Check with your Nginx config file located usually at"
msgstr "Sjekk med din Nginx-konfigurasjonsfil som vanligvis ligger på"

#: include/functions.class.php:2512
msgid "and remove any existing rewrite rules within"
msgstr "og fjern alle eksisterende omskrivingsregler innenfor"

#: include/functions.class.php:2513 include/functions.class.php:2601
msgid "If successfully compiled, restart the Nginx service."
msgstr "Hvis den kompileres, restart Nginx-tjenesten."

#: include/functions.class.php:2523 include/functions.class.php:2611
msgid "Continue to your Site"
msgstr "Fortsett til nettstedet ditt"

#: include/functions.class.php:2561
msgid "Headers Recovery"
msgstr "Headers-gjenoppretting"

#: include/functions.class.php:2562
msgid "The plugin Headers options have been disabled successfully."
msgstr "Plugin Headers-alternativene har blitt deaktivert."

#: include/functions.class.php:2569
msgid "Ensure the .htaccess file does not contain any rewrite Header lines. The plugin already attempted to clear the data. If the operation fails, manual removal is required."
msgstr "Forsikre deg om at .htaccess-filen ikke inneholder noen omskrivings-Header-linjer. Pluginen har allerede forsøkt å fjerne dataene. Hvis operasjonen mislykkes, kreves manuell fjerning."

#: include/functions.class.php:2576
msgid "Ensure the web.config file does not contain any rewrite Header lines. The plugin already attempted to clear the data. If the operation fails, manual removal is required."
msgstr "Forsikre deg om at web.config-filen ikke inneholder noen omskrivings-Header-linjer. Pluginen har allerede forsøkt å fjerne dataene. Hvis operasjonen mislykkes, kreves manuell fjerning."

#: include/functions.class.php:2587
msgid "Your site use WPEngine! You need to get in touch with live support and ask to remove the custom Nginx Header rewrite code from your account."
msgstr "Nettstedet ditt bruker WPEngine! Du må ta kontakt med kundestøtte og be om å fjerne den egendefinerte Nginx Header-omskrivingskoden fra kontoen din."

#: include/functions.class.php:2593
msgid "Your site use Kinsta! You need to get in touch with live support and ask to remove the custom Nginx Header rewrite code from your account."
msgstr "Nettstedet ditt bruker Kinsta! Du må ta kontakt med kundestøtte og be om å fjerne den egendefinerte Nginx Header-omskrivingskoden fra kontoen din."

#: include/functions.class.php:2600
msgid "and remove any Header rewrite rules within"
msgstr "og fjern alle Header-omskrivingsregler innenfor"

#: include/functions.class.php:2601
msgid "After the configuration file update"
msgstr "Etter konfigurasjonsfiloppdatering"

#: include/functions.class.php:2666
msgid "Acordingly the \"Save the Nginx Rewrites to a wphide-firewall-nginx.conf file\" option, the system encountered an unsuccessful attempt to write the custom Nginx rewrites to the file. Could you check if this file is writable?"
msgstr "I henhold til \"Lagre Nginx-omskrivingene til en wphide-firewall-nginx.conf-fil\"-alternativet, støtte systemet på et mislykket forsøk på å skrive de egendefinerte Nginx-omskrivingene til filen. Kan du sjekke om denne filen er skrivbar?"

#: include/functions.class.php:2679
msgid "Acordingly the \"Save the Nginx Rewrites to a wphide-firewall-nginx.conf file\" option, the system encountered an unsuccessful attempt to reset the wphide-firewall-nginx.conf file. Could you check if this file is writable?"
msgstr "I henhold til \"Lagre Nginx-omskrivingene til en wphide-firewall-nginx.conf-fil\"-alternativet, støtte systemet på et mislykket forsøk på å tilbakestille wphide-firewall-nginx.conf-filen. Kan du sjekke om denne filen er skrivbar?"

#: include/functions.class.php:2709
msgid "Acordingly the \"Save the Nginx Rewrites to a wphide-nginx.conf file\" option, the system encountered an unsuccessful attempt to write the custom Nginx rewrites to the file. Could you check if this file is writable?"
msgstr "I henhold til \"Lagre Nginx-omskrivingene til en wphide-nginx.conf-fil\"-alternativet, støtte systemet på et mislykket forsøk på å skrive de egendefinerte Nginx-omskrivingene til filen. Kan du sjekke om denne filen er skrivbar?"

#: include/functions.class.php:2733
msgid "Acordingly the \"Save the Nginx Rewrites to a wphide-nginx-headers.conf file\" option, the system encountered an unsuccessful attempt to write the custom Nginx rewrites to the file. Could you check if this file is writable?"
msgstr "I henhold til \"Lagre Nginx-omskrivingene til en wphide-nginx-headers.conf-fil\"-alternativet, støtte systemet på et mislykket forsøk på å skrive de egendefinerte Nginx-omskrivingene til filen. Kan du sjekke om denne filen er skrivbar?"

#: include/functions.class.php:2959
#, php-format
msgid "The %1$s plugin header is deprecated. Use %2$s instead."
msgstr "%1$s plugin-header er foreldet. Bruk %2$s i stedet."

#: include/functions.class.php:3043
#, php-format
msgid "By %s."
msgstr "Av %s."

#: include/functions.class.php:3747 include/functions.class.php:3793
msgid "The Confirmation failed:"
msgstr "Bekreftelsen mislyktes:"

#: include/functions.class.php:3749 include/functions.class.php:3796
msgid "The system returned the following errors: "
msgstr "Systemet returnerte følgende feil: "

#: include/functions.class.php:3752 include/functions.class.php:3799
msgid "- The Rewrites does not appear to apply! Ensure the custom lines are placed in correct file and at correct spot."
msgstr "- Omskrivingene ser ikke ut til å gjelde! Forsikre deg om at de egendefinerte linjene er plassert i riktig fil og på riktig sted."

#: include/functions.class.php:3753 include/functions.class.php:3800
msgid "- The Nginx service is required to be restarted."
msgstr "- Nginx-tjenesten må restartes."

#: include/functions.class.php:3754 include/functions.class.php:3801
msgid "- If your site require Basic Authentication ( HTTP password ) the procedure may fail."
msgstr "- Hvis nettstedet ditt krever grunnleggende autentisering (HTTP-passord) kan prosedyren mislykkes."

#: include/functions.class.php:3833 include/functions.class.php:3847
msgid "Unable to retrieve specific environment variables. Please check again the rewrite data on your server."
msgstr "Kan ikke hente spesifikke miljøvariabler. Vennligst sjekk omskrivingsdataene på serveren din igjen."

#: include/functions.class.php:3902
msgid "The server returned an unespected response code:"
msgstr "Serveren returnerte en uventet responskode:"

#: include/widgets.class.php:56
msgid "Run a fist scan to determine the current protection level of your website."
msgstr "Kjør en første skanning for å bestemme nåværende beskyttelsesnivå for nettstedet ditt."

#: include/wph.class.php:719
msgid "WP Hide Security Overview"
msgstr "WP Hide sikkerhetsoppsummering"

#: include/wph.class.php:1137 include/wph.class.php:1189
msgid "Server busy, unable to lock. Try again later."
msgstr "Server opptatt, kan ikke låse. Prøv igjen senere."

#: modules/components/admin-admin_ajax_php.php:53 modules/components/admin-admin_ajax_php.php:57
msgid "New admin-ajax&#46;php"
msgstr "Ny admin-ajax&#46;php"

#: modules/components/admin-admin_ajax_php.php:54
msgid "Map a new slug for admin-ajax&#46;php."
msgstr "Kartlegg en ny slug for admin-ajax&#46;php."

#: modules/components/admin-admin_ajax_php.php:57 modules/components/admin-admin_ajax_php.php:83 modules/components/admin-admin_url.php:57 modules/components/admin-admin_url.php:72 modules/components/admin-login_php.php:102 modules/components/admin-login_php.php:126 modules/components/admin-login_php.php:145 modules/components/admin-login_php.php:166 modules/components/cdn-setup.php:78 modules/components/cdn-setup.php:94 modules/components/cdn-setup.php:112 modules/components/firewall-query-string.php:57 modules/components/firewall-request-uri.php:56 modules/components/firewall-user-agent.php:56 modules/components/general-admin-bar.php:95 modules/components/general-block-detectors.php:45 modules/components/general-core.php:57 modules/components/general-core.php:79 modules/components/general-css-combine.php:129 modules/components/general-css-combine.php:158 modules/components/general-css-combine.php:177 modules/components/general-emulate.php:44 modules/components/general-feed.php:52 modules/components/general-feed.php:74 modules/components/general-headers.php:92 modules/components/general-headers.php:112 modules/components/general-headers.php:131 modules/components/general-headers.php:149 modules/components/general-headers.php:163 modules/components/general-html.php:114 modules/components/general-html.php:132 modules/components/general-html.php:159 modules/components/general-html.php:179 modules/components/general-html.php:200 modules/components/general-html.php:219 modules/components/general-html.php:237 modules/components/general-js-combine.php:136 modules/components/general-js-combine.php:170 modules/components/general-js-combine.php:190 modules/components/general-js-combine.php:212
#: modules/components/general-js-combine.php:228 modules/components/general-meta.php:161 modules/components/general-meta.php:181 modules/components/general-meta.php:201 modules/components/general-meta.php:219 modules/components/general-meta.php:237 modules/components/general-meta.php:257 modules/components/general-meta.php:275 modules/components/general-meta.php:295 modules/components/general-meta.php:315 modules/components/general-meta.php:336 modules/components/general-meta.php:356 modules/components/general-oembed.php:36 modules/components/general-scripts.php:43 modules/components/general-scripts.php:64 modules/components/general-styles.php:43 modules/components/general-styles.php:62 modules/components/general-tobots-txt.php:41 modules/components/general-user-interactions.php:179 modules/components/general-user-interactions.php:193 modules/components/general-user-interactions.php:212 modules/components/general-user-interactions.php:231 modules/components/general-user-interactions.php:249 modules/components/general-user-interactions.php:267 modules/components/general-user-interactions.php:285 modules/components/general-user-interactions.php:303 modules/components/general-user-interactions.php:322 modules/components/general-user-interactions.php:341 modules/components/general-user-interactions.php:359 modules/components/general-wp_die.php:44 modules/components/general-wpemoji.php:45 modules/components/general-wpemoji.php:61 modules/components/login_2fa_app.php:50 modules/components/login_2fa_defaults.php:102 modules/components/login_2fa_defaults.php:128 modules/components/login_2fa_defaults.php:142 modules/components/login_2fa_defaults.php:165 modules/components/login_2fa_defaults.php:192
#: modules/components/login_2fa_email.php:50 modules/components/login_2fa_recovery_codes.php:50 modules/components/login_captcha.php:96 modules/components/rewrite-author.php:60 modules/components/rewrite-author.php:77 modules/components/rewrite-author.php:100 modules/components/rewrite-comments.php:48 modules/components/rewrite-comments.php:64 modules/components/rewrite-json-rest.php:150 modules/components/rewrite-json-rest.php:169 modules/components/rewrite-json-rest.php:185 modules/components/rewrite-json-rest.php:207 modules/components/rewrite-json-rest.php:227 modules/components/rewrite-json-rest.php:248 modules/components/rewrite-json-rest.php:266 modules/components/rewrite-json-rest.php:284 modules/components/rewrite-mu-plugins.php:38 modules/components/rewrite-plugin_path.php:121 modules/components/rewrite-plugin_path.php:137 modules/components/rewrite-plugin_path.php:172 modules/components/rewrite-registration.php:66 modules/components/rewrite-registration.php:83 modules/components/rewrite-registration.php:99 modules/components/rewrite-registration.php:114 modules/components/rewrite-root-files.php:121 modules/components/rewrite-root-files.php:139 modules/components/rewrite-root-files.php:157 modules/components/rewrite-root-files.php:188 modules/components/rewrite-root-files.php:207 modules/components/rewrite-root-files.php:225 modules/components/rewrite-root-files.php:243 modules/components/rewrite-search.php:55 modules/components/rewrite-theme_path.php:72 modules/components/rewrite-theme_path.php:100 modules/components/rewrite-theme_path.php:128 modules/components/rewrite-upload_path.php:56 modules/components/rewrite-upload_path.php:69 modules/components/rewrite-upload_path.php:85
#: modules/components/rewrite-wp_content_path.php:56 modules/components/rewrite-wp_content_path.php:74 modules/components/rewrite-wp_includes_path.php:45 modules/components/rewrite-wp_includes_path.php:61 modules/components/rewrite-xml-rpc-path.php:72 modules/components/rewrite-xml-rpc-path.php:88 modules/components/rewrite-xml-rpc-path.php:105 modules/components/rewrite-xml-rpc-path.php:123 modules/components/rewrite-xml-rpc-path.php:147 modules/components/security-header-content-security-policy-report-only.php:49 modules/components/security-header-content-security-policy.php:49 modules/components/security-header-cross-origin-embedder-policy.php:50 modules/components/security-header-cross-origin-opener-policy.php:49 modules/components/security-header-cross-origin-resource-policy.php:49 modules/components/security-header-permissions-policy.php:49 modules/components/security-header-referrer-policy.php:50 modules/components/security-header-stricy-transport-security.php:50 modules/components/security-header-x-content-type-options.php:49 modules/components/security-header-x-download-options.php:49 modules/components/security-header-x-frame-options.php:49 modules/components/security-header-x-permitted-cross-domain-policies.php:50 modules/components/security-header-x-xss-protection.php:50
msgid "Help"
msgstr "Hjelp"

#: modules/components/admin-admin_ajax_php.php:58
msgid "The admin-ajax&#46;php is being used by WordPress core and many plugins to initiate AJAX calls from dashboard and front side. This is specific to WordPress, a site using such slug is an easy target to hack attempts."
msgstr "admin-ajax&#46;php brukes av WordPress-kjernen og mange plugins for å initiere AJAX-kall fra dashbord og frontside. Dette er spesifikt for WordPress, et nettsted som bruker en slik slug er et enkelt mål for hack-forsøk."

#: modules/components/admin-admin_ajax_php.php:59
msgid "Default url can be found in html source like this"
msgstr "Standard-URL kan finnes i html-kilde slik"

#: modules/components/admin-admin_ajax_php.php:61
msgid "or like this"
msgstr "eller slik"

#: modules/components/admin-admin_ajax_php.php:63
msgid "Rewriting the admin-ajax&#46;php to another slug to increase overall security for a WordPress site. It also allow to restrict admin access for a range of IPs without disabling the admin-ajax.php functionality calls."
msgstr "Omskriving av admin-ajax&#46;php til en annen slug for å øke den generelle sikkerheten for et WordPress-nettsted. Det tillater også å begrense admin-tilgang for et IP-område uten å deaktivere admin-ajax.php-funksjonskall."

#: modules/components/admin-admin_ajax_php.php:72
msgid "The new ajax slug should not include a PHP extension ( e.g. admin-ajax.php ) to allow a cookie to be set on the new AJAX path, if being different from admin URL."
msgstr "Den nye ajax-slugen bør ikke inkludere en PHP-utvidelse (f.eks. admin-ajax.php) for å tillate en informasjonskapsel å bli satt på den nye AJAX-stien, hvis den er forskjellig fra admin-URL."

#: modules/components/admin-admin_ajax_php.php:79 modules/components/admin-admin_ajax_php.php:83
msgid "Block default admin-ajax&#46;php"
msgstr "Blokker standard admin-ajax&#46;php"

#: modules/components/admin-admin_ajax_php.php:80
msgid "Block default admin-ajax&#46;php from being accesible."
msgstr "Blokker standard admin-ajax&#46;php fra å være tilgjengelig."

#: modules/components/admin-admin_ajax_php.php:84
msgid "If set to Yes, the old ajax url will be blocked and a default theme 404 error page will be returned."
msgstr "Hvis satt til Ja, vil den gamle ajax-URL-en bli blokkert og en standard tema 404-feilside vil bli returnert."

#: modules/components/admin-admin_ajax_php.php:434 modules/components/admin-admin_url.php:427 modules/components/admin-login_php.php:603 modules/components/rewrite-author.php:434 modules/components/rewrite-comments.php:308 modules/components/rewrite-plugin_path.php:576 modules/components/rewrite-root-files.php:585 modules/components/rewrite-root-files.php:706 modules/components/rewrite-root-files.php:816 modules/components/rewrite-root-files.php:918 modules/components/rewrite-wp_content_path.php:315
msgid "REPLACE THE FOLLOWING LINE WITH YOUR OWN INCLUDE! This can be found within block"
msgstr "ERSTATT FØLGENDE LINJE MED DIN EGEN INCLUDE! Dette kan finnes innenfor blokk"

#: modules/components/admin-admin_url.php:53
msgid "Create a new admin url instead default /wp-admin and /login."
msgstr "Opprett en ny admin-URL i stedet for standard /wp-admin og /login."

#: modules/components/admin-admin_url.php:58
msgid "Despite the flexibility of WordPress framework, there are few ways to configure the admin login url customization for making a bit safer against unauthorized access and brute force attempts. All methods are not provided out of the box through WordPress core but require custom code to make it happen."
msgstr "Til tross for fleksibiliteten i WordPress-rammeverket, er det få måter å konfigurere tilpasning av admin-innloggings-URL for å gjøre det litt sikrere mot uautorisert tilgang og brute force-forsøk. Alle metoder er ikke tilgjengelige umiddelbart gjennom WordPress-kjernen, men krever egendefinert kode for å gjennomføre det."

#: modules/components/admin-admin_url.php:59
msgid "This feature provide an easy way to change the default /wp-admin/ to a different slug."
msgstr "Denne funksjonen gir en enkel måte å endre standard /wp-admin/ til en annen slug."

#: modules/components/admin-admin_url.php:60
msgid "Once changed, the new url will be used to access all Dashboard sections, from Posts and Pages section to Plugins, Appearance and Settings."
msgstr "Når den er endret, vil den nye URL-en brukes for å få tilgang til alle Dashbord-seksjoner, fra Innlegg og Sider-seksjon til Plugins, Utseende og Innstillinger."

#: modules/components/admin-admin_url.php:68 modules/components/admin-admin_url.php:72
msgid "Block default Admin Url"
msgstr "Blokker standard Admin-URL"

#: modules/components/admin-admin_url.php:69
msgid "Block default admin url and files from being accesible."
msgstr "Blokker standard admin-URL og filer fra å være tilgjengelige."

#: modules/components/admin-admin_url.php:73
msgid "If set to Yes, the old admin url will be blocked and a default theme 404 error page will be returned."
msgstr "Hvis satt til Ja, vil den gamle admin-URL-en bli blokkert og en standard tema 404-feilside vil bli returnert."

#: modules/components/admin-login_php.php:99
msgid "Map a new wp-login.php instead default. This also need to include <i>.php</i> extension."
msgstr "Kartlegg en ny wp-login.php i stedet for standard. Dette må også inkludere <i>.php</i>-utvidelse."

#: modules/components/admin-login_php.php:103
msgid "There are a lot of security issues that come from having your login page open to the public. Most specifically, brute force attacks. Because of the ubiquity of WordPress, these kinds of attacks are becoming more and more common."
msgstr "Det er mange sikkerhetsproblemer som kommer av å ha innloggingssiden din åpen for offentligheten. Mest spesifikt, brute force-angrep. På grunn av WordPress's utbredelse, blir slike angrep mer og mer vanlige."

#: modules/components/admin-login_php.php:104
msgid "Map a new wp-login.php instead default prevent hackers boot to attempt to brute force a site login. Being known only by the site owner, the url itself becomes private."
msgstr "Kartlegg en ny wp-login.php i stedet for standard for å forhindre hackere i å forsøke brute force på en nettstedinnlogging. Ved å være kjent kun av nettstedeieren, blir URL-en selv privat."

#: modules/components/admin-login_php.php:105
msgid "Make sure you keep the new login url to a safe place, in case to forget."
msgstr "Forsikre deg om at du beholder den nye innloggings-URL-en på et sikkert sted, i tilfelle du glemmer den."

#: modules/components/admin-login_php.php:115
msgid "Make sure your log-in url is not already modified by another plugin or theme. In such case, you should disable other code and take advantage of these features."
msgstr "Forsikre deg om at innloggings-URL-en din ikke allerede er modifisert av en annen plugin eller tema. I så fall bør du deaktivere annen kode og dra nytte av disse funksjonene."

#: modules/components/admin-login_php.php:122 modules/components/admin-login_php.php:126
msgid "Block default wp-login.php"
msgstr "Blokker standard wp-login.php"

#: modules/components/admin-login_php.php:123
msgid "Block default wp-login.php file from being accesible."
msgstr "Blokker standard wp-login.php-fil fra å være tilgjengelig."

#: modules/components/admin-login_php.php:127
msgid "If set to Yes, the old login url will be blocked and a default theme 404 error page will be returned."
msgstr "Hvis satt til Ja, vil den gamle innloggings-URL-en bli blokkert og en standard tema 404-feilside vil bli returnert."

#: modules/components/admin-login_php.php:128
msgid "Ensure the New wp-login.php option works correctly on your server before activate this."
msgstr "Forsikre deg om at Ny wp-login.php-alternativet fungerer korrekt på serveren din før du aktiverer dette."

#: modules/components/admin-login_php.php:141 modules/components/admin-login_php.php:145
msgid "Use mere rewrite for Block Default"
msgstr "Bruk ren omskriving for Blokker Standard"

#: modules/components/admin-login_php.php:142
msgid "On specific servers, blocking might not work, trigger this setting to make it compatible."
msgstr "På spesifikke servere kan blokkering ikke fungere, utløs denne innstillingen for å gjøre den kompatibel."

#: modules/components/admin-login_php.php:146
msgid "When accessing the default login url, even if blocked, on certain servers the link might still be available. This option create an extra rewrite rule which might fix the blocking."
msgstr "Når du aksesserer standard påloggingsadresse, selv om den er blokkert, kan lenken på visse servere fortsatt være tilgjengelig. Dette alternativet oppretter en ekstra omskrivingsregel som kan fikse blokkeringen."

#: modules/components/admin-login_php.php:160 modules/components/admin-login_php.php:166
msgid "Custom Login Logo"
msgstr "Egendefinert påloggingslogo"

#: modules/components/admin-login_php.php:162
msgid "Change the default WordPress login Logo."
msgstr "Endre standard WordPress-påloggingslogo."

#: modules/components/admin-login_php.php:167
msgid "The feature in the WP Hide plugin allows you to replace the standard WordPress logo with a custom image of your choice. This customization enhances your site's branding by displaying your logo on the login page, admin dashboard, and other areas where the default logo appears. To use this feature, simply upload your desired logo in the WP Hide settings and save the changes. Your new logo will be displayed immediately, providing a more personalized and professional appearance for your WordPress site."
msgstr "Funksjonen i WP Hide-pluginen lar deg erstatte standard WordPress-logo med et egendefinert bilde etter ditt valg. Denne tilpasningen forbedrer nettstedets merkevarebygging ved å vise logoen din på påloggingssiden, admin-dashbordet og andre områder der standardlogo vises. For å bruke denne funksjonen, last opp ønsket logo i WP Hide-innstillingene og lagre endringene. Den nye logoen din vil vises umiddelbart, noe som gir et mer personlig og profesjonelt utseende for WordPress-nettstedet ditt."

#: modules/components/admin-login_php.php:168
msgid "Recommended width size is 320px."
msgstr "Anbefalt breddestørrelse er 320px."

#: modules/components/admin-login_php.php:465
msgid "This is an automated message to inform that your login url has been changed at"
msgstr "Dette er en automatisk melding for å informere om at påloggingsadressen din er endret på"

#: modules/components/admin-login_php.php:466
msgid "The new login url is"
msgstr "Den nye påloggingsadressen er"

#: modules/components/admin-login_php.php:467
msgid "Additionally, you can use the following link to recover the default login/admin access: "
msgstr "I tillegg kan du bruke følgende lenke for å gjenopprette standard påloggings-/admin-tilgang: "

#: modules/components/admin-login_php.php:468
msgid "Please ensure the safety of this URL for potential recovery in case of forgetfulness."
msgstr "Vennligst sørg for sikkerheten til denne URL-en for potensiell gjenoppretting i tilfelle glemthet."

#: modules/components/cdn-setup.php:74 modules/components/cdn-setup.php:78
msgid "CDN Url"
msgstr "CDN-adresse"

#: modules/components/cdn-setup.php:75
msgid "Some CDN providers (like stackpath.com ) replace site assets with custom url, enter here such url. Otherwise this option should stay empty."
msgstr "Noen CDN-leverandører (som stackpath.com) erstatter nettstedsressurser med egendefinert adresse, skriv inn slik adresse her. Ellers bør dette alternativet forbli tomt."

#: modules/components/cdn-setup.php:79
msgid "A Content Delivery Network - CDN - is a network of servers located around the globe in fundamental spots with fast access. It takes a while for a web page to load especially if the server is located far away from the user. So they are designed to host and deliver copies of your site's static and dynamic content such as images, CSS, JavaScript, audio and video streams."
msgstr "Et Content Delivery Network - CDN - er et nettverk av servere plassert rundt om i verden på strategiske steder med rask tilgang. Det tar en stund for en nettside å laste, spesielt hvis serveren er plassert langt fra brukeren. Så de er designet for å huse og levere kopier av nettstedets statiske og dynamiske innhold som bilder, CSS, JavaScript, lyd- og videostrømmer."

#: modules/components/cdn-setup.php:80
msgid "Sample CDN url:"
msgstr "Eksempel på CDN-adresse:"

#: modules/components/cdn-setup.php:82
msgid "Enter a CDN Url to allow the plugin to process assets provided through CDN service."
msgstr "Skriv inn en CDN-adresse for å tillate at pluginen behandler ressurser levert gjennom CDN-tjenesten."

#: modules/components/cdn-setup.php:90 modules/components/cdn-setup.php:94
msgid "Load Cache Files through CDN"
msgstr "Last hurtigbufferede filer gjennom CDN"

#: modules/components/cdn-setup.php:91
msgid "When creating Cache files, mainly used when using CSS Combine and JavaScript Cobine, the cache files should be loaded through CDN."
msgstr "Ved oppretting av hurtigbufferfiler, hovedsakelig brukt ved bruk av CSS- og JavaScript-kombinasjon, bør hurtigbufferfilene lastes gjennom CDN."

#: modules/components/cdn-setup.php:95
msgid "If provided a CDN, the processed cache assets will be loaded through it."
msgstr "Hvis CDN er oppgitt, vil de behandlede hurtigbufferressursene lastes gjennom den."

#: modules/components/cdn-setup.php:108 modules/components/cdn-setup.php:112
msgid "Load assets within Cache Files through CDN"
msgstr "Last ressurser i hurtigbufferfiler gjennom CDN"

#: modules/components/cdn-setup.php:109
msgid "When creating Cache files, mainly used when using CSS Combine and JavaScript Cobine, any assets ( images, fonts) inside cache files should be loaded through CDN."
msgstr "Ved oppretting av hurtigbufferfiler, hovedsakelig brukt ved bruk av CSS- og JavaScript-kombinasjon, bør alle ressurser (bilder, fonter) inni hurtigbufferfiler lastes gjennom CDN."

#: modules/components/cdn-setup.php:113
msgid "If provided a CDN, all media files inside the cached data will be using CDN to load."
msgstr "Hvis CDN er oppgitt, vil alle mediefiler i de hurtigbufferede dataene bruke CDN for lasting."

#: modules/components/cdn-setup.php:177 modules/components/general-css-combine.php:1434 modules/components/general-headers.php:288 modules/components/general-html-css-js-replacements.php:165 modules/components/general-js-combine.php:1385 modules/components/general-text-replace.php:118
msgid "Add New"
msgstr "Legg til ny"

#: modules/components/firewall-query-string.php:53 modules/components/firewall-query-string.php:57
msgid "Query String Rules"
msgstr "Spørringsstreng-regler"

#: modules/components/firewall-query-string.php:54
msgid "Add Firewall rules for Query String."
msgstr "Legg til brannmur-regler for spørringsstreng."

#: modules/components/firewall-query-string.php:58
msgid "The Query String is the portion of a URL where data is passed to a server application and/or back-end database."
msgstr "Spørringsstrengen er den delen av en URL der data sendes til en serverapplikasjon og/eller backend-database."

#: modules/components/firewall-query-string.php:59
msgid " Typical URL containing a query string is as follows:"
msgstr " Typisk URL som inneholder en spørringsstreng er som følger:"

#: modules/components/firewall-query-string.php:61
msgid "The arguments of an URL are the typical way for hackers to attempt to break into a server. This firewall gives your site a super strong layer of protection at the server level. So bad requests are blocked without having to load up PHP, MySQL, and everything else."
msgstr "Argumentene i en URL er den typiske måten hackere forsøker å bryte seg inn på en server på. Denne brannmuren gir nettstedet ditt et supersterkt beskyttelseslag på servernivå. Så dårlige forespørsler blir blokkert uten å måtte laste opp PHP, MySQL og alt annet."

#: modules/components/firewall-query-string.php:63 modules/components/firewall-request-uri.php:61
msgid "The firewall protects against the following type of attacks:"
msgstr "Brannmuren beskytter mot følgende type angrep:"

#: modules/components/firewall-query-string.php:64 modules/components/firewall-request-uri.php:62
msgid "HTTP Response Splitting"
msgstr "HTTP-responsdeling"

#: modules/components/firewall-query-string.php:65 modules/components/firewall-request-uri.php:63
msgid "XSS) Cross-Site Scripting"
msgstr "XSS) Tverrnettstedsskripting"

#: modules/components/firewall-query-string.php:66 modules/components/firewall-request-uri.php:64
msgid "Cache Poisoning"
msgstr "Hurtigbufferforgiftning"

#: modules/components/firewall-query-string.php:67 modules/components/firewall-request-uri.php:65
msgid "Dual-Header Exploits"
msgstr "Dobbeltheode-utnyttelser"

#: modules/components/firewall-query-string.php:68 modules/components/firewall-request-uri.php:66
msgid "SQL/PHP/Code Injection"
msgstr "SQL/PHP/kode-injeksjon"

#: modules/components/firewall-query-string.php:69 modules/components/firewall-request-uri.php:67
msgid "File Injection/Inclusion"
msgstr "Filinjeksjon/inkludering"

#: modules/components/firewall-query-string.php:70 modules/components/firewall-request-uri.php:68
msgid "Null Byte Injection"
msgstr "Nullbyte-injeksjon"

#: modules/components/firewall-query-string.php:71 modules/components/firewall-request-uri.php:69
msgid "WordPress exploits such as revslider, timthumb, fckeditor, et al"
msgstr "WordPress-utnyttelser som revslider, timthumb, fckeditor, etc."

#: modules/components/firewall-query-string.php:72 modules/components/firewall-request-uri.php:70
msgid "Exploits such as c99shell, phpshell, remoteview, site copier, et al"
msgstr "Utnyttelser som c99shell, phpshell, remoteview, site copier, etc."

#: modules/components/firewall-query-string.php:73 modules/components/firewall-request-uri.php:71
msgid "PHP information leakage"
msgstr "PHP-informasjonslekkasje"

#: modules/components/firewall-query-string.php:74 modules/components/firewall-request-uri.php:72
msgid "After activating the firewall, test everything thoroughly, to ensure none of the rules block the site functionality."
msgstr "Etter aktivering av brannmuren, test alt grundig for å sikre at ingen av reglene blokkerer nettstedets funksjonalitet."

#: modules/components/firewall-request-uri.php:52 modules/components/firewall-request-uri.php:56
msgid "Request URI Rules"
msgstr "Forespørsel-URI-regler"

#: modules/components/firewall-request-uri.php:53
msgid "Add Firewall rules for Request URI."
msgstr "Legg til brannmur-regler for forespørsel-URI."

#: modules/components/firewall-request-uri.php:57
msgid "The Request-URI is a Uniform Resource Identifier and identifies the resource upon which to apply the request. "
msgstr "Forespørsel-URI-en er en Uniform Resource Identifier og identifiserer ressursen som forespørselen skal brukes på. "

#: modules/components/firewall-request-uri.php:58
msgid " Typical URI is as follows:"
msgstr " Typisk URI er som følger:"

#: modules/components/firewall-user-agent.php:52 modules/components/firewall-user-agent.php:56
msgid "User Aget Rules"
msgstr "Brukeragent-regler"

#: modules/components/firewall-user-agent.php:53
msgid "Add Firewall rules for User Agent."
msgstr "Legg til brannmur-regler for brukeragent."

#: modules/components/firewall-user-agent.php:57
msgid "The User-Agent request header is a characteristic string that lets servers and network peers identify the application, operating system, vendor, and/or version of the requesting user agent."
msgstr "User-Agent-forespørselshodet er en karakteristisk streng som lar servere og nettverkslikemanner identifisere applikasjonen, operativsystemet, leverandøren og/eller versjonen til den forespørrende brukeragenten."

#: modules/components/firewall-user-agent.php:58
msgid " Typical legit user agent is:"
msgstr " Typisk legitim brukeragent er:"

#: modules/components/firewall-user-agent.php:61
msgid "Common format for legit user agent on web browsers:"
msgstr "Vanlig format for legitim brukeragent i nettlesere:"

#: modules/components/firewall-user-agent.php:63
msgid "Many malware sites, bots and hack scanners use their user agent. Using this firewall type, they get blocked before reaching your site."
msgstr "Mange skadevare-nettsteder, botter og hack-skannere bruker sin egen brukeragent. Ved å bruke denne brannmurtypen blir de blokkert før de når nettstedet ditt."

#: modules/components/general-admin-bar.php:85
msgid "The admin bar is a floating bar that contains useful administration screen links such as add a new post, see pending comments, edit your profile etc. It can be extended by plugins to add additional functionality for example SEO and more."
msgstr "Adminlinjen er en flytende linje som inneholder nyttige administrasjonsskjermlenker som å legge til et nytt innlegg, se ventende kommentarer, redigere profilen din etc. Den kan utvides av plugins for å legge til ytterligere funksjonalitet for eksempel SEO og mer."

#: modules/components/general-admin-bar.php:87 modules/components/general-admin-bar.php:92
msgid "Remove WordPress Admin Bar for "
msgstr "Fjern WordPress Admin-linje for "

#: modules/components/general-admin-bar.php:87
msgid "role"
msgstr "rolle"

#: modules/components/general-admin-bar.php:91 modules/components/general-admin-bar.php:95
msgid "Remove Admin Bar for "
msgstr "Fjern Admin-linje for "

#: modules/components/general-admin-bar.php:92
msgid "role, which is being displayed by default on front side of your website."
msgstr "rolle, som vises som standard på fremsiden av nettstedet ditt."

#: modules/components/general-admin-bar.php:95
msgid "role."
msgstr "rolle."

#: modules/components/general-block-detectors.php:41
msgid "Block Theme / Plugin detectors."
msgstr "Blokker tema-/plugin-detektorer."

#: modules/components/general-block-detectors.php:42
msgid "Block common Theme / Plugin detectors and canners."
msgstr "Blokker vanlige tema-/plugin-detektorer og skannere."

#: modules/components/general-block-detectors.php:45
msgid "Block Theme / Plugin detectors"
msgstr "Blokker tema-/plugin-detektorer"

#: modules/components/general-block-detectors.php:46
msgid "Enhance your website's privacy and security with the Block Theme Detectors feature. This tool prevents known user agents and IP addresses associated with popular theme detectors from accessing your site's design and theme-related information. By doing so, it keeps your creative choices private and reduces the risk of targeted attacks exploiting specific theme vulnerabilities."
msgstr "Forbedre nettstedets personvern og sikkerhet med funksjonen for blokkering av tema-detektorer. Dette verktøyet forhindrer kjente brukeragenter og IP-adresser knyttet til populære tema-detektorer fra å få tilgang til nettstedets design og tema-relatert informasjon. Ved å gjøre dette holder den dine kreative valg private og reduserer risikoen for målrettede angrep som utnytter spesifikke tema-sårbarheter."

#: modules/components/general-block-detectors.php:47
msgid "Key Benefits"
msgstr "Viktige fordeler"

#: modules/components/general-block-detectors.php:49
msgid "Privacy: Protect your website's theme details from being copied or analyzed"
msgstr "Personvern: Beskytter tema-detaljene på nettstedet ditt mot å bli kopiert eller analysert"

#: modules/components/general-block-detectors.php:50
msgid "Security: Minimize exposure to potential threats"
msgstr "Sikkerhet: Minimaliser eksponering for potensielle trusler"

#: modules/components/general-block-detectors.php:51
msgid "Performance: Optimize server resources by blocking unnecessary traffic"
msgstr "Ytelse: Optimaliser serverressurser ved å blokkere unødvendig trafikk"

#: modules/components/general-block-detectors.php:52
msgid "Competitive Edge: Maintain a unique brand identity"
msgstr "Konkurransefortrinn: Behold en unik merkeidentitet"

#: modules/components/general-core.php:53 modules/components/general-core.php:57
msgid "Disabling Directory Listing"
msgstr "Deaktiverer kataloglisting"

#: modules/components/general-core.php:54
msgid "Disabling Directory Listing for server folders."
msgstr "Deaktiverer kataloglisting for servermapper."

#: modules/components/general-core.php:58
msgid "By leveraging a rewrite directive, this feature prevents unauthorized users from browsing server directories, ensuring sensitive files remain inaccessible."
msgstr "Ved å utnytte en omskrivingsdirektiv, forhindrer denne funksjonen uautorisertebrukere i å bla gjennom serverkataloger, og sikrer at følsomme filer forblir utilgjengelige."

#: modules/components/general-core.php:59
msgid "Once enabled, the plugin injects the directive into your .htaccess / configuration file ( depending on server type ), blocking directory index views without manual edits. This simple addition fortifies your website by eliminating potential exposure of directory contents, reducing vulnerabilities. Protect assets and maintain a professional appearance by completely hiding file listings."
msgstr "Når den er aktivert, injiserer pluginen direktivet i din .htaccess / konfigurasjonsfil (avhengig av servertype), og blokkerer katalogindeksvisning uten manuelle endringer. Dette enkle tillegget styrker nettstedet ditt ved å eliminere potensiell eksponering av kataloginnhold, og reduserer sårbarheter. Beskytter eiendeler og opprettholder et profesjonelt utseende ved å skjule fillistinger fullstendig."

#: modules/components/general-core.php:60 modules/components/general-core.php:81
msgid "Benefits:"
msgstr "Fordeler:"

#: modules/components/general-core.php:61
msgid "Enhances security by hiding directory structure"
msgstr "Forbedrer sikkerheten ved å skjule katalogstruktur"

#: modules/components/general-core.php:62
msgid "Protects sensitive files and assets"
msgstr "Beskytter følsomme filer og eiendeler"

#: modules/components/general-core.php:75 modules/components/general-core.php:79
msgid "Disabling Author Archive"
msgstr "Deaktiverer forfatterarkiv"

#: modules/components/general-core.php:76
msgid "Prevent Access to Author Archives via user IDs"
msgstr "Forhindre tilgang til forfatterarkiv via bruker-IDer"

#: modules/components/general-core.php:80
msgid "The Disabling Author Archive option removes WordPress’s default author archive URLs (e.g., ?author=ID) to prevent enumeration of valid usernames. When enabled, WP Hide intercepts requests to author query strings and returns a 404 error, effectively hiding author archives that are not essential for most sites."
msgstr "Alternativet for deaktivering av forfatterarkiv fjerner WordPress sine standard forfatterarkiv-URL-er (f.eks. ?author=ID) for å forhindre oppregning av gyldige brukernavn. Når aktivert, avskjærer WP Hide forespørsler til forfatterspørringsstrenger og returnerer en 404-feil, og skjuler effektivt forfatterarkiv som ikke er essensielle for de fleste nettsteder."

#: modules/components/general-core.php:82
msgid "Mitigates user enumeration attacks by disabling ?author={int} URLs"
msgstr "Reduserer brukeroppregningsangrep ved å deaktivere ?author={int}-URL-er"

#: modules/components/general-core.php:83
msgid "Enhances site security and privacy"
msgstr "Forbedrer nettstedets sikkerhet og personvern"

#: modules/components/general-core.php:84
msgid "Simplifies administration by removing unnecessary archive pages"
msgstr "Forenkler administrasjon ved å fjerne unødvendige arkivsider"

#: modules/components/general-css-combine.php:125 modules/components/general-css-combine.php:129
msgid "CSS Post-Processing type"
msgstr "CSS-etterbehandlingstype"

#: modules/components/general-css-combine.php:126
msgid "All assets and inline CSS will be post-processed, using Combine or In-place technique."
msgstr "Alle ressurser og inline CSS vil bli etterbehandlet, ved bruk av Kombiner eller På plass-teknikk."

#: modules/components/general-css-combine.php:130
msgid "The module incorporates a Post-Processing engine specifically designed to offer a powerfull processing capabilities for Cascading Style Sheet (CSS) data types, for hiding and white labeling. The activation of this engine is essential for enabling the Replacements functionality."
msgstr "Modulen inneholder en etterbehandlingsmotor spesielt designet for å tilby kraftige behandlingsevner for Cascading Style Sheet (CSS) datatyper, for skjuling og white labeling. Aktivering av denne motoren er essensiell for å aktivere Erstatningsfunksjonaliteten."

#: modules/components/general-css-combine.php:132
msgid "There are 3 types of processing options:"
msgstr "Det er 3 typer behandlingsalternativer:"

#: modules/components/general-css-combine.php:133
msgid "<b>Combine</b>: Merge all CSS code in (usually) 2 files, one in the header and another in the footer."
msgstr "<b>Kombiner</b>: Slå sammen all CSS-kode i (vanligvis) 2 filer, en i toppen og en annen i bunnteksten."

#: modules/components/general-css-combine.php:134
msgid "<b>In Place</b>: All CSS code will be processed and the results will be placed in the same spot as an initial asset or in-line CSS. "
msgstr "<b>På plass</b>: All CSS-kode vil bli behandlet og resultatene vil bli plassert på samme sted som en innledende ressurs eller inline CSS. "

#: modules/components/general-css-combine.php:135
msgid "<b>In Place & Encode Inline</b>: All CSS code will be processed and the results will be placed in the same spot. Additionally, the Inline styles code will be base64 encoded and placed in the same spot. "
msgstr "<b>På plass & Koder inline</b>: All CSS-kode vil bli behandlet og resultatene vil bli plassert på samme sted. I tillegg vil inline stil-koden bli base64-kodet og plassert på samme sted. "

#: modules/components/general-css-combine.php:137 modules/components/general-js-combine.php:147
msgid "This also improves the overal site loading speed and SEO score"
msgstr "Dette forbedrer også nettstedets generelle lastingstid og SEO-score"

#: modules/components/general-css-combine.php:139 modules/components/general-js-combine.php:149
msgid "When using assets optimisation plugin (e.g.  WP Optimize, Autoptimize, Perfmatters etc ), the InPlace or In Place & Encode Inline selection is recommended."
msgstr "Ved bruk av ressursoptimaliseringsplugin (f.eks. WP Optimize, Autoptimize, Perfmatters etc), anbefales valget På plass eller På plass & Koder inline."

#: modules/components/general-css-combine.php:145 modules/components/general-js-combine.php:156
msgid "Combine"
msgstr "Kombiner"

#: modules/components/general-css-combine.php:146 modules/components/general-js-combine.php:158
msgid "In Place"
msgstr "På plass"

#: modules/components/general-css-combine.php:147 modules/components/general-js-combine.php:159
msgid "In Place & Encode Inline"
msgstr "På plass & koder inline"

#: modules/components/general-css-combine.php:155
msgid "Remove all Comments from combined css files."
msgstr "Fjern alle kommentarer fra kombinerte css-filer."

#: modules/components/general-css-combine.php:159 modules/components/general-css-combine.php:178
msgid "This option require CSS Combine Code to be active."
msgstr "Dette alternativet krever at CSS Combine Code er aktivt."

#: modules/components/general-css-combine.php:160
msgid "Remove all Comments from combined css files, which usualy specify Theme and Plugins Name and Version."
msgstr "Fjern alle kommentarer fra kombinerte css-filer, som vanligvis spesifiserer tema- og plugin-navn og versjon."

#: modules/components/general-css-combine.php:173 modules/components/general-css-combine.php:177 modules/components/general-html.php:128 modules/components/general-html.php:132
msgid "Minify"
msgstr "Minifiser"

#: modules/components/general-css-combine.php:174
msgid "Minify the combined css files. "
msgstr "Minifiser de kombinerte css-filene. "

#: modules/components/general-css-combine.php:179
msgid "Minify the Cascading Style Sheet data for smaller files. This slighlty increase the overal site speed."
msgstr "Minifiser Cascading Style Sheet-data for mindre filer. Dette øker nettstedets generelle hastighet litt."

#: modules/components/general-css-combine.php:192
msgid "Exclude style files from CSS Combine"
msgstr "Ekskluder stilfiler fra CSS-kombinasjon"

#: modules/components/general-css-combine.php:197
msgid "Specify any style files which will be excluded when using CSS Combine."
msgstr "Spesifiser eventuelle stilfiler som vil bli ekskludert ved bruk av CSS-kombinasjon."

#: modules/components/general-css-combine.php:198
msgid "Use only style filename and relative path e.g. <code>mediaelement.css</code>, <code>plugin-slug/player.min.css</code>  one per row."
msgstr "Bruk kun stilfilnavn og relativ sti f.eks. <code>mediaelement.css</code>, <code>plugin-slug/player.min.css</code> en per rad."

#: modules/components/general-css-combine.php:199
msgid "Excluding a file from processing prevents the replacements from being applied."
msgstr "Å ekskludere en fil fra behandling forhindrer at erstatninger brukes."

#: modules/components/general-css-combine.php:207
msgid "Exclude CSS Block from Combine"
msgstr "Ekskluder CSS-blokk fra kombinasjon"

#: modules/components/general-css-combine.php:213
msgid "Specify partial CSS code block to be excluded from Combine."
msgstr "Spesifiser delvis CSS-kodeblokk som skal ekskluderes fra kombinasjon."

#: modules/components/general-css-combine.php:213
msgid "Use a full line or part of it to avoid matching other codes, avoid simple words which can match other CSS code. For inline styles, tag attributes can be used."
msgstr "Bruk en full linje eller del av den for å unngå å matche andre koder, unngå enkle ord som kan matche annen CSS-kode. For inline-stiler kan tagg-attributter brukes."

#: modules/components/general-document-loaded-assets-postprocessing.php:78
msgid "Document Loaded Assets PostProcessing"
msgstr "Dokumentlastede ressurser etterbehandling"

#: modules/components/general-document-loaded-assets-postprocessing.php:83
msgid "This options works with the features "
msgstr "Dette alternativet fungerer med funksjonene "

#: modules/components/general-document-loaded-assets-postprocessing.php:83 modules/components/general-html-css-js-replacements.php:62
msgid "CSS Post-Processing"
msgstr "CSS-etterbehandling"

#: modules/components/general-document-loaded-assets-postprocessing.php:83
msgid "and/or"
msgstr "og/eller"

#: modules/components/general-document-loaded-assets-postprocessing.php:83 modules/components/general-html-css-js-replacements.php:62
msgid "JavaScript Post-Processing"
msgstr "JavaScript-etterbehandling"

#: modules/components/general-document-loaded-assets-postprocessing.php:83
msgid " are active."
msgstr " er aktive."

#: modules/components/general-document-loaded-assets-postprocessing.php:84
msgid "When the PostProcessing function is active, the plugin core applies the Replacements for all page elements including assets, before the HTML content is sent back to the browser. Rarely, some JavaScripts load additional assets, once the DOM document has loaded. In such a case, a Replacement filter is not possible as the browser loads the content directly through the file link. "
msgstr "Når PostProcessing-funksjonen er aktiv, bruker plugin-kjernen Erstatninger for alle sideelementer inkludert ressurser, før HTML-innholdet sendes tilbake til nettleseren. Sjelden laster noen JavaScripts ytterligere ressurser, når DOM-dokumentet har lastet. I slike tilfeller er et Erstatningsfilter ikke mulig da nettleseren laster innholdet direkte gjennom fillenken. "

#: modules/components/general-document-loaded-assets-postprocessing.php:85
msgid "Through this component, such asset URLs ( JavaScript and StyleSheet files ) can be provided to instruct the core to rewrite the link through a post-processor and apply the Replacements."
msgstr "Gjennom denne komponenten kan slike ressurs-URL-er (JavaScript- og StyleSheet-filer) oppgis for å instruere kjernen til å omskrive lenken gjennom en etterbehandler og bruke Erstatningene."

#: modules/components/general-document-loaded-assets-postprocessing.php:86
msgid "Provide the URLs, one per line, as they show within the browser console ( network ). On Save, the plugin attempts to reverse the URLs to the default format. "
msgstr "Oppgi URL-ene, en per linje, slik de vises i nettleserkonsollen (nettverk). Ved lagring forsøker pluginen å reversere URL-ene til standardformatet. "

#: modules/components/general-document-loaded-assets-postprocessing.php:131
msgid "The URL "
msgstr "URL-en "

#: modules/components/general-document-loaded-assets-postprocessing.php:131
msgid "couldn't be processed as appears invalid."
msgstr "kunne ikke behandles da den ser ut til å være ugyldig."

#: modules/components/general-document-loaded-assets-postprocessing.php:143
msgid "Invalid file type"
msgstr "Ugyldig filtype"

#: modules/components/general-document-loaded-assets-postprocessing.php:143
msgid "only CSS and JavaScript files can be provides."
msgstr "kun CSS- og JavaScript-filer kan oppgis."

#: modules/components/general-emulate.php:41
msgid "Use the option to output specific CMSs HTML traces to mislead any peculiar check."
msgstr "Bruk alternativet for å sende ut spesifikke CMS HTML-spor for å villede spesielle sjekker."

#: modules/components/general-emulate.php:45
msgid "Using the option the system try to misguide the used WordPress by outputting the wrong traces, of the selected CMS."
msgstr "Ved å bruke alternativet prøver systemet å villede den brukte WordPress ved å sende ut feil spor, fra den valgte CMS-en."

#: modules/components/general-emulate.php:46
msgid "Misleading and making a false lead provides an extra security, as the attacker search and attempt to hack something which not exist."
msgstr "Villedende og å lage en falsk ledetråd gir ekstra sikkerhet, ettersom angriperen søker og prøver å hacke noe som ikke eksisterer."

#: modules/components/general-emulate.php:47
msgid "The plugin can emulate systems like:"
msgstr "Pluginen kan emulere systemer som:"

#: modules/components/general-emulate.php:48
msgid "- Drupal"
msgstr "- Drupal"

#: modules/components/general-emulate.php:49
msgid "- Ghost"
msgstr "- Ghost"

#: modules/components/general-emulate.php:50
msgid "- HubSpot"
msgstr "- HubSpot"

#: modules/components/general-emulate.php:51
msgid "- Joomla"
msgstr "- Joomla"

#: modules/components/general-emulate.php:52
msgid "- TYPO3"
msgstr "- TYPO3"

#: modules/components/general-emulate.php:53
msgid "- Wix"
msgstr "- Wix"

#: modules/components/general-emulate.php:59
msgid "Drupal 8"
msgstr "Drupal 8"

#: modules/components/general-emulate.php:60
msgid "Drupal 9"
msgstr "Drupal 9"

#: modules/components/general-emulate.php:61
msgid "Ghost 4.15"
msgstr "Ghost 4.15"

#: modules/components/general-emulate.php:62
msgid "Ghost 4.31"
msgstr "Ghost 4.31"

#: modules/components/general-emulate.php:63
msgid "HubSpot"
msgstr "HubSpot"

#: modules/components/general-emulate.php:64
msgid "Joomla"
msgstr "Joomla"

#: modules/components/general-emulate.php:65
msgid "TYPO3"
msgstr "TYPO3"

#: modules/components/general-emulate.php:66
msgid "Wix"
msgstr "Wix"

#: modules/components/general-feed.php:48 modules/components/general-feed.php:52
msgid "Remove feed|rdf|rss|rss2|atom links"
msgstr "Fjern feed|rdf|rss|rss2|atom lenker"

#: modules/components/general-feed.php:49
msgid "Remove feed|rdf|rss|rss2|atom links within head. Also block such content functionality."
msgstr "Fjern feed|rdf|rss|rss2|atom lenker i head. Blokker også slik innholdsfunksjonalitet."

#: modules/components/general-feed.php:53
msgid "A feed is a function of special software that allows feedreaders to access a site, automatically looking for new content and then posting the information about new content and updates to another site. This provides a way for users to keep up with the latest and hottest information posted on different blogging sites."
msgstr "En feed er en funksjon i spesiell programvare som lar feed-lesere få tilgang til et nettsted, automatisk søke etter nytt innhold og deretter poste informasjon om nytt innhold og oppdateringer til et annet nettsted. Dette gir en måte for brukere å holde seg oppdatert med den siste og heteste informasjonen som er postet på forskjellige bloggnettsteder."

#: modules/components/general-feed.php:54
msgid "There are several different kinds of feeds, read by different feedreaders. Some feeds include RSS (alternately defined as 'Rich Site Summary' or 'Really Simple Syndication'), Atom or RDF files.."
msgstr "Det finnes flere forskjellige typer feeds, lest av forskjellige feed-lesere. Noen feeds inkluderer RSS (alternativt definert som 'Rich Site Summary' eller 'Really Simple Syndication'), Atom eller RDF-filer.."

#: modules/components/general-feed.php:55 modules/components/general-meta.php:239 modules/components/general-meta.php:277 modules/components/general-meta.php:297 modules/components/general-meta.php:317 modules/components/general-meta.php:338 modules/components/general-meta.php:358 modules/components/general-scripts.php:46
msgid "Sample tag:"
msgstr "Eksempel-tagg:"

#: modules/components/general-feed.php:57
msgid "Set this option to Yes also disable the feed service."
msgstr "Sett dette alternativet til Ja for også å deaktivere feed-tjenesten."

#: modules/components/general-feed.php:70 modules/components/general-feed.php:74
msgid "Block feed|rdf|rss|rss2|atom links"
msgstr "Blokker feed|rdf|rss|rss2|atom lenker"

#: modules/components/general-feed.php:71
msgid "Block default feed|rdf|rss|rss2|atom links."
msgstr "Blokker standard feed|rdf|rss|rss2|atom lenker."

#: modules/components/general-feed.php:75
msgid "Block access to any of default feed|rdf|rss|rss2|atom links."
msgstr "Blokker tilgang til noen av standard feed|rdf|rss|rss2|atom lenker."

#: modules/components/general-headers.php:89
msgid "Remove Link Header being set as default by WordPress which outputs the site JSON url."
msgstr "Fjern Link Header som er satt som standard av WordPress og som viser nettstedets JSON-adresse."

#: modules/components/general-headers.php:93
msgid "HTTP header fields are components of the header section of a request and response messages in the Hypertext Transfer Protocol (HTTP). They define the operating parameters of an HTTP transaction."
msgstr "HTTP-header-felt er komponenter i header-delen av forespørsels- og responsmeldinger i Hypertext Transfer Protocol (HTTP). De definerer operasjonsparametrene for en HTTP-transaksjon."

#: modules/components/general-headers.php:94 modules/components/general-headers.php:113
msgid "Sample header:"
msgstr "Eksempel-header:"

#: modules/components/general-headers.php:108 modules/components/general-headers.php:112
msgid "Remove X-Powered-By Header"
msgstr "Fjern X-Powered-By Header"

#: modules/components/general-headers.php:109
msgid "Remove X-Powered-By Header if being set."
msgstr "Fjern X-Powered-By Header hvis den er satt."

#: modules/components/general-headers.php:127 modules/components/general-headers.php:131
msgid "Remove X-Pingback Header"
msgstr "Fjern X-Pingback Header"

#: modules/components/general-headers.php:128
msgid "Remove X-Pingback Header if being set."
msgstr "Fjern X-Pingback Header hvis den er satt."

#: modules/components/general-headers.php:132
msgid "Pingback is one of four types of linkback methods for Web authors to request notification when somebody links to one of their documents. This enables authors to keep track of who is linking to, or referring to their articles. Pingback-enabled resources must either use an X-Pingback header or contain a element to the XML-RPC script."
msgstr "Pingback er en av fire typer linkback-metoder for web-forfattere for å be om varsling når noen lenker til et av deres dokumenter. Dette lar forfattere holde oversikt over hvem som lenker til eller refererer til artiklene deres. Pingback-aktiverte ressurser må enten bruke en X-Pingback-header eller inneholde et element til XML-RPC-skriptet."

#: modules/components/general-headers.php:145 modules/components/general-headers.php:149
msgid "Remove Custom Header"
msgstr "Fjern egendefinert header"

#: modules/components/general-headers.php:146
msgid "Remove a Custom Header if being set. "
msgstr "Fjern en egendefinert header hvis den er satt. "

#: modules/components/general-headers.php:150
msgid "Custom HTTP headers are commonly meant to provide additional information that may be pertinent to a web developer, or for troubleshooting purposes. These headers often begin with <code>X-</code>"
msgstr "Egendefinerte HTTP-headere er vanligvis ment å gi ytterligere informasjon som kan være relevant for en webutvikler, eller for feilsøkingsformål. Disse headerne starter ofte med <code>X-</code>"

#: modules/components/general-headers.php:151
msgid "Use with caution, removing specific headers produce malfunction to the site. Generally all headers which stats with X are safe to remove."
msgstr "Bruk med forsiktighet, fjerning av spesifikke headere kan forårsake funksjonsfeil på nettstedet. Generelt er alle headere som starter med X trygge å fjerne."

#: modules/components/general-headers.php:159 modules/components/general-headers.php:163
msgid "Remove Server Signature"
msgstr "Fjern serversignatur"

#: modules/components/general-headers.php:160
msgid "Remove the Server Signature. "
msgstr "Fjern serversignaturen. "

#: modules/components/general-headers.php:164
msgid "As a default, a server outputs a Server Header which outputs details on used system configuration:"
msgstr "Som standard sender en server ut en Server Header som viser detaljer om brukt systemkonfigurasjon:"

#: modules/components/general-headers.php:166
msgid "This option helps to prevent the details from being shown on the front side. This works for Apache server type and compatibles."
msgstr "Dette alternativet hjelper til med å forhindre at detaljene vises på fronsiden. Dette fungerer for Apache-servertype og kompatible."

#: modules/components/general-html-css-js-replacements.php:57
msgid "Code Replacements"
msgstr "Kodeerstatninger"

#: modules/components/general-html-css-js-replacements.php:62
msgid "This requires the "
msgstr "Dette krever at "

#: modules/components/general-html-css-js-replacements.php:62
msgid " to be Active."
msgstr " er aktiv."

#: modules/components/general-html-css-js-replacements.php:63
msgid "This option applies on the front side to HTML, CSS and JavaScript assets. The replaced and replacement words are case sensitive."
msgstr "Dette alternativet gjelder på fremsiden for HTML-, CSS- og JavaScript-ressurser. De erstattede og erstatningsordene er store/små bokstaver følsomme."

#: modules/components/general-html-css-js-replacements.php:64
msgid "Ensure the Replacement words are not commonly used on the front side or might conflict with existing POST and GET environment values after regex reversal. At least 5 chars word ( only letters ) is required for Replacement also it is recommended to use unusual/random char combinations to avoid conflicts."
msgstr "Sikre at erstatningsordene ikke er vanlig brukt på fremsiden eller kan konfliktere med eksisterende POST- og GET-miljøverdier etter regex-reversering. Minst 5 tegn ord (kun bokstaver) kreves for erstatning, og det anbefales å bruke uvanlige/tilfeldige tegnkombinasjoner for å unngå konflikter."

#: modules/components/general-html-css-js-replacements.php:84
msgid "You are trying to make a replacement for"
msgstr "Du prøver å gjøre en erstatning for"

#: modules/components/general-html-css-js-replacements.php:84
msgid "This requires the additional option "
msgstr "Dette krever det ekstra alternativet "

#: modules/components/general-html-css-js-replacements.php:84
msgid "For more details see"
msgstr "For flere detaljer se"

#: modules/components/general-html-css-js-replacements.php:204 modules/components/general-text-replace.php:152
msgid "Provided replaced word "
msgstr "Oppgitt erstattet ord "

#: modules/components/general-html-css-js-replacements.php:204 modules/components/general-html-css-js-replacements.php:212
msgid "need to be at least 3 chars."
msgstr "må være minst 3 tegn."

#: modules/components/general-html-css-js-replacements.php:212 modules/components/general-html-css-js-replacements.php:225
msgid "Provided replacement word "
msgstr "Oppgitt erstatningsord "

#: modules/components/general-html-css-js-replacements.php:225
msgid "already used."
msgstr "allerede brukt."

#: modules/components/general-html.php:111
msgid "Remove comments from HTML source code."
msgstr "Fjern kommentarer fra HTML-kildekode."

#: modules/components/general-html.php:129
msgid "Minify HTML, Inline Styles, Inline JavaScripts."
msgstr "Minifiser HTML, inline-stiler, inline JavaScripts."

#: modules/components/general-html.php:133
msgid "When you minify HTML it removes the unnecessary characters and lines in the source code. Indentation, comments, empty lines, etc. are not required in HTML. They just make the file easier to read. Cutting out all this unnecessary stuff can shave down your file size considerably. When you minify HTML code on your website, the server will send a much smaller page to the client making your website load quicker."
msgstr "Når du minifiserer HTML fjerner du unødvendige tegn og linjer i kildekoden. Innrykk, kommentarer, tomme linjer, etc. er ikke nødvendig i HTML. De gjør bare filen lettere å lese. Å kutte ut alt dette unødvendige kan betydelig redusere filstørrelsen din. Når du minifiserer HTML-kode på nettstedet ditt, vil serveren sende en mye mindre side til klienten, noe som gjør at nettstedet ditt lastes raskere."

#: modules/components/general-html.php:134
msgid "The Minify component include multiple options:"
msgstr "Minify-komponenten inkluderer flere alternativer:"

#: modules/components/general-html.php:139
msgid "Minify JavaScript might produce errors for specific plugins."
msgstr "Minifisering av JavaScript kan forårsake feil for spesifikke plugins."

#: modules/components/general-html.php:145
msgid "Html"
msgstr "Html"

#: modules/components/general-html.php:146
msgid "Html & Css"
msgstr "Html & Css"

#: modules/components/general-html.php:147
msgid "Html & JavaScript"
msgstr "Html & JavaScript"

#: modules/components/general-html.php:148 modules/components/rewrite-json-rest.php:196
msgid "All"
msgstr "Alle"

#: modules/components/general-html.php:155 modules/components/general-html.php:159
msgid "Remove general classes from body tag"
msgstr "Fjern generelle klasser fra body-tagg"

#: modules/components/general-html.php:156 modules/components/general-html.php:160
msgid "Remove general classes from body tag."
msgstr "Fjern generelle klasser fra body-tagg."

#: modules/components/general-html.php:161 modules/components/general-html.php:181 modules/components/general-html.php:202 modules/components/general-html.php:221 modules/components/general-html.php:239
msgid "This can produce layout issues with certain themes, if something break this should be turned off."
msgstr "Dette kan forårsake layout-problemer med visse temaer, hvis noe bryter skal dette skrus av."

#: modules/components/general-html.php:175 modules/components/general-html.php:179
msgid "Remove ID from Menu items"
msgstr "Fjern ID fra menyelementer"

#: modules/components/general-html.php:176 modules/components/general-html.php:197
msgid "Remove class attribute from all menu items."
msgstr "Fjern class-attributt fra alle menyelementer."

#: modules/components/general-html.php:180 modules/components/general-html.php:201
msgid "Remove class attribute from all menu items. Any classes which include a 'current' prefix or contain 'has-children' will be preserved."
msgstr "Fjern class-attributt fra alle menyelementer. Eventuelle klasser som inkluderer et 'current' prefiks eller inneholder 'has-children' vil bli bevart."

#: modules/components/general-html.php:196 modules/components/general-html.php:200
msgid "Remove class from Menu items"
msgstr "Fjern klasse fra menyelementer"

#: modules/components/general-html.php:215 modules/components/general-html.php:219
msgid "Remove general classes from post"
msgstr "Fjern generelle klasser fra innlegg"

#: modules/components/general-html.php:216 modules/components/general-html.php:220
msgid "Remove general classes from post."
msgstr "Fjern generelle klasser fra innlegg."

#: modules/components/general-html.php:233 modules/components/general-html.php:237
msgid "Remove general classes from images"
msgstr "Fjern generelle klasser fra bilder"

#: modules/components/general-html.php:234 modules/components/general-html.php:238
msgid "Remove general classes from media tags."
msgstr "Fjern generelle klasser fra media-tagger."

#: modules/components/general-js-combine.php:132 modules/components/general-js-combine.php:136
msgid "JavaScript Post-Processing type"
msgstr "JavaScript-etterbehandlingstype"

#: modules/components/general-js-combine.php:133
msgid "All assets and inline JavaScript will be post-processed, using Combine or In-place technique."
msgstr "Alle ressurser og inline JavaScript vil bli etterbehandlet, ved bruk av Kombiner eller På plass-teknikk."

#: modules/components/general-js-combine.php:137
msgid "The module incorporates a Post-Processing engine specifically designed to offer supplementary processing capabilities for JavaScript assets and datab locks, for hiding and white labeling. The activation of this engine is essential for enabling the Replacements functionality."
msgstr "Modulen inneholder en etterbehandlingsmotor spesielt designet for å tilby supplerende behandlingsevner for JavaScript-ressurser og datablokker, for skjuling og white labeling. Aktivering av denne motoren er essensiell for å aktivere Erstatningsfunksjonaliteten."

#: modules/components/general-js-combine.php:139
msgid "There are 4 types of processing options:"
msgstr "Det er 4 typer behandlingsalternativer:"

#: modules/components/general-js-combine.php:140
msgid "<b>Combine</b>: Merge all JavaScript code in (usually) 2 files, one in the header and another in the footer."
msgstr "<b>Kombiner</b>: Slå sammen all JavaScript-kode i (vanligvis) 2 filer, en i toppen og en annen i bunnteksten."

#: modules/components/general-js-combine.php:141
msgid "<b>Combine & Encode Inline</b>:Merge all JavaScript code in (usually) 2 files, one in the header and another in the footer. Additionally, the Inline JavaScript code will be base64 encoded and placed in the same spot. "
msgstr "<b>Kombiner & Koder inline</b>: Slå sammen all JavaScript-kode i (vanligvis) 2 filer, en i toppen og en annen i bunnteksten. I tillegg vil inline JavaScript-koden bli base64-kodet og plassert på samme sted. "

#: modules/components/general-js-combine.php:142
msgid "<b>In Place</b>: All JavaScript code will be processed and the results will be placed in the same spot. Any InLine JavaScript code will be processed and saved into a cached file."
msgstr "<b>På plass</b>: All JavaScript-kode vil bli behandlet og resultatene vil bli plassert på samme sted. Eventuell inline JavaScript-kode vil bli behandlet og lagret i en hurtigbufferfil."

#: modules/components/general-js-combine.php:143
msgid "<b>In Place & Encode Inline</b>: All JavaScript code will be processed and the results will be placed in the same spot. Additionally, the Inline JavaScript code will be base64 encoded and placed in the same spot. "
msgstr "<b>På plass & Koder inline</b>: All JavaScript-kode vil bli behandlet og resultatene vil bli plassert på samme sted. I tillegg vil inline JavaScript-koden bli base64-kodet og plassert på samme sted. "

#: modules/components/general-js-combine.php:145
msgid "If the site contains JavaScript errors, <b>In Place / In Place & Encode Inline</b> processing type should be selected instead <b>Combine / Combine & Encode Inline</b>, or the faulty code will break the site."
msgstr "Hvis nettstedet inneholder JavaScript-feil, bør behandlingstypen <b>På plass / På plass & Koder inline</b> velges i stedet for <b>Kombiner / Kombiner & Koder inline</b>, ellers vil den feilaktige koden ødelegge nettstedet."

#: modules/components/general-js-combine.php:157
msgid "Combine & Encode Inline"
msgstr "Kombiner & koder inline"

#: modules/components/general-js-combine.php:167
msgid "Remove all Comments from processed JavaScript files."
msgstr "Fjern alle kommentarer fra behandlede JavaScript-filer."

#: modules/components/general-js-combine.php:171
msgid "This option require JavaScript Combine/In Place Code to be active."
msgstr "Dette alternativet krever at JavaScript Combine/In Place Code er aktivt."

#: modules/components/general-js-combine.php:172
msgid "Remove all Comments from processed JavaScript files, which usualy specify Plugins Names."
msgstr "Fjern alle kommentarer fra behandlede JavaScript-filer, som vanligvis spesifiserer plugin-navn."

#: modules/components/general-js-combine.php:186 modules/components/general-js-combine.php:190
msgid "Defer processed JavaScript"
msgstr "Utsett behandlet JavaScript"

#: modules/components/general-js-combine.php:187
msgid "When a script is defered, the browser execute it when the page has finished parsing."
msgstr "Når et skript er utsatt, utfører nettleseren det når siden er ferdig analysert."

#: modules/components/general-js-combine.php:191
msgid "This is an advanced option mainly for SEO adjustments. All combined JavaScript assets will be deferred."
msgstr "Dette er et avansert alternativ hovedsakelig for SEO-justeringer. Alle kombinerte JavaScript-ressurser vil bli utsatt."

#: modules/components/general-js-combine.php:191 modules/components/general-js-combine.php:213
msgid "More detils about defer at"
msgstr "Flere detaljer om utsettelse på"

#: modules/components/general-js-combine.php:192
msgid "The jQuery asset will be left as is, to provide support for any on-line JavaScript code."
msgstr "jQuery-ressursen vil bli latt som den er, for å gi støtte for eventuell online JavaScript-kode."

#: modules/components/general-js-combine.php:193
msgid "Using the Exclude script from JavaScript Combine along with this option may produce isues."
msgstr "Bruk av Ekskluder skript fra JavaScript Combine sammen med dette alternativet kan forårsake problemer."

#: modules/components/general-js-combine.php:194
msgid "Use with caution, if any front-site feature or appearance appears to be broken, disable this option."
msgstr "Bruk med forsiktighet, hvis noen funksjoner eller utseende på fremsiden ser ut til å være ødelagt, deaktiver dette alternativet."

#: modules/components/general-js-combine.php:208 modules/components/general-js-combine.php:212
msgid "Defer a JavaScript asset"
msgstr "Utsett en JavaScript-ressurs"

#: modules/components/general-js-combine.php:209
msgid "When a script is defered, it specifies that the script is executed when the page has finished parsing."
msgstr "Når et skript er utsatt, spesifiserer det at skriptet utføres når siden er ferdig analysert."

#: modules/components/general-js-combine.php:213
msgid "This is an advanced option mainly for SEO adjustments, specify any script which will be excluded from JavaScript Combine, also will be deferred."
msgstr "Dette er et avansert alternativ hovedsakelig for SEO-justeringer, spesifiser eventuelle skript som vil bli ekskludert fra JavaScript Combine, og også vil bli utsatt."

#: modules/components/general-js-combine.php:214
msgid "The JavaScript code will still be processed while using Replacements."
msgstr "JavaScript-koden vil fortsatt bli behandlet mens Erstatninger brukes."

#: modules/components/general-js-combine.php:215
msgid "Use only script name e.g. <code>mediaelement-and-player.min.js</code>, one per row. If need to use async instead, specify the attribute after the file name e.g. jquery-migrate.min.js async"
msgstr "Bruk kun skriptnavn f.eks. <code>mediaelement-and-player.min.js</code>, en per rad. Hvis du trenger å bruke async i stedet, spesifiser attributtet etter filnavnet f.eks. jquery-migrate.min.js async"

#: modules/components/general-js-combine.php:216
msgid "Use with caution, only certain scripts can be deferred, otherwise specific front-site features and appearance can break."
msgstr "Bruk med forsiktighet, bare visse skript kan utsettes, ellers kan spesifikke funksjoner og utseende på fremsiden bryte."

#: modules/components/general-js-combine.php:224 modules/components/general-js-combine.php:228
msgid "Exclude script from JavaScript processing"
msgstr "Ekskluder skript fra JavaScript-behandling"

#: modules/components/general-js-combine.php:225
msgid "Specify any script which will be excluded when using JavaScript Combine."
msgstr "Spesifiser eventuelle skript som vil bli ekskludert ved bruk av JavaScript-kombinasjon."

#: modules/components/general-js-combine.php:229
msgid "Use only script name e.g. mediaelement-and-player.min.js, one per row."
msgstr "Bruk kun skriptnavn f.eks. mediaelement-and-player.min.js, en per rad."

#: modules/components/general-js-combine.php:230
msgid "Excluding from Combine and using Replacements, there will be no substitutions on this code which can break the layout and specific front-side functionality."
msgstr "Ved ekskludering fra Kombiner og bruk av Erstatninger, vil det ikke være noen erstatninger på denne koden som kan ødelegge layouten og spesifikke funksjoner på fremsiden."

#: modules/components/general-js-combine.php:238
msgid "Exclude JavaScript Block from processing"
msgstr "Ekskluder JavaScript-blokk fra behandling"

#: modules/components/general-js-combine.php:243
msgid "Specify partial JavaScript code block to be excluded from processing. Use a full line or part of it (not individual words) to avoid matching other JavaScript code."
msgstr "Spesifiser delvis JavaScript-kodeblokk som skal ekskluderes fra behandling. Bruk en full linje eller del av den (ikke enkelte ord) for å unngå å matche annen JavaScript-kode."

#: modules/components/general-js-combine.php:244
msgid "Excluding from Combine and using processing, there will be no substitutions on this code which can break the layout and specific front-side functionality."
msgstr "Ved ekskludering fra Kombiner og bruk av behandling, vil det ikke være noen erstatninger på denne koden som kan ødelegge layouten og spesifikke funksjoner på fremsiden."

#: modules/components/general-meta.php:163 modules/components/general-meta.php:183
msgid "Tag example:"
msgstr "Tagg-eksempel:"

#: modules/components/general-meta.php:197 modules/components/general-meta.php:201
msgid "Remove DNS Prefetch"
msgstr "Fjern DNS Prefetch"

#: modules/components/general-meta.php:198
msgid "Remove DNS Prefetch meta generated tag."
msgstr "Fjern DNS Prefetch meta-generert tagg."

#: modules/components/general-meta.php:202
msgid "DNS prefetching allows you to resolve domain names (perform a DNS lookup in the background) before a user clicks on a link, which in turn can help improve performance."
msgstr "DNS-prefetching lar deg løse domenenavn (utføre en DNS-oppslag i bakgrunnen) før en bruker klikker på en lenke, noe som igjen kan hjelpe til med å forbedre ytelsen."

#: modules/components/general-meta.php:215 modules/components/general-meta.php:219
msgid "Remove Resource Hints"
msgstr "Fjern ressurs-hints"

#: modules/components/general-meta.php:216
msgid "Remove Resource Hints meta generated tags within head (eg dns-prefetch, preconnect)."
msgstr "Fjern Resource Hints meta-genererte tagger i head (f.eks. dns-prefetch, preconnect)."

#: modules/components/general-meta.php:220
msgid "DNS prefetching and preconect allows you to resolve domain names before a user clicks on a link, which in turn can help and slightly improve performance."
msgstr "DNS-prefetching og preconnect lar deg løse domenenavn før en bruker klikker på en lenke, noe som igjen kan hjelpe til og forbedre ytelsen litt."

#: modules/components/general-meta.php:234
msgid "Remove the wlwmanifest tag within head."
msgstr "Fjern wlwmanifest-taggen i head."

#: modules/components/general-meta.php:238
msgid "The above link is actually used by Windows Live Writer. If you don't te application, this is just unnecessary code."
msgstr "Ovenstående lenke brukes faktisk av Windows Live Writer. Hvis du ikke bruker applikasjonen, er dette bare unødvendig kode."

#: modules/components/general-meta.php:253 modules/components/general-meta.php:257
msgid "Remove feed_links Meta"
msgstr "Fjern feed_links Meta"

#: modules/components/general-meta.php:254
msgid "Remove the feed_links tag within head."
msgstr "Fjern feed_links-taggen i head."

#: modules/components/general-meta.php:258
msgid "This option disable all feed links outputed in the page HTML head."
msgstr "Dette alternativet deaktiverer alle feed-linker i sidens HTML-head."

#: modules/components/general-meta.php:271 modules/components/general-meta.php:275 modules/components/rewrite-json-rest.php:244 modules/components/rewrite-json-rest.php:248
msgid "Disable output the REST API link tag into page header"
msgstr "Deaktiver utdata av REST API lenke-tagg til sideheader"

#: modules/components/general-meta.php:272 modules/components/rewrite-json-rest.php:245
msgid "By default a REST API link tag is being append to HTML."
msgstr "Som standard legges en REST API lenke-tagg til HTML."

#: modules/components/general-meta.php:276
msgid "This option disable the tag output with the JSON API url."
msgstr "Dette alternativet deaktiverer tagg-utdata med JSON API-adressen."

#: modules/components/general-meta.php:291 modules/components/general-meta.php:295
msgid "Remove rsd_link Meta"
msgstr "Fjern rsd_link Meta"

#: modules/components/general-meta.php:292
msgid "Remove the rsd_link tag within head."
msgstr "Fjern rsd_link-taggen i head."

#: modules/components/general-meta.php:296
msgid "This helps to hide the link to the Really Simple Discovery service endpoint."
msgstr "Dette hjelper til med å skjule lenken til Really Simple Discovery-tjenesten."

#: modules/components/general-meta.php:311 modules/components/general-meta.php:315
msgid "Remove adjacent_posts_rel Meta"
msgstr "Fjern adjacent_posts_rel Meta"

#: modules/components/general-meta.php:312
msgid "Remove the adjacent_posts_rel tag within head."
msgstr "Fjern adjacent_posts_rel-taggen i head."

#: modules/components/general-meta.php:316
msgid "This helps to hide the post adjacent tags."
msgstr "Dette hjelper til med å skjule de tilstøtende innleggstaggene."

#: modules/components/general-meta.php:332 modules/components/general-meta.php:336
msgid "Remove profile link"
msgstr "Fjern profil-lenke"

#: modules/components/general-meta.php:333
msgid "Remove profile link meta tag within head."
msgstr "Fjern profil-lenke meta-tagg i head."

#: modules/components/general-meta.php:337
msgid "This helps to hide the profile tags."
msgstr "Dette hjelper til med å skjule profil-taggene."

#: modules/components/general-meta.php:352 modules/components/general-meta.php:356
msgid "Remove canonical link"
msgstr "Fjern kanonisk lenke"

#: modules/components/general-meta.php:353
msgid "Remove canonical link meta tag within head."
msgstr "Fjern kanonisk lenke meta-tagg i head."

#: modules/components/general-meta.php:357
msgid "The rel=canonical element, often called the 'canonical link', is an HTML element that helps webmasters prevent duplicate content issues. It does this by specifying the 'canonical URL', the 'preferred' version of a web page - the original source, even."
msgstr "rel=canonical-elementet, ofte kalt 'kanonisk lenke', er et HTML-element som hjelper webmastere å forhindre duplisert innholdsproblemer. Det gjør dette ved å spesifisere 'kanonisk URL', den 'foretrukne' versjonen av en nettside - den opprinnelige kilden, til og med."

#: modules/components/general-oembed.php:33 modules/components/general-oembed.php:36
msgid "Remove Oembed"
msgstr "Fjern Oembed"

#: modules/components/general-oembed.php:34
msgid "Remove Oembed tags from header."
msgstr "Fjern Oembed-tagger fra header."

#: modules/components/general-oembed.php:37
msgid "WordPress oEmbed recognizes URLs to a number of services, for example Youtube videos. When WordPress sees the URL it will connect to the external service (Youtube) and ask for the relevant HTML code to embed the video into the page or post."
msgstr "WordPress oEmbed gjenkjenner URL-er til en rekke tjenester, for eksempel Youtube-videoer. Når WordPress ser URL-en vil den koble til den eksterne tjenesten (Youtube) og be om den relevante HTML-koden for å bygge inn videoen i siden eller innlegget."

#: modules/components/general-scripts.php:40 modules/components/general-scripts.php:43 modules/components/general-styles.php:39 modules/components/general-styles.php:43
msgid "Remove Version"
msgstr "Fjern versjon"

#: modules/components/general-scripts.php:41
msgid "Remove version number from enqueued script files."
msgstr "Fjern versjonsnummer fra køede skriptfiler."

#: modules/components/general-scripts.php:44
msgid "This provide a method to remove the JavaScript version number which is being append at the end of every script file. Generally this is intended to be a plain information upon the JavaScript code version, however not being used within any functionality or code run."
msgstr "Dette gir en metode for å fjerne JavaScript-versjonsnummeret som legges til på slutten av hver skriptfil. Generelt er dette ment å være vanlig informasjon om JavaScript-kodeversjonen, men den brukes ikke i noen funksjonalitet eller kodekjøring."

#: modules/components/general-scripts.php:45
msgid "Keeping version number for scripts provide additional information to hackers which try to identify specific JavaScript code and version which know as being vulnerable."
msgstr "Å beholde versjonsnummer for skript gir ekstra informasjon til hackere som prøver å identifisere spesifikk JavaScript-kode og versjon som er kjent for å være sårbar."

#: modules/components/general-scripts.php:48
msgid "Once option set to Yes the tag becomes:"
msgstr "Når alternativet er satt til Ja blir taggen:"

#: modules/components/general-scripts.php:61 modules/components/general-scripts.php:64
msgid "Remove ID from script tag"
msgstr "Fjern ID fra skript-tagg"

#: modules/components/general-scripts.php:62
msgid "Remove ID attribute from all script tags."
msgstr "Fjern ID-attributt fra alle skript-tagger."

#: modules/components/general-scripts.php:65
msgid "This provide a method to remove the Script ID attribute which generally has no usage."
msgstr "Dette gir en metode for å fjerne Script ID-attributtet som generelt ikke har noen bruk."

#: modules/components/general-styles.php:40
msgid "Remove version number from enqueued style files."
msgstr "Fjern versjonsnummer fra køede stilfiler."

#: modules/components/general-styles.php:44
msgid "This provide a method to remove the Style file version number which is being append at the end of every style tag. Generally this is intended to be a plain information upon the style code version, however not being used within any functionality or code run."
msgstr "Dette gir en metode for å fjerne stilfilens versjonsnummer som legges til på slutten av hver stil-tagg. Generelt er dette ment å være vanlig informasjon om stilkodeversjonen, men den brukes ikke i noen funksjonalitet eller kodekjøring."

#: modules/components/general-styles.php:45
msgid "Keeping version number for styles provide additional information to hackers which try to identify specific code and version which know as being vulnerable."
msgstr "Å beholde versjonsnummer for stiler gir ekstra informasjon til hackere som prøver å identifisere spesifikk kode og versjon som er kjent for å være sårbar."

#: modules/components/general-styles.php:58 modules/components/general-styles.php:62
msgid "Remove ID from link tags"
msgstr "Fjern ID fra lenke-tagger"

#: modules/components/general-styles.php:59
msgid "Remove ID attribute from all link tags which include a stylesheet."
msgstr "Fjern ID-attributt fra alle lenke-tagger som inkluderer en stilark."

#: modules/components/general-styles.php:63
msgid "This provide a method to remove the Style file ID attribute which generally has no usage."
msgstr "Dette gir en metode for å fjerne stilfilens ID-attributt som generelt ikke har noen bruk."

#: modules/components/general-text-replace.php:42
msgid "Text Replace"
msgstr "Teksterstatning"

#: modules/components/general-text-replace.php:43
msgid "Arbitrary text replacement from HTML."
msgstr "Vilkårlig teksterstatning fra HTML."

#: modules/components/general-text-replace.php:47
msgid "Arbitrary text replacement from HTML. The substitution is case-sensitive, also spaces in front or at the end are being used. The replacements occur only on front-side."
msgstr "Vilkårlig teksterstatning fra HTML. Erstatningen er store/små bokstaver følsom, og mellomrom foran eller på slutten brukes. Erstatningene skjer kun på fremsiden."

#: modules/components/general-text-replace.php:48
msgid "This can produce layout issues, use with caution. Ensure this is used with long texts or html blocks, which allows exact and focused replacements. For individual words, the CSS / JavaScript Replacements function should be considered."
msgstr "Dette kan forårsake layout-problemer, bruk med forsiktighet. Sikre at dette brukes med lange tekster eller html-blokker, som tillater nøyaktige og fokuserte erstatninger. For enkelte ord bør CSS / JavaScript Erstatnings-funksjonen vurderes."

#: modules/components/general-text-replace.php:152
msgid "need to be at least 5 chars."
msgstr "må være minst 5 tegn."

#: modules/components/general-tobots-txt.php:37 modules/components/general-tobots-txt.php:41
msgid "Disable admin url within Robots.txt"
msgstr "Deaktiver admin-adresse i Robots.txt"

#: modules/components/general-tobots-txt.php:38
msgid "Disable any admin url which is being automatically generated by WordPress when called robots.txt."
msgstr "Deaktiver eventuelle admin-adresser som automatisk genereres av WordPress når robots.txt kalles."

#: modules/components/general-tobots-txt.php:42
msgid "The robots.txt file plays a major role in search engine ranking. It blocks search engine bots and helps index and crawl important parts of your site."
msgstr "robots.txt-filen spiller en stor rolle i søkemotorrangering. Den blokkerer søkemotorboter og hjelper til med å indeksere og gjennomsøke viktige deler av nettstedet ditt."

#: modules/components/general-tobots-txt.php:43
msgid "As default the robots.txt also includes an allow clause to admin URL and admin-ajax.php url. Once customized those areas, the new slugs might not want to be show to anyone. Turn this option to Yes removed any reference to new wp-admin and admin-ajax.php."
msgstr "Som standard inkluderer robots.txt også en allow-klausul for admin-URL og admin-ajax.php URL. Når disse områdene er tilpasset, vil man kanskje ikke vise de nye slug-ene til noen. Sett dette alternativet til Ja for å fjerne alle referanser til ny wp-admin og admin-ajax.php."

#: modules/components/general-tobots-txt.php:44
msgid "Sample robots.txt url:"
msgstr "Eksempel på robots.txt-adresse:"

#: modules/components/general-user-interactions.php:175 modules/components/general-user-interactions.php:179
msgid "Disable user interaction function"
msgstr "Deaktiver brukerinteraksjonsfunksjon"

#: modules/components/general-user-interactions.php:176
msgid "Disable the following user interaction functions for the specified roles."
msgstr "Deaktiver følgende brukerinteraksjonsfunksjoner for de angitte rollene."

#: modules/components/general-user-interactions.php:180
msgid "Disable all user interaction functions for the specified roles."
msgstr "Deaktiver alle brukerinteraksjonsfunksjoner for de angitte rollene."

#: modules/components/general-user-interactions.php:181
msgid "This is useful, to avoid interfering with the logged-in user actions, like page Edit with an editor ( e.g. Elementor ), on the front-side."
msgstr "Dette er nyttig for å unngå å forstyrre de innloggede brukerens handlinger, som side-redigering med en editor (f.eks. Elementor), på fremsiden."

#: modules/components/general-user-interactions.php:189
msgid "Disable Mouse right click"
msgstr "Deaktiver høyreklikk på mus"

#: modules/components/general-user-interactions.php:190
msgid "Disable mouse right click on your pages."
msgstr "Deaktiver høyreklikk på mus på sidene dine."

#: modules/components/general-user-interactions.php:193
msgid "Disable right Mouse click"
msgstr "Deaktiver høyre museklikk"

#: modules/components/general-user-interactions.php:194
msgid "Disable right mouse click on your pages can protect your site content from being copied."
msgstr "Deaktivering av høyre museklikk på sidene dine kan beskytte innholdet på nettstedet ditt mot å bli kopiert."

#: modules/components/general-user-interactions.php:195
msgid "Some plugins, mainly visual editors, use mouse right-click, if use such code this option should be set to No."
msgstr "Noen plugins, hovedsakelig visuelle editorer, bruker høyreklikk på mus, hvis du bruker slik kode bør dette alternativet settes til Nei."

#: modules/components/general-user-interactions.php:208 modules/components/general-user-interactions.php:212
msgid "Disable Text Selection"
msgstr "Deaktiver tekstutvalg"

#: modules/components/general-user-interactions.php:209
msgid "Disable Text Selection on your pages."
msgstr "Deaktiver tekstutvalg på sidene dine."

#: modules/components/general-user-interactions.php:213
msgid "When the option is active, the text selection on pages is not possible."
msgstr "Når alternativet er aktivt, er tekstutvalg på sider ikke mulig."

#: modules/components/general-user-interactions.php:214
msgid "This is useful when don't want the site texts to be copied."
msgstr "Dette er nyttig når man ikke vil at nettstedstekster skal kopieres."

#: modules/components/general-user-interactions.php:227 modules/components/general-user-interactions.php:231
msgid "Disable Copy"
msgstr "Deaktiver kopiering"

#: modules/components/general-user-interactions.php:228
msgid "Disable text copy on your pages."
msgstr "Deaktiver tekstkopiering på sidene dine."

#: modules/components/general-user-interactions.php:232
msgid "Through this option, the browser copy functionality is disabled."
msgstr "Gjennom dette alternativet deaktiveres nettleserens kopieringsfunksjonalitet."

#: modules/components/general-user-interactions.php:245 modules/components/general-user-interactions.php:249
msgid "Disable Cut"
msgstr "Deaktiver klipp"

#: modules/components/general-user-interactions.php:246
msgid "Disable text cut on your pages."
msgstr "Deaktiver tekstklipp på sidene dine."

#: modules/components/general-user-interactions.php:250
msgid "Through this option, the browser cut functionality is disabled."
msgstr "Gjennom dette alternativet deaktiveres nettleserens klippefunksjonalitet."

#: modules/components/general-user-interactions.php:263 modules/components/general-user-interactions.php:267
msgid "Disable Paste"
msgstr "Deaktiver lim inn"

#: modules/components/general-user-interactions.php:264
msgid "Disable text paste on your pages."
msgstr "Deaktiver tekstliming på sidene dine."

#: modules/components/general-user-interactions.php:268
msgid "Through this option, the browser paste functionality is disabled."
msgstr "Gjennom dette alternativet deaktiveres nettleserens lim inn-funksjonalitet."

#: modules/components/general-user-interactions.php:281 modules/components/general-user-interactions.php:285
msgid "Disable Print"
msgstr "Deaktiver utskrift"

#: modules/components/general-user-interactions.php:282
msgid "Disable Print function on your pages."
msgstr "Deaktiver utskriftsfunksjon på sidene dine."

#: modules/components/general-user-interactions.php:286
msgid "When using the option, the browser Print dialogue is not available so a site print is disabled."
msgstr "Ved bruk av alternativet er ikke nettleserens utskriftsdialog tilgjengelig, så utskrift av nettstedet er deaktivert."

#: modules/components/general-user-interactions.php:299 modules/components/general-user-interactions.php:303
msgid "Disable Print Screen"
msgstr "Deaktiver skjermutskrift"

#: modules/components/general-user-interactions.php:300
msgid "Disable Print Screen function on your pages."
msgstr "Deaktiver skjermutskriftsfunksjon på sidene dine."

#: modules/components/general-user-interactions.php:304
msgid "The Print Screen function captures an image of the entire screen and copies it to the Clipboard in the computer's memory."
msgstr "Skjermutskriftsfunksjonen tar et bilde av hele skjermen og kopierer det til utklippstavlen i datamaskinens minne."

#: modules/components/general-user-interactions.php:305
msgid "If the functionality is not required, the option helps to disable it."
msgstr "Hvis funksjonaliteten ikke er nødvendig, hjelper alternativet til å deaktivere den."

#: modules/components/general-user-interactions.php:318 modules/components/general-user-interactions.php:322
msgid "Disable Developer Tools"
msgstr "Deaktiver utviklerverktøy"

#: modules/components/general-user-interactions.php:319
msgid "Disable the browser Developr Tools on your pages."
msgstr "Deaktiver nettleserens utviklerverktøy på sidene dine."

#: modules/components/general-user-interactions.php:323
msgid "Every modern web browser includes a powerful tool called Developer Tools. Through the application, a user can inspect currently-loaded HTML, CSS and JavaScript."
msgstr "Alle moderne nettlesere inkluderer et kraftig verktøy kalt Utviklerverktøy. Gjennom applikasjonen kan en bruker inspisere for tiden lastet HTML, CSS og JavaScript."

#: modules/components/general-user-interactions.php:324
msgid "To prevent the user from deeply checking into your site architecture, the functionality can be disabled using this option. "
msgstr "For å forhindre brukeren fra å dykke dypt inn i nettstedets arkitektur, kan funksjonaliteten deaktiveres ved hjelp av dette alternativet. "

#: modules/components/general-user-interactions.php:337 modules/components/general-user-interactions.php:341
msgid "Disable View Source"
msgstr "Deaktiver vis kilde"

#: modules/components/general-user-interactions.php:338
msgid "Disable the browser view source on your pages."
msgstr "Deaktiver nettleserens vis kilde på sidene dine."

#: modules/components/general-user-interactions.php:342
msgid "The page source is an HTML set of tags code. An HTML tag is an element that, along with CSS and JavaScript, tells the Web browser what to do and how to display the text and images."
msgstr "Sidekilden er et HTML-sett med tagg-kode. En HTML-tagg er et element som, sammen med CSS og JavaScript, forteller nettleseren hva den skal gjøre og hvordan den skal vise teksten og bildene."

#: modules/components/general-user-interactions.php:355 modules/components/general-user-interactions.php:359
msgid "Disable Drag / Drop"
msgstr "Deaktiver dra og slipp"

#: modules/components/general-user-interactions.php:356
msgid "Disable the browser drag and drop for images on your pages."
msgstr "Deaktiver nettleserens dra og slipp for bilder på sidene dine."

#: modules/components/general-user-interactions.php:360
msgid "The Drag and Drop operation describes the action o selecting an object or text on the page and moving it to a different area."
msgstr "Dra og slipp-operasjonen beskriver handlingen med å velge et objekt eller tekst på siden og flytte den til et annet område."

#: modules/components/general-wp_die.php:41 modules/components/general-wp_die.php:44
msgid "WP Die Layout"
msgstr "WP Die Layout"

#: modules/components/general-wp_die.php:42
msgid "On WP Die event, replace the default layout with a custom one."
msgstr "Ved WP Die-hendelse, erstatt standardlayouten med en egendefinert."

#: modules/components/general-wp_die.php:45
msgid "WordPress provides a default error screen, which displays a standardized layout for various error or notice situations. By default, the layout consists of a simple message with minimal styling."
msgstr "WordPress gir en standard feilskjerm, som viser en standardisert layout for forskjellige feil- eller merknadssituasjoner. Som standard består layouten av en enkel melding med minimal styling."

#: modules/components/general-wp_die.php:46
msgid "This is how a default layout appears:"
msgstr "Slik ser en standard layout ut:"

#: modules/components/general-wp_die.php:48
msgid "This option provides a way to change the screen layout with a custom one, that disguises WordPress. The new screen will show up as follows:"
msgstr "Dette alternativet gir en måte å endre skjermlayouten med en egendefinert, som skjuler WordPress. Den nye skjermen vil vises som følger:"

#: modules/components/general-wp_die.php:123
msgid "&laquo; Back"
msgstr "&laquo; Tilbake"

#: modules/components/general-wpemoji.php:42 modules/components/general-wpemoji.php:45
msgid "Disable Emoji"
msgstr "Deaktiver Emoji"

#: modules/components/general-wpemoji.php:43
msgid "Disable the Emoji icon library from being loaded."
msgstr "Deaktiver lasting av Emoji-ikonbiblioteket."

#: modules/components/general-wpemoji.php:46
msgid "Not everyone uses Emoji. Since WordPress loads the dependencies by default, it decreases the overall site speed. Disabling this will remove any code and related resources from being loaded on the front side."
msgstr "Ikke alle bruker Emoji. Siden WordPress laster avhengighetene som standard, reduserer den den generelle nettstedshastigheten. Deaktivering av dette vil fjerne all kode og relaterte ressurser fra å lastes på fremsiden."

#: modules/components/general-wpemoji.php:58 modules/components/general-wpemoji.php:61
msgid "Disable TinyMCE Emoji"
msgstr "Deaktiver TinyMCE Emoji"

#: modules/components/general-wpemoji.php:59
msgid "Disable the TinyMCE Emoji icons library from being loaded into TinyMCE."
msgstr "Deaktiver lasting av TinyMCE Emoji-ikonbiblioteket inn i TinyMCE."

#: modules/components/general-wpemoji.php:62
msgid "Disable TinyMCE Emoji. This is also loaded along with the WordPress default TinyMCE editor, but it can be disabled through this option."
msgstr "Deaktiver TinyMCE Emoji. Dette lastes også sammen med WordPress sin standard TinyMCE-editor, men det kan deaktiveres gjennom dette alternativet."

#: modules/components/login_2fa.php:155
msgid "Unable to create a login nonce."
msgstr "Kan ikke opprette en påloggings-nonce."

#: modules/components/login_2fa.php:260
msgid "You must also complete the setup for the following options before logging in:"
msgstr "Du må også fullføre oppsettet for følgende alternativer før du logger inn:"

#: modules/components/login_2fa.php:288
msgid "Or use other available options:"
msgstr "Eller bruk andre tilgjengelige alternativer:"

#: modules/components/login_2fa.php:412
msgid "Failed to locate the 2FA Option."
msgstr "Kunne ikke finne 2FA-alternativet."

#: modules/components/login_2fa.php:431
msgid "Failed to create a login nonce."
msgstr "Kunne ikke opprette en påloggings-nonce."

#: modules/components/login_2fa.php:498
msgid "Cheatin&#8217; uh?"
msgstr "Jukser du?"

#: modules/components/login_2fa.php:723
msgid "2FA Available Options"
msgstr "2FA Tilgjengelige Alternativer"

#: modules/components/login_2fa.php:728 modules/components/login_2fa.php:757
msgid "Primary"
msgstr "Primær"

#: modules/components/login_2fa.php:729 modules/components/login_2fa.php:758
msgid "Option Name"
msgstr "Alternativnavn"

#: modules/components/login_2fa_app.php:46 modules/components/login_2fa_app.php:50
msgid "Activate Authenticator app (TOTP)"
msgstr "Aktiver autentiseringsapp (TOTP)"

#: modules/components/login_2fa_app.php:47
msgid "Authenticator App (Google Authenticator, Microsoft Authenticator, and Similar Apps)"
msgstr "Autentiseringsapp (Google Authenticator, Microsoft Authenticator, og lignende apper)"

#: modules/components/login_2fa_app.php:51
msgid "Enhance your account security with an Authenticator App that generates time-based one-time passcodes for Two-Factor Authentication (2FA)"
msgstr "Forbedre kontosikkerheten din med en autentiseringsapp som genererer tidsbaserte engangspassord for to-faktor autentisering (2FA)"

#: modules/components/login_2fa_app.php:53
msgid "For a secure and reliable method of Two-Factor Authentication (2FA), you can use any of the popular authenticator apps. These apps generate time-based, one-time passcodes (TOTP) that are used to verify your identity. To set up this method, the user simply scan the QR code provided, then enter the verification code generated by your authenticator app into the 'Verification Code' field and click 'Verify' to complete the setup process."
msgstr "For en sikker og pålitelig metode for to-faktor autentisering (2FA), kan du bruke hvilken som helst av de populære autentiseringsappene. Disse appene genererer tidsbaserte, engangspassord (TOTP) som brukes til å verifisere identiteten din. For å sette opp denne metoden, brukeren bare skanner den leverte QR-koden, deretter skriver inn bekreftelseskoden generert av autentiseringsappen din i 'Bekreftelseskode'-feltet og klikker 'Bekreft' for å fullføre oppsettprosessen."

#: modules/components/login_2fa_app.php:55
msgid "Some of the most widely supported authenticator apps include:"
msgstr "Noen av de mest utbredte autentiseringsappene inkluderer:"

#: modules/components/login_2fa_app.php:57
msgid "<b>Google Authenticator</b>"
msgstr "<b>Google Authenticator</b>"

#: modules/components/login_2fa_app.php:58
msgid "<b>Microsoft Authenticator</b>"
msgstr "<b>Microsoft Authenticator</b>"

#: modules/components/login_2fa_app.php:59
msgid "<b>FreeOTP</b>"
msgstr "<b>FreeOTP</b>"

#: modules/components/login_2fa_app.php:60
msgid "<b>Duo Mobile</b>"
msgstr "<b>Duo Mobile</b>"

#: modules/components/login_2fa_app.php:61
msgid "<b>Authy</b>"
msgstr "<b>Authy</b>"

#: modules/components/login_2fa_app.php:62
msgid "<b>LastPass Authenticator</b>"
msgstr "<b>LastPass Authenticator</b>"

#: modules/components/login_2fa_app.php:63
msgid "These apps are available for download on both Android and iOS devices, ensuring users can securely authenticate their logins from their smartphones. "
msgstr "Disse appene er tilgjengelige for nedlasting på både Android- og iOS-enheter, noe som sikrer at brukere kan autentisere påloggingene sine sikkert fra smarttelefonene sine. "

#: modules/components/login_2fa_app.php:64 modules/components/login_2fa_email.php:56 modules/components/login_2fa_recovery_codes.php:56
msgid "Users can manage this option in the Profile section of their account."
msgstr "Brukere kan administrere dette alternativet i Profil-delen av kontoen sin."

#: modules/components/login_2fa_app.php:99
msgid "Authenticator APP"
msgstr "Autentiserings-APP"

#: modules/components/login_2fa_app.php:104
msgid "Login Code using APP"
msgstr "Påloggingskode ved bruk av APP"

#: modules/components/login_2fa_app.php:123 modules/components/login_2fa_app.php:353
msgid "The APP authentication setup is not yet complete."
msgstr "APP-autentiseringsoppsettet er ikke fullført ennå."

#: modules/components/login_2fa_app.php:124 modules/components/login_2fa_app.php:354
msgid "Use any of the following authentication applications to scan the QR code above. Then, enter the verification code from the app in the Verification Code field, and click Verify to complete the process."
msgstr "Bruk en av følgende autentiseringsapplikasjoner for å skanne QR-koden over. Deretter skriver du inn bekreftelseskoden fra appen i Bekreftelseskode-feltet, og klikker Bekreft for å fullføre prosessen."

#: modules/components/login_2fa_app.php:132 modules/components/login_2fa_app.php:154 modules/components/login_2fa_app.php:362 modules/components/login_2fa_recovery_codes.php:187
msgid "Verification Code:"
msgstr "Bekreftelseskode:"

#: modules/components/login_2fa_app.php:135 modules/components/login_2fa_app.php:365 modules/components/login_2fa_email.php:134 modules/components/login_2fa_recovery_codes.php:190
msgid "Verify"
msgstr "Bekreft"

#: modules/components/login_2fa_app.php:147
msgid "APP security Code"
msgstr "APP-sikkerhetskode"

#: modules/components/login_2fa_app.php:148
msgid "Open your authentication application, retrieve the verification code, and enter it into the Verification Code field."
msgstr "Åpne autentiseringsapplikasjonen din, hent bekreftelseskoden, og skriv den inn i Bekreftelseskode-feltet."

#: modules/components/login_2fa_app.php:149 modules/components/login_2fa_recovery_codes.php:182
msgid "Once entered, click Verify to proceed."
msgstr "Når den er skrevet inn, klikk Bekreft for å fortsette."

#: modules/components/login_2fa_app.php:157 modules/components/login_2fa_template_login_header.php:25
msgid "Log In"
msgstr "Logg inn"

#: modules/components/login_2fa_app.php:245 modules/components/login_2fa_email.php:293
msgid "ERROR: Invalid inpput code."
msgstr "FEIL: Ugyldig inndatakode."

#: modules/components/login_2fa_app.php:251 modules/components/login_2fa_email.php:298
msgid "ERROR: Invalid user or empty code."
msgstr "FEIL: Ugyldig bruker eller tom kode."

#: modules/components/login_2fa_app.php:259 modules/components/login_2fa_email.php:303
msgid "ERROR: Invalid verification code."
msgstr "FEIL: Ugyldig bekreftelseskode."

#: modules/components/login_2fa_app.php:374
msgid "The authenticator app is currently configured. If you reset it, you'll need to re-scan the QR code on all your devices to restore access. Ensure you have the necessary QR code or recovery details ready before proceeding to avoid disruptions to your account security or accessibility."
msgstr "Autentiseringsappen er for tiden konfigurert. Hvis du tilbakestiller den, må du skanne QR-koden på nytt på alle enhetene dine for å gjenopprette tilgangen. Sørg for at du har nødvendig QR-kode eller gjenopprettingsdetaljer klare før du fortsetter for å unngå forstyrrelser i kontosikkerheten eller tilgjengeligheten."

#: modules/components/login_2fa_app.php:375
msgid "Reset Authentication APP"
msgstr "Tilbakestill autentiserings-APP"

#: modules/components/login_2fa_app.php:437
msgid "<p class=\"notice error\">Error: Invalid verification code."
msgstr "<p class=\"notice error\">Feil: Ugyldig bekreftelseskode."

#: modules/components/login_2fa_defaults.php:98 modules/components/login_2fa_defaults.php:102
msgid "Enable 2FA"
msgstr "Aktiver 2FA"

#: modules/components/login_2fa_defaults.php:99
msgid "Enable 2FA for extra account protection."
msgstr "Aktiver 2FA for ekstra kontobeskyttelse."

#: modules/components/login_2fa_defaults.php:103
msgid "Two-factor authentication (2FA) adds an extra layer of security by requiring two different forms of verification to access your accounts. This means even if someone steals your password, they'll still need a second factor, like a code from your phone, to gain entry."
msgstr "To-faktor autentisering (2FA) legger til et ekstra sikkerhetslag ved å kreve to forskjellige former for verifisering for å få tilgang til kontoene dine. Dette betyr at selv om noen stjeler passordet ditt, vil de fortsatt trenge en andre faktor, som en kode fra telefonen din, for å komme inn."

#: modules/components/login_2fa_defaults.php:105
msgid "Two-Factor Authentication (2FA) enhances account security by requiring a second authentication method in addition to the primary password. This extra layer of protection helps safeguard accounts from unauthorized access, even if the primary password is compromised. To activate 2FA, users can enable one or more additional authentication methods for enhanced security. Three supported options can be used selectively or combined for maximum protection:"
msgstr "To-faktor autentisering (2FA) forbedrer kontosikkerheten ved å kreve en andre autentiseringsmetode i tillegg til hovedpassordet. Dette ekstra beskyttelseslaget hjelper til med å sikre kontoer mot uautorisert tilgang, selv om hovedpassordet er kompromittert. For å aktivere 2FA kan brukere aktivere en eller flere ekstra autentiseringsmetoder for forbedret sikkerhet. Tre støttede alternativer kan brukes selektivt eller kombinert for maksimal beskyttelse:"

#: modules/components/login_2fa_defaults.php:107
msgid "<b>Email Verification Code</b>"
msgstr "<b>E-post bekreftelseskode</b>"

#: modules/components/login_2fa_defaults.php:107
msgid ": A unique code is sent to the user's registered email, required during the login process."
msgstr ": En unik kode sendes til brukerens registrerte e-post, kreves under påloggingsprosessen."

#: modules/components/login_2fa_defaults.php:108
msgid "<b>Authenticator App</b>"
msgstr "<b>Autentiseringsapp</b>"

#: modules/components/login_2fa_defaults.php:108
msgid ": Applications like Google Authenticator or Microsoft Authenticator, available on iOS and Android, generate time-based, one-time passcodes (TOTP) for secure login."
msgstr ": Applikasjoner som Google Authenticator eller Microsoft Authenticator, tilgjengelig på iOS og Android, genererer tidsbaserte, engangspassord (TOTP) for sikker pålogging."

#: modules/components/login_2fa_defaults.php:109
msgid "<b>Recovery Codes</b>"
msgstr "<b>Gjenopprettingskoder</b>"

#: modules/components/login_2fa_defaults.php:109
msgid ": Pre-generated one-time-use codes provided during the 2FA setup. These can be securely stored and used as a backup when other methods are unavailable."
msgstr ": Forhåndsgenererte engangskoder gitt under 2FA-oppsettet. Disse kan lagres sikkert og brukes som en sikkerhetskopi når andre metoder ikke er tilgjengelige."

#: modules/components/login_2fa_defaults.php:110
msgid "Enabling 2FA significantly reduces the risk of unauthorized access by adding a robust secondary verification step."
msgstr "Aktivering av 2FA reduserer betydelig risikoen for uautorisert tilgang ved å legge til et robust sekundært verifiseringssteg."

#: modules/components/login_2fa_defaults.php:124 modules/components/login_2fa_defaults.php:128
msgid "Enable the 2FA for specific roles"
msgstr "Aktiver 2FA for spesifikke roller"

#: modules/components/login_2fa_defaults.php:125
msgid "Enable the 2FA functions for the specified roles."
msgstr "Aktiver 2FA-funksjonene for de angitte rollene."

#: modules/components/login_2fa_defaults.php:129
msgid "This option allows you to enforce Two-Factor Authentication (2FA) for selected user roles within your WordPress site. By enabling this feature, users assigned to the specified roles must authenticate using an additional verification step, enhancing account security. You can define which roles require 2FA, ensuring an extra layer of protection for administrators, editors, or other user groups as needed."
msgstr "Dette alternativet lar deg håndheve to-faktor autentisering (2FA) for valgte brukerroller i WordPress-nettstedet ditt. Ved å aktivere denne funksjonen må brukere tildelt de angitte rollene autentisere ved hjelp av et ekstra verifiseringssteg, noe som forbedrer kontosikkerheten. Du kan definere hvilke roller som krever 2FA, og sikre et ekstra beskyttelseslag for administratorer, redaktører eller andre brukergrupper etter behov."

#: modules/components/login_2fa_defaults.php:138 modules/components/login_2fa_defaults.php:142
msgid "Enforce User to Configure 2FA"
msgstr "Tving bruker til å konfigurere 2FA"

#: modules/components/login_2fa_defaults.php:139 modules/components/login_2fa_defaults.php:143
msgid "Mandate the user to configure Two-Factor Authentication (2FA) during their first login."
msgstr "Påtving brukeren å konfigurere to-faktor autentisering (2FA) under deres første pålogging."

#: modules/components/login_2fa_defaults.php:145
msgid "Require users to set up Two-Factor Authentication (2FA) during their initial login for enhanced security. Until the setup is completed, access to the dashboard will be restricted.  Users can configure the active 2FA methods, such as email verification codes, authenticator apps, or recovery codes. Once 2FA is successfully enabled, the user can access the dashboard and manage their account securely. "
msgstr "Krev at brukere setter opp to-faktor autentisering (2FA) under deres første pålogging for forbedret sikkerhet. Inntil oppsettet er fullført, vil tilgangen til dashbordet være begrenset. Brukere kan konfigurere de aktive 2FA-metodene, som e-post bekreftelseskoder, autentiseringsapper eller gjenopprettingskoder. Når 2FA er aktivert, kan brukeren få tilgang til dashbordet og administrere kontoen sin sikkert. "

#: modules/components/login_2fa_defaults.php:146
msgid "If needed, users can update or modify their 2FA settings anytime from their account settings within the dashboard."
msgstr "Om nødvendig kan brukere oppdatere eller endre sine 2FA-innstillinger når som helst fra kontoinnstillingene sine i dashbordet."

#: modules/components/login_2fa_defaults.php:147
msgid "Activating this option ensures straightforward stronger protection against unauthorized access by requiring users to establish an additional verification layer before accessing their account. This proactive approach enhances security and minimizes risks associated with compromised passwords."
msgstr "Aktivering av dette alternativet sikrer enkelt sterkere beskyttelse mot uautorisert tilgang ved å kreve at brukere etablerer et ekstra verifiseringslag før de får tilgang til kontoen sin. Denne proaktive tilnærmingen forbedrer sikkerheten og minimerer risikoer knyttet til kompromitterte passord."

#: modules/components/login_2fa_defaults.php:161 modules/components/login_2fa_defaults.php:165
msgid "Primary Two-Factor option"
msgstr "Primært to-faktor alternativ"

#: modules/components/login_2fa_defaults.php:162
msgid "Primary Two-Factor Authentication Method."
msgstr "Primær to-faktor autentiseringsmetode."

#: modules/components/login_2fa_defaults.php:166
msgid "Select the Primary Two-Factor Authentication Method, which will be presented to the user when they reach the 2FA step during login. This method will be the first authentication option, the user can also pick others."
msgstr "Velg den primære to-faktor autentiseringsmetoden, som vil bli presentert for brukeren når de når 2FA-trinnet under pålogging. Denne metoden vil være det første autentiseringsalternativet, brukeren kan også velge andre."

#: modules/components/login_2fa_defaults.php:168
msgid "The available 2FA methods include:"
msgstr "De tilgjengelige 2FA-metodene inkluderer:"

#: modules/components/login_2fa_defaults.php:170
msgid "<b>Email Verification</b>: A unique code is sent to the user's registered email address, which must be entered during login for authentication."
msgstr "<b>E-post bekreftelse</b>: En unik kode sendes til brukerens registrerte e-postadresse, som må skrives inn under pålogging for autentisering."

#: modules/components/login_2fa_defaults.php:171
msgid "<b>Authenticator App</b>: Use apps like Google Authenticator or Microsoft Authenticator to generate time-based one-time passcodes (TOTP) that the user will need to enter during login."
msgstr "<b>Autentiseringsapp</b>: Bruk apper som Google Authenticator eller Microsoft Authenticator for å generere tidsbaserte engangspassord (TOTP) som brukeren må skrive inn under pålogging."

#: modules/components/login_2fa_defaults.php:172
msgid "<b>Recovery Codes</b>: Pre-generated one-time-use codes provided during 2FA setup, which can be used as a backup if other methods are unavailable or inaccessible."
msgstr "<b>Gjenopprettingskoder</b>: Forhåndsgenererte engangskoder gitt under 2FA-oppsett, som kan brukes som en sikkerhetskopi hvis andre metoder ikke er tilgjengelige eller utilgjengelige."

#: modules/components/login_2fa_defaults.php:173
msgid "You can choose the most convenient or secure method for your users, ensuring an additional layer of protection for their accounts."
msgstr "Du kan velge den mest praktiske eller sikre metoden for brukerne dine, og sikre et ekstra beskyttelseslag for kontoene deres."

#: modules/components/login_2fa_defaults.php:179 modules/components/login_2fa_email.php:79
msgid "Email"
msgstr "E-post"

#: modules/components/login_2fa_defaults.php:180
msgid "Auth APP"
msgstr "Auth APP"

#: modules/components/login_2fa_defaults.php:181 modules/components/login_2fa_recovery_codes.php:91
msgid "Recovery Codes"
msgstr "Gjenopprettingskoder"

#: modules/components/login_2fa_defaults.php:188 modules/components/login_2fa_defaults.php:192
msgid "Disable 2FA when using Temporary Login"
msgstr "Deaktiver 2FA ved bruk av midlertidig pålogging"

#: modules/components/login_2fa_defaults.php:189
msgid "Disable 2FA when using wordpress plugins like Temporary Login Without Password."
msgstr "Deaktiver 2FA ved bruk av WordPress-plugins som Temporary Login Without Password."

#: modules/components/login_2fa_defaults.php:193
msgid "When enabled, this option bypasses Two-Factor Authentication (2FA) for users accessing the site via a temporary login URL, such as those generated by the Temporary Login Without Password plugin. This ensures seamless access without additional authentication steps."
msgstr "Når aktivert, omgår dette alternativet to-faktor autentisering (2FA) for brukere som får tilgang til nettstedet via en midlertidig påloggings-URL, som de som genereres av Temporary Login Without Password-plugin. Dette sikrer sømløs tilgang uten ekstra autentiseringssteg."

#: modules/components/login_2fa_defaults.php:195
msgid "The new 'Disable 2FA when using Temporary Login' option in the WP Hide plugin enhances site accessibility by allowing temporary bypassing of Two-Factor Authentication (2FA) for specific login scenarios. When activated, if 2FA is enabled, users who access the site via temporary login URLs, generated by plugins such as Temporary Login Without Password, can log in without undergoing the usual 2FA process. This feature simplifies the user experience during temporary access, ensuring a seamless transition while maintaining robust security measures for standard login procedures. It is an ideal solution for administrators who require controlled, temporary access without compromising overall security."
msgstr "Det nye alternativet 'Deaktiver 2FA ved bruk av midlertidig pålogging' i WP Hide-plugin forbedrer nettstedets tilgjengelighet ved å tillate midlertidig omgåelse av to-faktor autentisering (2FA) for spesifikke påloggingsscenarier. Når aktivert, hvis 2FA er aktivert, kan brukere som får tilgang til nettstedet via midlertidige påloggings-URL-er, generert av plugins som Temporary Login Without Password, logge inn uten å gjennomgå den vanlige 2FA-prosessen. Denne funksjonen forenkler brukeropplevelsen under midlertidig tilgang, sikrer en sømløs overgang samtidig som den opprettholder robuste sikkerhetstiltak for standard påloggingsprosedyrer. Det er en ideell løsning for administratorer som trenger kontrollert, midlertidig tilgang uten å kompromittere den generelle sikkerheten."

#: modules/components/login_2fa_defaults.php:237
msgid "No Role"
msgstr "Ingen rolle"

#: modules/components/login_2fa_email.php:46 modules/components/login_2fa_email.php:50
msgid "Activate Email"
msgstr "Aktiver e-post"

#: modules/components/login_2fa_email.php:47
msgid "Authentication codes will be sent to user e-mail address."
msgstr "Autentiseringskoder vil bli sendt til brukerens e-postadresse."

#: modules/components/login_2fa_email.php:51
msgid "Authentication codes will be sent directly to the user's registered email address as part of the Two-Factor Authentication (2FA) process."
msgstr "Autentiseringskoder vil bli sendt direkte til brukerens registrerte e-postadresse som en del av to-faktor autentiseringsprosessen (2FA)."

#: modules/components/login_2fa_email.php:53
msgid "Upon reaching the 2FA step during login, the user will receive a unique, time-sensitive code in their inbox. This code must be entered promptly to verify the user's identity and gain access to their account. The email-based authentication method offers an added layer of security by ensuring that only users with access to the registered email can proceed. It is a reliable method for users who prefer not to rely on third-party applications for authentication."
msgstr "Ved å nå 2FA-trinnet under pålogging, vil brukeren motta en unik, tidsfølsom kode i innboksen sin. Denne koden må skrives inn raskt for å verifisere brukerens identitet og få tilgang til kontoen deres. Den e-postbaserte autentiseringsmetoden tilbyr et ekstra sikkerhetslag ved å sikre at bare brukere med tilgang til den registrerte e-posten kan fortsette. Det er en pålitelig metode for brukere som foretrekker ikke å stole på tredjeparts-applikasjoner for autentisering."

#: modules/components/login_2fa_email.php:55
msgid "For the best experience with the Two-Factor Authentication (2FA) - Email option, it is highly recommended to use an SMTP plugin. An SMTP (Simple Mail Transfer Protocol) plugin ensures that authentication messages are sent securely and reliably from your server, helping to avoid issues with email delivery. By configuring an SMTP plugin, you can improve the chances of the 2FA email reaching the user's inbox instead of being mistakenly filtered into the spam or bulk folders. ."
msgstr "For best mulig opplevelse med to-faktor autentisering (2FA) - E-post alternativet, anbefales det på det sterkeste å bruke en SMTP-plugin. En SMTP (Simple Mail Transfer Protocol) plugin sikrer at autentiseringsmeldinger sendes sikkert og pålitelig fra serveren din, og hjelper til med å unngå problemer med e-postlevering. Ved å konfigurere en SMTP-plugin kan du forbedre sjansene for at 2FA-e-posten når brukerens innboks i stedet for å bli feilaktig filtrert inn i søppelpost eller bulk-mapper. ."

#: modules/components/login_2fa_email.php:89
msgid "Send a code to your email"
msgstr "Send en kode til e-posten din"

#: modules/components/login_2fa_email.php:102
#, php-format
msgid "Here is your login confirmation code for %s"
msgstr "Her er din påloggingsbekreftelseskode for %s"

#: modules/components/login_2fa_email.php:103
#, php-format
msgid ""
"Use the following code to securely log in to your account: %s \n"
"Please ensure you enter this code correctly to access your account. \n"
" \n"
"\n"
"If you did not request this code, please contact support for assistance."
msgstr ""
"Bruk følgende kode for å logge deg sikkert inn på kontoen din: %s \n"
"Vennligst sørg for at du skriver inn denne koden riktig for å få tilgang til kontoen din. \n"
" \n"
"\n"
"Hvis du ikke ba om denne koden, vennligst kontakt kundestøtte for hjelp."

#: modules/components/login_2fa_email.php:128
msgid "Email security Code"
msgstr "E-post sikkerhetskode"

#: modules/components/login_2fa_email.php:129
msgid "A verification code has been sent to the email address linked to your account. Please check your inbox and enter the code to proceed."
msgstr "En bekreftelseskode er sendt til e-postadressen knyttet til kontoen din. Vennligst sjekk innboksen din og skriv inn koden for å fortsette."

#: modules/components/login_2fa_email.php:131
msgid "Authentication Code:"
msgstr "Autentiseringskode:"

#: modules/components/login_2fa_email.php:135
msgid "Resend Code"
msgstr "Send kode på nytt"

#: modules/components/login_2fa_email.php:274
msgid "A new code has been sent. Please check your email inbox, including the spam or junk folder."
msgstr "En ny kode er sendt. Vennligst sjekk e-postinnboksen din, inkludert søppelpostmappen."

#: modules/components/login_2fa_email.php:306
msgid "ERROR: Expired verification code."
msgstr "FEIL: Utløpt bekreftelseskode."

#: modules/components/login_2fa_email.php:337
#, php-format
msgid "Authentication codes will be securely sent to the email address ( %s ) associated with your account. This added layer of security ensures that only you can access your account, even if your password is compromised. Make sure your email address is up-to-date to receive these important codes promptly."
msgstr "Autentiseringskoder vil bli sendt sikkert til e-postadressen ( %s ) knyttet til kontoen din. Dette ekstra sikkerhetslaget sikrer at bare du kan få tilgang til kontoen din, selv om passordet ditt er kompromittert. Sørg for at e-postadressen din er oppdatert for å motta disse viktige kodene raskt."

#: modules/components/login_2fa_recovery_codes.php:46 modules/components/login_2fa_recovery_codes.php:50
msgid "Activate Recovery Codes"
msgstr "Aktiver gjenopprettingskoder"

#: modules/components/login_2fa_recovery_codes.php:47
msgid "Recovery Codes."
msgstr "Gjenopprettingskoder."

#: modules/components/login_2fa_recovery_codes.php:51
msgid "Generate 10 one-time-use recovery codes as a backup for Two-Factor Authentication (2FA) to securely access your dashboard."
msgstr "Generer 10 engangs gjenopprettingskoder som en sikkerhetskopi for to-faktor autentisering (2FA) for å få sikker tilgang til dashbordet ditt."

#: modules/components/login_2fa_recovery_codes.php:53
msgid "The 2FA Recovery Codes method generates 10 unique, one-time-use codes that act as a secure backup for accessing your dashboard. These codes provide an alternative way to authenticate your login if you are unable to use your primary 2FA method, such as an email code or authenticator app. Each code can only be used once, ensuring added security and preventing unauthorized access. It is crucial to store these recovery codes in a safe and secure location, such as an encrypted password manager or physical safe, to avoid loss or misuse."
msgstr "2FA Gjenopprettingskoder-metoden genererer 10 unike, engangskoder som fungerer som en sikker sikkerhetskopi for tilgang til dashbordet ditt. Disse kodene gir en alternativ måte å autentisere påloggingen din på hvis du ikke kan bruke din primære 2FA-metode, som en e-postkode eller autentiseringsapp. Hver kode kan bare brukes én gang, noe som sikrer ekstra sikkerhet og forhindrer uautorisert tilgang. Det er avgjørende å lagre disse gjenopprettingskodene på et trygt og sikkert sted, for eksempel en kryptert passordbehandler eller fysisk safe, for å unngå tap eller misbruk."

#: modules/components/login_2fa_recovery_codes.php:55
msgid "While this method is primarily intended as a backup solution, it can also be used as the primary 2FA method if necessary. Recovery codes offer a reliable and easy-to-use fallback, ensuring you can always regain access to your account when needed, even if other 2FA options are unavailable."
msgstr "Selv om denne metoden primært er ment som en sikkerhetskopiløsning, kan den også brukes som den primære 2FA-metoden om nødvendig. Gjenopprettingskoder tilbyr en pålitelig og brukervennlig fallback, og sikrer at du alltid kan gjenvinne tilgang til kontoen din når det trengs, selv om andre 2FA-alternativer ikke er tilgjengelige."

#: modules/components/login_2fa_recovery_codes.php:97
msgid "Use a pre-saved recovery code"
msgstr "Bruk en forhåndslagret gjenopprettingskode"

#: modules/components/login_2fa_recovery_codes.php:110
msgid "The setup process generated 10 Recovery Codes, which serve as a secure backup method to access your dashboard. Each code can only be used once."
msgstr "Oppsettprosessen genererte 10 gjenopprettingskoder, som fungerer som en sikker sikkerhetskopimetode for å få tilgang til dashbordet ditt. Hver kode kan bare brukes én gang."

#: modules/components/login_2fa_recovery_codes.php:122 modules/components/login_2fa_recovery_codes.php:453
msgid "Be sure to store these codes in a safe location to prevent loss or unauthorized access."
msgstr "Vær nøye med å lagre disse kodene på et sikkert sted for å forhindre tap eller uautorisert tilgang."

#: modules/components/login_2fa_recovery_codes.php:157
msgid "Continue"
msgstr "Fortsett"

#: modules/components/login_2fa_recovery_codes.php:165
msgid "The Recovery Code setup is not yet completed."
msgstr "Gjenopprettingskode-oppsettet er ikke fullført ennå."

#: modules/components/login_2fa_recovery_codes.php:166
msgid "The setup process will generate 10 Recovery Codes, which serve as a secure backup method to access your dashboard. Each code can only be used once."
msgstr "Oppsettprosessen vil generere 10 gjenopprettingskoder, som fungerer som en sikker sikkerhetskopimetode for å få tilgang til dashbordet ditt. Hver kode kan bare brukes én gang."

#: modules/components/login_2fa_recovery_codes.php:169 modules/components/login_2fa_recovery_codes.php:424
msgid "Generate Recovery Codes"
msgstr "Generer gjenopprettingskoder"

#: modules/components/login_2fa_recovery_codes.php:180
msgid "Recovery Code"
msgstr "Gjenopprettingskode"

#: modules/components/login_2fa_recovery_codes.php:181
msgid "Enter a recovery code from the list you saved when setup the option."
msgstr "Skriv inn en gjenopprettingskode fra listen du lagret da du satte opp alternativet."

#: modules/components/login_2fa_recovery_codes.php:295
msgid "Error: Invalid inpput code."
msgstr "Feil: Ugyldig inndatakode."

#: modules/components/login_2fa_recovery_codes.php:300
msgid "Error: Invalid user or empty code."
msgstr "Feil: Ugyldig bruker eller tom kode."

#: modules/components/login_2fa_recovery_codes.php:304
msgid "Error: This option is unavailable as the internal list is exhausted. Please choose a different option and visit your Profile to generate a new Recovery Codes list. "
msgstr "Feil: Dette alternativet er utilgjengelig ettersom den interne listen er oppbrukt. Vennligst velg et annet alternativ og besøk Profilen din for å generere en ny gjenopprettingskodeliste. "

#: modules/components/login_2fa_recovery_codes.php:316
msgid "Error: Invalid verification code."
msgstr "Feil: Ugyldig bekreftelseskode."

#: modules/components/login_2fa_recovery_codes.php:405
msgid "The Recovery Code setup is not yet complete."
msgstr "Gjenopprettingskode-oppsettet er ikke fullført ennå."

#: modules/components/login_2fa_recovery_codes.php:418
#, php-format
msgid "You have %s recovery codes remaining, each of which can be used once."
msgstr "Du har %s gjenopprettingskoder igjen, hver av dem kan brukes én gang."

#: modules/components/login_2fa_recovery_codes.php:423
msgid "To generate a new list of recovery codes, click the button below."
msgstr "For å generere en ny liste med gjenopprettingskoder, klikk knappen nedenfor."

#: modules/components/login_2fa_recovery_codes.php:453
msgid "After leaving this page, you will no longer be able to view these codes !"
msgstr "Etter at du forlater denne siden, vil du ikke lenger kunne se disse kodene!"

#: modules/components/login_2fa_template_login_footer.php:74 modules/components/login_captcha-cloudFlare-turnstile.php:41 modules/components/login_captcha-google-v2.php:42
msgid "Language"
msgstr "Språk"

#: modules/components/login_2fa_template_login_footer.php:113
msgid "Change"
msgstr "Endre"

#: modules/components/login_2fa_template_login_header.php:56
#, php-format
msgid "%1$s &lsaquo; %2$s &#8212; WordPress"
msgstr "%1$s &lsaquo; %2$s &#8212; WordPress"

#: modules/components/login_2fa_template_login_header.php:60
#, php-format
msgid "Recovery Mode &#8212; %s"
msgstr "Gjenopprettingsmodus &#8212; %s"

#: modules/components/login_2fa_template_login_header.php:109
msgid "https://wordpress.org/"
msgstr "https://wordpress.org/"

#: modules/components/login_2fa_template_login_header.php:135
msgid "Usage of the title attribute on the login logo is not recommended for accessibility reasons. Use the link text instead."
msgstr "Bruk av title-attributtet på påloggingslogoen anbefales ikke av tilgjengelighetsgrunner. Bruk lenketeksten i stedet."

#: modules/components/login_2fa_template_login_header.php:138
msgid "Powered by WordPress"
msgstr "Drevet av WordPress"

#: modules/components/login_captcha-cloudFlare-turnstile.php:24 modules/components/login_captcha-google-v2.php:26 modules/components/login_captcha-google-v3.php:26
msgid "Site Key"
msgstr "Nettstedsnøkkel"

#: modules/components/login_captcha-cloudFlare-turnstile.php:28 modules/components/login_captcha-google-v2.php:30 modules/components/login_captcha-google-v3.php:30
msgid "Secret Key"
msgstr "Hemmelig nøkkel"

#: modules/components/login_captcha-cloudFlare-turnstile.php:32 modules/components/login_captcha-google-v2.php:34
msgid "Theme"
msgstr "Tema"

#: modules/components/login_captcha-cloudFlare-turnstile.php:35 modules/components/login_captcha-google-v2.php:37
msgid "Light"
msgstr "Lys"

#: modules/components/login_captcha-cloudFlare-turnstile.php:36 modules/components/login_captcha-google-v2.php:38
msgid "Dark"
msgstr "Mørk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:37
msgid "Auto"
msgstr "Auto"

#: modules/components/login_captcha-cloudFlare-turnstile.php:44 modules/components/login_captcha-google-v2.php:45
msgid "Auto Detect"
msgstr "Auto oppdag"

#: modules/components/login_captcha-cloudFlare-turnstile.php:45
msgid "Arabic (Egypt)"
msgstr "Arabisk (Egypt)"

#: modules/components/login_captcha-cloudFlare-turnstile.php:46 modules/components/login_captcha-google-v2.php:46
msgid "Arabic"
msgstr "Arabisk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:47 modules/components/login_captcha-google-v2.php:47
msgid "German"
msgstr "Tysk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:48 modules/components/login_captcha-google-v2.php:48
msgid "English"
msgstr "Engelsk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:49 modules/components/login_captcha-google-v2.php:49
msgid "Spanish"
msgstr "Spansk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:50 modules/components/login_captcha-google-v2.php:50
msgid "Farsi/Persian"
msgstr "Farsi/Persisk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:51 modules/components/login_captcha-google-v2.php:51
msgid "French"
msgstr "Fransk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:52 modules/components/login_captcha-google-v2.php:52
msgid "Indonesian"
msgstr "Indonesisk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:53 modules/components/login_captcha-google-v2.php:53
msgid "Italian"
msgstr "Italiensk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:54 modules/components/login_captcha-google-v2.php:54
msgid "Japanese"
msgstr "Japansk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:55 modules/components/login_captcha-google-v2.php:55
msgid "Korean"
msgstr "Koreansk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:56 modules/components/login_captcha-google-v2.php:56
msgid "Dutch"
msgstr "Nederlandsk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:57 modules/components/login_captcha-google-v2.php:57
msgid "Polish"
msgstr "Polsk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:58 modules/components/login_captcha-google-v2.php:58
msgid "Portuguese"
msgstr "Portugisisk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:59 modules/components/login_captcha-google-v2.php:59
msgid "Portuguese (Brazil)"
msgstr "Portugisisk (Brasil)"

#: modules/components/login_captcha-cloudFlare-turnstile.php:60 modules/components/login_captcha-google-v2.php:61
msgid "Russian"
msgstr "Russisk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:61
msgid "Klingon"
msgstr "Klingon"

#: modules/components/login_captcha-cloudFlare-turnstile.php:62 modules/components/login_captcha-google-v2.php:62
msgid "Turkish"
msgstr "Tyrkisk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:63 modules/components/login_captcha-google-v2.php:63
msgid "Ukrainian"
msgstr "Ukrainsk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:64 modules/components/login_captcha-google-v2.php:64
msgid "Chinese"
msgstr "Kinesisk"

#: modules/components/login_captcha-cloudFlare-turnstile.php:65 modules/components/login_captcha-google-v2.php:65
msgid "Chinese (Simplified)"
msgstr "Kinesisk (forenklet)"

#: modules/components/login_captcha-cloudFlare-turnstile.php:66 modules/components/login_captcha-google-v2.php:66
msgid "Chinese (Traditional)"
msgstr "Kinesisk (tradisjonell)"

#: modules/components/login_captcha-cloudFlare-turnstile.php:122 modules/components/login_captcha-google-v2.php:125 modules/components/login_captcha-google-v3.php:106
msgid "Test API"
msgstr "Test API"

#: modules/components/login_captcha-cloudFlare-turnstile.php:123 modules/components/login_captcha-google-v2.php:126 modules/components/login_captcha-google-v3.php:108
msgid "The captcha will not show on the front side until the Test is successful."
msgstr "Captcha-en vil ikke vises på fremsiden før testen er vellykket."

#: modules/components/login_captcha-cloudFlare-turnstile.php:137
msgid "The CloudFlare Turnstile integration is completed."
msgstr "CloudFlare Turnstile-integrasjonen er fullført."

#: modules/components/login_captcha-cloudFlare-turnstile.php:155 modules/components/login_captcha-google-v2.php:158 modules/components/login_captcha-google-v3.php:140
msgid "You can get your site key and secret key from"
msgstr "Du kan få din nettstedsnøkkel og hemmelige nøkkel fra"

#: modules/components/login_captcha-cloudFlare-turnstile.php:156 modules/components/login_captcha-google-v2.php:159 modules/components/login_captcha-google-v3.php:141
msgid "After filling in and saving the options, remember to click the <b class=\"important\">Test API</b> button located at the top of this section. The CAPTCHA won't appear on the front end until the test is successfully completed"
msgstr "Etter at du har fylt ut og lagret alternativene, husk å klikke på <b class=\"important\">Test API</b>-knappen øverst i denne delen. CAPTCHA-en vil ikke vises på frontend før testen er vellykket fullført"

#: modules/components/login_captcha-cloudFlare-turnstile.php:180 modules/components/login_captcha-google-v2.php:183 modules/components/login_captcha-google-v3.php:170
msgid "The API returned an error"
msgstr "API-en returnerte en feil"

#: modules/components/login_captcha-cloudFlare-turnstile.php:281 modules/components/login_captcha-cloudFlare-turnstile.php:302 modules/components/login_captcha-cloudFlare-turnstile.php:323 modules/components/login_captcha-google-v2.php:274 modules/components/login_captcha-google-v2.php:295 modules/components/login_captcha-google-v2.php:316 modules/components/login_captcha-google-v3.php:286 modules/components/login_captcha-google-v3.php:307 modules/components/login_captcha-google-v3.php:328
msgid "Unable to verify that you are human."
msgstr "Kan ikke verifisere at du er menneske."

#: modules/components/login_captcha-cloudFlare-turnstile.php:302 modules/components/login_captcha-cloudFlare-turnstile.php:323 modules/components/login_captcha-google-v2.php:295 modules/components/login_captcha-google-v2.php:316 modules/components/login_captcha-google-v3.php:307 modules/components/login_captcha-google-v3.php:328
msgid "Error!"
msgstr "Feil!"

#: modules/components/login_captcha-google-v2.php:60
msgid "Romania"
msgstr "Romania"

#: modules/components/login_captcha-google-v2.php:140
msgid "The Google Captcha V2 integration is completed."
msgstr "Google Captcha V2-integrasjonen er fullført."

#: modules/components/login_captcha-google-v3.php:34
msgid "Required Score to validate ( range 0.0 - 1.0 ). Default 0.5 "
msgstr "Påkrevd score for validering ( område 0.0 - 1.0 ). Standard 0.5 "

#: modules/components/login_captcha-google-v3.php:107
msgid "If the Test API button is not triggering, check the Google badge message on the bottom-right corner of your screen. The provided site key may be invalid for this domain."
msgstr "Hvis Test API-knappen ikke utløses, sjekk Google-merkemeldingen nederst til høyre på skjermen din. Den oppgitte nettstedsnøkkelen kan være ugyldig for dette domenet."

#: modules/components/login_captcha-google-v3.php:122
msgid "The Google Captcha V3 integration is completed."
msgstr "Google Captcha V3-integrasjonen er fullført."

#: modules/components/login_captcha-google-v3.php:142
msgid "reCAPTCHA v3 returns a score for each request without user friction. The score is based on interactions with your site and enables you to take an appropriate action for your site."
msgstr "reCAPTCHA v3 returnerer en score for hver forespørsel uten brukerfriksjon. Scoren er basert på interaksjoner med nettstedet ditt og lar deg ta en passende handling for nettstedet ditt."

#: modules/components/login_captcha-google-v3.php:143
msgid "The default score is 0.5 which is considered a safe value to distinguish between bots and real users. "
msgstr "Standardscoren er 0.5 som anses som en sikker verdi for å skille mellom botter og ekte brukere. "

#: modules/components/login_captcha-google-v3.php:144
msgid "Warning"
msgstr "Advarsel"

#: modules/components/login_captcha-google-v3.php:145
msgid "Setting an excessively high value may result in being locked out of your site's login. Conversely, using an extremely low value can validate bots. The optimal value is 0.5."
msgstr "Å sette en altfor høy verdi kan føre til at du blir utelukket fra påloggingen til nettstedet ditt. Omvendt kan bruk av en ekstremt lav verdi validere botter. Den optimale verdien er 0.5."

#: modules/components/login_captcha.php:91 modules/components/login_captcha.php:96
msgid "Captcha Type"
msgstr "Captcha-type"

#: modules/components/login_captcha.php:93
msgid "Select the required CAPTCHA type to protect the Login, Registration page, Password Forget etc."
msgstr "Velg nødvendig CAPTCHA-type for å beskytte påloggingssiden, registreringssiden, glemt passord etc."

#: modules/components/login_captcha.php:97
msgid "CAPTCHA, short for \"Completely Automated Public Turing test to tell Computers and Humans Apart,\" is a critical cybersecurity tool. It distinguishes human users from automated bots by presenting challenges like distorted characters or image recognition tasks. CAPTCHA safeguards websites, login pages, and online services from unwanted intrusion, spam, and fraud. Its evolution includes advanced variants and innovations like reCAPTCHA, continually enhancing digital security."
msgstr "CAPTCHA, kort for \"Completely Automated Public Turing test to tell Computers and Humans Apart,\" er et kritisk cybersikkerhetsverktøy. Det skiller menneskelige brukere fra automatiserte botter ved å presentere utfordringer som forvrengte tegn eller bildegjenkjenningsoppgaver. CAPTCHA sikrer nettsteder, påloggingssider og onlinetjenester mot uønsket inntrenging, spam og svindel. Dets utvikling inkluderer avanserte varianter og innovasjoner som reCAPTCHA, som kontinuerlig forbedrer digital sikkerhet."

#: modules/components/login_captcha.php:98
msgid "While it's a robust defense, adversaries are adapting, making CAPTCHA's ongoing development crucial in the fight against online threats."
msgstr "Selv om det er et robust forsvar, tilpasser motstandere seg, noe som gjør CAPTCHAs løpende utvikling avgjørende i kampen mot onlinetrusler."

#: modules/components/login_captcha.php:166
msgid "Disabled"
msgstr "Deaktivert"

#: modules/components/login_captcha.php:167
msgid "Google Captcha V2"
msgstr "Google Captcha V2"

#: modules/components/login_captcha.php:168
msgid "Google Captcha V3"
msgstr "Google Captcha V3"

#: modules/components/login_captcha.php:169
msgid "CloudFlare Turnstile <span class=\"wph-pro\">PRO</span>"
msgstr "CloudFlare Turnstile <span class=\"wph-pro\">PRO</span>"

#: modules/components/rewrite-author.php:18
msgid "e.g. profile"
msgstr "f.eks. profil"

#: modules/components/rewrite-author.php:57 modules/components/rewrite-author.php:60
msgid "New Author Path"
msgstr "Ny forfattersti"

#: modules/components/rewrite-author.php:58
msgid "The default path is set to /author/"
msgstr "Standardstien er satt til /forfatter/"

#: modules/components/rewrite-author.php:61
msgid "An author URL display all posts associated to a particular author. The default URL format is:"
msgstr "En forfatter-URL viser alle innlegg knyttet til en bestemt forfatter. Standard URL-format er:"

#: modules/components/rewrite-author.php:63
msgid "By using a value of 'contributor' this become:"
msgstr "Ved å bruke en verdi på 'bidragsyter' blir dette:"

#: modules/components/rewrite-author.php:73 modules/components/rewrite-author.php:77
msgid "Prevent Access to Author Archives"
msgstr "Forhindre tilgang til forfatterarkiv"

#: modules/components/rewrite-author.php:74
msgid "Prevent Access to Author Archives via User IDs"
msgstr "Forhindre tilgang til forfatterarkiv via bruker-IDer"

#: modules/components/rewrite-author.php:78
msgid "By default, WordPress generates author archive pages using URLs like "
msgstr "Som standard genererer WordPress forfatterarkivsider ved hjelp av URL-er som "

#: modules/components/rewrite-author.php:80
msgid ". This behavior can be exploited by attackers who repeatedly request URLs such as "
msgstr ". Denne oppførselen kan utnyttes av angripere som gjentatte ganger ber om URL-er som "

#: modules/components/rewrite-author.php:82
msgid ". and so on, until they find valid user IDs—revealing active usernames on your site."
msgstr ". og så videre, til de finner gyldige bruker-IDer—og avslører aktive brukernavn på nettstedet ditt."

#: modules/components/rewrite-author.php:83
msgid "To enhance security, it's best to completely disable access to these types of URLs, especially since author archive pages often serve little or no purpose on many sites."
msgstr "For å forbedre sikkerheten, er det best å fullstendig deaktivere tilgang til disse typene URL-er, spesielt siden forfatterarkivsider ofte tjener liten eller ingen hensikt på mange nettsteder."

#: modules/components/rewrite-author.php:84
msgid "Even if your permalink settings are not set to the default (i.e., 'Plain'), WordPress will still redirect ?author=ID URLs to the corresponding author archive page, if it exists. Therefore, additional measures are necessary to block these redirects and prevent username enumeration."
msgstr "Selv om permalink-innstillingene dine ikke er satt til standard (dvs. 'Plain'), vil WordPress fortsatt omdirigere ?author=ID URL-er til den tilsvarende forfatterarkivsiden, hvis den eksisterer. Derfor er ytterligere tiltak nødvendige for å blokkere disse omdirigeringene og forhindre brukernavn-oppregning."

#: modules/components/rewrite-author.php:97 modules/components/rewrite-author.php:100 modules/components/rewrite-search.php:52 modules/components/rewrite-search.php:55
msgid "Block default"
msgstr "Blokker standard"

#: modules/components/rewrite-author.php:98
msgid "Block default /author/ when using custom one."
msgstr "Blokker standard /forfatter/ når du bruker en egendefinert."

#: modules/components/rewrite-author.php:98 modules/components/rewrite-search.php:53
msgid "Apply only if "
msgstr "Gjelder bare hvis "

#: modules/components/rewrite-author.php:98 modules/components/rewrite-search.php:53
msgid "is not empty."
msgstr "ikke er tom."

#: modules/components/rewrite-author.php:101
msgid "After changing the default author, the old url is still accessible, this provide a way to block it.<br />The functionality apply only if <b>New Author Path</b> option is filled in."
msgstr "Etter å ha endret standard forfatter, er den gamle URL-en fortsatt tilgjengelig, dette gir en måte å blokkere den på.<br />Funksjonaliteten gjelder bare hvis <b>Ny forfattersti</b> alternativet er fylt ut."

#: modules/components/rewrite-comments.php:45
msgid "New wp-comments-post.php Path"
msgstr "Ny wp-comments-post.php sti"

#: modules/components/rewrite-comments.php:46
msgid "The default path is set to wp-comments-post.php"
msgstr "Standardstien er satt til wp-comments-post.php"

#: modules/components/rewrite-comments.php:49
msgid "As default the form data is being sent and processed at:"
msgstr "Som standard sendes skjemadataene og behandles på:"

#: modules/components/rewrite-comments.php:51
msgid "This makes it easy to recognise as WordPress form. Boots always search for such file ( wp-comments-post.php ) and automatically submit spam messages."
msgstr "Dette gjør det enkelt å gjenkjenne som et WordPress-skjema. Botter søker alltid etter slike filer (wp-comments-post.php) og sender automatisk spam-meldinger."

#: modules/components/rewrite-comments.php:52
msgid "Though this option a new file slug can replace the default."
msgstr "Gjennom dette alternativet kan en ny fil-slug erstatte standarden."

#: modules/components/rewrite-comments.php:55
msgid "e.g. user-input.php"
msgstr "f.eks. user-input.php"

#: modules/components/rewrite-comments.php:61 modules/components/rewrite-comments.php:64
msgid "Block default wp-comments-post.php"
msgstr "Blokker standard wp-comments-post.php"

#: modules/components/rewrite-comments.php:62
msgid "Block default wp-comments-post.php."
msgstr "Blokker standard wp-comments-post.php."

#: modules/components/rewrite-comments.php:65
msgid "After changing the default wp-comments-post.php, the old url is still accessible, this provide a way to block the old.<br />The functionality apply only if <b>New wp-comments-post.php</b> option is filled in."
msgstr "Etter å ha endret standard wp-comments-post.php, er den gamle URL-en fortsatt tilgjengelig, dette gir en måte å blokkere den gamle på.<br />Funksjonaliteten gjelder bare hvis <b>Ny wp-comments-post.php</b> alternativet er fylt ut."

#: modules/components/rewrite-json-rest.php:147
msgid "As default, when calling the REST API base route ( e.g. /wp-json/ ) the service outputs all available namespaces and routes."
msgstr "Som standard, når du kaller REST API base route (f.eks. /wp-json/), sender tjenesten ut alle tilgjengelige navneområder og ruter."

#: modules/components/rewrite-json-rest.php:151
msgid "When calling the site REST API base route ( e.g. /wp-json/ or ?rest_route=/ ) the service outputs all available namespaces and routes for current site. This can be a breach for the system, as outputs important information regarding certain used theme and plugins. "
msgstr "Ved å kalle nettstedets REST API base route (f.eks. /wp-json/ eller ?rest_route=/) sender tjenesten ut alle tilgjengelige navneområder og ruter for gjeldende nettsted. Dette kan være et sikkerhetsbrudd for systemet, ettersom det viktig informasjon om visse brukte temaer og plugins. "

#: modules/components/rewrite-json-rest.php:152
msgid "Recommended selection for this option is Yes, to ensure no inside data is being exposed. "
msgstr "Anbefalt valg for dette alternativet er Ja, for å sikre at ingen interne data blir eksponert. "

#: modules/components/rewrite-json-rest.php:165 modules/components/rewrite-json-rest.php:169
msgid "New JSON Path"
msgstr "Ny JSON-sti"

#: modules/components/rewrite-json-rest.php:166
msgid "The default JSON REST path is set to /wp-json."
msgstr "Standard JSON REST-sti er satt til /wp-json."

#: modules/components/rewrite-json-rest.php:170
msgid "Use any alphanumeric symbols for this field which will be used as the new slug for JSON API. Presuming the `apps-api` slug is being used, the new url becomes to:"
msgstr "Bruk alfanumeriske symboler for dette feltet som vil bli brukt som den nye slug-en for JSON API. Forutsatt at `apps-api` slug-en brukes, blir den nye URL-en:"

#: modules/components/rewrite-json-rest.php:175
msgid "e.g. api-json"
msgstr "f.eks. api-json"

#: modules/components/rewrite-json-rest.php:181 modules/components/rewrite-json-rest.php:185
msgid "Block default /wp-json"
msgstr "Blokker standard /wp-json"

#: modules/components/rewrite-json-rest.php:182
msgid "Block default /wp-json endpoint. This also can be used to block any JSON service version, even if not being re-mapped"
msgstr "Blokker standard /wp-json endepunkt. Dette kan også brukes til å blokkere enhver JSON tjenesteverjon, selv om den ikke er omtilordnet"

#: modules/components/rewrite-json-rest.php:186
msgid "This blocks the JSON REST API service."
msgstr "Dette blokkerer JSON REST API-tjenesten."

#: modules/components/rewrite-json-rest.php:187
msgid "When selecting the <b>Non logged-in</b> the service is blocked for all non-authenticated users."
msgstr "Når du velger <b>Ikke innlogget</b> blokkeres tjenesten for alle ikke-autentiserte brukere."

#: modules/components/rewrite-json-rest.php:188
msgid "When selecting the <b>All</b> the service is blocked for everyone."
msgstr "Når du velger <b>Alle</b> blokkeres tjenesten for alle."

#: modules/components/rewrite-json-rest.php:189
msgid "This might be required by specific plugins, including new WordPress editor Gutenberg. So if required to block the API, the <b>Non logged-in</b> is the appropriate option to use."
msgstr "Dette kan være nødvendig for spesifikke plugins, inkludert den nye WordPress-editoren Gutenberg. Så hvis det er nødvendig å blokkere API-en, er <b>Ikke innlogget</b> det riktige alternativet å bruke."

#: modules/components/rewrite-json-rest.php:195
msgid "Non logged-in"
msgstr "Ikke innlogget"

#: modules/components/rewrite-json-rest.php:203 modules/components/rewrite-json-rest.php:207
msgid "Disable JSON REST V1 service"
msgstr "Deaktiver JSON REST V1-tjeneste"

#: modules/components/rewrite-json-rest.php:204 modules/components/rewrite-json-rest.php:224
msgid "An API service for WordPress which is active by default."
msgstr "En API-tjeneste for WordPress som er aktiv som standard."

#: modules/components/rewrite-json-rest.php:208 modules/components/rewrite-json-rest.php:228
msgid "The WordPress REST API is an easy-to-use set of HTTP endpoints which allows access a site data in simple JSON format. That including users, posts, taxonomies and more. Retrieving or updating is as simple as sending a HTTP request."
msgstr "WordPress REST API er et brukervennlig sett med HTTP-endepunkter som gir tilgang til sidens data i enkel JSON-format. Dette inkluderer brukere, innlegg, taksonomier og mer. Henting eller oppdatering er like enkelt som å sende en HTTP-forespørsel."

#: modules/components/rewrite-json-rest.php:209 modules/components/rewrite-json-rest.php:229
msgid "A REST API can be consumed everywhere. On mobile applications, on front-end (web apps) or any other devices that have access on the net, practically everything can connect from anywhere to your site and interact though JSON REST API service."
msgstr "En REST API kan brukes overalt. På mobilapplikasjoner, på front-end (webapper) eller andre enheter med tilgang til nettet, praktisk talt alt kan koble til fra hvor som helst til din side og samhandle gjennom JSON REST API-tjenesten."

#: modules/components/rewrite-json-rest.php:210
msgid "V1 was the first development version of API, which currently is deprecated. To disable the usage of it, simply chose Yes."
msgstr "V1 var den første utviklingsversjonen av API-en, som nå er foreldet. For å deaktivere bruken av den, velg ganske enkelt Ja."

#: modules/components/rewrite-json-rest.php:223 modules/components/rewrite-json-rest.php:227
msgid "Disable JSON REST V2 service"
msgstr "Deaktiver JSON REST V2-tjeneste"

#: modules/components/rewrite-json-rest.php:230
msgid "V2 is the current development version of API, which is included into WordPress as default. To disable the usage of it, simply chose Yes."
msgstr "V2 er den nåværende utviklingsversjonen av API-en, som er inkludert i WordPress som standard. For å deaktivere bruken av den, velg ganske enkelt Ja."

#: modules/components/rewrite-json-rest.php:231
msgid "This might be required by specific plugins, including new WordPress editor Gutenberg."
msgstr "Dette kan være nødvendig for spesifikke plugins, inkludert den nye WordPress-editoren Gutenberg."

#: modules/components/rewrite-json-rest.php:249
msgid "As default the API url is being append into the front html head tag. Using this option, it will be replaced."
msgstr "Som standard blir API-URL-en lagt til i front HTML head-taggen. Ved å bruke dette alternativet vil den bli erstattet."

#: modules/components/rewrite-json-rest.php:262 modules/components/rewrite-json-rest.php:266
msgid "Disable JSON REST WP RSD endpoint from XML-RPC responses"
msgstr "Deaktiver JSON REST WP RSD endepunkt fra XML-RPC svar"

#: modules/components/rewrite-json-rest.php:263
msgid "By default a WP RSD endpoint is being append to the XML respose."
msgstr "Som standard legges et WP RSD endepunkt til i XML-svaret."

#: modules/components/rewrite-json-rest.php:267
msgid "Disable any RSD endpoint from a XML-RPC response."
msgstr "Deaktiver ethvert RSD endepunkt fra et XML-RPC svar."

#: modules/components/rewrite-json-rest.php:280 modules/components/rewrite-json-rest.php:284
msgid "Disable Sends a Link header for the REST API"
msgstr "Deaktiver 'Sender en Link-header for REST API'"

#: modules/components/rewrite-json-rest.php:281
msgid "On template_redirect, disable Sends a Link header for the REST API."
msgstr "På template_redirect, deaktiver 'Sender en Link-header for REST API'."

#: modules/components/rewrite-json-rest.php:285
msgid "Disable Sends a Link header for the REST API, on template_redirect"
msgstr "Deaktiver 'Sender en Link-header for REST API', på template_redirect"

#: modules/components/rewrite-map_custom_urls.php:34
msgid "Map Custom Urls"
msgstr "Tilpassede URL-kart"

#: modules/components/rewrite-map_custom_urls.php:35
msgid "Custom URLs mapping for links in HTML. The substitution is case-insensitive."
msgstr "Tilpasset URL-kartlegging for lenker i HTML. Erstatningen er ikke følsom for store/små bokstaver."

#: modules/components/rewrite-map_custom_urls.php:38
msgid "Any domain url can be mapped to something else. Any type of asset works with re-mapping e.g JavaScript, Cascading Style Sheets, Media Images etc."
msgstr "Enhver domene-URL kan kartlegges til noe annet. Alle typer ressurser fungerer med omtilordning, f.eks. JavaScript, Cascading Style Sheets, mediabilder etc."

#: modules/components/rewrite-map_custom_urls.php:39
msgid "For example the following link can be changed from:"
msgstr "For eksempel kan følgende lenke endres fra:"

#: modules/components/rewrite-map_custom_urls.php:41
msgid "to:"
msgstr "til:"

#: modules/components/rewrite-mu-plugins.php:35 modules/components/rewrite-mu-plugins.php:38
msgid "Block MU Plugins URL"
msgstr "Blokker MU-plugins URL"

#: modules/components/rewrite-mu-plugins.php:36
msgid "Block default /wp-content/mu-plugins/ files from being accessible through default urls."
msgstr "Blokker standard /wp-content/mu-plugins/ filer fra å være tilgjengelige gjennom standard URL-er."

#: modules/components/rewrite-mu-plugins.php:39
msgid "This blocks the default wp-content/mu-plugins/ url."
msgstr "Dette blokkerer standard wp-content/mu-plugins/ URL."

#: modules/components/rewrite-plugin_path.php:118
msgid "The default plugins path is set to"
msgstr "Standard plugins-sti er satt til"

#: modules/components/rewrite-plugin_path.php:122
msgid "Use any alphanumeric symbols for this field which will be used as the new slug for the plugins folder. Presuming the `apps` slug is being used, all plugins urls become to something like this:"
msgstr "Bruk alfanumeriske symboler for dette feltet som vil bli brukt som den nye slug-en for plugins-mappen. Forutsatt at `apps` slug-en brukes, blir alle plugin-URL-er til noe slikt:"

#: modules/components/rewrite-plugin_path.php:127
msgid "e.g. my_plugins"
msgstr "f.eks. mine_plugins"

#: modules/components/rewrite-plugin_path.php:133 modules/components/rewrite-plugin_path.php:137
msgid "Block plugins URL"
msgstr "Blokker plugins URL"

#: modules/components/rewrite-plugin_path.php:134
msgid "Block default /wp-content/plugins/ files from being accesible through default urls."
msgstr "Blokker standard /wp-content/plugins/ filer fra å være tilgjengelige gjennom standard URL-er."

#: modules/components/rewrite-plugin_path.php:138
msgid "This blocks the default wp-content/plugins/ url.<br />The functionality apply only if <b>New Plugins Path</b> option is filled in."
msgstr "Dette blokkerer standard wp-content/plugins/ URL.<br />Funksjonaliteten gjelder bare hvis <b>Ny Plugins Sti</b> alternativet er fylt ut."

#: modules/components/rewrite-plugin_path.php:168 modules/components/rewrite-plugin_path.php:172
msgid "New Path for"
msgstr "Ny sti for"

#: modules/components/rewrite-plugin_path.php:168
msgid "plugin"
msgstr "plugin"

#: modules/components/rewrite-plugin_path.php:169
msgid "This setting if set, overwrites the"
msgstr "Denne innstillingen, hvis satt, overskriver"

#: modules/components/rewrite-plugin_path.php:169
msgid "New Plugin Path"
msgstr "Ny Plugin Sti"

#: modules/components/rewrite-plugin_path.php:169
msgid "value for this plugin."
msgstr "verdien for denne pluginen."

#: modules/components/rewrite-plugin_path.php:173
msgid "Use any alphanumeric symbols for this field which will be used as the new slug for the plugin folder. Presuming the `module_name` slug is being used, this particular plugin urls become to"
msgstr "Bruk alfanumeriske symboler for dette feltet som vil bli brukt som den nye slug-en for plugin-mappen. Forutsatt at `module_name` slug-en brukes, blir denne spesifikke plugin-URL-en til"

#: modules/components/rewrite-plugin_path.php:179
msgid "e.g. modules/module"
msgstr "f.eks. moduler/modul"

#: modules/components/rewrite-registration.php:63 modules/components/rewrite-registration.php:66
msgid "New wp-signup·php"
msgstr "Ny wp-signup.php"

#: modules/components/rewrite-registration.php:64
msgid "Change default sign-up url."
msgstr "Endre standard registrerings-URL."

#: modules/components/rewrite-registration.php:67
msgid "This is the url through which users can register a site or / and a username."
msgstr "Dette er URL-en der brukere kan registrere en side og/eller et brukernavn."

#: modules/components/rewrite-registration.php:68
msgid "The registration status can be controlled through the network super admin interface:"
msgstr "Registreringsstatusen kan kontrolleres gjennom nettverks super admin grensesnittet:"

#: modules/components/rewrite-registration.php:70
msgid "If being active, it appears like the following URL:"
msgstr "Hvis den er aktiv, vises den som følgende URL:"

#: modules/components/rewrite-registration.php:74
msgid "e.g. register"
msgstr "f.eks. registrer"

#: modules/components/rewrite-registration.php:80
msgid "Block wp-signup·php URL"
msgstr "Blokker wp-signup.php URL"

#: modules/components/rewrite-registration.php:81
msgid "Block default wp-signup·php file."
msgstr "Blokker standard wp-signup.php fil."

#: modules/components/rewrite-registration.php:83
msgid "Block wp-signup·php"
msgstr "Blokker wp-signup.php"

#: modules/components/rewrite-registration.php:84
msgid "Block the default wp-signup·php file. If <b>New wp-signup·php</b> is being used, it is safe to block the default, and the registration process will continue to work."
msgstr "Blokker standard wp-signup.php fil. Hvis <b>Ny wp-signup.php</b> brukes, er det trygt å blokkere standard, og registreringsprosessen vil fortsette å fungere."

#: modules/components/rewrite-registration.php:96 modules/components/rewrite-registration.php:99
msgid "New wp-activate·php"
msgstr "Ny wp-activate.php"

#: modules/components/rewrite-registration.php:97
msgid "Change default blog activation url."
msgstr "Endre standard bloggaktiverings-URL."

#: modules/components/rewrite-registration.php:100
msgid "This is the URL through which a user can activate a registered blog."
msgstr "Dette er URL-en der en bruker kan aktivere en registrert blogg."

#: modules/components/rewrite-registration.php:101
msgid "The URL appears like the following:"
msgstr "URL-en vises som følgende:"

#: modules/components/rewrite-registration.php:105
msgid "e.g. account-activate"
msgstr "f.eks. konto-aktiver"

#: modules/components/rewrite-registration.php:111 modules/components/rewrite-registration.php:114
msgid "Block wp-activate·php"
msgstr "Blokker wp-activate.php"

#: modules/components/rewrite-registration.php:112
msgid "Block access to default wp-activate·php file."
msgstr "Blokker tilgang til standard wp-activate.php fil."

#: modules/components/rewrite-registration.php:115
msgid "Block access to wp-activate·php file. Through this file, new users confirm that the activation key they receive in the email after signing up for a new blog matches the key for that user."
msgstr "Blokker tilgang til wp-activate.php fil. Gjennom denne filen bekrefter nye brukere at aktiveringsnøkkelen de mottar i e-posten etter å ha registrert en ny blogg, samsvarer med nøkkelen for den brukeren."

#: modules/components/rewrite-registration.php:116
msgid "If <b>New wp-activate·php</b> is being used, it is safe to block the default, and the registration process will continue to work."
msgstr "Hvis <b>Ny wp-activate.php</b> brukes, er det trygt å blokkere standard, og registreringsprosessen vil fortsette å fungere."

#: modules/components/rewrite-root-files.php:118
msgid "Block access to license.txt root file"
msgstr "Blokker tilgang til license.txt rotfil"

#: modules/components/rewrite-root-files.php:136
msgid "Block access to readme.html root file"
msgstr "Blokker tilgang til readme.html rotfil"

#: modules/components/rewrite-root-files.php:153 modules/components/rewrite-root-files.php:157
msgid "Block wp-activate.php"
msgstr "Blokker wp-activate.php"

#: modules/components/rewrite-root-files.php:154
msgid "Block access to wp-activate.php file. This file confirms that the activation key that is sent in an email after a user signs up for a new blog matches the key for that user. If <b>anyone can register</b> on your site, you shold keep this off."
msgstr "Blokker tilgang til wp-activate.php fil. Denne filen bekrefter at aktiveringsnøkkelen som sendes i en e-post etter at en bruker registrerer en ny blogg, samsvarer med nøkkelen for den brukeren. Hvis <b>hvem som helst kan registrere seg</b> på din side, bør du holde dette av."

#: modules/components/rewrite-root-files.php:158
msgid "Block access to wp-activate.php file. Through this file new users confirms that the activation key that is received in the email after signs up for a new blog, matches the key for that user."
msgstr "Blokker tilgang til wp-activate.php fil. Gjennom denne filen bekrefter nye brukere at aktiveringsnøkkelen som mottas i e-posten etter registrering for en ny blogg, samsvarer med nøkkelen for den brukeren."

#: modules/components/rewrite-root-files.php:159
msgid "If anyone can register on your site, you should keep this to No."
msgstr "Hvis hvem som helst kan registrere seg på din side, bør du holde dette til Nei."

#: modules/components/rewrite-root-files.php:173
msgid "Block access to wp-cron.php file. If remote cron calls not being used this can be set to Yes."
msgstr "Blokker tilgang til wp-cron.php fil. Hvis eksterne cron-oppringninger ikke brukes, kan dette settes til Ja."

#: modules/components/rewrite-root-files.php:176
msgid "Unable to identify site domain IP, blocking wp-cron.php will stop the site internal WordPress cron functionality."
msgstr "Kan ikke identifisere sidens domene-IP, blokkering av wp-cron.php vil stoppe sidens interne WordPress cron-funksjonalitet."

#: modules/components/rewrite-root-files.php:180
msgid "Site domain rezolved to IP"
msgstr "Sidedomenet løst til IP"

#: modules/components/rewrite-root-files.php:180
msgid "If blocked, all internal calls to cron will continue to run fine. All calls from a different IP are blocked, including direct calls."
msgstr "Hvis blokkert, vil alle interne kall til cron fortsette å kjøre fint. Alle kall fra en annen IP er blokkert, inkludert direkte kall."

#: modules/components/rewrite-root-files.php:184 modules/components/rewrite-root-files.php:188
msgid "Block wp-cron.php"
msgstr "Blokker wp-cron.php"

#: modules/components/rewrite-root-files.php:189
msgid "The file wp-cron.php is the portion of WordPress that handles scheduled events within a WordPress site. If remote cron calls not being used this can be set to Yes.."
msgstr "Filen wp-cron.php er den delen av WordPress som håndterer planlagte hendelser i en WordPress-side. Hvis eksterne cron-oppringninger ikke brukes, kan dette settes til Ja."

#: modules/components/rewrite-root-files.php:203
msgid "Block wp-signup&period;php"
msgstr "Blokker wp-signup.php"

#: modules/components/rewrite-root-files.php:204
msgid "Block default wp-signup&period;php file. If <b>anyone can register</b> on your site, you shold keep this off."
msgstr "Blokker standard wp-signup.php fil. Hvis <b>hvem som helst kan registrere seg</b> på din side, bør du holde dette av."

#: modules/components/rewrite-root-files.php:207
msgid "Block default wp-signup&period;php"
msgstr "Blokker standard wp-signup.php"

#: modules/components/rewrite-root-files.php:208
msgid "The wp-signup&period;php allow for anyone to register to your site. If the registration functionality is turned off, is safe to block the  wp-signup&period;php."
msgstr "wp-signup.php tillater hvem som helst å registrere seg på din side. Hvis registreringsfunksjonaliteten er slått av, er det trygt å blokkere wp-signup.php."

#: modules/components/rewrite-root-files.php:221 modules/components/rewrite-root-files.php:225
msgid "Block wp-register.php"
msgstr "Blokker wp-register.php"

#: modules/components/rewrite-root-files.php:222
msgid "Block default wp-register.php file. This file is now deprecated however still exists within code and redirected to /register page."
msgstr "Blokker standard wp-register.php fil. Denne filen er nå foreldet, men eksisterer fortsatt i koden og omdirigeres til /register side."

#: modules/components/rewrite-root-files.php:226
msgid "This is a deprecated file but still present in many WordPress installs.  When called the user is redirected to /register page. Is safe to block the wp-register.php."
msgstr "Dette er en foreldet fil, men er fortsatt tilstede i mange WordPress-installasjoner. Når den kalles, omdirigeres brukeren til /register side. Det er trygt å blokkere wp-register.php."

#: modules/components/rewrite-root-files.php:239 modules/components/rewrite-root-files.php:243
msgid "Block other wp-*.php files"
msgstr "Blokker andre wp-*.php filer"

#: modules/components/rewrite-root-files.php:240 modules/components/rewrite-root-files.php:244
msgid "Block other wp-*.php files. E.g. wp-blog-header.php, wp-config.php, wp-cron.php. Those files are used internally, blocking those will not affect any functionality. Other root files (wp-activate.php, wp-login.php, wp-signup.php) are ignored, they can be controlled through own setting."
msgstr "Blokker andre wp-*.php filer. F.eks. wp-blog-header.php, wp-config.php, wp-cron.php. Disse filene brukes internt, blokkering av dem vil ikke påvirke noen funksjonalitet. Andre rotfiler (wp-activate.php, wp-login.php, wp-signup.php) ignoreres, de kan kontrolleres gjennom egne innstillinger."

#: modules/components/rewrite-search.php:44
msgid "New Search Path"
msgstr "Ny søkesti"

#: modules/components/rewrite-search.php:45
msgid "The default path is set to /search/"
msgstr "Standard sti er satt til /search/"

#: modules/components/rewrite-search.php:53
msgid "Block default /search/ when using custom one."
msgstr "Blokker standard /search/ når tilpasset søkesti brukes."

#: modules/components/rewrite-search.php:56
msgid "This option blocks the default /search/ URL from being accessed when a custom search path is in use. This applies only when <b>New Search Path</b> is set."
msgstr "Dette alternativet blokkerer standard /search/ URL fra å bli åpnet når en tilpasset søkesti er i bruk. Dette gjelder bare når <b>Ny Søkesti</b> er satt."

#: modules/components/rewrite-theme_path.php:69
msgid "Change the default theme url."
msgstr "Endre standard tema-URL."

#: modules/components/rewrite-theme_path.php:73
msgid "This option helps to change the theme url to a custom one. As default all theme assets ( styles, JavaScript etc ) are loaded using the theme url and appear on front side html source like this:"
msgstr "Dette alternativet hjelper til med å endre tema-URL-en til en tilpasset en. Som standard lastes alle temaresurser (stiler, JavaScript etc) ved hjelp av tema-URL-en og vises på frontend HTML-kilde slik:"

#: modules/components/rewrite-theme_path.php:75
msgid "When using this option, if filling with `template`, all urls on front side become as follow:"
msgstr "Når du bruker dette alternativet, hvis du fyller inn `template`, blir alle URL-er på frontsiden som følger:"

#: modules/components/rewrite-theme_path.php:80
msgid "e.g. my_template"
msgstr "f.eks. mitt_tema"

#: modules/components/rewrite-theme_path.php:96 modules/components/rewrite-theme_path.php:100
msgid "New Style File Path"
msgstr "Ny stil-fil sti"

#: modules/components/rewrite-theme_path.php:97
msgid "Change default theme style file style.css."
msgstr "Endre standard tema stil-fil style.css."

#: modules/components/rewrite-theme_path.php:101
msgid "This allow to change the default style.css filename to something else e.g. template-style.css. Per this example, on front side the main style link change from /style.css to /template-style.css"
msgstr "Dette tillater å endre standard style.css filnavnet til noe annet f.eks. template-style.css. I følge dette eksemplet, på frontsiden endres hovedstil-lenken fra /style.css til /template-style.css"

#: modules/components/rewrite-theme_path.php:107
msgid "e.g. custom-style-file.css"
msgstr "f.eks. tilpasset-stil-fil.css"

#: modules/components/rewrite-theme_path.php:124 modules/components/rewrite-theme_path.php:128
msgid "Remove description headers from Style file"
msgstr "Fjern beskrivelses-headere fra stil-fil"

#: modules/components/rewrite-theme_path.php:125
msgid "Strip out all meta data from style file."
msgstr "Fjern all metadata fra stil-fil."

#: modules/components/rewrite-theme_path.php:129
msgid "Strip out all meta data from style file as Theme Name, Theme URI, Author etc. Those are important informations for hackers to find out possible theme security breaches. A list of headers can e found at"
msgstr "Fjern all metadata fra stil-fil som Tema Navn, Tema URI, Forfatter etc. Dette er viktig informasjon for hackere for å finne ut mulige temasikkerhetsbrudd. En liste over headere kan finnes på"

#: modules/components/rewrite-theme_path.php:129
msgid "Theme Headers"
msgstr "Tema Headers"

#: modules/components/rewrite-theme_path.php:130
msgid "This feature may fail if style file url not available on html ( being concatenated )."
msgstr "Denne funksjonen kan feile hvis stil-fil URL ikke er tilgjengelig i HTML (blir satt sammen)."

#: modules/components/rewrite-upload_path.php:52 modules/components/rewrite-upload_path.php:56
msgid "New Uploads Path"
msgstr "Ny Opplastingssti"

#: modules/components/rewrite-upload_path.php:53
msgid "The default uploads path is set to"
msgstr "Standard opplastingssti er satt til"

#: modules/components/rewrite-upload_path.php:54
msgid "e.g. my_uploads"
msgstr "f.eks. mine_opplastinger"

#: modules/components/rewrite-upload_path.php:57
msgid "Use any alphanumeric symbols for this field which will be used as the new slug for the uploads folder. Using this option the default media folder can be mapped to another path. Filling with a slug like 'media' the links become like this:"
msgstr "Bruk alfanumeriske symboler for dette feltet som vil bli brukt som den nye slug-en for opplastingsmappen. Ved å bruke dette alternativet kan standard mediamappe kartlegges til en annen sti. Ved å fylle inn en slug som 'media' blir lenkene slik:"

#: modules/components/rewrite-upload_path.php:66 modules/components/rewrite-upload_path.php:69
msgid "Block default uploads URL"
msgstr "Blokker standard opplastings-URL"

#: modules/components/rewrite-upload_path.php:67
msgid "Block default /wp-content/uploads/ media folder from being accesible through default urls."
msgstr "Blokker standard /wp-content/uploads/ mediamappe fra å være tilgjengelig gjennom standard URL-er."

#: modules/components/rewrite-upload_path.php:70
msgid "This blocks the default wp-content/plugins/ URL.<br />The functionality applies only if <b>New Uploads Path</b> option is filled in."
msgstr "Dette blokkerer standard wp-content/plugins/ URL.<br />Funksjonaliteten gjelder bare hvis <b>Ny Opplastingssti</b> alternativet er fylt ut."

#: modules/components/rewrite-upload_path.php:82 modules/components/rewrite-upload_path.php:85
msgid "Redirect old URLs"
msgstr "Omdiriger gamle URL-er"

#: modules/components/rewrite-upload_path.php:83
msgid "All old URLs using format /wp-content/uploads/ will be redirected to new upload path."
msgstr "Alle gamle URL-er som bruker formatet /wp-content/uploads/ vil bli omdirigert til ny opplastingssti."

#: modules/components/rewrite-upload_path.php:86
msgid "If option active, all old URLs using format /wp-content/uploads/ will be redirected to the new upload path.<br />The redirect type is 301 - Moved Permanently, which is recommended for SEO purposes. <br />The functionality applies only if <b>New Uploads Path</b> option is filled in."
msgstr "Hvis alternativet er aktivt, vil alle gamle URL-er som bruker formatet /wp-content/uploads/ bli omdirigert til den nye opplastingsstien.<br />Omdirigeringstypen er 301 - Flyttet Permanent, som anbefales for SEO-formål. <br />Funksjonaliteten gjelder bare hvis <b>Ny Opplastingssti</b> alternativet er fylt ut."

#: modules/components/rewrite-wp_content_path.php:52 modules/components/rewrite-wp_content_path.php:56
msgid "New Content Path"
msgstr "Ny Innholdssti"

#: modules/components/rewrite-wp_content_path.php:53
msgid "Your default wp-content path is set to"
msgstr "Din standard wp-content sti er satt til"

#: modules/components/rewrite-wp_content_path.php:59
msgid "After filling in this option e.g. data the links become:"
msgstr "Etter å ha fylt ut dette alternativet f.eks. data blir lenkene:"

#: modules/components/rewrite-wp_content_path.php:64
msgid "e.g. my_content"
msgstr "f.eks. mitt_innhold"

#: modules/components/rewrite-wp_content_path.php:70 modules/components/rewrite-wp_content_path.php:74
msgid "Block wp-content URL"
msgstr "Blokker wp-content URL"

#: modules/components/rewrite-wp_content_path.php:71
msgid "Block default /wp-content/ path. Your default wp-content path is set to"
msgstr "Blokker standard /wp-content/ sti. Din standard wp-content sti er satt til"

#: modules/components/rewrite-wp_content_path.php:75
msgid "This blocks the default wp-content urls only for non loged-in users.<br />The functionality apply only if <b>New Content Path</b> option is filled in."
msgstr "Dette blokkerer standard wp-content URL-er bare for ikke innloggede brukere.<br />Funksjonaliteten gjelder bare hvis <b>Ny Innholdssti</b> alternativet er fylt ut."

#: modules/components/rewrite-wp_includes_path.php:42 modules/components/rewrite-wp_includes_path.php:45
msgid "New Includes Path"
msgstr "Ny Includes Sti"

#: modules/components/rewrite-wp_includes_path.php:43
msgid "Change default /wp-includes path."
msgstr "Endre standard /wp-includes sti."

#: modules/components/rewrite-wp_includes_path.php:48
msgid "After filling in this option e.g. resources the links will change to this:"
msgstr "Etter å ha fylt ut dette alternativet f.eks. ressurser vil lenkene endre til dette:"

#: modules/components/rewrite-wp_includes_path.php:52
msgid "e.g. my_includes"
msgstr "f.eks. mine_includes"

#: modules/components/rewrite-wp_includes_path.php:58 modules/components/rewrite-wp_includes_path.php:61
msgid "Block wp-includes URL"
msgstr "Blokker wp-includes URL"

#: modules/components/rewrite-wp_includes_path.php:59
msgid "Block /wp-includes/ files from being accesible through default urls. <br />Apply only if <b>New Includes Path</b> is not empty."
msgstr "Blokker /wp-includes/ filer fra å være tilgjengelige gjennom standard URL-er. <br />Gjelder bare hvis <b>Ny Includes Sti</b> ikke er tom."

#: modules/components/rewrite-wp_includes_path.php:62
msgid "This blocks the default wp-includes urls only for non loged-in users.<br />The functionality apply only if <b>New Includes Path</b> option is filled in."
msgstr "Dette blokkerer standard wp-includes URL-er bare for ikke innloggede brukere.<br />Funksjonaliteten gjelder bare hvis <b>Ny Includes Sti</b> alternativet er fylt ut."

#: modules/components/rewrite-xml-rpc-path.php:68 modules/components/rewrite-xml-rpc-path.php:72
msgid "New XML-RPC Path"
msgstr "Ny XML-RPC Sti"

#: modules/components/rewrite-xml-rpc-path.php:69
msgid "The default XML-RPC path is set to xmlrpc.php."
msgstr "Standard XML-RPC sti er satt til xmlrpc.php."

#: modules/components/rewrite-xml-rpc-path.php:70
msgid "e.g. my-xml-rpc.php"
msgstr "f.eks. min-xml-rpc.php"

#: modules/components/rewrite-xml-rpc-path.php:73
msgid "XML-RPC is a remote procedure call (RPC) protocol which uses XML to encode its calls and HTTP as a transport mechanism. This service allows other applications to talk to your WordPress site."
msgstr "XML-RPC er en fjernprosedyrekall (RPC) protokoll som bruker XML for å kode sine kall og HTTP som en transportmekanisme. Denne tjenesten tillater andre applikasjoner å snakke med din WordPress-side."

#: modules/components/rewrite-xml-rpc-path.php:74
msgid "As default the path to XML-RPC file is:"
msgstr "Som standard er stien til XML-RPC filen:"

#: modules/components/rewrite-xml-rpc-path.php:76
msgid "Through this option, it can be changed to anything else. This ensures the protocol will not be called by anyone who doesn't know the actual path."
msgstr "Gjennom dette alternativet kan den endres til hva som helst annet. Dette sikrer at protokollen ikke vil bli kalt av noen som ikke kjenner den faktiske stien."

#: modules/components/rewrite-xml-rpc-path.php:85 modules/components/rewrite-xml-rpc-path.php:88
msgid "Block default xmlrpc.php"
msgstr "Blokker standard xmlrpc.php"

#: modules/components/rewrite-xml-rpc-path.php:86
msgid "Block the default xmlrpc.php XML-RPC service."
msgstr "Blokker standard xmlrpc.php XML-RPC tjeneste."

#: modules/components/rewrite-xml-rpc-path.php:89
msgid "This blocks the default XML-RPC service. The functionality applies if <b>New XML-RPC Path</b> option is filled in."
msgstr "Dette blokkerer standard XML-RPC tjeneste. Funksjonaliteten gjelder hvis <b>Ny XML-RPC Sti</b> alternativet er fylt ut."

#: modules/components/rewrite-xml-rpc-path.php:90
msgid "Keep in mind that some third-party services, like Jetpack, rely on XML-RPC to connect to WordPress sites for features such as monitoring, statistics, and site management."
msgstr "Husk at noen tredjepartstjenester, som Jetpack, er avhengige av XML-RPC for å koble til WordPress-sider for funksjoner som overvåkning, statistikk og sideadministrasjon."

#: modules/components/rewrite-xml-rpc-path.php:102 modules/components/rewrite-xml-rpc-path.php:105
msgid "Disable XML-RPC methods requiring authentication"
msgstr "Deaktiver XML-RPC metoder som krever autentisering"

#: modules/components/rewrite-xml-rpc-path.php:103
msgid "Filter XML-RPC methods requiring authentication, such as for publishing purposes, are enabled."
msgstr "Filtrer XML-RPC metoder som krever autentisering, for eksempel for publiseringsformål, er aktivert."

#: modules/components/rewrite-xml-rpc-path.php:106
msgid "As default, certain methods require authentication for the protocol to be used along with a remote application (e.g., wp.restoreRevision, wp.getRevisions, wp.getPostTypes, wp.getPostType, wp.getPostFormats, wp.getMediaLibrary, wp.getMediaItem etc)."
msgstr "Som standard krever visse metoder autentisering for at protokollen skal brukes sammen med en fjernapplikasjon (f.eks. wp.restoreRevision, wp.getRevisions, wp.getPostTypes, wp.getPostType, wp.getPostFormats, wp.getMediaLibrary, wp.getMediaItem etc)."

#: modules/components/rewrite-xml-rpc-path.php:107
msgid "Activating the option, methods requiring authentication will be blocked through a call."
msgstr "Ved aktivering av alternativet, vil metoder som krever autentisering bli blokkert gjennom et kall."

#: modules/components/rewrite-xml-rpc-path.php:108
msgid "Brute force attacks often target the XML-RPC service. Therefore, it's advisable to enable this option unless you are using the service for specific purposes, such as with a remote mobile app."
msgstr "Brute force-angrep retter seg ofte mot XML-RPC-tjenesten. Derfor er det tilrådelig å aktivere dette alternativet med mindre du bruker tjenesten for spesifikke formål, som med en fjern mobilapp."

#: modules/components/rewrite-xml-rpc-path.php:120 modules/components/rewrite-xml-rpc-path.php:123
msgid "Disable XML-RPC service"
msgstr "Deaktiver XML-RPC tjeneste"

#: modules/components/rewrite-xml-rpc-path.php:121
msgid "When the XML-RPC service is deactivated, any calls to it result in the server returning a default 404 Not Found error page."
msgstr "Når XML-RPC-tjenesten er deaktivert, vil alle kall til den resultere i at serveren returnerer en standard 404 Not Found feilside."

#: modules/components/rewrite-xml-rpc-path.php:124
msgid "Before disabling the XML-RPC, ensure the service is not used for any of the followings:"
msgstr "Før du deaktiverer XML-RPC, sørg for at tjenesten ikke brukes til noe av følgende:"

#: modules/components/rewrite-xml-rpc-path.php:125
msgid "Mobile Apps: XML-RPC allows users to manage their WordPress sites via mobile apps. This feature makes it convenient for bloggers and administrators to create, edit, or delete posts from smartphones and tablets."
msgstr "Mobilapper: XML-RPC lar brukere administrere sine WordPress-sider via mobilapper. Denne funksjonen gjør det praktisk for bloggere og administratorer å opprette, redigere eller slette innlegg fra smarttelefoner og nettbrett."

#: modules/components/rewrite-xml-rpc-path.php:126
msgid "Third-Party Services: Many third-party services, like Jetpack, rely on XML-RPC to connect to WordPress sites for features such as monitoring, statistics, and site management."
msgstr "Tredjepartstjenester: Mange tredjepartstjenester, som Jetpack, er avhengige av XML-RPC for å koble til WordPress-sider for funksjoner som overvåkning, statistikk og sideadministrasjon."

#: modules/components/rewrite-xml-rpc-path.php:127
msgid "Content Syndication: XML-RPC can be used to syndicate content between different WordPress sites, sharing posts and updates."
msgstr "Innholdssyndikering: XML-RPC kan brukes til å syndikere innhold mellom forskjellige WordPress-sider, dele innlegg og oppdateringer."

#: modules/components/rewrite-xml-rpc-path.php:128
msgid "The Benefits of Disabling XML-RPC:"
msgstr "Fordelene med å deaktivere XML-RPC:"

#: modules/components/rewrite-xml-rpc-path.php:129
msgid "Improved Security: Disabling XML-RPC eliminates a potential entry point for attackers, protecting your site from brute force attacks and other malicious activities."
msgstr "Forbedret sikkerhet: Deaktivering av XML-RPC eliminerer et potensielt inngangspunkt for angripere, og beskytter din side mot brute force-angrep og andre ondsinnede aktiviteter."

#: modules/components/rewrite-xml-rpc-path.php:130
msgid "Reduced Server Load: By preventing DDoS attacks through XML-RPC, you can reduce the load on your server and improve site performance and availability."
msgstr "Redusert serverbelastning: Ved å forhindre DDoS-angrep gjennom XML-RPC kan du redusere belastningen på serveren din og forbedre sidens ytelse og tilgjengelighet."

#: modules/components/rewrite-xml-rpc-path.php:131
msgid "Better Control: Disabling XML-RPC ensures that your site remains under your control, minimizing the risk of unauthorized access or content manipulation."
msgstr "Bedre kontroll: Deaktivering av XML-RPC sikrer at din side forblir under din kontroll, og minimerer risikoen for uautorisert tilgang eller innholdsmanipulasjon."

#: modules/components/rewrite-xml-rpc-path.php:144 modules/components/rewrite-xml-rpc-path.php:147
msgid "Remove pingback"
msgstr "Fjern pingback"

#: modules/components/rewrite-xml-rpc-path.php:145
msgid "Remove pingback link tag from theme."
msgstr "Fjern pingback lenke-tag fra tema."

#: modules/components/rewrite-xml-rpc-path.php:148
msgid "A pingback is one of four types of link-back methods for Web authors to request notification when somebody links to one of their documents. This enables authors to keep track of who is linking to, or referring to their articles. Using this option, this functionality can be removed."
msgstr "En pingback er en av fire typer link-back metoder for web-forfattere for å be om varsling når noen lenker til et av deres dokumenter. Dette gjør at forfattere kan holde oversikt over hvem som lenker til eller refererer til deres artikler. Ved å bruke dette alternativet kan denne funksjonaliteten fjernes."

#: modules/components/security-check_headers.php:43
msgid "Allows a server to declare an embedder policy for a given document."
msgstr "Tillater en server å deklarere en innbydningspolicy for et gitt dokument."

#: modules/components/security-check_headers.php:49
msgid "Prevents other domains from opening/controlling a window."
msgstr "Forhindrer andre domener fra å åpne/kontrollere et vindu."

#: modules/components/security-check_headers.php:55
msgid "Prevents other domains from reading the response of the resources to which this header is applied."
msgstr "Forhindrer andre domener fra å lese svaret til ressursene som denne headeren er brukt på."

#: modules/components/security-check_headers.php:61
msgid "Controls resources the user agent is allowed to load for a given page."
msgstr "Kontrollerer ressurser som brukeragenten har lov til å laste for en gitt side."

#: modules/components/security-check_headers.php:67
msgid "Allows web developers to experiment with policies by monitoring, but not enforcing, their effects. These violation reports consist of JSON documents sent via an HTTP POST request to the specified URI."
msgstr "Tillater webutviklere å eksperimentere med policyer ved å overvåke, men ikke håndheve, deres effekter. Disse overtredelsesrapportene består av JSON-dokumenter sendt via en HTTP POST-forespørsel til den angitte URI-en."

#: modules/components/security-check_headers.php:73 modules/components/security-header-permissions-policy.php:50
msgid "Provides a mechanism to allow and deny the use of browser features in its own frame, and in iframes that it embeds."
msgstr "Gir en mekanisme for å tillate og nekte bruk av nettleserfunksjoner i sin egen ramme, og i iframes som den inneholder."

#: modules/components/security-check_headers.php:79
msgid "A policy that controls how much information is shared through the HTTP referrer header. Helps to protect user privacy."
msgstr "En policy som kontrollerer hvor mye informasjon som deles gjennom HTTP referrer headeren. Hjelper til med å beskytte brukerens personvern."

#: modules/components/security-check_headers.php:85
msgid "Force communication using HTTPS instead of HTTP."
msgstr "Tving kommunikasjon ved å bruke HTTPS i stedet for HTTP."

#: modules/components/security-check_headers.php:91
msgid "Disables MIME sniffing and forces browser to use the type given in Content-Type."
msgstr "Deaktiverer MIME-sniffing og tvinger nettleseren til å bruke typen gitt i Content-Type."

#: modules/components/security-check_headers.php:97
msgid "The X-Download-Options HTTP header indicates that the browser (Internet Explorer) should not display the option to \"Open\" a file that has been downloaded from an application, to prevent phishing attacks as the file otherwise would gain access to execute in the context of the application."
msgstr "X-Download-Options HTTP-headeren indikerer at nettleseren (Internet Explorer) ikke skal vise alternativet for å \"Åpne\" en fil som er lastet ned fra en applikasjon, for å forhindre phishing-angrep ettersom filen ellers ville få tilgang til å kjøre i applikasjonens kontekst."

#: modules/components/security-check_headers.php:103
msgid "Indicates whether a browser should be allowed to render a page in a &#60;frame&#62;, &#60;iframe&#62;, &#60;embed&#62; or &#60;object&#62;"
msgstr "Angir om en nettleser skal tillates å gjengi en side i en &#60;frame&#62;, &#60;iframe&#62;, &#60;embed&#62; eller &#60;object&#62;"

#: modules/components/security-check_headers.php:109
msgid "Specifies if a cross-domain policy file (crossdomain.xml) is allowed. The file may define a policy to grant clients, such as Adobe's Flash Player (now obsolete), Adobe Acrobat, Microsoft Silverlight (now obsolete), or Apache Flex, permission to handle data across domains that would otherwise be restricted due to the Same-Origin Policy. See the Cross-domain Policy File Specification for more information."
msgstr "Spesifiserer om en cross-domain policy fil (crossdomain.xml) er tillatt. Filen kan definere en policy for å gi klienter, som Adobe's Flash Player (nå foreldet), Adobe Acrobat, Microsoft Silverlight (nå foreldet), eller Apache Flex, tillatelse til å håndtere data på tvers av domener som ellers ville være begrenset på grunn av Same-Origin Policy. Se Cross-domain Policy File Specification for mer informasjon."

#: modules/components/security-check_headers.php:115
msgid "Created for browsers equipped with XSS filters, this non-standard header was intended as a way to control the filtering functionality."
msgstr "Opprettet for nettlesere utstyrt med XSS-filtre, denne ikke-standard headeren var ment som en måte å kontrollere filterfunksjonaliteten på."

#: modules/components/security-check_headers.php:135
msgid "Check Headers"
msgstr "Sjekk Headere"

#: modules/components/security-check_headers.php:138
msgid "HTTP Response Headers are a powerful tool to Harden Your Website.<br />Misusing the headers, can easily break the site layout and functionality. Ensure you understand the proper usage for each option before configuring. Once the Headers setup is completed, a thorough check for the front side is recommended."
msgstr "HTTP Response Headers er et kraftig verktøy for å styrke din nettside.<br />Feil bruk av headerne kan lett ødelegge sidens layout og funksjonalitet. Forsikre deg om at du forstår riktig bruk for hvert alternativ før konfigurering. Når Header-oppsettet er fullført, anbefales en grundig sjekk for frontsiden."

#: modules/components/security-check_headers.php:140
msgid "Copy the following link to a safe place. You can use it to reset the header options if something goes wrong:"
msgstr "Kopier følgende lenke til et trygt sted. Du kan bruke den til å tilbakestille header-alternativene hvis noe går galt:"

#: modules/components/security-check_headers.php:143
msgid "Create a sample setup for Headers. That will overwrite any Headers settings previously created through the plugin options. The sample setup creates a basic Headers implementation that is commonly safe on any site. For better performances, further manual adjustments are necessary."
msgstr "Opprett en prøveoppsett for Headere. Dette vil overskrive alle Header-innstillinger som tidligere er opprettet gjennom plugin-alternativene. Prøveoppsettet oppretter en grunnleggende Header-implementering som vanligvis er trygg på enhver side. For bedre ytelse er ytterligere manuelle justeringer nødvendige."

#: modules/components/security-check_headers.php:143
msgid "Create Sample Setup"
msgstr "Opprett Prøveoppsett"

#: modules/components/security-check_headers.php:145
msgid "The Hypertext Transfer Protocol (HTTP) is based on a client-server architecture, in which the client ( typically a web browser application ) establishes a connection with the server through a destination URL and waits for a response."
msgstr "Hypertext Transfer Protocol (HTTP) er basert på en klient-server arkitektur, der klienten (vanligvis en nettleserapplikasjon) etablerer en tilkobling med serveren gjennom en destinasjons-URL og venter på et svar."

#: modules/components/security-check_headers.php:146
msgid "The HTTP Headers allow the client and the server send additional pieces of information with the HTTP request or response."
msgstr "HTTP Headerne tillater klienten og serveren å sende ekstra informasjon med HTTP-forespørselen eller svaret."

#: modules/components/security-check_headers.php:147
msgid "The HTTP Headers are categorised by their purpose: Authentication, Caching, Client hints, Conditionals, Connection management, Content negotiation, Controls, Cookies, CORS, Downloads, Message body information, Proxies, Redirects, Request context, Response context, Range requests, <b>Security</b>, Server-sent events, Transfer coding, WebSockets, etc."
msgstr "HTTP Headerne er kategorisert etter deres formål: Autentisering, Caching, Client hints, Conditionals, Connection management, Content negotiation, Controls, Cookies, CORS, Downloads, Message body information, Proxies, Redirects, Request context, Response context, Range requests, <b>Sikkerhet</b>, Server-sent events, Transfer coding, WebSockets, etc."

#: modules/components/security-check_headers.php:148
msgid "This area provides support for the <b>"
msgstr "Dette området gir støtte for <b>"

#: modules/components/security-check_headers.php:148
msgid " type. Those are the ones responsible for the security implementation for any page."
msgstr " type. Disse er de som er ansvarlige for sikkerhetsimplementeringen for enhver side."

#: modules/components/security-check_headers.php:174
msgid "The current protection level is"
msgstr "Nåværende beskyttelsesnivå er"

#: modules/components/security-check_headers.php:186
msgid "Check Current Headers"
msgstr "Sjekk Nåværende Headere"

#: modules/components/security-check_headers.php:209
msgid "<br />Unable to parse the site Headers. The wp_remote_head() returned an invalid Response, check with your host support for more details.  Unable to identify your site Headers."
msgstr "<br />Kan ikke parse sidens Headere. wp_remote_head() returnerte et ugyldig svar, sjekk med din host support for flere detaljer. Kan ikke identifisere sidens Headere."

#: modules/components/security-check_headers.php:221
msgid "<br />Invalid WP_HTTP_Requests_Response object. The wp_remote_head() returned an invalid Response, check with your host support for more details."
msgstr "<br />Ugyldig WP_HTTP_Requests_Response objekt. wp_remote_head() returnerte et ugyldig svar, sjekk med din host support for flere detaljer."

#: modules/components/security-check_headers.php:230
msgid "<br />Unable to parse the site Headers. The wp_remote_head() returns invalid Response Code, check with your host support for more details."
msgstr "<br />Kan ikke parse sidens Headere. wp_remote_head() returnerer ugyldig Response Code, sjekk med din host support for flere detaljer."

#: modules/components/security-check_headers.php:240
msgid "<br />Unable to parse the site Headers. The wp_remote_head() returns a 401 error code, the request could not be authenticated. Does the site use an httpd password?"
msgstr "<br />Kan ikke parse sidens Headere. wp_remote_head() returnerer en 401 feilkode, forespørselen kunne ikke autentiseres. Bruker siden et httpd-passord?"

#: modules/components/security-check_headers.php:247
msgid "<br />Unable to parse the site Headers. The wp_remote_head() returns wrong Response Code"
msgstr "<br />Kan ikke parse sidens Headere. wp_remote_head() returnerer feil Response Code"

#: modules/components/security-check_headers.php:247
msgid ", check with your host support for more details."
msgstr ", sjekk med din host support for flere detaljer."

#: modules/components/security-check_headers.php:263
msgid "Header"
msgstr "Header"

#: modules/components/security-check_headers.php:334
msgid "Warning! The following headers could not be found:"
msgstr "Advarsel! Følgende headere kunne ikke finnes:"

#: modules/components/security-check_headers.php:335
msgid "Ensure the server mod_headers module is active."
msgstr "Forsikre deg om at serverens mod_headers modul er aktiv."

#: modules/components/security-check_headers.php:356
msgid "Consider adding more security headers:"
msgstr "Vurder å legge til flere sikkerhetsheadere:"

#: modules/components/security-header-content-security-policy-report-only.php:46 modules/components/security-header-content-security-policy-report-only.php:49
msgid "Content-Security-Policy-Report-Only"
msgstr "Content-Security-Policy-Report-Only"

#: modules/components/security-header-content-security-policy-report-only.php:50
msgid "The HTTP Content-Security-Policy-Report-Only response header allows web developers to experiment with Content-Security-Policy policies by monitoring (but not enforcing) their effects. These violation reports consist of JSON documents sent via an HTTP POST request to the specified URI."
msgstr "HTTP Content-Security-Policy-Report-Only responsheaderen tillater webutviklere å eksperimentere med Content-Security-Policy policyer ved å overvåke (men ikke håndheve) deres effekter. Disse overtredelsesrapportene består av JSON-dokumenter sendt via en HTTP POST-forespørsel til den angitte URI-en."

#: modules/components/security-header-content-security-policy-report-only.php:52 modules/components/security-header-content-security-policy.php:52 modules/components/security-header-permissions-policy.php:52
msgid "Directives:"
msgstr "Direktiver:"

#: modules/components/security-header-content-security-policy-report-only.php:53 modules/components/security-header-content-security-policy.php:53
msgid "Serves as a fallback for the other fetch directives.."
msgstr "Fungerer som en fallback for de andre hentedirektivene."

#: modules/components/security-header-content-security-policy-report-only.php:54 modules/components/security-header-content-security-policy.php:54
msgid "Defines the valid sources for web workers and nested browsing contexts loaded using elements such as &#60;frame&#62; and &#60;iframe&#62;."
msgstr "Definerer de gyldige kildene for web workers og nested browsing contexts lastet med elementer som &#60;frame&#62; og &#60;iframe&#62;."

#: modules/components/security-header-content-security-policy-report-only.php:55 modules/components/security-header-content-security-policy.php:55
msgid "Restricts the URLs which can be loaded using script interfaces."
msgstr "Begrenser URL-ene som kan lastes ved hjelp av skriptgrensesnitt."

#: modules/components/security-header-content-security-policy-report-only.php:56 modules/components/security-header-content-security-policy.php:56
msgid "Specifies valid sources for fonts loaded using @font-face."
msgstr "Spesifiserer gyldige kilder for fonter lastet med @font-face."

#: modules/components/security-header-content-security-policy-report-only.php:57 modules/components/security-header-content-security-policy-report-only.php:62 modules/components/security-header-content-security-policy.php:57 modules/components/security-header-content-security-policy.php:62
msgid "Specifies valid sources for nested browsing contexts loading using elements such as &#60;frame&#62; and &#60;iframe&#62;."
msgstr "Spesifiserer gyldige kilder for nested browsing contexts lasting med elementer som &#60;frame&#62; og &#60;iframe&#62;."

#: modules/components/security-header-content-security-policy-report-only.php:58 modules/components/security-header-content-security-policy.php:58
msgid "Specifies valid sources of images and favicons.."
msgstr "Spesifiserer gyldige kilder for bilder og favikoner."

#: modules/components/security-header-content-security-policy-report-only.php:59 modules/components/security-header-content-security-policy.php:59
msgid "Specifies valid sources of application manifest files."
msgstr "Spesifiserer gyldige kilder for applikasjonsmanifestfiler."

#: modules/components/security-header-content-security-policy-report-only.php:60 modules/components/security-header-content-security-policy.php:60
msgid "Specifies valid sources for loading media using the &#60;audio&#62; , &#60;video&#62; and &#60;track&#62; elements."
msgstr "Spesifiserer gyldige kilder for lasting av media ved hjelp av &#60;audio&#62;, &#60;video&#62; og &#60;track&#62; elementer."

#: modules/components/security-header-content-security-policy-report-only.php:61 modules/components/security-header-content-security-policy.php:61
msgid "Specifies valid sources for the &#60;object&#62;, &#60;embed&#62;, and &#60;applet&#62; elements."
msgstr "Spesifiserer gyldige kilder for &#60;object&#62;, &#60;embed&#62; og &#60;applet&#62; elementer."

#: modules/components/security-header-content-security-policy-report-only.php:63 modules/components/security-header-content-security-policy.php:63
msgid "Specifies valid sources for JavaScript."
msgstr "Spesifiserer gyldige kilder for JavaScript."

#: modules/components/security-header-content-security-policy-report-only.php:64 modules/components/security-header-content-security-policy.php:64
msgid "Specifies valid sources for JavaScript &#60;script&#62; elements."
msgstr "Spesifiserer gyldige kilder for JavaScript &#60;script&#62; elementer."

#: modules/components/security-header-content-security-policy-report-only.php:65 modules/components/security-header-content-security-policy.php:65
msgid "Specifies valid sources for JavaScript inline event handlers."
msgstr "Spesifiserer gyldige kilder for JavaScript inline event handlers."

#: modules/components/security-header-content-security-policy-report-only.php:66 modules/components/security-header-content-security-policy.php:66
msgid "Specifies valid sources for stylesheets."
msgstr "Spesifiserer gyldige kilder for stilark."

#: modules/components/security-header-content-security-policy-report-only.php:67 modules/components/security-header-content-security-policy.php:67
msgid "Specifies valid sources for stylesheets &#60;style&#62; elements and &#60;link&#62; elements with rel='stylesheet'. "
msgstr "Spesifiserer gyldige kilder for stilark &#60;style&#62; elementer og &#60;link&#62; elementer med rel='stylesheet'."

#: modules/components/security-header-content-security-policy-report-only.php:68 modules/components/security-header-content-security-policy.php:68
msgid "Specifies valid sources for inline styles applied to individual DOM elements."
msgstr "Spesifiserer gyldige kilder for inline stiler brukt på individuelle DOM-elementer."

#: modules/components/security-header-content-security-policy-report-only.php:69 modules/components/security-header-content-security-policy.php:69
msgid "Specifies valid sources for Worker, SharedWorker, or ServiceWorker scripts."
msgstr "Spesifiserer gyldige kilder for Worker, SharedWorker eller ServiceWorker skript."

#: modules/components/security-header-content-security-policy-report-only.php:70 modules/components/security-header-content-security-policy.php:70
msgid "Restricts the URLs which can be used in a document's &#60;base&#62; element. "
msgstr "Begrenser URL-ene som kan brukes i et dokuments &#60;base&#62; element."

#: modules/components/security-header-content-security-policy-report-only.php:71 modules/components/security-header-content-security-policy.php:71
msgid "Enables a sandbox for the requested resource similar to the &#60;iframe&#62; sandbox attribute."
msgstr "Aktiverer en sandkasse for den forespurte ressursen som ligner på &#60;iframe&#62; sandbox-attributtet."

#: modules/components/security-header-content-security-policy-report-only.php:72 modules/components/security-header-content-security-policy.php:72
msgid "Restricts the URLs which can be used as the target of a form submissions from a given context."
msgstr "Begrenser URL-ene som kan brukes som målet for en skjemainnsending fra en gitt kontekst."

#: modules/components/security-header-content-security-policy-report-only.php:73 modules/components/security-header-content-security-policy.php:73
msgid "Specifies valid parents that may embed a page using &#60;frame&#62;, &#60;iframe&#62;, &#60;object&#62;, &#60;embed&#62;, or &#60;applet&#62;. "
msgstr "Spesifiserer gyldige foreldre som kan bygge inn en side ved hjelp av &#60;frame&#62;, &#60;iframe&#62;, &#60;object&#62;, &#60;embed&#62; eller &#60;applet&#62;."

#: modules/components/security-header-content-security-policy-report-only.php:74 modules/components/security-header-content-security-policy.php:74
msgid "Restricts the URLs to which a document can initiate navigation by any means, including &#60;form&#62; (if form-action is not specified), &#60;a&#62;, window.location, window.open, etc."
msgstr "Begrenser URL-ene som et dokument kan initiere navigering til på noen måte, inkludert &#60;form&#62; (hvis form-action ikke er spesifisert), &#60;a&#62;, window.location, window.open, etc."

#: modules/components/security-header-content-security-policy-report-only.php:75 modules/components/security-header-content-security-policy.php:75
msgid "The directive instructs the user agent to report attempts to violate the Content Security Policy. These violation reports consist of JSON documents sent via an HTTP POST request to the specified URI."
msgstr "Direktivet instruerer brukeragenten om å rapportere forsøk på å krenke Content Security Policy. Disse overtredelsesrapportene består av JSON-dokumenter sendt via en HTTP POST-forespørsel til den angitte URI-en."

#: modules/components/security-header-content-security-policy-report-only.php:76 modules/components/security-header-content-security-policy.php:76
msgid "Fires a SecurityPolicyViolationEvent. These violation reports consist of JSON documents sent via an HTTP POST request to the specified URI."
msgstr "Utløser en SecurityPolicyViolationEvent. Disse overtredelsesrapportene består av JSON-dokumenter sendt via en HTTP POST-forespørsel til den angitte URI-en."

#: modules/components/security-header-content-security-policy-report-only.php:77 modules/components/security-header-content-security-policy.php:77
msgid "Requires the use of SRI for scripts or styles on the page."
msgstr "Krever bruk av SRI for skript eller stiler på siden."

#: modules/components/security-header-content-security-policy-report-only.php:78 modules/components/security-header-content-security-policy.php:78
msgid "Enforces Trusted Types at the DOM XSS injection sinks."
msgstr "Håndhever Trusted Types på DOM XSS injeksjonspunkter."

#: modules/components/security-header-content-security-policy-report-only.php:79 modules/components/security-header-content-security-policy.php:79
msgid "Used to specify an allow-list of Trusted Types policies. Trusted Types allows applications to lock down DOM XSS injection sinks to only accept non-spoofable, typed values in place of strings."
msgstr "Brukes til å spesifisere en tillatelsesliste for Trusted Types policyer. Trusted Types lar applikasjoner låse DOM XSS injeksjonspunkter for kun å akseptere ikke-forfalskbare, typede verdier i stedet for strenger."

#: modules/components/security-header-content-security-policy-report-only.php:80 modules/components/security-header-content-security-policy.php:80
msgid "Instructs user agents to treat all of a site's insecure URLs (those served over HTTP) as though they have been replaced with secure URLs (those served over HTTPS). This directive is intended for web sites with large numbers of insecure legacy URLs that need to be rewritten."
msgstr "Instruerer brukeragenter om å behandle alle en sidens usikre URL-er (de som serveres over HTTP) som om de er erstattet med sikre URL-er (de som serveres over HTTPS). Dette direktivet er ment for nettsider med store mengder usikre eldre URL-er som må omskrives."

#: modules/components/security-header-content-security-policy-report-only.php:82 modules/components/security-header-content-security-policy.php:82
msgid "Values:"
msgstr "Verdier:"

#: modules/components/security-header-content-security-policy-report-only.php:83 modules/components/security-header-content-security-policy.php:83
msgid "Won't allow loading of any resources."
msgstr "Tillater ikke lasting av noen ressurser."

#: modules/components/security-header-content-security-policy-report-only.php:84 modules/components/security-header-content-security-policy.php:84
msgid "Only allow resources from the current origin."
msgstr "Tillater kun ressurser fra gjeldende opprinnelse."

#: modules/components/security-header-content-security-policy-report-only.php:85 modules/components/security-header-content-security-policy.php:85
msgid "The trust granted to a script in the page due to an accompanying nonce or hash is extended to the scripts it loads."
msgstr "Tilliten gitt til et skript på siden på grunn av en medfølgende nonce eller hash utvides til skriptene det laster."

#: modules/components/security-header-content-security-policy-report-only.php:86 modules/components/security-header-content-security-policy.php:86
msgid "Require a sample of the violating code to be included in the violation report."
msgstr "Krever at et utvalg av den krenkende koden inkluderes i overtredelsesrapporten."

#: modules/components/security-header-content-security-policy-report-only.php:87 modules/components/security-header-content-security-policy.php:87
msgid "Allow use of inline resources."
msgstr "Tillat bruk av inline ressurser."

#: modules/components/security-header-content-security-policy-report-only.php:88 modules/components/security-header-content-security-policy.php:88
msgid "Allow use of dynamic code evaluation such as eval, setImmediate , and window.execScript."
msgstr "Tillat bruk av dynamisk kodeevaluering som eval, setImmediate og window.execScript."

#: modules/components/security-header-content-security-policy-report-only.php:89 modules/components/security-header-content-security-policy.php:89
msgid "Only allow loading of resources from a specific host, with optional scheme, port, and path. e.g. example.com, *.example.com, https://*.example.com:12/path/to/file.js."
msgstr "Tillater kun lasting av ressurser fra en spesifikk vert, med valgfri skjema, port og sti. f.eks. example.com, *.example.com, https://*.example.com:12/path/to/file.js."

#: modules/components/security-header-content-security-policy-report-only.php:90 modules/components/security-header-content-security-policy.php:90
msgid "Path parts in the CSP that end in / match any path they are a prefix of. e.g. example.com/api/ will match URLs like example.com/api/users/new."
msgstr "Stideler i CSP som slutter med / matcher enhver sti de er et prefiks av. f.eks. example.com/api/ vil matche URL-er som example.com/api/users/new."

#: modules/components/security-header-content-security-policy-report-only.php:91 modules/components/security-header-content-security-policy.php:91
msgid "Other path parts in the CSP are matched exactly e.g. example.com/file.js will match http://example.com/file.js and https://example.com/file.js, but not https://example.com/file.js/file2.js."
msgstr "Andre stideler i CSP matches nøyaktig f.eks. example.com/file.js vil matche http://example.com/file.js og https://example.com/file.js, men ikke https://example.com/file.js/file2.js."

#: modules/components/security-header-content-security-policy-report-only.php:92 modules/components/security-header-content-security-policy.php:92
msgid "Only allow loading of resources over a specific scheme e.g. https:, http:, data:, mediastream:, blob:, filesystem:"
msgstr "Tillater kun lasting av ressurser over et spesifikt skjema f.eks. https:, http:, data:, mediastream:, blob:, filesystem:"

#: modules/components/security-header-content-security-policy-report-only.php:93 modules/components/security-header-content-security-policy.php:93
msgid "Alternatively, a JavaScript hash can be used instead.  The CSP Level 2 specification allows to compute the SHA-256 / sha384 / sha512 for the inline JavaScript code."
msgstr "Alternativt kan en JavaScript hash brukes i stedet. CSP Level 2-spesifikasjonen tillater å beregne SHA-256 / sha384 / sha512 for den inline JavaScript-koden."

#: modules/components/security-header-content-security-policy-report-only.php:158 modules/components/security-header-content-security-policy.php:159 modules/components/security-header-cross-origin-embedder-policy.php:93 modules/components/security-header-cross-origin-opener-policy.php:97 modules/components/security-header-cross-origin-resource-policy.php:93 modules/components/security-header-permissions-policy.php:154 modules/components/security-header-referrer-policy.php:99 modules/components/security-header-stricy-transport-security.php:97 modules/components/security-header-x-content-type-options.php:93 modules/components/security-header-x-download-options.php:91 modules/components/security-header-x-frame-options.php:97 modules/components/security-header-x-permitted-cross-domain-policies.php:97 modules/components/security-header-x-xss-protection.php:98
msgid "Enable Header"
msgstr "Aktiver Header"

#: modules/components/security-header-content-security-policy-report-only.php:256 modules/components/security-header-content-security-policy.php:257
msgid "report-uri"
msgstr "report-uri"

#: modules/components/security-header-content-security-policy-report-only.php:263 modules/components/security-header-content-security-policy.php:264
msgid "report-to"
msgstr "report-to"

#: modules/components/security-header-content-security-policy-report-only.php:270 modules/components/security-header-content-security-policy.php:271
msgid "sandbox"
msgstr "sandbox"

#: modules/components/security-header-content-security-policy-report-only.php:328 modules/components/security-header-content-security-policy.php:329
msgid "require-sri-for"
msgstr "require-sri-for"

#: modules/components/security-header-content-security-policy-report-only.php:374 modules/components/security-header-content-security-policy.php:375
msgid "block-all-mixed-content"
msgstr "block-all-mixed-content"

#: modules/components/security-header-content-security-policy-report-only.php:382 modules/components/security-header-content-security-policy.php:383
msgid "upgrade-insecure-requests"
msgstr "upgrade-insecure-requests"

#: modules/components/security-header-content-security-policy.php:46 modules/components/security-header-content-security-policy.php:49
msgid "Content-Security-Policy"
msgstr "Content-Security-Policy"

#: modules/components/security-header-content-security-policy.php:50
msgid "The HTTP Content-Security-Policy response header allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints. This helps guard against cross-site scripting attacks (Cross-site_scripting)."
msgstr "HTTP Content-Security-Policy responsheaderen lar nettsideadministratorer kontrollere ressurser som brukeragenten har lov til å laste for en gitt side. Med noen få unntak involverer policyer for det meste å spesifisere serveropprinnelser og skriptendepunkter. Dette hjelper til med å beskytte mot tverrside skriptangrep (Cross-site_scripting)."

#: modules/components/security-header-cross-origin-embedder-policy.php:47
msgid "Cross-Origin-Embedder-Policy (COEP)"
msgstr "Cross-Origin-Embedder-Policy (COEP)"

#: modules/components/security-header-cross-origin-embedder-policy.php:50
msgid "Cross-Origin-Embedder-Policy"
msgstr "Cross-Origin-Embedder-Policy"

#: modules/components/security-header-cross-origin-embedder-policy.php:51
msgid "The HTTP Cross-Origin-Embedder-Policy (COEP) response header prevents a document from loading any cross-origin resources that don't explicitly grant the document permission (using CORP or CORS)."
msgstr "HTTP Cross-Origin-Embedder-Policy (COEP) responsheaderen forhindrer et dokument i å laste noen tverropprinnelige ressurser som ikke eksplisitt gir dokumentet tillatelse (ved bruk av CORP eller CORS)."

#: modules/components/security-header-cross-origin-embedder-policy.php:52 modules/components/security-header-cross-origin-opener-policy.php:53 modules/components/security-header-cross-origin-resource-policy.php:51 modules/components/security-header-referrer-policy.php:52 modules/components/security-header-stricy-transport-security.php:52 modules/components/security-header-x-content-type-options.php:53 modules/components/security-header-x-frame-options.php:52 modules/components/security-header-x-permitted-cross-domain-policies.php:54 modules/components/security-header-x-xss-protection.php:52
msgid "Options:"
msgstr "Alternativer:"

#: modules/components/security-header-cross-origin-embedder-policy.php:53
msgid "This is the default value. Allows the document to fetch cross-origin resources without giving explicit permission through the CORS protocol or the Cross-Origin-Resource-Policy header."
msgstr "Dette er standardverdien. Tillater dokumentet å hente tverropprinnelige ressurser uten å gi eksplisitt tillatelse gjennom CORS-protokollen eller Cross-Origin-Resource-Policy headeren."

#: modules/components/security-header-cross-origin-embedder-policy.php:54
msgid "A document can only load resources from the same origin, or resources explicitly marked as loadable from another origin. If a cross origin resource supports CORS, the crossorigin attribute or the Cross-Origin-Resource-Policy header must be used to load it without being blocked by COEP."
msgstr "Et dokument kan bare laste ressurser fra samme opprinnelse, eller ressurser eksplisitt merket som lastbare fra en annen opprinnelse. Hvis en tverropprinnelig ressurs støtter CORS, må crossorigin-attributtet eller Cross-Origin-Resource-Policy headeren brukes for å laste den uten å bli blokkert av COEP."

#: modules/components/security-header-cross-origin-embedder-policy.php:104 modules/components/security-header-cross-origin-opener-policy.php:108 modules/components/security-header-cross-origin-resource-policy.php:104 modules/components/security-header-referrer-policy.php:110 modules/components/security-header-stricy-transport-security.php:108 modules/components/security-header-x-content-type-options.php:104 modules/components/security-header-x-download-options.php:102 modules/components/security-header-x-frame-options.php:108 modules/components/security-header-x-permitted-cross-domain-policies.php:108 modules/components/security-header-x-xss-protection.php:109
msgid "Header Options"
msgstr "Header Alternativer"

#: modules/components/security-header-cross-origin-opener-policy.php:46
msgid "Cross-Origin-Opener-Policy (COOP)"
msgstr "Cross-Origin-Opener-Policy (COOP)"

#: modules/components/security-header-cross-origin-opener-policy.php:49
msgid "Cross-Origin-Opener-Policy"
msgstr "Cross-Origin-Opener-Policy"

#: modules/components/security-header-cross-origin-opener-policy.php:50
msgid "The HTTP Cross-Origin-Opener-Policy (COOP) response header allows you to ensure a top-level document does not share a browsing context group with cross-origin documents."
msgstr "HTTP Cross-Origin-Opener-Policy (COOP) responsheaderen lar deg sikre at et toppnivådokument ikke deler en browsing context gruppe med tverropprinnelige dokumenter."

#: modules/components/security-header-cross-origin-opener-policy.php:51
msgid "COOP will process-isolate your document and potential attackers can't access your global object if they were to open it in a popup, preventing a set of cross-origin attacks dubbed XS-Leaks."
msgstr "COOP vil prosess-isolere dokumentet ditt og potensielle angripere kan ikke få tilgang til ditt globale objekt hvis de skulle åpne det i en popup, noe som forhindrer en rekke tverropprinnelige angrep kalt XS-Leaks."

#: modules/components/security-header-cross-origin-opener-policy.php:52
msgid "If a cross-origin document with COOP is opened in a new window, the opening document will not have a reference to it, and the window.opener property of the new window will be null. This allows you to have more control over references to a window than rel=noopener, which only affects outgoing navigations."
msgstr "Hvis et tverropprinnelig dokument med COOP åpnes i et nytt vindu, vil åpningsdokumentet ikke ha en referanse til det, og window.opener-egenskapen til det nye vinduet vil være null. Dette gir deg mer kontroll over referanser til et vindu enn rel=noopener, som bare påvirker utgående navigeringer."

#: modules/components/security-header-cross-origin-opener-policy.php:54
msgid "This is the default value. Allows the document to be added to its opener's browsing context group unless the opener itself has a COOP of same-origin or same-origin-allow-popups."
msgstr "Dette er standardverdien. Tillater dokumentet å bli lagt til i åpnerens browsing context gruppe med mindre åpneren selv har en COOP av same-origin eller same-origin-allow-popups."

#: modules/components/security-header-cross-origin-opener-policy.php:55
msgid "Retains references to newly opened windows or tabs that either don't set COOP or that opt out of isolation by setting a COOP of unsafe-none."
msgstr "Beholder referanser til nylig åpnede vinduer eller faner som enten ikke setter COOP eller som velger bort isolasjon ved å sette en COOP av unsafe-none."

#: modules/components/security-header-cross-origin-opener-policy.php:56
msgid "Isolates the browsing context exclusively to same-origin documents. Cross-origin documents are not loaded in the same browsing context."
msgstr "Isolerer browsing context utelukkende til samme opprinnelsesdokumenter. Tverropprinnelige dokumenter lastes ikke i samme browsing context."

#: modules/components/security-header-cross-origin-resource-policy.php:46
msgid "Cross-Origin-Resource-Policy (CORP)"
msgstr "Cross-Origin-Resource-Policy (CORP)"

#: modules/components/security-header-cross-origin-resource-policy.php:49
msgid "Cross-Origin-Resource-Policy"
msgstr "Cross-Origin-Resource-Policy"

#: modules/components/security-header-cross-origin-resource-policy.php:50
msgid "The HTTP Content-Security-Policy response header allows web site administrators to control resources the user agent is allowed to load for a given page. With a few exceptions, policies mostly involve specifying server origins and script endpoints. This helps guard against cross-site scripting attacks (Cross-site_scripting). "
msgstr "HTTP Content-Security-Policy responsheaderen lar nettsideadministratorer kontrollere ressurser som brukeragenten har lov til å laste for en gitt side. Med noen få unntak involverer policyer for det meste å spesifisere serveropprinnelser og skriptendepunkter. Dette hjelper til med å beskytte mot tverrside skriptangrep (Cross-site_scripting)."

#: modules/components/security-header-cross-origin-resource-policy.php:52
msgid "Only requests from the same Site can read the resource."
msgstr "Kun forespørsler fra samme nettsted kan lese ressursen."

#: modules/components/security-header-cross-origin-resource-policy.php:53
msgid "Only requests from the same origin (i.e. scheme + host + port) can read the resource."
msgstr "Kun forespørsler fra samme opprinnelse (dvs. skjema + vert + port) kan lese ressursen."

#: modules/components/security-header-cross-origin-resource-policy.php:54
msgid "Requests from any origin (both same-site and cross-site) can read the resource. This is useful when COEP is used"
msgstr "Forespørsler fra enhver opprinnelse (både samme nettsted og tverrnettsted) kan lese ressursen. Dette er nyttig når COEP brukes"

#: modules/components/security-header-permissions-policy.php:46 modules/components/security-header-permissions-policy.php:49
msgid "Permissions Policy"
msgstr "Permissions Policy"

#: modules/components/security-header-permissions-policy.php:53
msgid "Controls whether the current document is allowed to gather information about the acceleration of the device through the Accelerometer interface."
msgstr "Kontrollerer om gjeldende dokument har lov til å samle informasjon om akselerasjonen til enheten gjennom Accelerometer-grensesnittet."

#: modules/components/security-header-permissions-policy.php:54
msgid "Controls whether the current document is allowed to gather information about the amount of light in the environment around the device through the AmbientLightSensor interface."
msgstr "Kontrollerer om gjeldende dokument har lov til å samle informasjon om mengden lys i miljøet rundt enheten gjennom AmbientLightSensor-grensesnittet."

#: modules/components/security-header-permissions-policy.php:55
msgid "Controls whether the current document is allowed to autoplay media requested through the HTMLMediaElement interface. When this policy is disabled and there were no user gestures, the Promise returned by HTMLMediaElement.play() will reject with a DOMException. The autoplay attribute on <audio> and <video> elements will be ignored."
msgstr "Kontrollerer om gjeldende dokument har lov til å automatisk avspille media forespurt gjennom HTMLMediaElement-grensesnittet. Når denne policyen er deaktivert og det ikke var noen brukergester, vil Promise returnert av HTMLMediaElement.play() avvise med en DOMException. autoplay-attributtet på <audio> og <video> elementer vil bli ignorert."

#: modules/components/security-header-permissions-policy.php:56
msgid "Controls whether the use of the Battery Status API is allowed. When this policy is disabled, the Promise returned by Navigator.getBattery() will reject with a NotAllowedError DOMException."
msgstr "Kontrollerer om bruk av Battery Status API er tillatt. Når denne policyen er deaktivert, vil Promise returnert av Navigator.getBattery() avvise med en NotAllowedError DOMException."

#: modules/components/security-header-permissions-policy.php:57
msgid "Controls whether the current document is allowed to use video input devices. When this policy is disabled, the Promise returned by getUserMedia() will reject with a NotAllowedError DOMException."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke videoinngangsenheter. Når denne policyen er deaktivert, vil Promise returnert av getUserMedia() avvise med en NotAllowedError DOMException."

#: modules/components/security-header-permissions-policy.php:58
msgid "Controls whether or not the current document is permitted to use the getDisplayMedia() method to capture screen contents. When this policy is disabled, the promise returned by getDisplayMedia() will reject with a NotAllowedError if permission is not obtained to capture the display's contents."
msgstr "Kontrollerer om gjeldende dokument har tillatelse til å bruke getDisplayMedia()-metoden for å fange skjerminnhold. Når denne policyen er deaktivert, vil promise returnert av getDisplayMedia() avvise med en NotAllowedError hvis tillatelse ikke er innhentet for å fange skjermens innhold."

#: modules/components/security-header-permissions-policy.php:59
msgid "Controls whether the current document is allowed to set document.domain. When this policy is disabled, attempting to set document.domain will fail and cause a SecurityError DOMException to be thrown."
msgstr "Kontrollerer om gjeldende dokument har lov til å sette document.domain. Når denne policyen er deaktivert, vil forsøk på å sette document.domain mislykkes og forårsake at en SecurityError DOMException kastes."

#: modules/components/security-header-permissions-policy.php:60
msgid "Controls whether the current document is allowed to use the Encrypted Media Extensions API (EME). When this policy is disabled, the Promise returned by Navigator.requestMediaKeySystemAccess() will reject with a DOMException."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Encrypted Media Extensions API (EME). Når denne policyen er deaktivert, vil Promise returnert av Navigator.requestMediaKeySystemAccess() avvise med en DOMException."

#: modules/components/security-header-permissions-policy.php:61
msgid "Controls whether tasks should execute in frames while they're not being rendered (e.g. if an iframe is hidden or display: none)."
msgstr "Kontrollerer om oppgaver skal utføres i rammer mens de ikke gjengis (f.eks. hvis en iframe er skjult eller display: none)."

#: modules/components/security-header-permissions-policy.php:62
msgid "Controls whether tasks should execute in frames while they're outside of the visible viewport."
msgstr "Kontrollerer om oppgaver skal utføres i rammer mens de er utenfor det synlige visningsområdet."

#: modules/components/security-header-permissions-policy.php:63
msgid "Controls whether the current document is allowed to use Element.requestFullScreen(). When this policy is disabled, the returned Promise rejects with a TypeError."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Element.requestFullScreen(). Når denne policyen er deaktivert, avviser den returnerte Promise med en TypeError."

#: modules/components/security-header-permissions-policy.php:64
msgid "Controls whether the current document is allowed to use the Gamepad API. When this policy is disabled, calls to Navigator.getGamepads() will throw a SecurityError DOMException, and the gamepadconnected and gamepaddisconnected events will not fire. "
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Gamepad API. Når denne policyen er deaktivert, vil kall til Navigator.getGamepads() kaste en SecurityError DOMException, og gamepadconnected og gamepaddisconnected hendelser vil ikke utløses."

#: modules/components/security-header-permissions-policy.php:65
msgid "Controls whether the current document is allowed to use the Geolocation Interface. When this policy is disabled, calls to getCurrentPosition() and watchPosition() will cause those functions' callbacks to be invoked with a GeolocationPositionError code of PERMISSION_DENIED."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Geolocation Interface. Når denne policyen er deaktivert, vil kall til getCurrentPosition() og watchPosition() føre til at disse funksjonenes tilbakeringinger påkalles med en GeolocationPositionError kode på PERMISSION_DENIED."

#: modules/components/security-header-permissions-policy.php:66
msgid "Controls whether the current document is allowed to gather information about the orientation of the device through the Gyroscope interface."
msgstr "Kontrollerer om gjeldende dokument har lov til å samle informasjon om enhetens orientering gjennom Gyroscope-grensesnittet."

#: modules/components/security-header-permissions-policy.php:67
msgid "Controls whether the current document is allowed to show layout animations."
msgstr "Kontrollerer om gjeldende dokument har lov til å vise layoutanimasjoner."

#: modules/components/security-header-permissions-policy.php:68
msgid "Controls whether the current document is allowed to display images in legacy formats."
msgstr "Kontrollerer om gjeldende dokument har lov til å vise bilder i eldre formater."

#: modules/components/security-header-permissions-policy.php:69
msgid "Controls whether the current document is allowed to gather information about the orientation of the device through the Magnetometer interface."
msgstr "Kontrollerer om gjeldende dokument har lov til å samle informasjon om enhetens orientering gjennom Magnetometer-grensesnittet."

#: modules/components/security-header-permissions-policy.php:70
msgid "Controls whether the current document is allowed to use audio input devices. When this policy is disabled, the Promise returned by MediaDevices.getUserMedia() will reject with a NotAllowedError."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke lydinngangsenheter. Når denne policyen er deaktivert, vil Promise returnert av MediaDevices.getUserMedia() avvise med en NotAllowedError."

#: modules/components/security-header-permissions-policy.php:71
msgid "Controls whether the current document is allowed to use the Web MIDI API. When this policy is disabled, the Promise returned by Navigator.requestMIDIAccess() will reject with a DOMException."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Web MIDI API. Når denne policyen er deaktivert, vil Promise returnert av Navigator.requestMIDIAccess() avvise med en DOMException."

#: modules/components/security-header-permissions-policy.php:72
msgid "Controls the availability of mechanisms that enables the page author to take control over the behavior of spatial navigation, or to cancel it outright."
msgstr "Kontrollerer tilgjengeligheten av mekanismer som gjør at sideforfatteren kan ta kontroll over oppførselen til romlig navigering, eller avbryte den helt."

#: modules/components/security-header-permissions-policy.php:73
msgid "Controls whether the current document is allowed to download and display large images."
msgstr "Kontrollerer om gjeldende dokument har lov til å laste ned og vise store bilder."

#: modules/components/security-header-permissions-policy.php:74
msgid "Controls whether the current document is allowed to use the Payment Request API. When this policy is enabled, the PaymentRequest() constructor will throw a SecurityError DOMException."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Payment Request API. Når denne policyen er aktivert, vil PaymentRequest() konstruktøren kaste en SecurityError DOMException."

#: modules/components/security-header-permissions-policy.php:75
msgid "Controls whether the current document is allowed to play a video in a Picture-in-Picture mode via the corresponding API."
msgstr "Kontrollerer om gjeldende dokument har lov til å spille av en video i Picture-in-Picture modus via det tilsvarende API-et."

#: modules/components/security-header-permissions-policy.php:76
msgid "Controls whether the current document is allowed to use the Web Authentication API to retrieve already stored public-key credentials, i.e. via navigator.credentials.get({publicKey: ..., ...})."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Web Authentication API for å hente allerede lagrede offentlige nøkkelreferanser, dvs. via navigator.credentials.get({publicKey: ..., ...})."

#: modules/components/security-header-permissions-policy.php:77
msgid "Controls whether the current document is allowed to use the Audio Output Devices API to list and select speakers."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Audio Output Devices API for å liste og velge høyttalere."

#: modules/components/security-header-permissions-policy.php:78
msgid "Controls whether the current document is allowed to make synchronous XMLHttpRequest requests."
msgstr "Kontrollerer om gjeldende dokument har lov til å gjøre synkrone XMLHttpRequest forespørsler."

#: modules/components/security-header-permissions-policy.php:79
msgid "Controls whether the current document is allowed to download and display unoptimized images."
msgstr "Kontrollerer om gjeldende dokument har lov til å laste ned og vise uoptimaliserte bilder."

#: modules/components/security-header-permissions-policy.php:80
msgid "Controls whether the current document is allowed to change the size of media elements after the initial layout is complete."
msgstr "Kontrollerer om gjeldende dokument har lov til å endre størrelsen på mediaelementer etter at den innledende layouten er fullført."

#: modules/components/security-header-permissions-policy.php:81
msgid "Controls whether the current document is allowed to use the WebUSB API."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke WebUSB API."

#: modules/components/security-header-permissions-policy.php:82
msgid "Controls whether the current document is allowed to use Screen Wake Lock API to indicate that device should not turn off or dim the screen."
msgstr "Kontrollerer om gjeldende dokument har lov til å bruke Screen Wake Lock API for å indikere at enheten ikke skal slå av eller demme skjermen."

#: modules/components/security-header-permissions-policy.php:83
msgid "Controls whether or not the current document is allowed to use the Navigator.share() of Web Share API to share text, links, images, and other content to arbitrary destinations of user's choice, e.g. mobile apps."
msgstr "Kontrollerer om gjeldende dokument har tillatelse til å bruke Navigator.share() av Web Share API for å dele tekst, lenker, bilder og annet innhold til vilkårlige destinasjoner av brukerens valg, f.eks. mobilapper."

#: modules/components/security-header-permissions-policy.php:84
msgid "Controls whether or not the current document is allowed to use the WebXR Device API to interact with a WebXR session."
msgstr "Kontrollerer om gjeldende dokument har tillatelse til å bruke WebXR Device API for å samhandle med en WebXR-økt."

#: modules/components/security-header-permissions-policy.php:176
msgid "Enabled"
msgstr "Aktivert"

#: modules/components/security-header-referrer-policy.php:47 modules/components/security-header-referrer-policy.php:50
msgid "Referrer-Policy"
msgstr "Referrer-Policy"

#: modules/components/security-header-referrer-policy.php:51
msgid "The Referrer-Policy HTTP header determines the amount of referral information (sent through the Referer header) that should accompany requests. In addition to the HTTP header, this policy can also be set in HTML"
msgstr "Referrer-Policy HTTP-headeren bestemmer mengden henvisningsinformasjon (sendt gjennom Referer-headeren) som skal følge med forespørsler. I tillegg til HTTP-headeren kan denne policyen også settes i HTML"

#: modules/components/security-header-referrer-policy.php:53
msgid "The Referer header will be omitted: sent requests do not include any referrer information."
msgstr "Referer-headeren vil utelates: sendte forespørsler inkluderer ikke noen henvisningsinformasjon."

#: modules/components/security-header-referrer-policy.php:54
msgid "Send the origin, path, and querystring in Referer when the protocol security level stays the same or improves (HTTP→HTTP, HTTP→HTTPS, HTTPS→HTTPS). Don't send the Referer header for requests to less secure destinations (HTTPS→HTTP, HTTPS→file)."
msgstr "Send opprinnelse, sti og spørringsstreng i Referer når protokollsikkerhetsnivået forblir det samme eller forbedres (HTTP→HTTP, HTTP→HTTPS, HTTPS→HTTPS). Ikke send Referer-headeren for forespørsler til mindre sikre destinasjoner (HTTPS→HTTP, HTTPS→file)."

#: modules/components/security-header-referrer-policy.php:55
msgid "Send only the origin in the Referer header. For example, a document at https://example.com/page.html will send the referrer https://example.com/."
msgstr "Send kun opprinnelsen i Referer-headeren. For eksempel vil et dokument på https://example.com/page.html sende henviseren https://example.com/."

#: modules/components/security-header-referrer-policy.php:56
msgid "When performing a same-origin request to the same protocol level (HTTP→HTTP, HTTPS→HTTPS), send the origin, path, and query string. Send only the origin for cross origin requests and requests to less secure destinations (HTTPS→HTTP)."
msgstr "Når du utfører en samme opprinnelse forespørsel til samme protokollnivå (HTTP→HTTP, HTTPS→HTTPS), send opprinnelse, sti og spørringsstreng. Send kun opprinnelsen for tverropprinnelige forespørsler og forespørsler til mindre sikre destinasjoner (HTTPS→HTTP)."

#: modules/components/security-header-referrer-policy.php:57
msgid "Send the origin, path, and query string for same-origin requests. Don't send the Referer header for cross-origin requests."
msgstr "Send opprinnelse, sti og spørringsstreng for samme opprinnelse forespørsler. Ikke send Referer-headeren for tverropprinnelige forespørsler."

#: modules/components/security-header-referrer-policy.php:58
msgid "Send only the origin when the protocol security level stays the same (HTTPS→HTTPS). Don't send the Referer header to less secure destinations (HTTPS→HTTP)."
msgstr "Send kun opprinnelsen når protokollsikkerhetsnivået forblir det samme (HTTPS→HTTPS). Ikke send Referer-headeren til mindre sikre destinasjoner (HTTPS→HTTP)."

#: modules/components/security-header-referrer-policy.php:59
msgid "Send the origin, path, and querystring when performing a same-origin request. For cross-origin requests send the origin (only) when the protocol security level stays same (HTTPS→HTTPS). Don't send the Referer header to less secure destinations (HTTPS→HTTP)."
msgstr "Send opprinnelse, sti og spørringsstreng når du utfører en samme opprinnelse forespørsel. For tverropprinnelige forespørsler send opprinnelsen (kun) når protokollsikkerhetsnivået forblir det samme (HTTPS→HTTPS). Ikke send Referer-headeren til mindre sikre destinasjoner (HTTPS→HTTP)."

#: modules/components/security-header-referrer-policy.php:60
msgid "Send the origin, path, and query string when performing any request, regardless of security."
msgstr "Send opprinnelse, sti og spørringsstreng når du utfører enhver forespørsel, uavhengig av sikkerhet."

#: modules/components/security-header-stricy-transport-security.php:47 modules/components/security-header-stricy-transport-security.php:50
msgid "Strict-Transport-Security (HSTS)"
msgstr "Strict-Transport-Security (HSTS)"

#: modules/components/security-header-stricy-transport-security.php:51
msgid "The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) informs browsers that the site should only be accessed using HTTPS, and that any future attempts to access it using HTTP should automatically be converted to HTTPS."
msgstr "HTTP Strict-Transport-Security responsheaderen (ofte forkortet som HSTS) informerer nettlesere om at nettstedet bare skal aksesseres ved bruk av HTTPS, og at alle fremtidige forsøk på å aksessere det ved bruk av HTTP automatisk skal konverteres til HTTPS."

#: modules/components/security-header-stricy-transport-security.php:53
msgid "The time, in seconds, that the browser should remember that a site is only to be accessed using HTTPS."
msgstr "Tiden, i sekunder, som nettleseren skal huske at et nettsted bare skal aksesseres ved bruk av HTTPS."

#: modules/components/security-header-stricy-transport-security.php:54
msgid "If this optional parameter is specified, this rule applies to all of the site's subdomains as well."
msgstr "Hvis denne valgfrie parameteren er spesifisert, gjelder denne regelen for alle nettstedets underdomener også."

#: modules/components/security-header-stricy-transport-security.php:55
msgid "See Preloading Strict Transport Security for details. Not part of the specification."
msgstr "Se Preloading Strict Transport Security for detaljer. Ikke en del av spesifikasjonen."

#: modules/components/security-header-stricy-transport-security.php:114
msgid "hour"
msgstr "time"

#: modules/components/security-header-stricy-transport-security.php:115
msgid "day"
msgstr "dag"

#: modules/components/security-header-stricy-transport-security.php:116 modules/components/security-header-stricy-transport-security.php:117 modules/components/security-header-stricy-transport-security.php:118
msgid "days"
msgstr "dager"

#: modules/components/security-header-stricy-transport-security.php:119
msgid "year"
msgstr "år"

#: modules/components/security-header-stricy-transport-security.php:120
msgid "years"
msgstr "år"

#: modules/components/security-header-x-content-type-options.php:46 modules/components/security-header-x-content-type-options.php:49
msgid "X-Content-Type-Options"
msgstr "X-Content-Type-Options"

#: modules/components/security-header-x-content-type-options.php:50
msgid "The X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the MIME types advertised in the Content-Type headers should be followed and not be changed. The header allows you to avoid MIME type sniffing by saying that the MIME types are deliberately configured."
msgstr "X-Content-Type-Options HTTP responsheaderen er en markør brukt av serveren for å indikere at MIME-typene annonsert i Content-Type headere skal følges og ikke endres. Headeren lar deg unngå MIME-type sniffing ved å si at MIME-typene er bevisst konfigurert."

#: modules/components/security-header-x-content-type-options.php:51
msgid "This header was introduced by Microsoft in IE 8 as a way for webmasters to block content sniffing that was happening and could transform non-executable MIME types into executable MIME types. Since then, other browsers have introduced it, even if their MIME sniffing algorithms were less aggressive."
msgstr "Denne headeren ble introdusert av Microsoft i IE 8 som en måte for webmastere å blokkere innholdssniffing som skjedde og kunne transformere ikke-eksekverbare MIME-typer til eksekverbare MIME-typer. Siden den gang har andre nettlesere introdusert den, selv om deres MIME-sniffing-algoritmer var mindre aggressive."

#: modules/components/security-header-x-content-type-options.php:52
msgid "Starting with Firefox 72, top-level documents also avoid MIME sniffing (if Content-type is provided). This can cause HTML web pages to be downloaded instead of being rendered when they are served with a MIME type other than text/html. Make sure to set both headers correctly."
msgstr "Med start med Firefox 72, unngår toppnivådokumenter også MIME-sniffing (hvis Content-type er gitt). Dette kan føre til at HTML-nettsider lastes ned i stedet for å bli gjengitt når de serveres med en MIME-type annet enn text/html. Pass på å sette begge headerne riktig."

#: modules/components/security-header-x-content-type-options.php:54
msgid "Blocks a request if the request destination is of type style and the MIME type is not text/css, or of type script and the MIME type is not a JavaScript MIME type."
msgstr "Blokkerer en forespørsel hvis forespørselens destinasjon er av type style og MIME-typen ikke er text/css, eller av type script og MIME-typen ikke er en JavaScript MIME-type."

#: modules/components/security-header-x-download-options.php:46 modules/components/security-header-x-download-options.php:49
msgid "X-Download-Options"
msgstr "X-Download-Options"

#: modules/components/security-header-x-download-options.php:50
msgid "The X-Download-Options is specific to IE 8, and is related to how IE 8 handles downloaded HTML files. Turns out if you download an HTML file from a web page and chooses to \"Open\" it in IE, it will execute in the context of the web site. That means that any scripts in that file will also execute with the origin of the web site."
msgstr "X-Download-Options er spesifikk for IE 8, og er relatert til hvordan IE 8 håndterer nedlastede HTML-filer. Det viser seg at hvis du laster ned en HTML-fil fra en nettside og velger å \"Åpne\" den i IE, vil den kjøre i konteksten av nettsiden. Det betyr at alle skript i den filen også vil kjøre med opprinnelsen til nettsiden."

#: modules/components/security-header-x-frame-options.php:46
msgid "X-Frame-Options (XFO)"
msgstr "X-Frame-Options (XFO)"

#: modules/components/security-header-x-frame-options.php:49
msgid "X-Frame-Options"
msgstr "X-Frame-Options"

#: modules/components/security-header-x-frame-options.php:50
msgid "The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a &#60;frame&#62;, &#60;iframe&#62;, &#60;embed&#62; or &#60;object&#62;. Sites can use this to avoid click-jacking attacks, by ensuring that their content is not embedded into other sites."
msgstr "X-Frame-Options HTTP responsheaderen kan brukes til å indikere om en nettleser skal tillates å gjengi en side i en &#60;frame&#62;, &#60;iframe&#62;, &#60;embed&#62; eller &#60;object&#62;. Nettsteder kan bruke dette for å unngå click-jacking-angrep, ved å sikre at deres innhold ikke bygges inn i andre nettsteder."

#: modules/components/security-header-x-frame-options.php:51
msgid "The added security is provided only if the user accessing the document is using a browser that supports X-Frame-Options."
msgstr "Den ekstra sikkerheten gis bare hvis brukeren som aksesserer dokumentet bruker en nettleser som støtter X-Frame-Options."

#: modules/components/security-header-x-frame-options.php:53
msgid "The page cannot be displayed in a frame, regardless of the site attempting to do so."
msgstr "Siden kan ikke vises i en ramme, uavhengig av hvilket nettsted som prøver å gjøre det."

#: modules/components/security-header-x-frame-options.php:54
msgid "The page can only be displayed in a frame on the same origin as the page itself. The spec leaves it up to browser vendors to decide whether this option applies to the top level, the parent, or the whole chain, although it is argued that the option is not very useful unless all ancestors are also in the same origin."
msgstr "Siden kan bare vises i en ramme på samme opprinnelse som siden selv. Spesifikasjonen overlater til nettleserleverandører å avgjøre om dette alternativet gjelder for toppnivået, forelderen eller hele kjeden, selv om det hevdes at alternativet ikke er veldig nyttig med mindre alle forfedre også er i samme opprinnelse."

#: modules/components/security-header-x-frame-options.php:55
msgid "If you specify DENY, not only will the browser attempt to load the page in a frame fail when loaded from other sites, attempts to do so will fail when loaded from the same site. On the other hand, if you specify SAMEORIGIN, you can still use the page in a frame as long as the site including it in a frame is the same as the one serving the page."
msgstr "Hvis du spesifiserer DENY, vil ikke bare nettleserens forsøk på å laste siden i en ramme mislykkes når den lastes fra andre nettsteder, forsøk på å gjøre det vil mislykkes når den lastes fra samme nettsted. På den annen side, hvis du spesifiserer SAMEORIGIN, kan du fortsatt bruke siden i en ramme så lenge nettstedet som inkluderer den i en ramme er det samme som det som serverer siden."

#: modules/components/security-header-x-permitted-cross-domain-policies.php:47 modules/components/security-header-x-permitted-cross-domain-policies.php:50
msgid "X-Permitted-Cross-Domain-Policies"
msgstr "X-Permitted-Cross-Domain-Policies"

#: modules/components/security-header-x-permitted-cross-domain-policies.php:51
msgid "A cross-domain policy file is an XML document that grants a web client, such as Adobe Flash Player or Adobe Acrobat (though not necessarily limited to these), permission to handle data across domains."
msgstr "En cross-domain policy fil er et XML-dokument som gir en webklient, som Adobe Flash Player eller Adobe Acrobat (men ikke nødvendigvis begrenset til disse), tillatelse til å håndtere data på tvers av domener."

#: modules/components/security-header-x-permitted-cross-domain-policies.php:52
msgid "When clients request content hosted on a particular source domain and that content makes requests directed towards a domain other than its own, the remote domain needs to host a cross-domain policy file that grants access to the source domain, allowing the client to continue the transaction."
msgstr "Når klienter forespørrer innhold vert på et bestemt kildedomen og det innholdet gjør forespørsler rettet mot et annet domene enn sitt eget, må det fjerne domenet være vert for en cross-domain policy fil som gir tilgang til kildedomenet, noe som tillater klienten å fortsette transaksjonen."

#: modules/components/security-header-x-permitted-cross-domain-policies.php:53
msgid "Normally a meta-policy is declared in the master policy file, but for those who can’t write to the root directory, they can also declare a meta-policy using the X-Permitted-Cross-Domain-Policies HTTP response header."
msgstr "Normalt erklæres en meta-policy i master policy filen, men for de som ikke kan skrive til rotkatalogen, kan de også erklære en meta-policy ved å bruke X-Permitted-Cross-Domain-Policies HTTP responsheaderen."

#: modules/components/security-header-x-permitted-cross-domain-policies.php:55
msgid "No policy files are allowed anywhere on the target server, including this master policy file."
msgstr "Ingen policyfiler er tillatt noe sted på målserveren, inkludert denne master policy filen."

#: modules/components/security-header-x-permitted-cross-domain-policies.php:56
msgid "Only this master policy file is allowed."
msgstr "Kun denne master policy filen er tillatt."

#: modules/components/security-header-x-permitted-cross-domain-policies.php:57
msgid "[HTTP/HTTPS only] Only policy files served with Content-Type: text/x-cross-domain-policy are allowed."
msgstr "[Kun HTTP/HTTPS] Kun policyfiler servert med Content-Type: text/x-cross-domain-policy er tillatt."

#: modules/components/security-header-x-permitted-cross-domain-policies.php:58
msgid "[FTP only] Only policy files whose file names are crossdomain.xml (i.e. URLs ending in /crossdomain.xml) are allowed."
msgstr "[Kun FTP] Kun policyfiler hvis filnavn er crossdomain.xml (dvs. URL-er som slutter på /crossdomain.xml) er tillatt."

#: modules/components/security-header-x-permitted-cross-domain-policies.php:59
msgid "All policy files on this target domain are allowed."
msgstr "Alle policyfiler på dette måldomenet er tillatt."

#: modules/components/security-header-x-xss-protection.php:47 modules/components/security-header-x-xss-protection.php:50
msgid "X-XSS-Protection"
msgstr "X-XSS-Protection"

#: modules/components/security-header-x-xss-protection.php:51
msgid "The HTTP X-XSS-Protection response header is a feature of Internet Explorer, Chrome and Safari that stops pages from loading when they detect reflected cross-site scripting (XSS) attacks. These protections are largely unnecessary in modern browsers when sites implement a strong Content-Security-Policy that disables the use of inline JavaScript ('unsafe-inline')."
msgstr "HTTP X-XSS-Protection responsheaderen er en funksjon i Internet Explorer, Chrome og Safari som stopper sider fra å laste når de oppdager reflekterte tverrside skriptangrep (XSS). Disse beskyttelsene er i stor grad unødvendige i moderne nettlesere når nettsteder implementerer en sterk Content-Security-Policy som deaktiverer bruk av inline JavaScript ('unsafe-inline')."

#: modules/components/security-header-x-xss-protection.php:53
msgid "Disables XSS filtering."
msgstr "Deaktiverer XSS-filtering."

#: modules/components/security-header-x-xss-protection.php:54
msgid "Enables XSS filtering (usually default in browsers). If a cross-site scripting attack is detected, the browser will sanitize the page (remove the unsafe parts)."
msgstr "Aktiverer XSS-filtering (vanligvis standard i nettlesere). Hvis et tverrside skriptangrep oppdages, vil nettleseren rense siden (fjerne de usikre delene)."

#: modules/components/security-header-x-xss-protection.php:55
msgid "Enables XSS filtering. Rather than sanitizing the page, the browser will prevent rendering of the page if an attack is detected."
msgstr "Aktiverer XSS-filtering. I stedet for å rense siden, vil nettleseren forhindre gjengivelse av siden hvis et angrep oppdages."

#: modules/components/security-header-x-xss-protection.php:56
msgid "Chromium only. Enables XSS filtering. If a cross-site scripting attack is detected, the browser will sanitize the page and report the violation. This uses the functionality of the CSP report-uri directive to send a report."
msgstr "Kun Chromium. Aktiverer XSS-filtering. Hvis et tverrside skriptangrep oppdages, vil nettleseren rense siden og rapportere overtredelsen. Dette bruker funksjonaliteten til CSP report-uri direktivet for å sende en rapport."

#: modules/module-2fa.php:54
msgid "<span class=\"wph-info\">Security&rarr;</span> 2FA"
msgstr "<span class=\"wph-info\">Sikkerhet&rarr;</span> 2FA"

#: modules/module-2fa.php:66
msgid "WP Hide & Security Enhancer - Login 2FA"
msgstr "WP Hide & Security Enhancer - Login 2FA"

#: modules/module-admin.php:48
msgid "<span class=\"wph-info\">Hide&rarr;</span> Login / Admin"
msgstr "<span class=\"wph-info\">Skjul&rarr;</span> Login / Admin"

#: modules/module-admin.php:60
msgid "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - Admin"
msgstr "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - Admin"

#: modules/module-captcha.php:43
msgid "<span class=\"wph-info\">Security&rarr;</span> Captcha"
msgstr "<span class=\"wph-info\">Sikkerhet&rarr;</span> Captcha"

#: modules/module-captcha.php:55
msgid "WP Hide & Security Enhancer - Login Captcha"
msgstr "WP Hide & Security Enhancer - Login Captcha"

#: modules/module-cdn.php:43
msgid "<span class=\"wph-info\">Setting&rarr;</span> CDN"
msgstr "<span class=\"wph-info\">Innstilling&rarr;</span> CDN"

#: modules/module-cdn.php:55
msgid "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - CDN"
msgstr "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - CDN"

#: modules/module-firewall.php:51
msgid "<span class=\"wph-info\">Security&rarr;</span> Firewall"
msgstr "<span class=\"wph-info\">Sikkerhet&rarr;</span> Brannmur"

#: modules/module-firewall.php:63
msgid "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - Firewall"
msgstr "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - Brannmur"

#: modules/module-general.php:84
msgid "<span class=\"wph-info\">Hide&rarr;</span> General / Html"
msgstr "<span class=\"wph-info\">Skjul&rarr;</span> Generelt / Html"

#: modules/module-general.php:96
msgid "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - General / Html"
msgstr "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - Generelt / Html"

#: modules/module-postprocessing.php:54
msgid "<span class=\"wph-info\">Hide&rarr;</span> Post-Processing"
msgstr "<span class=\"wph-info\">Skjul&rarr;</span> Etterbehandling"

#: modules/module-postprocessing.php:66
msgid "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - Post-Processing"
msgstr "WP Hide & Security Enhancer <span class=\"plugin-mark\">PRO</span> - Etterbehandling"

#: modules/module-rewrite.php:86
msgid "<span class=\"wph-info\">Hide&rarr;</span> Rewrite"
msgstr "<span class=\"wph-info\">Skjul&rarr;</span> Rewrite"

#: modules/module-rewrite.php:97 modules/module-security_headers.php:93
msgid "WP Hide & Security Enhancer"
msgstr "WP Hide & Security Enhancer"

#: modules/module-rewrite.php:97
msgid "Rewrite"
msgstr "Rewrite"

#: modules/module-security_headers.php:81
msgid "<span class=\"wph-info\">Security&rarr;</span> Headers"
msgstr "<span class=\"wph-info\">Sikkerhet&rarr;</span> Headere"

#: modules/module-security_headers.php:93
msgid "Security"
msgstr "Sikkerhet"
