Support » Plugin: Atomic Blocks - Gutenberg Blocks Collection » Post Grid Conflict with Super Socializer Plugin

  • hardonhorsepoweradmin

    (@hardonhorsepoweradmin)


    Hello,

    I posted about this issue on Super Socializer’s support page but figured I’d drop some info here as well. I’m getting a conflict with their Social Sharing interface on any page which contains AB Post Grid content.

    On such pages, a duplicate (yet misformatted) instance of their floating social sharing interface is generated inside of the excerpt markup on the first post in the grid – deactivating AB altogether solves the issue, as does simply removing the post grid from a given page. No other AB blocks seem to conflict, only the post grid.

    I force-disabled the floating interface for the particular post that was being called in the post grid and generating the markup, but the markup for the floating social sharing interface is still generated (yes, the cache is cleared after making such changes).

    I have posted about this in their support area as well, temporarily my workaround is to convert the post grid content into actual typed content in the meanwhile, as there won’t be any updated posts being added to our site for a few more weeks so I am okay with this for now. Eventually, however, when the site is more active with more posts being added, I’d love to restore the ability for these post grids to automatically populate rather than manually typing all of my front page content.

    Please advise, I’m not sure if this is on your end or Super Socializer’s but let me know what you think!

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author John Parris

    (@mindctrl)

    @hardonhorsepoweradmin thanks for the report. Does this look similar to the issue you describe? https://github.com/studiopress/atomic-blocks/issues/108

    hardonhorsepoweradmin

    (@hardonhorsepoweradmin)

    @mindctrl Thank you for the swift reply, I had sent another response yesterday but it seems as if it never posted!

    Visually speaking, my case initially appears different, as I’m not getting any raw js or jquery output. The output I’m seeing is purely parsed html – styled incorrectly, but the elements are built nonetheless. The styling issue is simply due to the fact that the element is being called outside of its normal parent therefore not all css is applying.

    Perhaps it may be caused by the same issue that is affecting Genesis Simple Share as indicated above on github, but unfortunately without having experience with or knowing more about Genesis Simple Share I cannot confirm.

    For now, I do have a workaround to retain my homepage content while still using my other social sharing plugin without the need to remove atomic blocks, so if there’s any other tests or information that I can provide just let me know! I can set up a private or password-protected page just to test conflict with the post grid if you would like.

    hardonhorsepoweradmin

    (@hardonhorsepoweradmin)

    I have created two test pages to offer a firsthand look at the issue. One page contains an ab post grid like the one I used on my front page, the other contains ab grid without excerpt. The first page with excerpt shows the issue, whereas the second page without excerpt is unaffected by the issue.

    https://lloydz.com/ab-grid-super-socializer-test-page/
    https://lloydz.com/ab-grid-super-socializer-test-page-2/

    Both pages are password protected with the following password: absstesting

    Thank you for your time

    hardonhorsepoweradmin

    (@hardonhorsepoweradmin)

    I forgot to mention, this is only visually noticeable under 1000px screen size unless you inspect the source code in the console. Above 1000px you can still see the Html structure in console/source, however, it only is shown at 1000px or less.

Viewing 4 replies - 1 through 4 (of 4 total)
  • You must be logged in to reply to this topic.