Farhan Shafi

Thank you for the detailed troubleshooting, it really helped us identify the issue.

This was a conflict with Gutenberg plugin version 23.3.0. That has since been updated and the core problem is resolved.

There is one known issue still remaining though, when you insert a new block it may look broken at first, but saving the page and refreshing fixes it. We are still investigating whether this is on our end or a Gutenberg issue, so we want to be sure before pushing any fix.

Also worth noting, Gutenberg is not fully compatible with WordPress 7.0 right now, so some editor quirks are expected on that version until it gets addressed upstream.

We will release a fix as soon as it is confirmed. Thanks for your patience!

Best Regards

Hello @romanstrel,

Thank you for the suggestion!

If I understand correctly, you’re looking for a left-to-right masonry ordering, where the first image appears at the top-left, the second image appears to the right of it, and then the layout continues horizontally before moving down.

At the moment, the masonry layout follows the traditional column-based approach, where items are placed vertically within columns (so the second image may appear below the first rather than beside it). This is how most masonry implementations work, and currently we don’t have an option to change the ordering behavior.

That said, I appreciate the feedback and can see how a left-to-right reading flow could be beneficial in some cases. I’ll keep it in mind for future improvements and investigate whether it’s feasible to support as an optional layout setting.

Thanks again for the suggestion!

Hello @johnboyson,

Sorry for the late reply. I just checked your site, and everything seems to be working fine. I was able to share it on X without any issues.

Regarding the double posts when sharing, that might be a temporary glitch with X itself.

Let me know if you continue to see the issue.

Hi @whistlerdan we will look into it in deep and fix it. I hope both issues will be fixed in the upcoming release.

Hi @opheliemj ,

We only add rel="noopener noreferrer" when the link is set to open in a new tab (target="_blank"). This is a security best practice because without it, the newly opened page can access the original page and potentially perform harmful actions (a known issue called tabnabbing). It also prevents sending referrer information if you don’t want the destination site to see where the traffic is coming from.

For links that open in the same tab, this attribute isn’t necessary and we don’t plan to enforce it there. That’s why you’ll only see it applied on links opening in a new tab.

Best Regards
Farhan Shafi

Thank you for reporting this issue! We will look into it and hopefully fix will be available in the upcoming release.

Please send an email at [email protected]

@newtlabs Let me know, If you are still facing the error.

Kind Regards
Farhan