Title: Awesome Newsletter Author: awesomecoders Published: 2019-10-28 Last modified: 2019-10-29 --- Szukaj wtyczek ![](https://ps.w.org/awesome-newsletter/assets/banner-772x250.png?rev=2181224) Wtyczka **nie została przetestowana z trzema ostatnimi głównymi wydaniami WordPressa**. Może nie być już utrzymywana lub obsługiwana, co może skutkować problemem ze zgodnością z nowszymi wersjami WordPressa. ![](https://s.w.org/plugins/geopattern-icon/awesome-newsletter_ff5757.svg) # Awesome Newsletter Autor: [awesomecoders](https://profiles.wordpress.org/awesomecoders/) [Pobierz](https://downloads.wordpress.org/plugin/awesome-newsletter.zip) * [Szczegóły](https://pl.wordpress.org/plugins/awesome-newsletter/#description) * [Recenzje](https://pl.wordpress.org/plugins/awesome-newsletter/#reviews) * [Instalacja](https://pl.wordpress.org/plugins/awesome-newsletter/#installation) * [Rozwój](https://pl.wordpress.org/plugins/awesome-newsletter/#developers) [Wsparcie](https://wordpress.org/support/plugin/awesome-newsletter/) ## Opis Use shortcode ( [newsletter_form] ) to show the subscriber form A few notes about the sections above: * „Contributors” is a comma separated list of wordpress.org usernames * „Tags” is a comma separated list of tags that apply to the plugin * „Requires at least” is the lowest version that the plugin will work on * „Tested up to” is the highest version that you’ve _successfully used to test the plugin_. Note that it might work on higher versions… this is just the highest one you’ve verified. * Stable tag should indicate the Subversion „tag” of the latest stable version, or „trunk,” if you use `/trunk/` for stable. * Note that the `readme.txt` of the stable tag is the one that is considered the defining one for the plugin, so if the `/trunk/readme.txt` file says that the stable tag is `4.3`, then it is `/tags/4.3/readme.txt` that’ll be used for displaying information about the plugin. In this situation, the only thing considered from the trunk `readme.txt` is the stable tag pointer. Thus, if you develop in trunk, you can update the trunk `readme.txt` to reflect changes in your in-development version, without having that information incorrectly disclosed about the current stable version that lacks those changes — as long as the trunk’s `readme.txt` points to the correct stable tag. * If no stable tag is provided, it is assumed that trunk is stable, but you should specify „trunk” if that’s where you put the stable version, in order to eliminate any doubt. ### Arbitrary section You may provide arbitrary sections, in the same format as the ones above. This may be of use for extremely complicated plugins where more information needs to be conveyed that doesn’t fit into the categories of „description” or „installation.” Arbitrary sections will be shown below the built-in sections outlined above. ### A brief Markdown Example Ordered list: 1. Some feature 2. Another feature 3. Something else about the plugin Unordered list: * something * something else * third thing Here’s a link to [WordPress](https://wordpress.org/) and one to [Markdown’s Syntax Documentation](https://daringfireball.net/projects/markdown/syntax). Titles are optional, naturally. Markdown uses email style notation for blockquotes and I’ve been told: > Asterisks for _emphasis_. Double it up for **strong**. ``` ``` ## Instalacja This section describes how to install the plugin and get it working. e.g. 1. Upload the plugin files to the `/wp-content/plugins/plugin-name` directory, or install the plugin through the WordPress plugins screen directly. 2. Activate the plugin through the 'Plugins’ screen in WordPress 3. Use the Settings->Plugin Name screen to configure the plugin 4. (Make your instructions match the desired user flow for activating and installing your plugin. Include any steps that might be needed for explanatory purposes) ## Najczęściej zadawane pytania A question that someone might have An answer to that question. What about foo bar? Answer to foo bar dilemma. ## Recenzje Wtyczka nie ma jeszcze żadnej recenzji. ## Kontrybutorzy i deweloperzy „Awesome Newsletter” jest oprogramowaniem open source. Poniższe osoby miały wkład w rozwój wtyczki. Zaangażowani * [ awesomecoders ](https://profiles.wordpress.org/awesomecoders/) [Przetłumacz wtyczkę “Awesome Newsletter” na swój język.](https://translate.wordpress.org/projects/wp-plugins/awesome-newsletter) ### Interesuje cię rozwój wtyczki? [Przeglądaj kod](https://plugins.trac.wordpress.org/browser/awesome-newsletter/), sprawdź [repozytorium SVN](https://plugins.svn.wordpress.org/awesome-newsletter/) lub czytaj [dziennik rozwoju](https://plugins.trac.wordpress.org/log/awesome-newsletter/) przez [RSS](https://plugins.trac.wordpress.org/log/awesome-newsletter/?limit=100&mode=stop_on_copy&format=rss). ## Rejestr zmian #### 1.0 * A change since the previous version. * Another change. #### 0.5 * List versions from most recent at top to oldest at bottom. ## Meta * Wersja **1.0.0** * Ostatnia aktualizacja **7 lat temu** * Włączone instalacje **Mniej niż 10** * Wersja WordPressa ** 4.7 lub nowszej ** * Testowano do **5.2.29** * Wersja PHP ** 5.4 lub nowszej ** * Język * [English (US)](https://wordpress.org/plugins/awesome-newsletter/) * Tagi * [email subscriber](https://pl.wordpress.org/plugins/tags/email-subscriber/)[newsletter](https://pl.wordpress.org/plugins/tags/newsletter/) [subscriber](https://pl.wordpress.org/plugins/tags/subscriber/) * [Widok zaawansowany](https://pl.wordpress.org/plugins/awesome-newsletter/advanced/) ## Oceny Nie przesłano jeszcze żadnych recenzji. [Twoja opinia](https://wordpress.org/support/plugin/awesome-newsletter/reviews/#new-post) [Zobacz wszystkierecenzje.](https://wordpress.org/support/plugin/awesome-newsletter/reviews/) ## Zaangażowani * [ awesomecoders ](https://profiles.wordpress.org/awesomecoders/) ## Wsparcie Masz coś do dodania? Potrzebujesz pomocy? [Zobacz forum wsparcia](https://wordpress.org/support/plugin/awesome-newsletter/) ## Złóż datek Czy chcesz wesprzeć rozwój wtyczki? [ Wspomóż wtyczkę ](https://example.com/)