rinh
Forum Replies Created
-
Forum: Fixing WordPress
In reply to: Format the date and time from custom meta fieldsI reached out to ACF support and I got help quick. I wasn’t doing this correctly. The solution is here for anyone else who might need it: https://www.advancedcustomfields.com/blog/acf-6-2-8/#block-bindings-api
Forum: Fixing WordPress
In reply to: Format the date and time from custom meta fieldsThanks for finding! That is a very old bug :/
Forum: Fixing WordPress
In reply to: Format the date and time from custom meta fieldsThanks for the reply! I use the code snippets plugin to for snippets of PHP. The problem for me when editing is rather that I do not know PHP.
I’ll try out the script in a bit. I also found this, so perhaps it’s actually a bug within ACF? https://github.com/AdvancedCustomFields/acf/issues/673Forum: Fixing WordPress
In reply to: Format the date and time from custom meta fieldsThank you for the reply and the snippet! Unfortunately it still remains in the same date format 🙁
@asafm7 kind of, but I had to install an additional plugin: https://wordpress.org/plugins/display-a-meta-field-as-block/
With that plugin I was able to get ACF fields to work on Site Editor templates.
Oddly enough ACF shortcodes work on pages and posts, but not in templates without that plugin. I’m not sure if it’s a bug with ACF or Site Editor.
Hope you get it work!Forum: Developing with WordPress
In reply to: FSE random p tags when adding blocks in code editorHi and thank you for your reply.
I’m using the Custom HTML widget for a couple of features in templates where I build the actual layout.However, I’m currently trying WordPress 6.1.1, since I’m using 6.2 RC2 for what I’m creating. I should’ve tested that before even posting this in the first place, so I apologise for that. So far I cannot reproduce the issue in 6.1.1. The HTML block behaves like you’d expect it to: keeping the HTML and scripts intact.
This is very good news, it sure was stressful! Though, seems the bug might be back in 6.2 so perhaps I should report it.
Forum: Developing with WordPress
In reply to: FSE random p tags when adding blocks in code editorSorry, I’m opening this again because now I have huge issues with this
wpautopusing the HTML block. I used it for a custom button with a script and after closing and opening the template it was all destroyed by p and br tags and divs had been removed. I understand adding these tags automatically is necessary when writing content, but it shouldn’t be in the HTML block?<p><button id="btn">Menu</button></p><p><script></p><p>var btn = document.getElementById("btn");</p><p>btn.addEventListener("click", e => {<br /> document.documentElement.setAttribute("data-modal-active",<br /> document.documentElement.getAttribute("data-modal-active") === "true" ? "false" : "true")<br />});</p><p></script></p>I found this on github: https://github.com/WordPress/gutenberg/issues/33832
It looks like it was fixed, but I can’t see how.
Is there any way to disable autop from being in the HTML block only?
Thank you in advance.Forum: Developing with WordPress
In reply to: FSE random p tags when adding blocks in code editorThank you for the reply and explanations!
It definitely seems to have a mind of its own, and probably not supposed to mix it all like I tried first. I think I’ll do this properly with column blocks and the HTML block when I do need my own HTML for smaller things.
I found out why. I had to enable this in Ultimate Member – Settings – Access – Enable the “Content Restriction” settings for the Gutenberg Blocks
Thank you for the help!
Hi and thank you for your reply.
For some reason I’m missing the UM settings option in your second image. For me it just looks like this

I tried reinstalling Ultimate Member as well as deactivating other plugins and change block theme. I’m using WordPress 6.2 RC2
Thank you in advance.
Forum: Developing with WordPress
In reply to: FSE random p tags when adding blocks in code editorI feel my post is somewhat embarassing since I’m probably supposed to use the columns block for the layout, but it seemed so convenient to throw my own markup in there and add blocks where I needed them.
Also aware this<!-- wp:post-title /-->is just a HTML commentary, but it somehow displays the post title.
Thank you for your reply.
Appearance – Menus doesn’t exist in block themes, there’s only the Navigation block. In classic themes however it’s possible to make the menu items conditional with the UM plugin in Appearance – Menus.
Any plans on making it work for the Navigation block too?
I’ll try to solve it with code for now.Forum: Fixing WordPress
In reply to: Shortcodes in FSE templatesOkay thank you. I’ll ask over there instead
Forum: Fixing WordPress
In reply to: Shortcodes in FSE templatesHi and thank you for the reply.
I failed to provide more detail on this so I’ll do it now.
I’m trying to get Advanced custom fields (free version) shortcodes to work in templates. They work fine if added directly in a page or post with the shortcode block, but I can’t make them work in templates using the shortcode block.
I also tried with a shortcode from another plugin and it wouldn’t either so I was perhaps too quick to assume it isn’t working.
I’ve tried with Twenty Twenty Three on WordPress 6.1.1 and 6.2 RC2.
Thank you in advance.