Completed
Push — develop ( adcc2c...e29763 )
by Zack
17:41
created

GravityView_Field_FileUpload::__construct()   A

Complexity

Conditions 1
Paths 1

Size

Total Lines 4

Duplication

Lines 0
Ratio 0 %

Code Coverage

Tests 0
CRAP Score 2

Importance

Changes 0
Metric Value
cc 1
nc 1
nop 0
dl 0
loc 4
ccs 0
cts 4
cp 0
crap 2
rs 10
c 0
b 0
f 0
1
<?php
0 ignored issues
show
Coding Style Compatibility introduced by
For compatibility and reusability of your code, PSR1 recommends that a file should introduce either new symbols (like classes, functions, etc.) or have side-effects (like outputting something, or including other files), but not both at the same time. The first symbol is defined on line 8 and the first side effect is on line 374.

The PSR-1: Basic Coding Standard recommends that a file should either introduce new symbols, that is classes, functions, constants or similar, or have side effects. Side effects are anything that executes logic, like for example printing output, changing ini settings or writing to a file.

The idea behind this recommendation is that merely auto-loading a class should not change the state of an application. It also promotes a cleaner style of programming and makes your code less prone to errors, because the logic is not spread out all over the place.

To learn more about the PSR-1, please see the PHP-FIG site on the PSR-1.

Loading history...
2
/**
3
 * @file class-gravityview-field-fileupload.php
4
 * @package GravityView
5
 * @subpackage includes\fields
6
 */
7
8
class GravityView_Field_FileUpload extends GravityView_Field {
9
10
	var $name = 'fileupload';
0 ignored issues
show
Coding Style introduced by
The visibility should be declared for property $name.

The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using

class A {
    var $property;
}

the property is implicitly global.

To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2.

Loading history...
11
12
	var $_gf_field_class_name = 'GF_Field_FileUpload';
0 ignored issues
show
Coding Style introduced by
The visibility should be declared for property $_gf_field_class_name.

The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using

class A {
    var $property;
}

the property is implicitly global.

To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2.

Loading history...
13
14
	var $is_searchable = true;
0 ignored issues
show
Coding Style introduced by
The visibility should be declared for property $is_searchable.

The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using

class A {
    var $property;
}

the property is implicitly global.

To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2.

Loading history...
15
16
	var $search_operators = array( 'contains' );
0 ignored issues
show
Coding Style introduced by
The visibility should be declared for property $search_operators.

The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using

class A {
    var $property;
}

the property is implicitly global.

To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2.

Loading history...
17
18
	var $group = 'advanced';
0 ignored issues
show
Coding Style introduced by
The visibility should be declared for property $group.

The PSR-2 coding standard requires that all properties in a class have their visibility explicitly declared. If you declare a property using

class A {
    var $property;
}

the property is implicitly global.

To learn more about the PSR-2, please see the PHP-FIG site on the PSR-2.

Loading history...
19
20
	public function __construct() {
21
		$this->label = esc_html__( 'File Upload', 'gravityview' );
22
		parent::__construct();
23
	}
24
25
	function field_options( $field_options, $template_id, $field_id, $context, $input_type ) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
26
27
		unset( $field_options['search_filter'] );
28
29
		if( 'edit' === $context ) {
30
			return $field_options;
31
		}
32
33
		$add_options['link_to_file'] = array(
0 ignored issues
show
Coding Style Comprehensibility introduced by
$add_options was never initialized. Although not strictly required by PHP, it is generally a good practice to add $add_options = array(); before regardless.

Adding an explicit array definition is generally preferable to implicit array definition as it guarantees a stable state of the code.

Let’s take a look at an example:

foreach ($collection as $item) {
    $myArray['foo'] = $item->getFoo();

    if ($item->hasBar()) {
        $myArray['bar'] = $item->getBar();
    }

    // do something with $myArray
}

As you can see in this example, the array $myArray is initialized the first time when the foreach loop is entered. You can also see that the value of the bar key is only written conditionally; thus, its value might result from a previous iteration.

This might or might not be intended. To make your intention clear, your code more readible and to avoid accidental bugs, we recommend to add an explicit initialization $myArray = array() either outside or inside the foreach loop.

Loading history...
34
			'type' => 'checkbox',
35
			'label' => __( 'Display as a Link:', 'gravityview' ),
36
			'desc' => __('Display the uploaded files as links, rather than embedded content.', 'gravityview'),
0 ignored issues
show
Coding Style introduced by
Expected 1 spaces after opening bracket; 0 found
Loading history...
Coding Style introduced by
Expected 1 spaces before closing bracket; 0 found
Loading history...
37
			'value' => false,
38
			'merge_tags' => false,
39
		);
40
41
		return $add_options + $field_options;
42
	}
