# Translation of Plugins - No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor - Development Readme (trunk) in Oriya
# This file is distributed under the same license as the Plugins - No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor - Development Readme (trunk) package.
msgid ""
msgstr ""
"PO-Revision-Date: +0000\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: GlotPress/4.1.0\n"
"Language: or_IN\n"
"Project-Id-Version: Plugins - No Gutenberg? – Choose Where to Use the Block Editor or the Classic Editor - Development Readme (trunk)\n"

#. Short description.
#, gp-priority: high
msgid "Decide where the block editor stays and where the Classic Editor comes back. It also removes Global Styles, patterns, block widgets and block CSS."
msgstr ""

#. Plugin name.
#, gp-priority: high
msgid "No Gutenberg? - Choose Where to Use the Block Editor or the Classic Editor"
msgstr ""

#. Found in faq paragraph.
msgid "With classic themes, and with plugins that do not depend on blocks, yes: it removes block features instead of fighting them for control. Block themes are the exception, and there is a question about them right below. A plugin that registers blocks of its own keeps working, but those blocks lose their styles on the frontend if you remove the block assets, which is what the status panel is there to warn you about."
msgstr ""

#. Found in faq paragraph.
msgid "Everything comes back immediately: the block editor, Global Styles, the patterns and the block assets. Your content is exactly as it was, because the plugin never rewrote any of it."
msgstr ""

#. Found in faq paragraph.
msgid "No. Activating the plugin disables everything across the site. The settings page under Settings > No Gutenberg? is there only if you want to bring some part of the block editor back."
msgstr ""

#. Found in installation list item.
msgid "That is it. The block editor is disabled across the site and the Classic Editor is back"
msgstr ""

#. Found in description paragraph.
msgid ""
"It fits sites that:\n"
"- Work better in the Classic Editor and want it back\n"
"- Run classic themes and plugins that were never built around blocks\n"
"- Are paying for block CSS and JavaScript on pages with no blocks in them\n"
"- Need the Classic Editor for everyone except a few post types, roles or people\n"
"- Are a multisite network that wants the same editing experience on every site"
msgstr ""

#. Found in description paragraph.
msgid "<strong>A default that asks nothing, and a settings page for everything else</strong> - Activating the plugin disables the block editor and every block feature across the site, which is what most people install it for. The rest of this page is about wanting less than that."
msgstr ""

#. Found in description list item.
msgid "Nothing else: leave blocks on for products and the block product editor keeps working"
msgstr ""

#. Found in description list item.
msgid "The WooCommerce block styles and scripts, removed along with the rest of the block assets"
msgstr ""

#. Found in description list item.
msgid "The block based product editor, which follows the same rules as any other post type"
msgstr ""

#. Found in description list item.
msgid "The block editor assets in the admin, wherever the Classic Editor is the one opening"
msgstr ""

#. Found in description list item.
msgid "The block assets of any other plugin that registers blocks, on pages where no block appears"
msgstr ""

#. Found in description list item.
msgid "The Global Styles inline CSS, which dequeuing the handle never reaches"
msgstr ""

#. Found in description list item.
msgid "The block library CSS and JavaScript that every page loads"
msgstr ""

#. Screenshot description.
msgid "Settings page"
msgstr ""

#. Found in description paragraph.
msgid "The most configurable way to leave the block editor behind. Activate it and everything block related is gone: the block editor, Global Styles, patterns, block widgets, the Site Editor and the block CSS and JavaScript that every page loads. From there you decide the scope: everywhere, or only for the post types, roles, templates and entries you choose."
msgstr ""

#. Found in faq paragraph.
msgid "Yes. Uncheck the content protection under the master switch, on the settings page. From that point the rules apply to every entry, and the plugin warns you inside the Classic Editor whenever you open one that is built with blocks, because saving it there can break its blocks."
msgstr ""

#. Found in faq paragraph.
msgid "There is one visible change on the frontend: with the frontend block assets removed, content built with blocks loses the block styles. The status panel tells you how many entries are affected before you decide."
msgstr ""

