Setting Select Post Types not working

Hi @deothemes,

Are you talking about the bsf_rt_marker ID in the source code?

I look forward to hearing from you.

Kind regards,
Herman ??

Exactly, prior to version 1.0.7 this Html tag didn’t appear on a regular pages, since only posts selected in post type settings. When I rollback to 1.0.6 this tag disappears from a regular pages.

I had the same problem. Its useless, you use your customers as lab rats. You do this with the theme – even the paid version. You do it here. Im giving up on BSF

I came across this issue as well. There are styles in the project I am working on that targets top level blocks that are direct children of the content unless it’s a group or cover. With this filter applied it becomes the sole top level item of the content.

e.g. .content > *:not(.wp-block-cover) {} which fails now because the structure has changed to .content > #bsf_rt_marker

I think the thing that is a bit more odd about this is that I have the Progress Bar’s Display Position set to None and this is happening on a post type that should not receive any treatment from this plugin.

I have a few suggestions to include inside of bsf_rt_add_marker_for_progress_bar_scroll:

• Check the value of bsf_rt_check_selected_post_types, if false return the content without modifications.
• Check the value of bsf_rt_get_option( 'bsf_rt_position_of_progress_bar' ), if none return the content without modifications.

For those out there that do not require the progress bar in their project, you can use this snippet the prevent the bsf_rt_marker from wrapping your content.

remove_filter( 'the_content', 'bsf_rt_add_marker_for_progress_bar_scroll', 100 );

What I said above is wrong, the filter should be on priority 90 and removing array('BSFRT_ReadTime', 'bsf_rt_add_marker_for_progress_bar_scroll') but that doesn’t seem to work.

Hi @deothemes,

We just released an update contains the fix.

@geistit, please understand that this plugin is free and open source. We initially created it for ourselves, but then we thought to share it with the community, so everyone can benefit from it.

What you said is completely incorrect. We never made our users as experiment. We do our best, despite this plugin is a free one. We just do not offer professional support for this plugin, though we always try to help whenever we can.

Instead of saying something demotivated, you can report the problem you are facing like what @deothemes did. You can always rollback to/install the older version that works for you too.

Or if you are a developer or know how to code, you can do the same as @maxinacube (thanks for sharing your insight, Maxwell), or even contribute to fix this issue by raising a PR on our GitHub.

Anyway everyone, please update the plugin and confirm the fix.

Kind regards,
Herman ??