forked from kevinweber/wbounce
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathreadme.txt
210 lines (148 loc) · 11.4 KB
/
readme.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
=== wBounce ===
Contributors: kevinweber
Donate link: http://kevinw.de/donate/wBounce/
License: MIT
Tags: admin, newsletter, exit popup, exit popups, ab-testing, roi, conversion, conversion rate optimisation, free, plugin, wordpress, marketing, landing page
Requires at least: 3.5
Tested up to: 4.7.2
Stable tag: 1.6.3
wBounce improves bounce rate to boost conversions and sales. The free alternative to Bounce Exchange for WordPress.
== Description ==
wBounce is the free exit popup software for WordPress, evolved by [Kevin Weber](http://kevinw.de). This plugin bases on [Ouibounce]( http://carlsednaoui.github.io/ouibounce/) by Carl Sednaoui.
Exit popups are not only "in vogue", they are provably increasing conversions and therefore boost marketing, signups and sales. wBounce displays an inline popup before the user leaves your site. ("Inline popup" means that this is NOT one of those out-dated, annoying popups windows.) Inline popups catch the visitor's attention even if they are in the process of leaving your site.
wBounce is the free alternative to charged services like Bounce Exchange or OptinMonster that are often used for landing page optimisation. wBounce is lightweight and renounces unnecessary scripts. You decide which features will be developed and implemented next.
One concern in everyone's interest: Make sure to provide VALUE when you use wBounce and don't spam your visitors.
This plugin makes it extremely easy to implement exit popups. You don't have to manually "hack" your WordPress theme. Just activate and modify it via your admin backend. It works with WordPress Multisite so that you can define a wBounce template for each site in your network.
Demo and more information on the developer's website: [kevinw.de/wbounce/](http://kevinw.de/wbounce/)
You want to enhance this plugin? Please [contribute on Github](https://github.com/kevinweber/wbounce).
= Features: =
* Display inline popup before the user leaves the site
* Alternatively display popup on enter or after a certain time period (self-acting fire)
* Set custom content via backend
* Define custom content for pages and posts individually using a flexible template engine which uses so-called "magic shortcodes"
* Lots of open/exit animation styles
* Shortcodes from other plugins are also supported
* Determine sensitivity, cookie expiration, hesitation, and more
* Add custom CSS
* Set default status: Define if wBounce should be fired on posts and/or pages by default. You can override the default setting on every post and page individually.
* Event tracking with Google Analytics
== Installation ==
1. Upload wBounce into your plugin directory (/wp-content/plugins/) and activate it through the 'Plugins' menu in WordPress.
2. Configure the plugin via the admin backend and define your template. You can even insert shortcodes that are provided by your other plugins.
3. Optionally: Sign up to the wBounce newsletter to get notified about major updates.
Important: wBounce does not collect and store e-mail addresses itself. Therefore, you can insert any HTML. For example, you can copy the form code that's provided by MailChimp (or any other newsletter service) and the signups will be stored using your newsletter service.
== Frequently Asked Questions ==
= Does wBounce work with MailChimp, aWeber, GetResponse? =
Yes! You can use any form from every newsletter service since you can insert HTML code into the "wBounce content" text field. Simply copy the form code that's provided by MailChimp (or any other newsletter service) into the "wBounce content" text field.
Additionally, you can add CSS using the "Custom CSS" text field.
= How to use MailPoet, SendPress Newsletters and other plugins with wBounce? =
You can actually insert any shortcode that is provided by other plugins, such as GravityForms or SendPress Newsletters. For example, to use MailPoet with wBounce, simply insert the provided shortcode that contains the form's ID, as follows:
`[wysija_form id="1"]`
By the way, [MailPoet](https://wordpress.org/plugins/wysija-newsletters/) allows to set up autoresponders, so give it a try.
Another well-known newsletter plugin, [SendPress](https://wordpress.org/plugins/sendpress/), offers shortcodes that look like this:
`[sp-form formid=18547]`
Notice: If a plugin or service doesn't offer such a shortcode, you can still insert any HTML code. I’m pretty sure that every useful newsletter service offers at least a piece of HTML code that works with wBounce :-)
= wBounce does not fire, scripts are not loaded or jQuery is loaded too late. What's wrong? =
Probably your theme does not implement the wp_footer() function in the appropriate position, if at all. Always have it just before the closing </body> tag of your theme. [#support](https://wordpress.org/support/topic/plugin-does-not-fire-the-popup?replies=3#post-6530865)
= How to translate popups (using WPML)? =
You must have installed WPML Translation Management. Then you can do the following in the menu:
1) Go to WPML > Translation Management > Multilingual Content Setup > Edit translatable admin strings
2) Context: admin_texts_plugin_wbounce-master > Translate
As soon as you save, the popup will appear in the appropriate language.
(Thanks to Jan Sass for providing this answer.)
= How to use Jetpack's Subscriptions module with wBounce? =
Use Jetpack's shortcode within the wBounce content field:
`[jetpack_subscription_form]`
You can even extend the shortcode using modifiers as [explained by Jetpack](http://jetpack.me/support/subscriptions/).
== Changelog ==
= 1.6.3 =
* New: Disable demo CSS used for exemplary template. This reduces the file size and makes it easier to use custom popup styles.
* Fix: Never display scrollbars for popup underlay.
= 1.6.2.3 =
* Fix: Incorrect cookie expiration date.
= 1.6.2.2 =
* Fix: Change how array is created to work with PHP versions lower than 5.4.
* Fix: Solve JavaScript error that occurred when Google Analytics option was checked.
= 1.6.2 =
* Allow HTML and script tags to be used when using the "total overrides" feature for individual posts.
* Improvements for developers/contributors: Separation of PHP and JavaScript. (There was way to much JS located within one PHP file.) A package.json now defines a set of tools to build JS and SCSS. Use: "npm run watch" and "npm run build".
= 1.6.1.1 =
* Removed minified JavaScript file (which was used in WordPress backend only) because it caused (false) positives in several virus scanners.
= 1.6.1 =
* New: Users can close popup using ESC key.
* New analytics event 'hidden_escape': Triggered when user closes popup using ESC key.
* Fix: Popup triggered by self-acting timer and exit animation was closed immediately when user clicked somewhere before it showed up.
* Fix: 'hidden_outside' analytics event was triggered to often.
= 1.6 =
* New feature: Popup animations. You find them under your styling tab. Merged pull request from @rahilwazir on Github (https://github.com/kevinweber/wbounce/pull/10).
* Allow shortcodes in "Template Total Override".
= 1.5.1.5 =
* Merged pull request from @dima-stefantsov on Github (https://github.com/kevinweber/wbounce/pull/7): wBounce can by default be disabled with post meta flag.
= 1.5.1.4 =
* Fix: Cookie storage didn't work correctly when user has no Google Analytics script on his site but GA event tracking (in plugin settings) is enabled.
= 1.5.1.3 =
* Updated exit popup script and improved self-acting fire.
= 1.5.1.1 =
* Fixed not working meta box besides page/post editor.
= 1.5 =
* HOT! New feature: Template engine to override templates on individual pages/posts. Introducing magic shortcodes.
* Made the plugin translatable. Great thanks to @senlin (https://github.com/senlin) for his contributions via wBounce on Github (https://github.com/kevinweber/wbounce).
= 1.4.0.1 =
* Improved CSS to hide scrollbars in some browsers. Note: To hide scrollbars in all browsers completely, use the following custom CSS: .wbounce-modal .wbounce-modal-sub { overflow: hidden; }
= 1.4 =
* New feature: Event tracking with Google Analytics.
* Extended "Default status" drop-down list with "Fire on posts and pages".
* Added 15% discount code for OptinMonster.
= 1.3.4.5 =
* Fixed not working cookieDomain.
= 1.3.4.4 =
* Fixed not working cookieExpire and cookieDomain.
= 1.3.4.3 =
* CSS fix.
= 1.3.4.2 =
* Fix: Make aggressive mode working as expected.
= 1.3.4 =
* Fix: Make cookie option work with self-acting fire.
= 1.3.3 =
* Fix: Improved self-acting fire. When self-acting fire fired, don't use exit popup again.
* Major CSS update: Removed fix height so that the content determines the modal's height. Default width is still 600px. When the modal's content requires more space than the screen is high, the modal is scrollable. Raised z-index from 1 to 21. Use CSS property "transform" to centre the modal vertically. Added margin to prevent the modal from being overlapped by the admin bar.
* New feature: Load script before footer. Normally, scripts are placed in <head> of the HTML document. If this parameter is true, the script is placed before the </body> end tag. This requires the theme to have the wp_footer() template tag in the appropriate place.
* Improvement: Use not minified JavaScript files when SCRIPT_DEBUG is true (defined in wp-config.php).
* Added version number to scripts.
= 1.3 =
* Renamed functions.php to wbounce.php. (This will cause your WordPress site to automatically deactivate wBounce. So you simply have to activate it again, that’s it.)
* New feature: Self-acting fire (timer). Automatically trigger the popup after a certain time period.
* New feature: Cookie domain.
* New: The cookie is stored for the whole site (and not only for specific pages/posts).
* New feature: Cookie per page. With this option enabled, every page/post gets its own cookie.
* Fix: Added CSS "box-sizing: border-box".
* Fix: Added CSS to make wBounce work with themes that use Bootstrap 3.
= 1.2.1 =
* Fixed broken post view.
= 1.2 =
* Improvement: Added support for shortcodes that are inserted into the "wBounce content" text area.
* New feature: Hesitation. wBounce waits x milliseconds before showing the model when the user's cursor leaves the window.
* Improvement: Only load scripts and CSS when they are actually needed.
* Improvement: Merged CSS from two files into one.
* Fixed "unexpected T_PAAMAYIM_NEKUDOTAYIM".
= 1.1.1 =
* New feature: Deactivate wBounce for pages and posts individually ("wBounce status").
* New feature: Define if wBounce should be fired on posts and/or pages by default.
* New feature: The wBounce status can be seen in an additional column on the overview for posts and pages.
* New feature: Sensitivity.
* New feature: Cookie expiration. wBounce sets a cookie by default to prevent the modal from appearing more than once per user. You can add a cookie expiration (in days) to adjust the time period before the modal will appear again for a user.
* wBounce is ready for WordPress 4.0.
= 1.0 =
* Plugin goes public.
* First available features: Admin panel to customise settings. Insert content/code + example template. Test mode. Aggressive mode. Timer. Custom CSS.
== Upgrade Notice ==
= 1.2.2 =
* Renamed functions.php to wbounce.php. This will cause your WordPress site to automatically deactivate wBounce. So you simply have to activate it again, that’s it.
= 1.0 =
* Plugin goes public.
== Screenshots ==
1. Screenshot of a site that uses wBounce.
2. Admin panel tab "content".
3. Admin panel tab "options".
4. Meta box besides post editor (v1.1).
5. Post column displays status (v1.1).