#. Found in faq paragraph.
msgid "No, and the plugin goes out of its way to keep it that way. It never rewrites a single entry, and an entry that is already built with blocks keeps the block editor whatever the rules say, so nothing you set here can send it to an editor that would reflow its markup. The entries list labels those entries and can be narrowed down to them, so you can see exactly what you have."
msgstr ""

#. Found in faq header.
msgid "I want the Classic Editor on everything, block content included. Can I?"
msgstr ""

#. Found in faq paragraph.
msgid "Because it does not stop at the editor. Others disable the block editor and leave the rest running: this one also removes the FSE Global Styles, the block widgets, the patterns, the WooCommerce blocks and the block CSS and JavaScript that every page of your site is loading. It also tells you what it is doing, with a status panel measured on your own site instead of a list of promises. And on a multisite network it is configured for every site at once from a single file, all of it, not only which editor opens."
msgstr ""

#. Found in faq paragraph.
msgid "For the whole network at once, the place is wp-config.php, the same file every site reads: what you define there reaches all of them, covers every setting the plugin has and wins over whatever each site has stored. There is no network settings screen, because that file does the job for the entire network in a couple of lines. They are in the description, under \"One configuration for a whole network, or for a site you deliver\"."
msgstr ""

#. Found in faq paragraph.
msgid "Yes, and it is what the plugin is best at. Activate it site by site, or Network Activate it and it runs on every site of the network. Settings are stored per site, so each site has its own Settings &gt; No Gutenberg? and each site administrator manages their own."
msgstr ""

#. Found in faq paragraph.
msgid "Yes, from wp-config.php. <code>define( 'NO_GUTENBERG_LOCK_SETTINGS', true );</code> leaves Settings &gt; No Gutenberg? visible but read only, and <code>define( 'NO_GUTENBERG_HIDE_SETTINGS', true );</code> takes it out of the menu. To fix the configuration itself, and not only lock the screen, there is NO_GUTENBERG_OPTIONS. The description has the three of them together, with the settings you can fix and the details worth knowing."
msgstr ""

#. Found in faq header.
msgid "Does it work on a multisite network?"
msgstr ""

#. Found in installation paragraph.
msgid "On a multisite network you can also Network Activate it, so it runs on every site of the network at once. Settings stay per site, and the description explains how to configure the whole network from wp-config.php."
msgstr ""

#. Found in description paragraph.
msgid "The keys are the settings on the screen. complete, widgets, patterns, frontend_css, theme_json, site_editor and fse_notices take true or false, while disable_post_types, disable_roles, disable_templates and switch_post_types take an array of slugs, and disable_ids an array of entry IDs. Any key you leave out keeps the value stored on the site. Note that defining NO_GUTENBERG_OPTIONS already turns the whole screen read only, so NO_GUTENBERG_LOCK_SETTINGS is not needed on top of it."
msgstr ""

#. Found in description paragraph.
msgid "NO_GUTENBERG_OPTIONS takes any of the settings on the screen, so a selective setup is written the same way:"
msgstr ""

#. Found in description paragraph.
msgid "Drop that second line and the settings page is still there, showing the configuration the site is really running, but read only. And if all you want is to lock the screen, leaving the configuration as each site has it stored:"
msgstr ""

#. Found in description paragraph.
msgid "To disable Gutenberg everywhere and leave no settings screen for anyone to touch, which is the usual setup both for a network and for a site you hand over to a client:"
msgstr ""

#. Found in description paragraph.
msgid "Everything the settings screen does can also be written in wp-config.php, where nobody changes it by accident, and what you write there wins over whatever is stored in the database. It is the same file for every site of a multisite network, so it is also how you set up a network without repeating the configuration site by site. Add the lines you need above the comment that says \"That's all, stop editing! Happy publishing.\""
msgstr ""