43
44
	/**
45
	 * Trick the GF fileupload field to render with the proper HTML ID to enable the plupload JS to work properly
46
	 *
47
	 * @param array               $form  The Form Object currently being processed.
48
	 * @param string|array        $value The field value. From default/dynamic population, $_POST, or a resumed incomplete submission.
0 ignored issues
show
Bug introduced by
There is no parameter named $value. Was it maybe removed?

This check looks for PHPDoc comments describing methods or function parameters that do not exist on the corresponding method or function.

Consider the following example. The parameter $italy is not defined by the method finale(...).

/**
 * @param array $germany
 * @param array $island
 * @param array $italy
 */
function finale($germany, $island) {
    return "2:1";
}

The most likely cause is that the parameter was removed, but the annotation was not.

Loading history...
49
	 * @param null|array          $entry Null or the Entry Object currently being edited.
50
	 * @param GF_Field_FileUpload $field Gravity Forms field
51
	 *
52
	 * @return string
53
	 */
54 1
	function get_field_input( $form, $field_value, $entry, $field ) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
55
56 1
		$field->_is_entry_detail = true;
57
58 1
		$return = $field->get_field_input( $form, $field_value, $entry );
59
60 1
		return $return;
61
	}
62
63
	/**
64
	 * Return an array of files prepared for output.
65
	 *
66
	 * Processes files by file type and generates unique output for each. Returns array for each file, with the following keys:
67
	 * - `file_path` => The file path of the file, with a line break
68
	 * - `html` => The file output HTML formatted
69
	 *
70
	 * @since  1.2
71
	 * @todo  Support `playlist` shortcode for playlist of video/audio
72
	 * @param  string $value    Field value passed by Gravity Forms. String of file URL, or serialized string of file URL array
73
	 * @param  string $gv_class Field class to add to the output HTML
74
	 *
75
	 * @since 2.0
76
	 * @param \GV\Template_Context The context.
77
	 *
78
	 * @return array           Array of file output, with `file_path` and `html` keys (see comments above)
79
	 */
