jhnpldng

Are you specifying the field you want?

[pods id="1" field="post_title"]

Search docs.pos.io for “shortcode” for both basic shortcode or php with shortcode usage. It’s one of the few Pods subjects the docs cover well.

Select the Relationship field type. That’s the only field type that has those.

The Select/multiselect selected on Add New come from either a list you create when adding the field or from a relationship to some other field/taxonomy.

Edit Pod. Choose the Connections tab and tick the box for the taxonomy you created. That will make it show on Add New/Edit screen just like native WP Categories/Tags do when adding a new Post.

When adding a new Field, there is an option to allow oEmbed and Allow Shortcodes on the HTML, Plain Paragraph and WYSIWYG field types.

There’s an option to Allow HTML on the Plain Paragraph field type and it’s already a built in option with WYSIWYG field type. An iFrame is html. There’s also an option to sanitize html for Plain Paragraph.

For Plain Paragraph and WYSIWYG, you would add the youtube url when using Add New and it would only show on the front end for that single CPT. For WYSIWYG on Add New, swap the editor to from Visual to Text. For Block Editor, use the Custom html block.

With the HTML field type, HTML Options of the add HTML field has a little code box. Add a youtube url there(no <a href needed), and the video will show on the Add New/Edit screen in admin and that same video will show on the front end for all of those CPTs. Could be useful for a Custom Settings Page for client where it’s a one time use strictly in the backend.

Any html added to HTML field type would do the same as youtube url. It would exist on every Add New screen and new CPT of that type on both the backend and frontend.

That fixed it. Thanks

Thanks for the fast reply.

The goal; enter a date, enter number(of days) get new date returned with number of days subtracted

It’s subtracting months instead of days. Entering a date of 05/05/2025 and number of 2 returns 03/05/2025. Number of 1 returns 04/05/2025

Date Field is fieldname3
Number Field is fieldname2
Calculated Field is fieldname1

CDATE(fieldname3-fieldname2, 'dd/mm/yyyy');

Results based on number entered
1 = 04/05/2025
2 = 03/05/2025
3 = 02/05/2025
4 = 01/05/2025
5 = 30/04/2025
6 = 29/04/2025
7 = 28/04/2025

• This reply was modified 2 months, 2 weeks ago by jhnpldng. Reason: adding more info

Actually @anlino & @vitaliikolisnyk
Since this theme has the admin menu item for cuntomizer, no custom CSS plugin is needed. You can use Additional CSS in the customizer.

Even with block themes that remove that menu item, customizer still exists and works because most themes require it.

/wp-admin/customize.php

Likewise with /nav-menus.php and /widgets.php

They all come in handy with block themes. I find it easier to build a menu the old fashioned way. Some plugins add their own sidebar with “legacy” widgets and /widgets.php is the only place to work with those.

@vitaliikolisnyk

greenshift plugin has a special button with cookie and a tutorial on their site on how to use it to make a dark/light mode switch.

background/foreground variable gets swapped but other colors can be dealt with in the same manner, even those that are not var.

2023 is a block theme so everything gets done in the site-editor, not the customizer. Same with menus. They’re created in the site-editor, not nav-menus.php page and the same with widgets.

It’s an entirely new way of doing things and WordPress hasn’t gotten the word out very well. Everything is a block.

It’s actually quite flexible as you can now create multiple headers, footer and sidebars, even on themes that don’t come with sidebars. Then you can display any of those template parts when/where you choose.

2022 is also a FSE capable block theme. FSE = Full Site Editing. Technically still in Beta.

I figured some things out.

Two different block themes give white screen of death on subsite if I use the link; Appearance > Editor (beta) in admin menu which is this;

/wp-admin/site-editor.php

The above link in wp-admin always adds &postid= the postid of which varies depending on theme.

There are no links in wp-admin to these site-editor sub pages but I can get to them just fine;

/wp-admin/site-editor.php?postType=wp_template
/wp-admin/site-editor.php?postType=wp_template_part

I can also get to any Template or Template Part from there. That means anything can be done if bypassing the appearance>site-editor link.

Running the same block theme on both main and subsite, made changes to the Header and Front Page Template on both and as mentioned in my previous post, those changes are done in the DB so one has no affect on the other and either one can be undone.

Swapped both to a different block theme and got the same results. Tried yet a third block theme and did not get the white screen of death on;

/wp-admin/site-editor.php

So, bottom line is, yes you can use a block theme and make changes to one site of a multisite and it doesn’t affect the others BUT, you may get the WSofD.

I keep these two links handy…

/wp-admin/site-editor.php?postType=wp_template
/wp-admin/site-editor.php?postType=wp_template_part

…plus links to customize, nav-menus, blocks(reusable) and widgets because most block themes hide those even though they still exist and customize especially is useful for the Additional CSS section. Nav-menus can also be handy because it’s quicker to build a menu there and then select it from the block editor, Navigation block.

