Forum Replies Created

Viewing 7 replies - 1 through 7 (of 7 total)
  • 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.

    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 );

    Thread Starter Maxwell Morgan

    (@maxinacube)

    Oh I see, that’s awesome and should work well. Thank you @eugenewhite

    Thread Starter Maxwell Morgan

    (@maxinacube)

    Thank you @dimned

    I have a follow-up question/a feature request. Is there any way to handle this so it can be version controlled? Something that might be more reliable out-of-the-box when multiple devs are working on one project?

    Plugin Author Maxwell Morgan

    (@maxinacube)

    Hi @andrespr,

    Sorry for the long delay, but we rolled out an update today that includes a new field on Mesh sections for Row Class. With the update, you’ll notice that the pre-existing field for CSS Class on a section is now known as “Section Class”, while we have also introduced a few new fields for “Section ID” and “Row Class”.

    @dogdogma – As far as the xy-grid is concerned, we have plans for a larger update in Mesh to be able to select one of their grid systems.

    Plugin Author Maxwell Morgan

    (@maxinacube)

    Hi @andrespr,

    Unfortunately this is not currently an available option in Mesh. But this is a great feature request that I strongly agree would be a helpful addition.

    I’ve added an issue to our GitHub, https://github.com/linchpin/mesh/issues/188, so progress toward this specific improvement may be tracked there.

    I agree that the documentation would be easier to understand if it was formatted differently, but the GitHub link is a great top-down “how-to” of the plugin. Make sure you start at line 23, and read each & every line. All the explanation is in the comments and is broken into 4 steps; check for plugin dependency, register your shortcode, register shortcode UI for your shortcode, and then your stand WordPress shortcode function.

    It’s worth noting that the dev.php file linked to on GitHub is an example of an additional plugin you can add to your theme to handle all of your Shortcode functions and the Shortcode UI. You could also take what they have available in that file and add it to your functions.php or a separate class in your theme.

Viewing 7 replies - 1 through 7 (of 7 total)