#. Found in description paragraph.
msgid "<strong>A whole network configured in one file</strong> - This is where the plugin stands alone. Every single setting it has, and not just which editor opens, can be written in wp-config.php, the same file every site of a multisite network reads. A network of a hundred sites is set up once, all of them with the same rules, all of them with the same block CSS gone, and none of them able to drift away from it. The plugin can also be network activated and left alone, because settings are stored per site, so a network can equally let each site decide for itself. Same mechanism as the locking above, and this is how it is written."
msgstr ""

#. Found in description header.
msgid "One configuration for a whole network, or for a site you deliver"
msgstr ""

#. Found in faq paragraph.
msgid "You can, but block themes are built around the very features this plugin removes, so their Site Editor and template editing will not work while it is active. The plugin warns you when it detects a block theme. If you need that theme, switch off the Site Editor and theme.json modules on the settings page, or use a classic theme instead."
msgstr ""

#. Found in faq paragraph.
msgid "Yes. Products behave like any other post type: with the master switch on, or with Products checked in the rules, the classic product editor is forced and the WooCommerce block assets are removed from the frontend. If you leave blocks on for products, the block based product editor keeps working, without a separate setting contradicting it."
msgstr ""

#. Found in faq paragraph.
msgid "Yes. In the post types table there is a second column, \"Let each entry switch\": check it for the post types where it makes sense. Those entries then get \"Edit (Classic)\" and \"Edit (Blocks)\" links in the list and a switch inside both editors, and each one remembers the editor you chose for it."
msgstr ""

#. Found in faq paragraph.
msgid "That is exactly why the plugin unchecks the frontend block assets and theme.json options for you when you switch to a partial setup: the content that still uses blocks would lose its styles on the frontend. The status panel tells you how many of your published entries are built with blocks, so you can decide with real numbers."
msgstr ""

#. Found in faq paragraph.
msgid "Yes. Once the master switch is off, the site wide pieces are independent checkboxes, so you can, for example, restore the classic Widgets screen and remove the block patterns while leaving the editor itself alone."
msgstr ""

#. Found in faq paragraph.
msgid "Yes. Go to Settings &gt; No Gutenberg?, uncheck \"Disable Gutenberg completely\", and then choose where the block editor should go away: post types, user roles, page templates or individual entry IDs. Rules are independent, so anything that matches gets the Classic Editor and everything else keeps working as usual."
msgstr ""

#. Found in faq header.
msgid "Can I use it with a block theme?"
msgstr ""

#. Found in faq header.
msgid "Can I open one entry with the other editor?"
msgstr ""

#. Found in faq header.
msgid "Can I lock the configuration so a client cannot change it?"
msgstr ""

#. Found in faq header.
msgid "If I only disable the editor for some content, what happens to the block styles?"
msgstr ""

#. Found in faq header.
msgid "Can I disable just one part of Gutenberg?"
msgstr ""

#. Found in faq header.
msgid "Can I disable Gutenberg only for some content or some people?"
msgstr ""

#. Found in faq header.
msgid "Do I have to configure anything?"
msgstr ""

#. Found in description paragraph.
msgid "<strong>Built for agencies and managed sites</strong> - The whole configuration can be fixed from wp-config.php, and the settings screen locked as read only or hidden altogether, so a site you deliver keeps the setup you left behind."
msgstr ""

#. Found in description paragraph.
msgid "<strong>It tells you what it is doing</strong> - The settings screen opens with a status panel for your particular site: how many block patterns are being blocked, how much weight is off every page, whether your theme is a block theme, and how much of your published content is really built with blocks. That last number is the one that should decide whether you strip the block styles from the frontend or not, and no other plugin tells you."
msgstr ""

#. Found in description paragraph.
msgid "<strong>Switch editors entry by entry, where it makes sense</strong> - Editor switching is chosen per post type, right next to the rule that disables the block editor. Enable it for pages, for instance, and every page gets \"Edit (Classic)\" and \"Edit (Blocks)\" links in the list plus a switch inside both editors, while your posts stay untouched. Each entry remembers the editor chosen for it, and that choice beats the rules in both directions: one landing page can stay on the Classic Editor while the rest keep blocks, or the other way around."
msgstr ""

