diff --git a/composer.lock b/composer.lock index 168a1108..5c09ad39 100644 --- a/composer.lock +++ b/composer.lock @@ -4,7 +4,7 @@ "Read more about it at https://getcomposer.org/doc/01-basic-usage.md#installing-dependencies", "This file is @generated automatically" ], - "content-hash": "a808848d5eccd5aa5f22bbd5bae2ae94", + "content-hash": "7488d4129de5990865a52d66c863dce7", "packages": [], "packages-dev": [ { diff --git a/languages/block-visibility.pot b/languages/block-visibility.pot new file mode 100644 index 00000000..83ad453f --- /dev/null +++ b/languages/block-visibility.pot @@ -0,0 +1,412 @@ +# Copyright (C) 2020 Nick Diego +# This file is distributed under the same license as the Block Visibility plugin. +msgid "" +msgstr "" +"Project-Id-Version: Block Visibility 1.0.0\n" +"Report-Msgid-Bugs-To: https://wordpress.org/support/plugin/block-visibility\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" +"POT-Creation-Date: 2020-08-03T10:59:58+00:00\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"X-Generator: WP-CLI 2.4.0\n" +"X-Domain: block-visibility\n" + +#. Plugin Name of the plugin +#: includes/admin/settings.php:21 +#: includes/admin/settings.php:22 +#: dist/block-visibility-settings.js:6 +#: src/settings/masthead.js:29 +msgid "Block Visibility" +msgstr "" + +#. Plugin URI of the plugin +msgid "http://www.outermost.co/" +msgstr "" + +#. Description of the plugin +msgid "Block-based visibility control for WordPress" +msgstr "" + +#. Author of the plugin +msgid "Nick Diego" +msgstr "" + +#. Author URI of the plugin +msgid "https://www.nickdiego.com" +msgstr "" + +#: class-blockvisibility.php:68 +#: class-blockvisibility.php:82 +msgid "Something went wrong." +msgstr "" + +#: includes/admin/plugin-action-links.php:29 +msgid "Settings" +msgstr "" + +#: includes/admin/plugin-action-links.php:56 +msgid "Review Block Visibility on WordPress.org" +msgstr "" + +#: includes/admin/plugin-action-links.php:57 +msgid "Leave a Review" +msgstr "" + +#: includes/utils/get-user-roles.php:24 +msgid "Public (Logged-out Users)" +msgstr "" + +#: dist/block-visibility-editor.js:1 +#: src/editor/hide-block.js:27 +msgid "Hide block" +msgstr "" + +#: dist/block-visibility-editor.js:1 +#: src/editor/hide-block.js:37 +msgid "Hide selected block from everyone." +msgstr "" + +#: dist/block-visibility-editor.js:1 +#: src/editor/user-roles.js:33 +msgid "Restrict by User Role" +msgstr "" + +#: dist/block-visibility-editor.js:1 +#: src/editor/user-roles.js:36 +msgid "The block will only be visible to users with one of the selected roles." +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "All" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "Visible to everyone" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "Public" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "Visible to all logged-out users" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "Private" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "Visible to all logged-in users" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "User Role" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "Restrict visibility to specific user roles" +msgstr "" + +#: dist/block-visibility-editor.js:1 +#: dist/block-visibility-settings.js:6 +msgid "Visibility by User Role" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "The User Role option was previously selected, but is now disabled. Choose another option or update the Visibility Control settings." +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "Visibility" +msgstr "" + +#: dist/block-visibility-editor.js:1 +msgid "Looks like all Visibility Controls have been disabled. To control block visibility again, re-enable some Visibility Controls." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/masthead.js:33 +msgid "Block-based visibility control for the WordPress editor. Allows you to dynamically control which blocks are visible on your website and who can see them. Compatible with all blocks." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/masthead.js:51 +msgid "Review" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/masthead.js:60 +msgid "Plugin Support" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:38 +msgid "Welcome" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:41 +msgid "Thank you for choosing Block Visibility. As the name suggests, this plugin allows you to easily control the visibility of blocks in the WordPress editor. To get started, watch the video below for an overview of how the plugin works. You'll become a pro in no time!" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:49 +msgid "Block Visibility - Getting Started" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:62 +msgid "How does it work?" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:65 +msgid "The Block Visibility plugin is designed exclusively for the block editor and does not work in the classic editor. So long as you are running the latest version of WordPress and are not utilizing the Classic Editor plugin, you are good to go!" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:82 +msgid "By default, this plugin adds a Visibility panel to the settings sidebar of each selected block in the WordPress editor. While there are a few minor exceptions, see the FAQs below, this means that visibility controls will be enabled for all core WordPress blocks as well as any third-party blocks that you might be using." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:98 +msgid "On the Visibility panel, you will be able show or hide the selected block based on a number of different controls. The primary option is to simply hide the block from view. This can be useful if you want to disable some content, but you still need to publish other changes to the page or post. You can also restrict who can see certain blocks. For example, maybe you have a special promotion that you only want show subscribers of your website. If you haven’t already, watch the video above for a quick demo." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:104 +msgid "Block Visibility provides a number of advanced settings so you can configure the plugin exactly the way you want. Lets examine these in the drop-downs below and answer a few frequently asked questions." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings.js:110 +#: src/settings/getting-started.js:112 +msgid "Visibility Controls" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:117 +msgid "Visibility controls are the settings that determine whether a block is hidden on the frontend of your website. We strive to provide as much visibility control as possible, and as development for Block Visibility continues, expect even more functionality in the future. However, we understand that some users do not need every option. It is equally important to have a decluttered and streamlined user interface. Therefore, on the Visibility Controls tab of this settings page, you can enable or disable any control." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings.js:115 +#: src/settings/getting-started.js:125 +msgid "Block Manager" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:130 +msgid "By default, this plugin adds visibility controls to all blocks in the WordPress editor. Similar to visibility controls, we understand that not all users may want this functionality. You might decide to restrict visibility controls to only a handful of block types. On the Block Manager tab of this settings page, you can do just that. Simply disable the block types that should not have visibility controls and the settings will no longer be available in the WordPress editor." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings.js:120 +#: src/settings/getting-started.js:138 +msgid "General Settings" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:143 +msgid "The General Settings tab contains a collection of miscellaneous plugin options including Full Control Mode and uninstall settings. As development of Block Visibility continues, expect more settings to be developed." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:151 +msgid "Frequently Asked Questions" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:159 +msgid "Does this plugin really work for every block?" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:165 +msgid "Yes! However, not all block types are enabled by default. Visibility controls are only provided to blocks that can be added directly to a page/post by the block inserter. Therefore, some specialized blocks, such as child blocks, are not included by default. An example being the individual Column block that is part of the larger Columns block." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:171 +msgid "That said, you can enable Full Control Mode in the plugin settings. This removes all restrictions and adds visibility controls to every block. You probably will not need Full Control Mode, but it is there if you do." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:178 +msgid "Furthermore, while this plugin was designed to be compatible with all blocks, the WordPress ecosystem is ever expanding. If you find a conflict with a certain block, please let us know in the plugin support forum and we will investigate. We are committed to bringing visibility control to every block." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:194 +msgid "Will more visibility controls be added in the future?" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:201 +msgid "Yes, and if you have a specific idea of what you would like to see, please submit a feature request in the plugin support forum on WordPress.org." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:217 +msgid "Does this plugin work with the upcoming full site editing functionality?" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:223 +msgid "Since full site editing is still in the development phase, this plugin does not currently work with this new functionality. However, Block Visibility was designed with full site editing in mind. There are tons of interesting applications for visibility control and we plan to get the plugin ready for full site implementation in the coming months." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:229 +msgid "Is there a pro/premium version of Block Visibility?" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:236 +msgid "A premium version of Block Visibility is in the works and will include some specialized controls, such as time-based restrictions. For current information on Block Visibility Premium, please visit blockvisibilitywp.com." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:255 +msgid "How can we help?" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:257 +msgid "Whether you need more help, have a quick question, or you would like to request a new feature, please create a topic in this plugin's support forum on WordPress.org." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/getting-started.js:267 +msgid "Get Support" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/save-settings.js:35 +msgid "Updating…" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/save-settings.js:36 +msgid "Update" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/save-settings.js:46 +msgid "Saving" +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings/save-settings.js:61 +msgid "Update failed. Try again or contact support." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Learn More" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "When a visibility control is disabled, blocks that relied on the disabled control will become visible again. Likely this is what you intended, but we wanted to provide this warning just in case." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "To learn more about Visibility Controls, review the plugin documentation using the link below." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "The settings below allow you to configure the visibility controls that power this plugin. Pick and choose which controls you would like to enable and how you would like them to function." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Configure Controls" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Hide Block" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "To learn more about the Hide Block control, review the plugin documentation using the link below." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Enable the ability to hide blocks completely from the frontend of your website." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "To learn more about the Visibility by User Role control, review the plugin documentation using the link below." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Enable the ability to restrict block visibility by whether a user is logged-in or logged-out." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Enable the ability to restrict block visibility by individual user role (Administrator, Editor, Subscriber, etc.)" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Visibility is enabled for all blocks" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Not every block type may need visibility controls. The Block Manager allows you to decide which blocks do. If you are looking for a block, and do not see it listed, you may need to enable Full Control Mode on the General Settings tab." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "To learn more about the Block Manager, review the plugin documentation using the link below." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "The settings below allow you restrict visibility controls to specific block types. By default, all block types have visibility enabled, but you may want to limit this functionality depending on your needs." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Search for a block" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "To learn more about General Settings, review the plugin documentation using the link below." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "This page allows you to confiure settings that affect the general functionality of the Block Visibility plugin. As development continues, addtional settings will be added, giving you even more control over how the plugin operates." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Configure Settings" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Full Control Mode" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "By default, not all blocks are provided with visibility controls. These include child blocks and blocks that may exist in WordPress, but cannot actually be added directly to the editor. Most of the time, you will not need Full Control Mode, but it's there in case you do. Use with caution. Click the link below for complete details." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Enable Full Control Mode to add visibility controls to every block. Use with caution." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Uninstall" +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Settings that impact what happens when the Block Visibility plugin is uninstalled." +msgstr "" + +#: dist/block-visibility-settings.js:6 +msgid "Remove all plugin settings when Block Visibility is uninstalled." +msgstr "" + +#: dist/block-visibility-settings.js:6 +#: src/settings.js:105 +msgid "Getting Started" +msgstr ""