Changeset 1704040
- Timestamp:
- 07/27/2017 09:02:16 PM (9 years ago)
- Location:
- futusign/trunk
- Files:
-
- 4 edited
-
futusign.php (modified) (1 diff)
-
includes/class-futusign.php (modified) (1 diff)
-
readme.md (modified) (3 diffs)
-
readme.txt (modified) (13 diffs)
Legend:
- Unmodified
- Added
- Removed
-
futusign/trunk/futusign.php
r1703962 r1704040 11 11 * Plugin URI: https://github.com/larkintuckerllc/futusign 12 12 * Description: Manage and display digital signage content 13 * Version: 2.5. 113 * Version: 2.5.3 14 14 * Author: John Tucker 15 15 * Author URI: https://github.com/larkintuckerllc -
futusign/trunk/includes/class-futusign.php
r1703962 r1704040 93 93 public function __construct() { 94 94 $this->plugin_name = 'futusign'; 95 $this->version = '2.5. 1';95 $this->version = '2.5.3'; 96 96 $this->load_dependencies(); 97 97 $this->set_locale(); -
futusign/trunk/readme.md
r1703962 r1704040 13 13 === 14 14 15 Simply put... WordPress is one of the best content managements systems 16 available today. Digital signage management is a content management 17 problem. 15 Simply put... *WordPress* is one of the best content managements systems available today. Digital signage management is a content management problem. As for *futusign* itself, hearing how others are using it is the best way to understand the possibilities. 18 16 19 As for futusign itself, hearing how others are using futusign is the 20 best way to understand the possibilities. 21 22 The [Digital Signage Case Study: Warrington College of Business]( https://www.futusign.com/stories/digital-signage-case-study-warrington/) 23 illustrates a medium-sized futusign deployment at an educational institution. 17 The *[Digital Signage Case Study: Warrington College of Business]( https://www.futusign.com/stories/digital-signage-case-study-warrington/)* illustrates a medium-sized futusign deployment at an educational institution. 24 18 25 19 Installation 26 20 ==== 27 21 28 Install and activate the *futusign* plugin via the WordPress *Plugins* admin22 Install and activate the *futusign* plugin via the *WordPress Plugins* admin 29 23 screen. 30 24 31 25 Usage 32 26 ==== 33 Using your favorite presentation tool, e.g., PowerPoint, create a slide 34 show with the same resolution and aspect ratio of the target display screen; 35 for example 1920px by 1080px for an landscape HD screen. Save it as a series of 36 images. 27 Using your favorite presentation tool, e.g., *PowerPoint*, create a slide show with the same resolution and aspect ratio of the target display screen; for example 1920px by 1080px for an landscape HD screen. Save it as a series of images. 37 28 38 From the WordPressadministrative screens.29 From the *WordPress* administrative screens. 39 30 40 31 1. Add a new *Image* (or multiple) from the admin menu; uploading the … … 49 40 When editing a screen; a list of the currently playing media is provided. 50 41 51 To create a digital sign, connect a television to a computer with Chrome 52 browser and have it load the *Screen's* URL. The loaded web application will 53 check every hour (configurable) to automatically apply changes made on the 54 admin screens. 42 To create a digital sign, connect a television to a computer with *Chrome* browser and have it load the *Screen's* URL. The loaded web application will check every hour (configurable) to automatically apply changes made on the admin screens. 55 43 56 44 Additional information available at [www.futusign.com](https://www.futusign.com/). … … 58 46 Contributing 59 47 ==== 60 Submit bug or enhancement requests using the GitHubissues feature.48 Submit bug or enhancement requests using the *GitHub* issues feature. 61 49 62 50 Contact -
futusign/trunk/readme.txt
r1703962 r1704040 4 4 Requires at least: 4.3 5 5 Tested up to: 4.8 6 Stable tag: 2.5. 16 Stable tag: 2.5.3 7 7 License: GPLv2 or later 8 8 License URI: https://www.gnu.org/licenses/gpl.html … … 12 12 == Description == 13 13 14 Simply put... WordPress is one of the best content managements systems 15 available today. Digital signage management is a content management 16 problem. 17 18 As for futusign itself, hearing how others are using futusign is the 19 best way to understand the possibilities. 20 21 The [Digital Signage Case Study: Warrington College of Business]( https://www.futusign.com/stories/digital-signage-case-study-warrington/) 22 illustrates a medium-sized futusign deployment at an educational institution. 14 Simply put... *WordPress* is one of the best content managements systems available today. Digital signage management is a content management problem. As for *futusign* itself, hearing how others are using it is the best way to understand the possibilities. 15 16 The *[Digital Signage Case Study: Warrington College of Business]( https://www.futusign.com/stories/digital-signage-case-study-warrington/)* illustrates a medium-sized futusign deployment at an educational institution. 23 17 24 18 == Installation == 25 19 26 Install and activate the *futusign* plugin via the WordPress *Plugins* admin 27 screen. 20 Install and activate the *futusign* plugin via the *WordPress Plugins* admin screen. 28 21 29 22 == Frequently Asked Questions == … … 31 24 = How do I use futusign? = 32 25 33 Using your favorite presentation tool, e.g., *PowerPoint*, create a slide show with 34 the same resolution and aspect ratio of the target display screen; for example 35 1920px by 1080px for an landscape HD screen. Save it as a series of images. 26 Using your favorite presentation tool, e.g., *PowerPoint*, create a slide show with the same resolution and aspect ratio of the target display screen; for example 1920px by 1080px for an landscape HD screen. Save it as a series of images. 36 27 37 28 From the *WordPress* administrative screens. … … 47 38 When editing a screen; a list of the currently playing media is provided. 48 39 49 To create a digital sign, connect a television to a computer with Chrome 50 browser and have it load the *Screen's* URL. The loaded web application will 51 check every hour (configurable) to automatically apply changes made on the 52 admin screens. 40 To create a digital sign, connect a television to a computer with *Chrome* browser and have it load the *Screen's* URL. The loaded web application will check every hour (configurable) to automatically apply changes made on the admin screens. 53 41 54 42 Additional information available at [www.futusign.com](https://www.futusign.com/). 55 43 56 44 == Changelog == 45 46 = 2.5.3 = 47 48 Continuing to rework documentation. 49 50 = 2.5.2 = 51 52 Fix word-wrapping in documentation. 57 53 58 54 = 2.5.1 = … … 97 93 = 2.2.5 = 98 94 99 Fix bug with relative require causing endpoint to fail; thus 100 the screen player to fail. 95 Fix bug with relative require causing endpoint to fail; thus the screen player to fail. 101 96 102 97 = 2.2.4 = 103 98 104 Added debugging points to find error in endpoint API for a 105 customer. 99 Added debugging points to find error in endpoint API for a customer. 106 100 107 101 = 2.2.3 = 108 102 109 Bug fix: Hopefully final attempt to fix problem during upgrade; 110 current work-around is to deactivate and activate the plugin. 103 Bug fix: Hopefully final attempt to fix problem during upgrade; current work-around is to deactivate and activate the plugin. 111 104 112 105 = 2.2.2 = 113 106 114 Bug fix: Try to fix problem during upgrade; current work-around is to 115 deactivate and activate the plugin. 107 Bug fix: Try to fix problem during upgrade; current work-around is to deactivate and activate the plugin. 116 108 117 109 = 2.2.1 = 118 110 119 Bug fix: On upgrade to 2.2.0, the plugin needed to be reactivated 120 before screens would play again. 111 Bug fix: On upgrade to 2.2.0, the plugin needed to be reactivated before screens would play again. 121 112 122 113 = 2.2.0 = … … 132 123 = 2.1.1 = 133 124 134 Band-aid fix; changed polling from once per minute to once per hour. 135 Eating up too much CPU cyles on WordPress instance. Future will default 136 to an hour but let you change. 125 Band-aid fix; changed polling from once per minute to once per hour. Eating up too much CPU cyles on WordPress instance. Future will default to an hour but let you change. 137 126 138 127 = 2.1.0 = 139 128 140 Enhancement: Updated to support Media Decks commercial feature; replacement 141 for Slide Decks. 129 Enhancement: Updated to support Media Decks commercial feature; replacement for Slide Decks. 142 130 143 131 = 2.0.0 = 144 132 145 Slide Decks are now deprecated and will be removed in a future version; 146 primarily due to unresolvable issues with the PDF rendering library. 147 148 Images are now included in the core futusign plugin; also replaces Slide 149 Decks in offline behavior. 133 Slide Decks are now deprecated and will be removed in a future version; primarily due to unresolvable issues with the PDF rendering library. 134 135 Images are now included in the core futusign plugin; also replaces Slide Decks in offline behavior. 150 136 151 137 Media play alphabetically by title. … … 171 157 = 1.4.1 = 172 158 173 Bug fix; continue showing spinner until next media plays. Manifested itself 174 with futusign Web plugin (in development). 159 Bug fix; continue showing spinner until next media plays. Manifested itself with futusign Web plugin (in development). 175 160 176 161 = 1.4.0 = … … 178 163 Bug fix; slow memory leak when playing Slide Decks. 179 164 180 Bug fix; with futusign Overlay, not removing widgets when removed 181 overlay from screen or delete overlay entirely. 165 Bug fix; with futusign Overlay, not removing widgets when removed overlay from screen or delete overlay entirely. 182 166 183 167 Refactor player; Replace fade with spinner (when required). … … 193 177 = 1.2.3 = 194 178 195 Security hardening of the PHP code; tests to ensure run through 196 WordPress. 179 Security hardening of the PHP code; tests to ensure run through WordPress. 197 180 198 181 = 1.2.2 = 199 182 200 PDF viewer delay from 1 sec to 2 sec; allow smoother fade in. 201 Fix bug in offline mode where it doubled up on the last slide. 183 PDF viewer delay from 1 sec to 2 sec; allow smoother fade in. Fix bug in offline mode where it doubled up on the last slide. 202 184 203 185 = 1.2.1 = … … 215 197 = 1.0.0 = 216 198 217 Add support for offline operation; play first Slide Deck 218 in subscribed Playlist. 199 Add support for offline operation; play first Slide Deck in subscribed Playlist. 219 200 220 201 Add support for automatic updates on plugin update. … … 228 209 Cosmetic custom post type icons. 229 210 230 Player upgrade to support additional media; image and YouTube video 231 provided by future WordPress plugins. 211 Player upgrade to support additional media; image and YouTube video provided by future WordPress plugins. 232 212 233 213 = 0.3.5 = … … 235 215 Minor code cleanup in screen web application. 236 216 237 Add 'key' to Advanced Custom Fields registration to address 238 bug introduced in ACF Pro v5.5.8 (fixed in v5.5.9). 239 Future-proofs code. 217 Add 'key' to Advanced Custom Fields registration to address bug introduced in ACF Pro v5.5.8 (fixed in v5.5.9). Future-proofs code. 240 218 241 219 = 0.3.4 = … … 263 241 = 0.2.2 = 264 242 265 Fix JavaScript player to bust API caching; some hosting service 266 not handling caching right. 243 Fix JavaScript player to bust API caching; some hosting service not handling caching right. 267 244 268 245 = 0.2.1 =
Note: See TracChangeset
for help on using the changeset viewer.