bbsetheme

<ul>
<li>Support multisite network ! 
BBS e-Popup support features to produce and manage popups. 
You can set popups for websites conveniently and efficiently. 
BBS e-Popup support shortcode for the posts or pages. 
This is a free word press popup plug-in that can generate popups infinitely. (For PCs or MOBILEs) 
[Free] 25 templates and 36 close buttons included.</li>
</ul>
<h4>* 한국어 : </h4>
<ul>
<li>멀티사이트 지원 ! 
BBS e-Popup은 팝업을 직접생성하고 관리할 수 있는 기능을 제공합니다. 
편리하고 효율적으로 웹사이트에 팝업을 설정할 수 있습니다. 
BBS e-Popup은 포스트 및 페이지를 위한 숏코드를 지원합니다. 
무제한으로 팝업을 생성할 수 있는 무료 워드프레스 팝업 플러그인 입니다. (PC, Mobile 선택 적용) 
[무료] 25개의 템플릿, 36개의 닫기버튼 포함</li>
</ul>
[Main Features] 
Generate popups easily using the editor for desired contents. 
Use images, HTML or other codes to add popups, and it is the same as adding word press contents pages. 
By using condition functions for specific users, it offers the functions to use popup in the exact location. to expose to specific users or users that access a specific page. 
Possible to manage use of popups generated infinitely. 
Select popup animation to set the popup method. 
Provides functions to set exact location and font size. With the fixed popup in the center, you can set the exact location in the website. 
You can change image, background, border, shadow, popup period message and types. 
You can change the word press site and harmonious popup shape and feel.
<h4>* 한국어 : </h4>
원하는 콘텐츠를 에디터를 활용해 쉽게 만들어 팝업을 생성할 수 있습니다. 
이미지 또는 HTML 및 기타 코드를 사용하여 팝업을 추가하는 것은 단지, 워드프레스 콘텐츠페이지를 추가하는 것과 같습니다. 
특정사용자를 대상으로 조건 기능을 사용하면 원하는 위치에 정확하게 팝업을 사용할 수 있는 기능을 제공하여, 
특정 사용자 및 특정페이지에 접근한 사용자에게 팝업을 노출 할 수 있습니다. 
무제한 팝업생성 생성된 팝업 사용여부 관리를 할 수 있습니다. 
팝업 애니메이션을 선택하여 팝업 방식을 설정 할 수 있습니다. 
완벽한 위치 및 크기 설정 기능을 제공합니다. 고정팝업을 중심으로 웹사이트에 맞는 완벽한 위치 설정을 할 수 있습니다. 
이미지, 배경, 테두리, 그림자, 팝업기간 메세지 및 유형 등을 변경할 수 있습니다. 
워드프레스 사이트와 조화로운 팝업의 모양과 느낌을 변경할 수 있습니다.
[Other Features]
You can select template or design with preview screen. 
Click on the Apply button to apply designs. 
Changes to desired contents to complete popup design.
<h4>* 한국어 : </h4>
템플릿을 선택, 미리보기 화면으로 디자인을 확인 할 수 있습니다. 
적용 버튼을 클릭 하면 디자인이 적용 됩니다. 
원하는 내용으로 텍스트를 변경하여 팝업디자인을 완성합니다.
<h4>* 中国語 : </h4>
选择模板后,可在预览画面确认设计。 
点击适用键即可使用设计。 
将文本变更为需要的内容后，完成弹窗设计。
<h4>* 日本語 : </h4>
テンプレートを選択し、あらかじめ見ることができます。 
適用ボタンをクリックするとデザインが適用します。 
テキストをお好みに合わせて変更しポップアップデザインを完成させます。
[Templates & Design]
Offers popup design template that can be utilized for various uses. 
Offers various button designs. 
Offers various languages such as English, Japanese(日本語), Chinese(中国語) and Korean(한국어).
<h4>* 한국어 : </h4>
다양한 용도로 활용 할 수 있는 팝업 디자인 템플릿을 제공 합니다. 
다양한 버튼 디자인을 제공합니다. 
영어(English), 일본어(日本語), 중국어(中国語), 한국어 등 다양한 언어 제공
<h4>* 中国語 : </h4>
提供适用于多种用途的弹窗设计模板。 
提供多种按键设计。 
提供英语、日语、中国语、韩国语等多种语言。
<h4>* 日本語 : </h4>
多様な用途で活用できるポップアップデザインテンプレートを提供します。 
多様なボタンデザインを提供します。 
英語、日本語、中国語、韓国語など多様な言語を提供

BBS e-Popup

BBS e-Popup support features to produce and manage popups.(English,日本語,中国語,한국어)

Blackbam

Tim Reeves

rawrly