80 1
	static function get_files_array( $value, $gv_class, $context = null ) {
0 ignored issues
show
Best Practice introduced by
It is generally recommended to explicitly declare the visibility for methods.

Adding explicit visibility (private, protected, or public) is generally recommend to communicate to other developers how, and from where this method is intended to be used.

Loading history...
81
82 1
		if ( $context instanceof \GV\Template_Context ) {
83 1
			$field = $context->field->field;
0 ignored issues
show
Bug introduced by
The property field does not seem to exist in GV\Field.

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
84 1
			$field_settings = $context->field->as_configuration();
85 1
			$entry = $context->entry->as_entry();
86 1
			$field_value = $context->value;
87 1
			global $post;
0 ignored issues
show
Compatibility Best Practice introduced by
Use of global functionality is not recommended; it makes your code harder to test, and less reusable.

Instead of relying on global state, we recommend one of these alternatives:

1. Pass all data via parameters

function myFunction($a, $b) {
    // Do something
}

2. Create a class that maintains your state

class MyClass {
    private $a;
    private $b;

    public function __construct($a, $b) {
        $this->a = $a;
        $this->b = $b;
    }

    public function myFunction() {
        // Do something
    }
}
Loading history...
88 1
			$base_id = $post ? $post->ID : $context->view->ID;
89
90 1
			$is_single = $context->request->is_entry();
91 1
			$lightbox = $context->view->settings->get( 'lightbox', false );
92
93
			/** A compatibility array that's required by some of the deprecated filters. */
94
			$field_compat = array(
95 1
				'form' => $context->source->form,
0 ignored issues
show
Bug introduced by
The property form does not seem to exist in GV\Source.

An attempt at access to an undefined property has been detected. This may either be a typographical error or the property has been renamed but there are still references to its old name.

If you really want to allow access to undefined properties, you can define magic methods to allow access. See the php core documentation on Overloading.

Loading history...
96 1
				'field_id' => $context->field->ID,
97 1
				'field' => $field,
98 1
				'field_settings' => $field_settings,
99 1
				'value' => $field_value,
100 1
				'display_value' => $context->display_value,
101 1
				'format' => 'html',
102 1
				'entry' => $entry,
103 1
				'field_type' => $context->field->type,
0 ignored issues
show
Documentation introduced by
The property type does not exist on object<GV\Field>. Since you implemented __get, maybe consider adding a @property annotation.

Since your code implements the magic getter _get, this function will be called for any read access on an undefined variable. You can add the @property annotation to your class or interface to document the existence of this variable.

<?php

/**
 * @property int $x
 * @property int $y
 * @property string $text
 */
class MyLabel
{
    private $properties;

    private $allowedProperties = array('x', 'y', 'text');

    public function __get($name)
    {
        if (isset($properties[$name]) && in_array($name, $this->allowedProperties)) {
            return $properties[$name];
        } else {
            return null;
        }
    }

    public function __set($name, $value)
    {
        if (in_array($name, $this->allowedProperties)) {
            $properties[$name] = $value;
        } else {
            throw new \LogicException("Property $name is not defined.");
        }
    }

}

If the property has read access only, you can use the @property-read annotation instead.

Of course, you may also just have mistyped another name, in which case you should fix the error.

See also the PhpDoc documentation for @property.

Loading history...
104 1
				'field_path' => $context->template->located_template,
105
			);
106
		} else {
107
108
			_doing_it_wrong( __METHOD__, '2.0', 'Please pass a \GV\Template_Context object as the 3rd parameter' );
109
110
			$gravityview_view = GravityView_View::getInstance();
111
			/** @deprecated path */
112
			$gv_field_array = $gravityview_view->getCurrentField();
113
114
			/** @var GF_Field_FileUpload $field */
115
			$field = \GV\Utils::get( $gv_field_array, 'field' );
116
			$field_settings = \GV\Utils::get( $gv_field_array, 'field_settings' );
117
			$entry = \GV\Utils::get( $gv_field_array, 'entry' );
118
			$field_value = \GV\Utils::get( $gv_field_array, 'value' );
119
			$base_id = null;
120
121
			$is_single = gravityview_get_context() === 'single';
0 ignored issues
show
Deprecated Code introduced by
The function gravityview_get_context() has been deprecated with message: since 2.0.6.2 Use `gravityview()->request`

This function has been deprecated. The supplier of the file has supplied an explanatory message.

The explanatory message should give you some clue as to whether and when the function will be removed from the class and what other function to use instead.

Loading history...
122
			$lightbox = ! empty( $gravityview_view->atts['lightbox'] );
0 ignored issues
show
Documentation introduced by
The property $atts is declared protected in GravityView_View. Since you implemented __get(), maybe consider adding a @property or @property-read annotation. This makes it easier for IDEs to provide auto-completion.

Since your code implements the magic setter _set, this function will be called for any write access on an undefined variable. You can add the @property annotation to your class or interface to document the existence of this variable.

<?php

/**
 * @property int $x
 * @property int $y
 * @property string $text
 */
class MyLabel
{
    private $properties;

    private $allowedProperties = array('x', 'y', 'text');

    public function __get($name)
    {
        if (isset($properties[$name]) && in_array($name, $this->allowedProperties)) {
            return $properties[$name];
        } else {
            return null;
        }
    }

    public function __set($name, $value)
    {
        if (in_array($name, $this->allowedProperties)) {
            $properties[$name] = $value;
        } else {
            throw new \LogicException("Property $name is not defined.");
        }
    }

}

Since the property has write access only, you can use the @property-write annotation instead.

Of course, you may also just have mistyped another name, in which case you should fix the error.

See also the PhpDoc documentation for @property.

Loading history...
123
			$field_compat = $gravityview_view->getCurrentField();
124
		}
125
126 1
		$output_arr = array();
127
128
		// Get an array of file paths for the field.
129 1
		$file_paths = \GV\Utils::get( $field , 'multipleFiles' ) ? json_decode( $value ) : array( $value );
130
131
		// The $value JSON was probably truncated; let's check lead_detail_long.
132 1
		if ( ! is_array( $file_paths ) ) {
133
			$full_value = RGFormsModel::get_lead_field_value( $entry, $field );
134
			$file_paths = json_decode( $full_value );
135
		}
136
137 1
		if ( ! is_array( $file_paths ) ) {
138
			gravityview()->log->error( 'Field does not have a valid image array. JSON decode may have failed.', array( 'data' => array( '$value' => $value, '$field_value' => $field_value ) ) );
139
			return $output_arr;
140
		}
141
142
		// Process each file path
143 1
		foreach( $file_paths as $file_path ) {
144
145
			// If the site is HTTPS, use HTTPS
146 1
			if(function_exists('set_url_scheme')) { $file_path = set_url_scheme( $file_path ); }
0 ignored issues
show
introduced by
No space after opening parenthesis is prohibited
Loading history...
Coding Style introduced by
Expected 1 spaces after opening bracket; 0 found
Loading history...
Coding Style introduced by
Expected 1 spaces before closing bracket; 0 found
Loading history...
introduced by
No space before closing parenthesis is prohibited
Loading history...
147
148
			// This is from Gravity Forms's code
149 1
			$file_path = esc_attr( str_replace( " ", "%20", $file_path ) );
0 ignored issues
show
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...
Coding Style Comprehensibility introduced by
The string literal %20 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
151 1
			$file_path = $field->get_download_url( $file_path );
152
153
			/**
154
			 * @filter `gravityview/fields/fileupload/file_path` Modify the file path before generating a link to it
155
			 * @since 1.22.3
156
			 * @since 2.0 Added $context parameter
157
			 * @param string $file_path Path to the file uploaded by Gravity Forms
158
			 * @param array  $field_settings Array of GravityView field settings
159
			 * @param \GV\Template_Context $context The context.
160
			 */
161 1
			$file_path = apply_filters( 'gravityview/fields/fileupload/file_path', $file_path, $field_settings, $context );
162
163
			// Get file path information
164 1
			$file_path_info = pathinfo( $file_path );
165
166
			// If the field is set to link to the single entry, link to it.
167 1
			$link = !empty( $field_settings['show_as_link'] ) ? GravityView_API::entry_link( $entry, $field, $base_id ) : $file_path;
0 ignored issues
show
introduced by
Expected 1 space after "!"; 0 found
Loading history...
168
169 1
			$html_format = NULL;
0 ignored issues
show
Coding Style introduced by
TRUE, FALSE and NULL must be lowercase; expected null, but found NULL.
Loading history...
170
171 1
			$disable_lightbox = false;
172
173 1
			$disable_wrapped_link = false;
174
175
			$image_atts = array(
176 1
				'src' => $file_path,
177 1
				'class' => 'gv-image gv-field-id-'.$field_settings['id'],
178 1
				'alt' => $field_settings['label'],
179 1
				'width' => ( $is_single ? NULL : 250 )
0 ignored issues
show
introduced by
Each line in an array declaration must end in a comma
Loading history...
Coding Style introduced by
TRUE, FALSE and NULL must be lowercase; expected null, but found NULL.
Loading history...
180
			);
181
182
			/**
183
			 * Modify the default image attributes for uploaded images
184
			 * @since 2.0
185
			 * @see GravityView_Image For the available attributes
186
			 * @param array $image_atts
187
			 */
188 1
			$image_atts = apply_filters( 'gravityview/fields/fileupload/image_atts', $image_atts );
189
190
			// Is this an image?
191 1
			$image = new GravityView_Image( $image_atts );
192
193 1
			$content = $image->html();
194
195
			// The new default content is the image, if it exists. If not, use the file name as the content.
196 1
			$content = !empty( $content ) ? $content : $file_path_info['basename'];
0 ignored issues
show
introduced by
Expected 1 space after "!"; 0 found
Loading history...
197
198
			// If pathinfo() gave us the extension of the file, run the switch statement using that.
199 1
			$extension = empty( $file_path_info['extension'] ) ? NULL : strtolower( $file_path_info['extension'] );
0 ignored issues
show
Coding Style introduced by
TRUE, FALSE and NULL must be lowercase; expected null, but found NULL.
Loading history...
200
0 ignored issues
show
Coding Style introduced by
Functions must not contain multiple empty lines in a row; found 2 empty lines
Loading history...
201
202
			switch( true ) {
203
204
				// Audio file
205 1
				case in_array( $extension, wp_get_audio_extensions() ):
206
207 1
					$disable_lightbox = true;
208
209 1
					if( shortcode_exists( 'audio' ) ) {
210
211 1
						$disable_wrapped_link = true;
212
213
						/**
214
						 * @filter `gravityview_audio_settings` Modify the settings passed to the `wp_video_shortcode()` function
215
						 * @since  1.2
216
						 * @param array $audio_settings Array with `src` and `class` keys
217
						 * @since 2.0
218
						 * @param \GV\Template_Context $context The context.
219
						 */
220 1
						$audio_settings = apply_filters( 'gravityview_audio_settings', array(
221 1
							'src' => $file_path,
222 1
							'class' => 'wp-audio-shortcode gv-audio gv-field-id-'.$field_settings['id']
0 ignored issues
show
introduced by
Each line in an array declaration must end in a comma
Loading history...
223 1
						), $context );
224
225
						/**
226
						 * Generate the audio shortcode
227
						 * @see http://codex.wordpress.org/Audio_Shortcode
228
						 * @see https://developer.wordpress.org/reference/functions/wp_audio_shortcode/
229
						 */
230 1
						$content = wp_audio_shortcode( $audio_settings );
231
232
					}
233
234 1
					break;
235
236
				// Video file
237 1
				case in_array( $extension, wp_get_video_extensions() ):
238
239
					$disable_lightbox = true;
240
241
					if( shortcode_exists( 'video' ) ) {
242
243
						$disable_wrapped_link = true;
244
245
						/**
246
						 * @filter `gravityview_video_settings` Modify the settings passed to the `wp_video_shortcode()` function
247
						 * @since  1.2
248
						 * @param array $video_settings Array with `src` and `class` keys
249
						 * @since 2.0
250
						 * @param \GV\Template_Context $context The context.
251
						 */
252
						$video_settings = apply_filters( 'gravityview_video_settings', array(
253
							'src' => $file_path,
254
							'class' => 'wp-video-shortcode gv-video gv-field-id-'.$field_settings['id']
0 ignored issues
show
introduced by
Each line in an array declaration must end in a comma
Loading history...
255
						), $context );
256
257
						/**
258
						 * Generate the video shortcode
259
						 * @see http://codex.wordpress.org/Video_Shortcode
260
						 * @see https://developer.wordpress.org/reference/functions/wp_video_shortcode/
261
						 */
262
						$content = wp_video_shortcode( $video_settings );
263
264
					}
265
266
					break;
267
268
				// PDF
269 1
				case $extension === 'pdf':
270
271
					// PDF needs to be displayed in an IFRAME
272
					$link = add_query_arg( array( 'TB_iframe' => 'true' ), $link );
273
274
					break;
275
276
				// if not image, do not set the lightbox (@since 1.5.3)
277 1
				case !in_array( $extension, array( 'jpg', 'jpeg', 'jpe', 'gif', 'png' ) ):
0 ignored issues
show
introduced by
Expected 1 space after "!"; 0 found
Loading history...
278
279
					$disable_lightbox = true;
280
281
					break;
282
283
			}
284
285
			// If using Link to File, override the content.
286
			// (We do this here so that the $disable_lightbox can be set. Yes, there's a little more processing time, but oh well.)
287 1
			if( !empty( $field_settings['link_to_file'] ) ) {
0 ignored issues
show
introduced by
Expected 1 space after "!"; 0 found
Loading history...
288
289
				// Force the content to be the file name
290 1
				$content =  $file_path_info["basename"];
0 ignored issues
show
introduced by
Expected 1 space after "="; 2 found
Loading history...
Coding Style Comprehensibility introduced by
The string literal basename 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...
291
292
				// Restore the wrapped link
293 1
				$disable_wrapped_link = false;
294
295
			}
296
297
			// Whether to use lightbox or not
298 1
			if ( $disable_lightbox || ! $lightbox || ! empty( $field_settings['show_as_link'] ) ) {
299
300 1
				$link_atts = empty( $field_settings['show_as_link'] ) ? array( 'target' => '_blank' ) : array();
301
302
			} else {
303
304
				$entry_slug = GravityView_API::get_entry_slug( $entry['id'], $entry );
305
306
				$link_atts = array(
307
					'rel' => sprintf( "%s-%s", $gv_class, $entry_slug ),
0 ignored issues
show
Coding Style Comprehensibility introduced by
The string literal %s-%s 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...
308
					'class' => 'thickbox',
309
				);
310
311
			}
312
313
			/**
314
			 * @filter `gravityview/fields/fileupload/link_atts` Modify the link attributes for a file upload field
315
			 * @param array|string $link_atts Array or attributes string
316
			 * @param array $field_compat Current GravityView field array
317
			 * @since 2.0
318
			 * @param \GV\Template_Context $context The context.
319
			 */
320 1
			$link_atts = apply_filters( 'gravityview/fields/fileupload/link_atts', $link_atts, $field_compat, $context );
321
322
			/**
323
			 * @filter `gravityview/fields/fileupload/disable_link` Filter to alter the default behaviour of wrapping images (or image names) with a link to the content object
324
			 * @since 1.5.1
325
			 * @param bool $disable_wrapped_link whether to wrap the content with a link to the content object.
326
			 * @param array $field_compat Current GravityView field array
327
			 * @see GravityView_API:field_value() for info about $gravityview_view->field_data
328
			 * @since 2.0
329
			 * @param \GV\Template_Context $context The context.
330
			 */
331 1
			$disable_wrapped_link = apply_filters( 'gravityview/fields/fileupload/disable_link', $disable_wrapped_link, $field_compat, $context );
332
333
			// If the HTML output hasn't been overridden by the switch statement above, use the default format
334 1
			if ( !empty( $content ) && empty( $disable_wrapped_link ) ) {
0 ignored issues
show
introduced by
Expected 1 space after "!"; 0 found
Loading history...
335
336
				/**
337
				 * Modify the link text (defaults to the file name)
338
				 *
339
				 * @since 1.7
340
				 *
341
				 * @param string $content The existing anchor content. Could be `<img>` tag, audio/video embed or the file name
342
				 * @param array $field_compat Current GravityView field array
343
				 * @since 2.0
344
				 * @param \GV\Template_Context $context The context.
345
				 */
346 1
				$content = apply_filters( 'gravityview/fields/fileupload/link_content', $content, $field_compat, $context );
347
348 1
                $content = gravityview_get_link( $link, $content, $link_atts );
349
			}
350
351 1
			$output_arr[] = array(
352 1
				'file_path' => $file_path,
353 1
				'content' => $content
0 ignored issues
show
introduced by
Each line in an array declaration must end in a comma
Loading history...
354
			);
355
356
		} // End foreach loop
357
358
		/**
359
		 * @filter `gravityview/fields/fileupload/files_array` Modify the files array
360
		 * @since 1.7
361
		 * @param array $output_arr Associative array of files \n
362
		 *  @type string $file_path The path to the file as stored in Gravity Forms \n
363
		 *  @type string $content The generated output for the file \n
364
		 * @param array $field_compat Current GravityView field array
365
		 * @since 2.0
366
		 * @param \GV\Template_Context $context The context.
367
		 */
368 1
		$output_arr = apply_filters( 'gravityview/fields/fileupload/files_array', $output_arr, $field_compat, $context );
369
370 1
		return $output_arr;
371
	}
372
}
373
374
new GravityView_Field_FileUpload;
375