Likewise, I have a KB plugin that has it’s own sidebar with widgets, regardless of the theme so I need to be able to get to wp-admin/widgets.

Any of the above are a lot faster than that main FSE page and none give you WSofD.

Copy this, add your example.com in front and keep them handy for block themes.

/wp-admin/site-editor.php?postType=wp_template_part
/wp-admin/site-editor.php?postType=wp_template
/wp-admin/edit.php?post_type=wp_block
/wp-admin/customize.php
/wp-admin/nav-menus.php
/wp-admin/widgets.php

Of course, keep in mind, beta so ymmv and should probably not be used for critical sites.

@kahless

Multisite + FSE/block themes are fairly incompatible as of yet as referenced here.

github.com/WordPress/gutenberg/issues/33989
core.trac.www.ads-software.com/ticket/55023

Several plugins are the same in that they look for a header.php and/or footer.php which block themes don’t use. (enable debugging and you may even get an error saying header.php is Deprecated since 3.0)

That being said, I’ve had mixed results using a block theme on multisite. A few seem to work ok while others give you the white screen of death by simply being activated.

Found out when converting several blogspot sites into one WP site for someone. They were using a unified, hand coded html, menu for all, plus slightly varied headers to make it look like one blog. They basically created a multisite in a way.

Multisite + block theme would have been perfect for me but I gave up pretty quick because I was on the clock. He did end up with a block theme so I could create multiple headers for multiple CPT templates and their archives templates, plus the main blog.

As far as FSE editing, even though the templates and template parts are in the theme folder, your edits go into the DB. That’s how you’re able to “Clear customizations” to those on these pages;

/wp-admin/site-editor.php?postType=wp_template
/wp-admin/site-editor.php?postType=wp_template_part

The ones you’ve customized and can clear the customization of, show a little blue dot. Any template or part that you created from scratch, you can’t clear customizations but can delete it from the db because that’s the only place it exists.

The feature of being able to make changes to block theme templates & parts and then export it as a distinct theme gives more options, however, you’d have to go through that theme on your local machine and make it it’s own theme. Rename it etc and there’s more to it than simply changing the name in style.css.

When you do export a changed block theme and then install on a new site, all those templates and parts you created from scratch, are now part of the theme and are in the theme folder. Any subsequent changes you make will be in the db and as per above, can be cleared but not deleted.

On a side note for FYI, I was only able to create all the CPT templates for that site with the Gutenberg plugin installed and activated. You get a lot more options for what you can create. That thing really bogs down work with my oldish laptop and cheap shared hosting but once I did what I needed, I was able to deactivate Gutenberg and the changes remain.

IF FSE=beta THEN Gutenberg=alpha

Sorry about the long winded reply. Just wanted to convey all I’ve learned.

Gonna go see what I can break now! ;~)

Same thing happens with wp multisite registration page/form with wp 2022 theme so it’s definitely up to core devs.

Same issue with Basepress KB, WCFM vendor dashboard page, Youzify and probably many more.

Just wanted to fill you in since it’s an issue with block themes and since that includes the default theme, you’re bound to hear about it again.

Even though FSE is beta, I’m hooked. Very cool being able to create multiple headers, footers, add sidebars to a theme that has none and create full page/post/archive templates to use them on.

Block themes are fast too. All my basic blog/brochure/portfolio sites score 98-100 on pagespeed/gtmetrix since making the switch.

WordPress is headed towards being fully block based so plugin/theme devs might as well get ready.

Confirmed, all is fixed. Thanks again.

All good

Thx

Also on my staging site, I got rid of that theme and it’s plugin and am using blockpress which takes care of the headings. BlockPress + GreenShift + Twentig for every site now.

• This reply was modified 2 years, 4 months ago by jhnpldng.

Here’s the thing. I was planning on creating a really nice custom nightmode theme, not simply swap foreground for background. You’re tutorial taught me the concept but that javascript file will prevent a few things from being changed with that method.

Infobox, I would probably not want to change as it’s kind of a standard so I can understand why you would give them predefined colors. Initial paddings, margins, etc I can also understand because you want the blocks to look good when first inserted and after that, people can change them if they want.

So as of now, the subtitle on the Circle Number Heading Block is one that I see no good reason for being hard coded to a light blueish gray. It’s just text.

The icons for Icon Box also default to a hard coded #565D66 and again, I don’t see the reason. Figured that out when I went to recreate the look of the Circle Number Heading Block but with an icon which is my preference to a circled number anyway.

I do have a couple of colors I can use for both light and dark backgrounds as a workaround.

So we’re both right I think. Infobox colors were mostly standardized by bootstrap and the traffic light or universal safety standards colors make sense. An icon or that subtitle, not so much.

So if you think you should/could fix those two items, great.

In the meantime, I’ve read the roadmap and anxiously await seeing what you do with woocommerce.