#. Found in description paragraph.
msgid "<strong>Full control when you need it</strong> - The settings page lives under Settings &gt; No Gutenberg?, built around one master switch. Leave it on and the whole site keeps the complete disable. Turn it off and you decide where the block editor goes away: by post type, by user role, by page template or by individual entry. The site wide pieces (classic widgets, block patterns, frontend block assets, theme.json and the Site Editor) are then yours to keep or remove one by one. Every checkbox means the same thing, so no setting ever undoes another one."
msgstr ""

#. Found in description list item.
msgid "Adds settings and support links to plugin actions"
msgstr ""

#. Found in description list item.
msgid "Warns you when a block theme is active"
msgstr ""

#. Found in description list item.
msgid "Removes the Fonts submenu from the Appearance menu (WP 7.0+)"
msgstr ""

#. Found in description list item.
msgid "Removes the welcome panel that promotes the block editor"
msgstr ""

#. Found in description paragraph.
msgid "Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just <a href=\"mailto:no-gutenberg@ayudawp.com\">contact me</a> and tell me what you need."
msgstr ""

#. Found in description header.
msgid "Need private support or custom development?"
msgstr ""

#. Found in description list item.
msgid "Blocks access to Site Editor pages"
msgstr ""

#. Found in description list item.
msgid "Removes the Patterns submenu from the Appearance menu (WP 6.5+)"
msgstr ""

#. Found in description paragraph.
msgid "We are specialists in WordPress security, SEO, and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements."
msgstr ""

#. Found in description paragraph.
msgid "<strong>Love the plugin?</strong> Please leave us a 5-star review and help spread the word!"
msgstr ""

#. Found in description list item.
msgid "<a href=\"https://ayudawp.com/\">Documentation and tutorials</a>"
msgstr ""

#. Found in description list item.
msgid "<a href=\"https://www.youtube.com/AyudaWordPressES\">YouTube channel</a>"
msgstr ""

#. Found in description list item.
msgid "<a href=\"https://wordpress.org/support/plugin/no-gutenberg/\">WordPress support forum</a>"
msgstr ""

#. Found in description list item.
msgid "<a href=\"https://servicios.ayudawp.com/\">Official website</a>"
msgstr ""

#. Found in description header.
msgid "About AyudaWP"
msgstr ""

#. Found in description header.
msgid "Need help or have suggestions?"
msgstr ""

#. Found in description header.
msgid "Support"
msgstr ""

#. Found in faq header.
msgid "Why choose this over other similar plugins?"
msgstr ""

#. Found in faq header.
msgid "Is this compatible with my theme and my plugins?"
msgstr ""

#. Found in faq header.
msgid "What happens if I deactivate the plugin?"
msgstr ""

#. Found in faq header.
msgid "Will this break my existing content?"
msgstr ""

#. Found in faq header.
msgid "Does this work with WooCommerce?"
msgstr ""

#. Found in description paragraph.
msgid "<strong>What this plugin removes:</strong>"
msgstr ""

#. Found in description list item.
msgid "Shows activation success notice"
msgstr ""

#. Found in description list item.
msgid "Site Editor functionality"
msgstr ""

#. Found in description list item.
msgid "Block Directory integration"
msgstr ""

#. Found in description list item.
msgid "Theme.json support and processing"
msgstr ""

#. Found in description list item.
msgid "Block Patterns and Pattern Directory"
msgstr ""

#. Found in description list item.
msgid "Block-based Widget Editor (reverts to Classic Widgets)"
msgstr ""

#. Found in description list item.
msgid "Full Site Editing (FSE) Global Styles and inline CSS"
msgstr ""

#. Found in description list item.
msgid "Gutenberg Block Editor (completely disabled)"
msgstr ""

#. Found in description header.
msgid "Admin Experience"
msgstr ""

#. Found in description header.
msgid "WooCommerce Integration"
msgstr ""

