The channel list shortcode displays a single stack of Twitch.tv channels…with style. This is a highly flexible shortcode with a lot of development potential when the options available aren’t enough for your needs.
Pro Upgrade Required
You must have the pro upgrade installed to use this shortcode. The upgrade is a reward for supporting the project – it is not for sale. Read more about TwitchPress Pro and also consider joining the projects Discord server for more information.
If you don’t see an example that suits your needs. Please come to the projects Discord and discuss your project.
List a the giving members of a stream team. The default content for this shortcode is also a stream-team. To replace the default content we need to add the type and team parameters.
When activating the BugNet feature within TwitchPress you may see the following PHP log entry…
PHP Warning: trim() expects parameter 1 to be string, object given in \wp-includes\class-wp-user.php on line 206
This warning begun to appear many weeks before I got around to investigating it. My findings confirm that the core is to blame. A back-trace I setup in class-wp-user.php near line 206 points to the dashboard.
On examining the dashboard source I can confirm that the warning happens within the Recent Comments widget and will not investigate this issue any further without evidence that suggests a cause by TwitchPress.
The professional edition of TwitchPress Beta can be downloaded from Patreon.com and Discord (backers only). The pro edition has changed in ways not everyone will see i.e. the code has evolved while I try different approaches used in the free edition and it should lead to better performance.
The freely downloadable plugin will continue to improve but my work will focus on performance and bugs with very little new features being added unless I’m paid to do so. The free edition will always have basic support with respect to the Twitch.tv and WordPress.org communities.
Request Beta 0.0.3
Already, version 0.0.3 offers something new in the form of a sensible shortcode. The sensibility of this shortcode comes from two factors. The first is that it has been designed in a generic way, where other shortcodes are very close to what has been requested by specific users. The new shortcode taps into an object of many values and makes each value available as an individual output. Rather than a design that includes difficult to customize output i.e. HTML is included that might not suit everyone’s needs.
The second factor relates to the fact that the new shortcode can be used many times on a single page, without making many calls to Twitch API. This is nothing special, I’ve not done anything technically clever and this type of shortcode is a natural approach within a plugin like this. What makes it interesting is how long it has taking for this to be done, simply because I’ve been wrapped up in finishing other things within the project and completing the features I was hired to create.
So now, we’ll begin to see a plugin that adds a wealth of content to pages. This will trickle down to the free edition just a little but the pro edition will offer far more.
Feel free to request 0.0.3 if you ever backed** the project.
* * All funds raised through Patreon.com or donations will be spent on the project and achieving a professional solution that can only be done with funding. This is not for-profit.
Yes, it is easy to upgrade the free-edition from WordPress.org with the professional edition. This does not apply to custom changes to the free core or features added using extensions.
Here are some factors you should know…
The free edition plugin folder is named “channel-solution-for-twitch”
The pro edition folder is named “twitchpress”
Both plugins share the same WordPress options
Both plugins use the same Twitch API credentials
Only the free edition uses extensions
The pro edition replaces extensions with an internal/core approach
In theory, both plugins can be active at the same time, in theory!
Do not use both plugins at the same time!
This FAQ answer is being added while the pro edition is still new. There will likely be scenarios where a feature becomes disabled because the pro edition has expanded and requires more configuration.
There is also a slight possibility that a feature offered in the free edition is no longer the same – through constant updates over a few years. Maybe to a point where a user thinks that the original feature (in free edition) has been removed completely from the professional one. This should never happen and I’d want to rectify the lack of such a feature in my product especially because it would make upgrading appear more difficult than I claim.