Please someone take over maintaining this plugin, or it will get abandoned – with over 9.000 active installations.
I’m now 69 and although retired, all my time is taken up with other projects, while I still have the energy for them. Why you might want to take it over? It’s really useful:
Make your editing experience as simple and good as possible by improving the way you work with the TinyMCE visual editor (including Gutenberg Classic block). This plugin adds custom CSS file(s) to the frontend and to the TinyMCE editor; and it allows you to populate TinyMCE’s ‘Formats’ dropdown with your own styles. The features in more detail:
1. Installs two CSS stylesheet files into your chosen location (so you can still do updates of the active theme and this plugin and even switch to another theme). In general you will need to fetch the auto-created stub files via FTP, edit them locally and upload them, overwriting the previous versions.
<ul>
<li>editor-style.css is used for styling your TinyMCE Editor</li>
<li>editor-style-shared.css is used for styles to be used by the frontend AND in your TinyMCE editor (so you do not have to copy)</li>
</ul>
To use this feature, you have to write your own CSS code into these files.
2. The main feature of this Plugin is to offer a Backend-GUI to create custom styles for TinyMCE (‘Formats’ dropdown) dynamically.
<ul>
<li>Easy to add, change and delete styles</li>
<li>No editing of source code required (excepting the CSS stylesheets)</li>
<li>Allows you to add block- and inline elements which are not provided by TinyMCE, e.g. <figure>, <cite>, <q> etc.</li>
<li>The plugin’s backend page contains a lot of description and some links to help you define your styles correctly</li>
<li>Note that each style can have both CSS Classes and/or CSS Inline-Styles. The latter (excepting color) will even be applied to the Formats dropdown menu items. However, I do not recommend inline styles as they are inserted into the text of the post/page and remain unchanged if you later alter the style in the plugin settings – so in general stick to Classes!</li>
</ul>
How the two stylesheets are applied 
The shared style sheet file is enqueued to be included on frontend pages (via the usual <link> tag in the <head> area) using the standard WordPress function <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_style/" rel="nofollow ugc">wp_enqueue_style</a>.
So, as with most other stylesheets, the statements in it will automatically apply to the whole HTML page. So define class names which will not collide with any already in use by the theme – and do not define styles for HTML elements without a limiting class name unless you want them to apply to all elements of that tag type (including in header, footer, sidebar…).
Both stylesheets are passed to TinyMCE by calling: add_filter(‘mce_css’, …)
What this causes to happen is that they are linked in to the HTML document which is the source for an <iframe>, which is the editing area of TinyMCE. So they should definitely only apply to HTML in the iframe – although I have heard that some situations, e.g. a cache plugin, may break this mechanism.
Gutenberg classic blocks 
As of version 1.1.1 this plugin works for the Gutenberg classic block.
WordPress MultiSite 
Although it does not check for MultiSite, the plugin works in the MultiSite environment, since WordPress uses a separate Options table for each MultiSite. You can reuse the same CSS files (by supplying the same custom directory in each Site), or add separate ones for each Site.
Current Languages 
– en_US 
– de_DE (Tim Reeves)
<h3>Background Information</h3>
Then and Now 
This plugin was originally written by David Stöckl in 2013 – long before Gutenberg had been conceived, and at a time when several different plugins all tried to enhance the TinyMCE editor in different ways. It was abandoned a year later by David and I forked it in 2016, renamed to TinyMCE Custom Styles” (“TCS”). Most of those other TinyMCE-related plugins, notably WP Edit, are now abandoned; apart from this plugin, only TinyMCE Advanced, now also handling Gutenberg and renamed to <a href="https://wordpress.org/plugins/tinymce-advanced/" rel="ugc">Advanced Editor Tools</a> (abbreviated hereafter to “AET”) seems to still be notably active in this area. AET is a great plugin – you can also check out its companion for developers <a href="https://wordpress.org/plugins/advanced-tinymce-configuration/" rel="ugc">Advanced TinyMCE Configuration</a>. I use AET myself on most websites – but there are a few things it’s not designed to do, and that’s where this plugin fills the gap. You can consider it as AET’s sidekick 🙂
TinyMCE and the WordPress theme 
The goal is to configure the TinyMCE backend editor so that its ‘Visual’ tab displays content as closely as possible to how it will look on the content area of the actual website. To this end, WordPress has for years provided a feature which can be used by themes, called ‘editor styles’. This allows a theme to make known to WordPress one or more CSS files, which should contain a subset of the theme’s styles, those which apply to the display of content in the content area (i.e. excluding styles applying to headers, sidebars, footers, archives, comments, …). If the theme provides this feature, that CSS file (or files) are loaded to TinyMCE to achieve the goal. The default location is one file named ‘editor-style.css’ in the theme’s root directory. In fact, WordPress seems to find this file, if present, even if the theme does not register it. All good modern themes provide this feature.
Advanced Editor Tools 
The really good plugin ‘Advanced Editor Tools’ (“AET”, from and maintained by Andrew Ozz, a WordPress core developer, now attributed to Automattic, the company effectively behind WordPress) helps with one of the problems noted above: It gives you complete freedom to select which buttons and dropdowns are displayed in TinyMCEs header – in particular you can just drag the ‘Formats’ dropdown into one of the bar areas, exactly where you want it. AET also has a number of other options, for example to prevent TinyMCE from removing tags and minifying the text in the ‘Text’ tab, which is very useful when you need to look at the HTML and do any manual adjustment.
Shortcomings in the standard setup 
There are some regrettable weaknesses in the unenhanced situation:
<ul>
<li>
Any custom CSS which you set in the WordPress Customizer is not applied to TinyMCE (it is written out as direct styles in the <head> of each website page).
</li>
<li>
The styles which the theme provides for TinyMCE are applied to the HTML displayed by the editor. This is fine with fixed styling of elements like , <ul> or <blockquote>. But a theme may also include optional styles to change or enhance the display of an element – e.g. ‘.small’, ‘.screen-reader-text’, ‘.beforelist’, ‘.hilitebox’ and so on. In this case, and without help from any plugin, there is no way to select any of them from the menu or toolbar of TinyMCE in order to apply them to an element, so a user would need to know the style names and apply them manually in the ‘Text’ tab – not good. See below ‘importcss’, but note that it overwrites anything other plugins have put in the ‘Formats’ dropdown.
</li>
<li>
In the standard configuration (i.e. without enhancer plugins) TinyMCE is not even configured to show the ‘Formats’ dropdown, which we need to apply custom styles to elements in the text.
</li>
</ul>
The TinyMCE Formats dropdown 
Internal name: ‘styleselect’. By default, this dropdown is not displayed. You can <a href="https://codex.wordpress.org/TinyMCE_Custom_Styles" rel="nofollow ugc">add code</a> e.g. to your theme’s functions.php, to have it shown. Its default contents are 4 entries with corresponding submenus: Headings, Inline, Blocks and Alignement.
TCS always registers the ‘Formats’ dropdown to TinyMCE’s second toolbar, this does not seem to be a problem for AET.
It is in this area that TCS is really usefull: It allows you to create named styles, so you can name them descriptively, e.g. to show if the style is a block or inline style, if it uses the Wrapper option, and so on. Basically you will be adding styles to the dropdown which are defined in a stylesheet from the theme, or in your ‘editor-style-shared.css’, to allow you (or your customer) convenient and understandable access to them while editing.
The TinyMCE JavaScript plugin ‘importcss’ 
When the AET plugin is active, it offers an option “Create CSS classes menu” (subtitle: Load the CSS classes used in editor-style.css and replace the Formats menu). When checked, a TinyMCE JavaScript plugin called ‘importcss’ is loaded to the frontend, which parses the CSS loaded to TinyMCE (i.e. from your theme’s ‘editor styles’ and this plugins ‘editor-style.css’) and populates the ‘Formats’ dropdown with a selection of those styles. Styles applying directly to HTML elements without a class name are skipped. Styles applying to a tag and containing a class, e.g. “h1.page-title” will be included and work as expected. But for classes not limited to a tag, it has no way of knowing if the class is intended to be applied to a block element or as an inline element, nor to which tags it should apply or should use, so it simply offers them as inline elements, which may or may not be their intended use. Styles with a pseudo-class or pseudo-element (e.g. ‘:hover’, ‘::before’) will be omitted. The bottom line is, that however good the themes editor styles are, we end up with a sub-optimal population of the Formats dropdown: It will be too long (including many styles we don’t need or don’t understand), and some valuable styles will be missing or wrongly classified as inline styles. Given all these shortcomings, I have not found this feature to be of much use in practice.
<h3>Credits</h3>
This plugin is a fork of <a href="https://wordpress.org/plugins/tinymce-and-tinymce-advanced-professsional-formats-and-styles/" rel="ugc">TinyMCE Advanced Professsional Formats and Styles</a> which has been abandoned by the original author. Initially I just fixed a JavaScript bug so that it worked again, and cleaned up the code and messages a bit. Since then, a number of further improvements, see the changelog. I was born in 1954 and would be glad if someone else would now take over this plugin and further improve it. Translations are also very welcome.
<ul>
<li><a href="https://blog.blackbam.at/" rel="nofollow ugc">David Stöckl</a>, Vienna, the original author. Many thanks!</li>
<li>The plugin icon (<a href="https://timreeves.de/kompetenz/" rel="nofollow ugc">Der Bitkönig</a>) was drawn by Gabriele Meischner, muchas Gracias!</li>
<li><a href="https://profiles.wordpress.org/rawrly/" rel="nofollow ugc">Rawrly</a> for providing security updates.</li>
</ul>
<h3>Report Security Bugs</h3>
Please report all security bugs found in this project by following the <a href="https://patchstack.com/database/vdp/tinymce-custom-styles" rel="nofollow ugc">vulnerability disclosure process</a>.

TinyMCE Custom Styles

My publishers love it!  Thank you for this plugin.

Great plugin

Enhance TinyMCE visual editor with a dedicated stylesheet, a stylesheet shared with the frontend, and custom styles in the Formats dropdown.

BBS e-Popup vs TinyMCE Custom Styles