GitHub Access Token became invalid

It seems like the GitHub access token used for retrieving details about this repository from GitHub became invalid. This might prevent certain types of inspections from being run (in particular, everything related to pull requests).
Please ask an admin of your repository to re-new the access token on this website.
Completed
Push — master ( fc808e...eee123 )
by Christian
10s
created

Button::render()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 19
Code Lines 14

Duplication

Lines 0
Ratio 0 %

Importance

Changes 0
Metric Value
cc 1
eloc 14
c 0
b 0
f 0
nc 1
nop 8
dl 0
loc 19
rs 9.7998

How to fix   Many Parameters   

Many Parameters

Methods with many parameters are not only hard to understand, but their parameters also often become inconsistent when you need more, or different data.

There are several approaches to avoid long parameter lists:

1
<?php
0 ignored issues
show
introduced by
Class file names should be based on the class name with "class-" prepended. Expected class-button.php, but found button.php.
Loading history...
2
/**
0 ignored issues
show
Coding Style introduced by
Missing short description in doc comment
Loading history...
3
 * @author    Podlove <[email protected]>
4
 * @copyright Copyright (c) 2014-2018, Podlove
5
 * @license   https://github.com/podlove/podlove-subscribe-button-wp-plugin/blob/master/LICENSE MIT
6
 * @package   Podlove\PodloveSubscribeButton
7
 */
