Deprecated: Optional parameter $function declared before required parameter $page is implicitly treated as a required parameter in /home/swalsh/public_html/wp-content/plugins/cron-view/plugin.php on line 201

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property autoptimizeCompatibility::$conf is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCompatibility.php on line 18

Deprecated: Creation of dynamic property autoptimizeCriticalCSSCore::$criticalcss is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeCriticalCSSCore.php on line 20

Deprecated: Creation of dynamic property autoptimizeImages::$lazyload_counter is deprecated in /home/swalsh/public_html/wp-content/plugins/autoptimize/classes/autoptimizeImages.php on line 34

Deprecated: Creation of dynamic property Smush\Core\Modules::$webp is deprecated in /home/swalsh/public_html/wp-content/plugins/wp-smushit/core/class-modules.php on line 109

Deprecated: Creation of dynamic property Jetpack_Publicize::$modules is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 38

Deprecated: Creation of dynamic property Automattic\Jetpack\Publicize\Publicize_UI::$in_jetpack is deprecated in /home/swalsh/public_html/wp-content/plugins/jetpack/modules/publicize.php on line 101

Deprecated: Return type of Requests_Cookie_Jar::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 63

Deprecated: Return type of Requests_Cookie_Jar::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 73

Deprecated: Return type of Requests_Cookie_Jar::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 89

Deprecated: Return type of Requests_Cookie_Jar::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 102

Deprecated: Return type of Requests_Cookie_Jar::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Cookie/Jar.php on line 111

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetExists($key) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 40

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetGet($key) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 51

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetSet($key, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 68

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::offsetUnset($key) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 82

Deprecated: Return type of Requests_Utility_CaseInsensitiveDictionary::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/swalsh/public_html/wp-includes/Requests/Utility/CaseInsensitiveDictionary.php on line 91

Warning: Cannot modify header information - headers already sent by (output started at /home/swalsh/public_html/wp-content/plugins/cron-view/plugin.php:201) in /home/swalsh/public_html/wp-includes/feed-rss2-comments.php on line 8
Comments on: 5 Obstacles Football Clubs face undertaking Social Media http://digital-football.com/featured/5-obstacles-football-clubs-face-undertaking-social-media/ Football Social Media: The ultimate guide on how football clubs are using Social Media. News, tactics, opinion and stats Sat, 31 Aug 2013 18:06:58 +0000 hourly 1 By: Sean Walsh http://digital-football.com/featured/5-obstacles-football-clubs-face-undertaking-social-media/#comment-463898 Sat, 31 Aug 2013 18:06:58 +0000 http://digital-football.com/?p=6176123266#comment-463898 In reply to Jay B.

Hi Jay,

Its not something I know off – I would imagine most would keep it in house to be honest!

]]> By: Tom Flumé http://digital-football.com/featured/5-obstacles-football-clubs-face-undertaking-social-media/#comment-463872 Fri, 30 Aug 2013 12:42:38 +0000 http://digital-football.com/?p=6176123266#comment-463872 In reply to Sean Walsh.

Hi Chris,

When players are sigend/recruited it should be clear that this is a “requirement” from the club’s side. The player is expected to line up on such details. That’s what I think!

// Tom

]]> By: Jay B http://digital-football.com/featured/5-obstacles-football-clubs-face-undertaking-social-media/#comment-463788 Thu, 22 Aug 2013 23:36:19 +0000 http://digital-football.com/?p=6176123266#comment-463788 Sean, do you know much about these ‘one or two’ individuals that look after large sporting organisations’ twitter accounts? eg. how much they might be paid, how they operate?

]]> By: Sean Walsh http://digital-football.com/featured/5-obstacles-football-clubs-face-undertaking-social-media/#comment-463781 Thu, 22 Aug 2013 14:43:12 +0000 http://digital-football.com/?p=6176123266#comment-463781 In reply to Chris Samson.

Hi Chris,

Thanks for the comment. Tis an interesting problem – not everyone wants their work life document and made public, so why wouldn’t footballers be the same. Takes a certain level of trust I think for somebody in the Social Media team to be accepted into the backroom staff.

Sean

]]> By: Chris Samson http://digital-football.com/featured/5-obstacles-football-clubs-face-undertaking-social-media/#comment-463777 Thu, 22 Aug 2013 08:48:45 +0000 http://digital-football.com/?p=6176123266#comment-463777 I run the Facebook account for my local amateur team and I’ve found, on occasion, that while some managers or coaches may not like the intrusiveness, some players can be the same! It’s taking me a fair few weeks to chase our new players simply to get a photo of them holding our kit for a picture on our page.

]]>