#. Found in description header.
msgid "Performance Optimizations"
msgstr ""

#. Found in description header.
msgid "Core Gutenberg Features"
msgstr ""

#. Screenshot description.
msgid "FSE theme activation warning"
msgstr ""

#. Screenshot description.
msgid "Activation success notice"
msgstr ""

#. Screenshot description.
msgid "Classic Widgets interface instead of block widgets"
msgstr ""

#. Screenshot description.
msgid "WordPress posts page with Classic Editor restored"
msgstr ""

#. Found in installation list item.
msgid "Activate the plugin through the 'Plugins' menu in WordPress"
msgstr ""

#. Found in installation list item.
msgid "Upload the 'no-gutenberg' folder to the '/wp-content/plugins/' directory"
msgstr ""

#. Found in installation list item.
msgid "Download the plugin from WP repository"
msgstr ""

#. Found in installation list item.
msgid "Go to your WP Dashboard &gt; Plugins and search for 'no gutenberg' or…"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Fix: The status panel said \"1 still added by other plugins\" when a single pattern was left, and gave translators two identical plural forms"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Fix: Removed a filter removal that never did anything: the callback it named was never part of WordPress"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Fix: Block widgets already saved on a site stopped being rendered on the frontend and disappeared from the Widgets screen. Nothing was lost, they are back on update, but do not save the Widgets screen while running 2.3.1"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Fix: Sites running Divi 5 got a fatal error on every frontend page. Removing the block widgets from the classic Widgets screen unregistered the Block widget itself, and Divi asks WordPress for it while deciding which stylesheets a page needs. The classic Widgets screen is restored the same way as before, without touching the widget"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Fix: The Block widget is now really gone from the classic Widgets screen. The cleanup ran after WordPress had already registered it, so it stayed on the list"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Fix: Pages were loading the block styles and scripts of every plugin that registers blocks, even where no block appears. Removing the block CSS also turned off the on-demand loading that WordPress 6.8 tied to the same switch, so on a site with block plugins installed this plugin was adding weight instead of saving it"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Improved: The plugin calls itself No Gutenberg? everywhere now, the same name it has on WordPress.org, instead of No Gutenberg in the plugins list, the Settings menu, its settings screen and its notices"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Improved: Tested up to WordPress 7.1, with no changes needed. The always iframed post editor, the persistent toolbar and the new client-side media processing headers only reach the block editor, and the Site Editor, Patterns and Fonts screens this plugin removes keep the same slugs"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Fix: Uninstall now also removes the version option, the per entry editor meta and the content count transients"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Improved: The activation notice says how many entries are built with blocks and what is going to happen to them"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Improved: The status panel counts drafts, pending, private and scheduled entries too, not only published ones, and links to the entries it is counting. A site in the middle of a migration was being told it had no block content"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Improved: Sites arriving from the Classic Editor plugin keep the editor it recorded for each entry, instead of starting from zero"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "Improved: The editor chosen for a single entry is now honored whatever the configuration is, master switch included. It used to be read only where per entry switching was enabled, which left no way out on a site with everything disabled"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "New: The Classic Editor warns you when the entry you are editing is built with blocks, before you save it, with a link to open it in the block editor instead"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "New: The entries list says which editor each entry opens with, and flags the entries built with blocks that are opening in the Classic Editor. A \"Built with blocks\" link next to All and Published narrows the list down to them, so you can finally see which entries they are instead of only how many"
msgstr ""

#. Found in changelog list item.
#, gp-priority: low
msgid "New: Existing block content is protected. An entry that already contains blocks keeps the block editor whatever the rules say, so installing the plugin on a site with mixed content no longer sends that content to an editor that reflows its markup. A checkbox under the master switch gives the protection up when you really want the Classic Editor on everything"
msgstr ""

#. Found in changelog paragraph.
#, gp-priority: low
msgid "For older changelog entries, please check the <a href=\"https://plugins.svn.wordpress.org/no-gutenberg/trunk/changelog.txt\">changelog.txt</a> file"
msgstr ""