Severity: 8192
Message: Return type of CI_Session_files_driver::open($save_path, $name) should either be compatible with SessionHandlerInterface::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 113
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::close() should either be compatible with SessionHandlerInterface::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 280
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::read($session_id) should either be compatible with SessionHandlerInterface::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 145
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::write($session_id, $session_data) should either be compatible with SessionHandlerInterface::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 223
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::destroy($session_id) should either be compatible with SessionHandlerInterface::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 303
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: 8192
Message: Return type of CI_Session_files_driver::gc($maxlifetime) should either be compatible with SessionHandlerInterface::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice
Filename: drivers/Session_files_driver.php
Line Number: 344
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 281
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_cookie_params(): Session cookie parameters cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 293
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 303
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 313
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 314
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 315
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 316
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: ini_set(): Session ini settings cannot be changed after headers have already been sent
Filename: drivers/Session_files_driver.php
Line Number: 94
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_set_save_handler(): Session save handler cannot be changed after headers have already been sent
Filename: Session/Session.php
Line Number: 107
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
Severity: Warning
Message: session_start(): Session cannot be started after headers have already been sent
Filename: Session/Session.php
Line Number: 140
Backtrace:
File: /home/alfonso/public_html/application/controllers/Noticias.php
Line: 7
Function: __construct
File: /home/alfonso/public_html/index.php
Line: 315
Function: require_once
El storytelling no entiende de formatos ni canales: desde charlas hasta narraciones escritas, pasando por visuales, audiovisuales, y un largo etcétera.
Haciendo un repaso por las páginas de Facebook de algunas de las principales marcas y más allá de éstas, vemos cómo algunos formatos que funcionan, generalmente llamadas a la acción, buscando promover directamente la interacción, se repiten en distintas y diversas páginas.
Tres buenos ejemplos de formatos que funcionan en este sentido y vemos en unas y otras páginas son el de completar frases, los packs perfectos para algo que incluyen producto y el del puzzle:
El fin último de cualquier imagen en Facebook es la interacción sean del tipo que sean, al igual que sucede con otros formatos en esta misma red. Según datos de Hubspot, las fotos obtienen un 53% más de ‘me gusta’, un 104% más de comentarios y un 84% más de clics en los links que les acompañan, que las publicaciones con links de solo texto.
9 claves para el storytelling visual en Facebook
Ejemplos de algunas imágenes en páginas de marcas que cuentan historias en Facebook:
¿Qué os han parecido estos ejemplos? ¿Se os vienen otros a la mente? En definitiva, lo prioritario en materia de imágenes de Facebook es que probemos cosas nuevas y nos salgamos de lo habitual para contar historias, exprimamos este formato al 100%: tiene mucho que decir :).
Fuente: 40defiebre