8
9
namespace PodloveSubscribeButton\Model;
10
11
class Button extends Base {
0 ignored issues
show
Coding Style Documentation introduced by
Missing doc comment for class Button
Loading history...
12
13
	public static $properties = array(
0 ignored issues
show
Coding Style Documentation introduced by
Missing member variable doc comment
Loading history...
14
		// $property => $default value
0 ignored issues
show
Unused Code Comprehensibility introduced by
43% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
15
		'size'      => 'big',
16
		'color'     => '#599677',
17
		'autowidth' => 'on',
18
		'style'     => 'filled',
19
		'format'    => 'rectangle',
20
		'hide'      => 'false',
21
		'buttonid'  => '',
22
		// Note: the fields 'language' and 'json-data' cannot be set here (No function call allowed within class variables)
0 ignored issues
show
Coding Style introduced by
Inline comments must end in full-stops, exclamation marks, or question marks
Loading history...
23
	);
24
25
	public static $style = array(
0 ignored issues
show
Coding Style Documentation introduced by
Missing member variable doc comment
Loading history...
26
		'filled'    => 'Filled',
27
		'outline'   => 'Outline',
28
		'frameless' => 'Frameless',
29
	);
30
31
	public static $format = array(
0 ignored issues
show
Coding Style Documentation introduced by
Missing member variable doc comment
Loading history...
32
		'rectangle' => 'Rectangle',
33
		'square'    => 'Square',
34
		'cover'     => 'Cover',
35
	);
36
37
	public static $width = array(
0 ignored issues
show
Coding Style Documentation introduced by
Missing member variable doc comment
Loading history...
38
		'on'  => 'Yes',
39
		'off' => 'No',
40
	);
41
42
	public static $size = array(
0 ignored issues
show
Coding Style Documentation introduced by
Missing member variable doc comment
Loading history...
43
		'small'  => 'Small',
44
		'medium' => 'Medium',
45
		'big'    => 'Big',
46
	);
47
48
49
	/**
50
	 * Fetches a Button or Network Button with a specific name
51
	 * @param  string $name
0 ignored issues
show
Coding Style introduced by
There must be exactly one blank line before the tags in a doc comment
Loading history...
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
52
	 * @return object||FALSE
0 ignored issues
show
Documentation Bug introduced by
The doc comment object||FALSE at position 2 could not be parsed: Unknown type name '|' at position 2 in object||FALSE.
Loading history...
53
	 */
54
	public static function get_button_by_name( $name ) {
0 ignored issues
show
Coding Style introduced by
Method name "Button::get_button_by_name" is not in camel caps format
Loading history...
55
		if ( $button = \PodloveSubscribeButton\Model\Button::find_one_by_property( 'name', $name ) ) {
0 ignored issues
show
introduced by
Variable assignment found within a condition. Did you mean to do a comparison?
Loading history...
Coding Style introduced by
Assignments must be the first block of code on a line
Loading history...
Coding Style introduced by
As per coding style, self should be used for accessing local static members.

This check looks for accesses to local static members using the fully qualified name instead of self::.

<?php

class Certificate {
    const TRIPLEDES_CBC = 'ASDFGHJKL';

    private $key;

    public function __construct()
    {
        $this->key = Certificate::TRIPLEDES_CBC;
    }
}

While this is perfectly valid, the fully qualified name of Certificate::TRIPLEDES_CBC could just as well be replaced by self::TRIPLEDES_CBC. Referencing local members with self:: assured the access will still work when the class is renamed, makes it perfectly clear that the member is in fact local and will usually be shorter.

Loading history...
56
			return $button;
57
		}
58
59
		if ( $network_button = \PodloveSubscribeButton\Model\NetworkButton::find_one_by_property( 'name', $name ) ) {
0 ignored issues
show
introduced by
Variable assignment found within a condition. Did you mean to do a comparison?
Loading history...
Coding Style introduced by
Assignments must be the first block of code on a line
Loading history...
60
			$network_button->id = $network_button->id . 'N';
61
			return $network_button;
62
		}
63
64
		return false;
65
66
	}
67
68
	/**
0 ignored issues
show
Coding Style Documentation introduced by
Doc comment for parameter "$settings" missing
Loading history...
69
	 * Returns either global buttons settings or the default settings
70
	 * @param  array
0 ignored issues
show
Coding Style introduced by
There must be exactly one blank line before the tags in a doc comment
Loading history...
Coding Style introduced by
Missing parameter name
Loading history...
71
	 * @return array
72
	 */
73
	public static function get_global_setting_with_fallback( $settings = array() ) {
0 ignored issues
show
Coding Style introduced by
Method name "Button::get_global_setting_with_fallback" is not in camel caps format
Loading history...
74
		foreach ( self::$properties as $property => $default ) {
75
			$settings[ $property ] = ( get_option( 'podlove_subscribe_button_default_' . $property ) ? get_option( 'podlove_subscribe_button_default_' . $property ) : $default );
76
		}
77
78
		return $settings;
79
	}
0 ignored issues
show
Coding Style introduced by
Expected 1 blank line before closing function brace; 0 found
Loading history...
80
81
	/**
0 ignored issues
show
Coding Style Documentation introduced by
Doc comment for parameter "$language" missing
Loading history...
82
	 * Gathers all information and renders the Subscribe button.
83
	 * @param  string  $size
0 ignored issues
show
Coding Style introduced by
There must be exactly one blank line before the tags in a doc comment
Loading history...
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
84
	 * @param  string  $autowidth
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
85
	 * @param  string  $style
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
86
	 * @param  string  $format
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
87
	 * @param  string  $color
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
88
	 * @param  boolean $hide
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
89
	 * @param  boolean $buttonid
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
90
	 * @return string
91
	 */
92
	public function render( $size = 'big', $autowidth = 'on', $style = 'filled', $format = 'rectangle', $color = '#599677', $hide = false, $buttonid = false, $language = 'en' ) {
93
		$button_styling = array_merge(
94
			$this->get_button_styling( $size, $autowidth, $style, $format, $color ),
95
			array(
96
				'hide'     => $hide,
97
				'buttonid' => $buttonid,
98
				'language' => $language,
99
			)
100
		);
101
102
		return $this->provide_button_html(
103
			array(
104
				'title'       => $this->title,
0 ignored issues
show
Bug Best Practice introduced by
The property title does not exist on PodloveSubscribeButton\Model\Button. Since you implemented __get, consider adding a @property annotation.
Loading history...
105
				'subtitle'    => $this->subtitle,
0 ignored issues
show
Bug Best Practice introduced by
The property subtitle does not exist on PodloveSubscribeButton\Model\Button. Since you implemented __get, consider adding a @property annotation.
Loading history...
106
				'description' => $this->description,
0 ignored issues
show
Bug Best Practice introduced by
The property description does not exist on PodloveSubscribeButton\Model\Button. Since you implemented __get, consider adding a @property annotation.
Loading history...
107
				'cover'       => $this->cover,
0 ignored issues
show
Bug Best Practice introduced by
The property cover does not exist on PodloveSubscribeButton\Model\Button. Since you implemented __get, consider adding a @property annotation.
Loading history...
108
				'feeds'       => $this->get_feeds_as_array( $this->feeds ),
0 ignored issues
show
Bug Best Practice introduced by
The property feeds does not exist on PodloveSubscribeButton\Model\Button. Since you implemented __get, consider adding a @property annotation.
Loading history...
109
			),
110
			$button_styling
111
		);
112
113
	}
114
115
	/**
0 ignored issues
show
Coding Style Documentation introduced by
Doc comment for parameter "$feeds" missing
Loading history...
116
	 * Provides the feed as an array in the required format
117
	 * @return array
0 ignored issues
show
Coding Style introduced by
There must be exactly one blank line before the tags in a doc comment
Loading history...
118
	 */
119
	private function get_feeds_as_array( $feeds = array() ) {
0 ignored issues
show
Coding Style introduced by
Method name "Button::get_feeds_as_array" is not in camel caps format
Loading history...
120
		foreach ( $feeds as $feed ) {
121
			if ( isset( \PodloveSubscribeButton\MediaTypes::$audio[ $feed[ 'format' ] ][ 'extension' ] ) ) {
0 ignored issues
show
introduced by
Array keys must NOT be surrounded by spaces if they only contain a string or an integer.
Loading history...
122
				$new_feed = array(
123
					'type'    => 'audio',
124
					'format'  => \PodloveSubscribeButton\MediaTypes::$audio[ $feed['format'] ]['extension'],
125
					'url'     => $feed['url'],
126
					'variant' => 'high',
127
				);
128
129
				if ( isset( $feed[ 'itunesfeedid' ] ) && $feed[ 'itunesfeedid' ] > 0 ) {
0 ignored issues
show
introduced by
Array keys must NOT be surrounded by spaces if they only contain a string or an integer.
Loading history...
130
					$new_feed['directory-url-itunes'] = "https://itunes.apple.com/podcast/id" . $feed['itunesfeedid'];
0 ignored issues
show
Coding Style Comprehensibility introduced by
The string literal https://itunes.apple.com/podcast/id does not require double quotes, as per coding-style, please use single quotes.

PHP provides two ways to mark string literals. Either with single quotes 'literal' or with double quotes "literal". The difference between these is that string literals in double quotes may contain variables with are evaluated at run-time as well as escape sequences.

String literals in single quotes on the other hand are evaluated very literally and the only two characters that needs escaping in the literal are the single quote itself (\') and the backslash (\\). Every other character is displayed as is.

Double quoted string literals may contain other variables or more complex escape sequences.

<?php

$singleQuoted = 'Value';
$doubleQuoted = "\tSingle is $singleQuoted";

print $doubleQuoted;

will print an indented: Single is Value

If your string literal does not contain variables or escape sequences, it should be defined using single quotes to make that fact clear.

For more information on PHP string literals and available escape sequences see the PHP core documentation.

Loading history...
131
				}
132
133
				$feeds[] = $new_feed;
134
135
			}
136
		}
137
138
		return $feeds;
139
140
	}
141
142
	/**
143
	 * Provides the HTML source of the Subscribe Button
144
	 * @param  array $podcast_data
0 ignored issues
show
Coding Style introduced by
There must be exactly one blank line before the tags in a doc comment
Loading history...
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
Coding Style introduced by
Expected 2 spaces after parameter type; 1 found
Loading history...
145
	 * @param  array $button_styling
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
Coding Style introduced by
Expected 2 spaces after parameter type; 1 found
Loading history...
146
	 * @param  string $data_attributes
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
147
	 * @return string
148
	 */
149
	private function provide_button_html( $podcast_data, $button_styling, $data_attributes = "" ) {
0 ignored issues
show
Coding Style introduced by
Method name "Button::provide_button_html" is not in camel caps format
Loading history...
Coding Style Comprehensibility introduced by
The string literal does not require double quotes, as per coding-style, please use single quotes.

PHP provides two ways to mark string literals. Either with single quotes 'literal' or with double quotes "literal". The difference between these is that string literals in double quotes may contain variables with are evaluated at run-time as well as escape sequences.

String literals in single quotes on the other hand are evaluated very literally and the only two characters that needs escaping in the literal are the single quote itself (\') and the backslash (\\). Every other character is displayed as is.

Double quoted string literals may contain other variables or more complex escape sequences.

<?php

$singleQuoted = 'Value';
$doubleQuoted = "\tSingle is $singleQuoted";

print $doubleQuoted;

will print an indented: Single is Value

If your string literal does not contain variables or escape sequences, it should be defined using single quotes to make that fact clear.

For more information on PHP string literals and available escape sequences see the PHP core documentation.

Loading history...
150
		// Create data attributes for Button
0 ignored issues
show
Coding Style introduced by
Inline comments must end in full-stops, exclamation marks, or question marks
Loading history...
151
		foreach ( $button_styling as $attribute => $value ) {
152
			$data_attributes .= 'data-' . $attribute . '="' . $value . '" ';
153
		}
154
155
		return"
0 ignored issues
show
Coding Style introduced by
Language constructs must be followed by a single space; expected "return "
" but found "return"
"
Loading history...
Coding Style Comprehensibility introduced by
The string literal \n <script>\n podcastData does not require double quotes, as per coding-style, please use single quotes.

PHP provides two ways to mark string literals. Either with single quotes 'literal' or with double quotes "literal". The difference between these is that string literals in double quotes may contain variables with are evaluated at run-time as well as escape sequences.

String literals in single quotes on the other hand are evaluated very literally and the only two characters that needs escaping in the literal are the single quote itself (\') and the backslash (\\). Every other character is displayed as is.

Double quoted string literals may contain other variables or more complex escape sequences.

<?php

$singleQuoted = 'Value';
$doubleQuoted = "\tSingle is $singleQuoted";

print $doubleQuoted;

will print an indented: Single is Value

If your string literal does not contain variables or escape sequences, it should be defined using single quotes to make that fact clear.

For more information on PHP string literals and available escape sequences see the PHP core documentation.

Loading history...
156
			<script>
157
				podcastData".$this->id . " = " . json_encode( $podcast_data ) . "
0 ignored issues
show
Coding Style introduced by
Concat operator must be surrounded by a single space
Loading history...
Coding Style Comprehensibility introduced by
The string literal = does not require double quotes, as per coding-style, please use single quotes.

PHP provides two ways to mark string literals. Either with single quotes 'literal' or with double quotes "literal". The difference between these is that string literals in double quotes may contain variables with are evaluated at run-time as well as escape sequences.

String literals in single quotes on the other hand are evaluated very literally and the only two characters that needs escaping in the literal are the single quote itself (\') and the backslash (\\). Every other character is displayed as is.

Double quoted string literals may contain other variables or more complex escape sequences.

<?php

$singleQuoted = 'Value';
$doubleQuoted = "\tSingle is $singleQuoted";

print $doubleQuoted;

will print an indented: Single is Value

If your string literal does not contain variables or escape sequences, it should be defined using single quotes to make that fact clear.

For more information on PHP string literals and available escape sequences see the PHP core documentation.

Loading history...
introduced by
json_encode() is discouraged. Use wp_json_encode() instead.
Loading history...
Coding Style Comprehensibility introduced by
The string literal \n </script>\n <scri...n/javascripts/app.js\" does not require double quotes, as per coding-style, please use single quotes.

PHP provides two ways to mark string literals. Either with single quotes 'literal' or with double quotes "literal". The difference between these is that string literals in double quotes may contain variables with are evaluated at run-time as well as escape sequences.

String literals in single quotes on the other hand are evaluated very literally and the only two characters that needs escaping in the literal are the single quote itself (\') and the backslash (\\). Every other character is displayed as is.

Double quoted string literals may contain other variables or more complex escape sequences.

<?php

$singleQuoted = 'Value';
$doubleQuoted = "\tSingle is $singleQuoted";

print $doubleQuoted;

will print an indented: Single is Value

If your string literal does not contain variables or escape sequences, it should be defined using single quotes to make that fact clear.

For more information on PHP string literals and available escape sequences see the PHP core documentation.

Loading history...
158
			</script>
159
			<script 
160
				class=\"podlove-subscribe-button\" 
161
				src=\"https://cdn.podlove.org/subscribe-button/javascripts/app.js\" " . $data_attributes . ">
0 ignored issues
show
Coding Style Comprehensibility introduced by
The string literal >\n </script>\n does not require double quotes, as per coding-style, please use single quotes.

PHP provides two ways to mark string literals. Either with single quotes 'literal' or with double quotes "literal". The difference between these is that string literals in double quotes may contain variables with are evaluated at run-time as well as escape sequences.

String literals in single quotes on the other hand are evaluated very literally and the only two characters that needs escaping in the literal are the single quote itself (\') and the backslash (\\). Every other character is displayed as is.

Double quoted string literals may contain other variables or more complex escape sequences.

<?php

$singleQuoted = 'Value';
$doubleQuoted = "\tSingle is $singleQuoted";

print $doubleQuoted;

will print an indented: Single is Value

If your string literal does not contain variables or escape sequences, it should be defined using single quotes to make that fact clear.

For more information on PHP string literals and available escape sequences see the PHP core documentation.

Loading history...
162
			</script>
163
		";
164
165
	}
166
167
	/**
168
	 * Returns an array with either the set or default values
169
	 * @param  string $size
0 ignored issues
show
Coding Style introduced by
There must be exactly one blank line before the tags in a doc comment
Loading history...
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
170
	 * @param  string $autowidth
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
171
	 * @param  string $style
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
172
	 * @param  string $format
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
173
	 * @param  string $color
0 ignored issues
show
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
174
	 * @return array
175
	 */
176
	public function get_button_styling( $size, $autowidth, $style, $format, $color ) {
0 ignored issues
show
Coding Style introduced by
Method name "Button::get_button_styling" is not in camel caps format
Loading history...
177
178
		return array(
179
				// $attribute => $value
0 ignored issues
show
Unused Code Comprehensibility introduced by
60% of this comment could be valid code. Did you maybe forget this after debugging?

Sometimes obsolete code just ends up commented out instead of removed. In this case it is better to remove the code once you have checked you do not need it.

The code might also have been commented out for debugging purposes. In this case it is vital that someone uncomments it again or your project may behave in very unexpected ways in production.

This check looks for comments that seem to be mostly valid code and reports them.

Loading history...
introduced by
Array item not aligned correctly; expected 12 spaces but found 16
Loading history...
180
				'size' => ( $size == 'default' ? get_option( 'podlove_subscribe_button_default_size', $size ) : $size )
0 ignored issues
show
Bug introduced by
Are you sure $size == 'default' ? get...t_size', $size) : $size of type mixed|false|string can be used in concatenation? ( Ignorable by Annotation )

If this is a false-positive, you can also ignore this issue in your code via the ignore-type  annotation

180
				'size' => ( /** @scrutinizer ignore-type */ $size == 'default' ? get_option( 'podlove_subscribe_button_default_size', $size ) : $size )
Loading history...
introduced by
Multi-line array item not aligned correctly; expected 12 spaces, but found 16
Loading history...
introduced by
Array double arrow not aligned correctly; expected 6 space(s) between "'size'" and double arrow, but found 1.
Loading history...
introduced by
Found: ==. Use strict comparisons (=== or !==).
Loading history...
introduced by
Use Yoda Condition checks, you must.
Loading history...
181
			 	. self::interpret_autowidth_attribute( $autowidth ),
182
				'style' => ( $style == 'default' ? get_option( 'podlove_subscribe_button_default_style', $style ) : $style ),
0 ignored issues
show
introduced by
Array item not aligned correctly; expected 12 spaces but found 16
Loading history...
introduced by
Array double arrow not aligned correctly; expected 5 space(s) between "'style'" and double arrow, but found 1.
Loading history...
introduced by
Found: ==. Use strict comparisons (=== or !==).
Loading history...
introduced by
Use Yoda Condition checks, you must.
Loading history...
183
				'format' => ( $format == 'default' ? get_option( 'podlove_subscribe_button_default_format', $format ) : $format ),
0 ignored issues
show
introduced by
Array item not aligned correctly; expected 12 spaces but found 16
Loading history...
introduced by
Array double arrow not aligned correctly; expected 4 space(s) between "'format'" and double arrow, but found 1.
Loading history...
introduced by
Found: ==. Use strict comparisons (=== or !==).
Loading history...
introduced by
Use Yoda Condition checks, you must.
Loading history...
184
				'color' => ( isset( $color ) ? $color : get_option( 'podlove_subscribe_button_default_color', $color ) ),
0 ignored issues
show
introduced by
Array item not aligned correctly; expected 12 spaces but found 16
Loading history...
introduced by
Array double arrow not aligned correctly; expected 5 space(s) between "'color'" and double arrow, but found 1.
Loading history...
185
				'json-data' => 'podcastData' . $this->id
0 ignored issues
show
introduced by
Array item not aligned correctly; expected 12 spaces but found 16
Loading history...
introduced by
Each array item in a multi-line array declaration must end in a comma
Loading history...
186
			);
0 ignored issues
show
introduced by
Array closer not aligned correctly; expected 8 space(s) but found 12
Loading history...
187
188
	}
189
190
	/**
191
	 * Helper function to interpret the given $autowidth value correctly
192
	 * @param  string $autowidth
0 ignored issues
show
Coding Style introduced by
There must be exactly one blank line before the tags in a doc comment
Loading history...
Coding Style Documentation introduced by
Missing parameter comment
Loading history...
193
	 * @return string
194
	 */
195
	private static function interpret_autowidth_attribute( $autowidth ) {
0 ignored issues
show
Coding Style introduced by
Method name "Button::interpret_autowidth_attribute" is not in camel caps format
Loading history...
196
		if ( $autowidth == 'default' && get_option( 'podlove_subscribe_button_default_autowidth' ) !== 'on' )
0 ignored issues
show
Coding Style Best Practice introduced by
It is generally a best practice to always use braces with control structures.

Adding braces to control structures avoids accidental mistakes as your code changes:

// Without braces (not recommended)
if (true)
    doSomething();

// Recommended
if (true) {
    doSomething();
}
Loading history...
introduced by
Found: ==. Use strict comparisons (=== or !==).
Loading history...
introduced by
Use Yoda Condition checks, you must.
Loading history...
197
			return '';
198
199
		if ( $autowidth !== 'default' && $autowidth !== 'on' )
0 ignored issues
show
Coding Style Best Practice introduced by
It is generally a best practice to always use braces with control structures.

Adding braces to control structures avoids accidental mistakes as your code changes:

// Without braces (not recommended)
if (true)
    doSomething();

// Recommended
if (true) {
    doSomething();
}
Loading history...
introduced by
Use Yoda Condition checks, you must.
Loading history...
200
			return '';
201
202
		return ' auto';
203
204
	}
205
206
} // END class
207
208
Button::property( 'id', 'INT NOT NULL AUTO_INCREMENT PRIMARY KEY' );
209
Button::property( 'name', 'VARCHAR(255)' );
210
Button::property( 'title', 'VARCHAR(255)' );
211
Button::property( 'subtitle', 'VARCHAR(255)' );
212
Button::property( 'description', 'TEXT' );
213
Button::property( 'cover', 'VARCHAR(255)' );
214
Button::property( 'feeds', 'TEXT' );
215