You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to have the option to place LiveBlogs at the top of posts rather than below them. We serve mobile stories adaptively and insert sidebar widgets into the content. With the liveblog at the bottom of the content, it gets pushed down by ads and other widgets.
The code that places the liveblog block is in /liveblog.php L1138:
public static function add_liveblog_to_content( $content ) {
...
return $content . wp_kses_post( $liveblog_output );
}
I would be happy to fork the repo and write this code if the change is approved.
This would involve adding either a global or a post-level setting (or both) to set/get $show_liveblog_at_top in post meta or options.
For the time being I am adding a filter to my functions.php file. This is a fragile hack and relies on particular HTML existing in the LiveBlog output, but it works for now.
Fixes: #525
Some users would prefer having Liveblog output at the top of their posts rather than the bottom. This filter introduces the simple functionality to choose whether the Liveblog output should be above the content or below it (default).
I would like to have the option to place LiveBlogs at the top of posts rather than below them. We serve mobile stories adaptively and insert sidebar widgets into the content. With the liveblog at the bottom of the content, it gets pushed down by ads and other widgets.
The code that places the liveblog block is in /liveblog.php L1138:
I would prefer:
I would be happy to fork the repo and write this code if the change is approved.
This would involve adding either a global or a post-level setting (or both) to set/get $show_liveblog_at_top in post meta or options.
For the time being I am adding a filter to my functions.php file. This is a fragile hack and relies on particular HTML existing in the LiveBlog output, but it works for now.
Charles
The text was updated successfully, but these errors were encountered: