WP 5.8 (not released yet) will include support for transforming legacy widgets into blocks. I have a custom legacy widget I’m trying to add support for transforming it into a block. Reading the docs I added the following code to one of my blocks. My legacy widget had two attributes (attribute1 and attribute2):
I am trying to exclude posts from a custom taxonomy from displaying on a specific custom post type archive. How can I accomplish that? Today, I do this on a per post basis which is not practical. Thanks so much!
I’m trying to completely disable access to my parents page menu.
For example, I have a menu made like this :
parent page -> child page 1
-> child page 2
Hello, how can I do this in the menu
First of all, I know there are many questions related to this question. But what the problem is that they are all related somehow to jquery.
Hi there and thanks in advance for any help. I am trying to display custom taxonomies(Themes and Guests)on the current post (of custom post type, Podcasts). I have tried the code below, but I am getting an empty result ie. nothing is showing. I added $post->ID after I realised that the code was working fine, but was displaying ALL categories, not just the ones for the current post.
I have a main menu of 3 items, and for each of these I have a different secondary menu. I would like to show the related secondary menu on each page.
I currently used is_page with slug. I will need to add wpml, so each page will have more slugs. I would like to ask if you can suggest me a cleaner and more maintainable solution.
This is what I did at the moment:
I have a plugin which is dependent on another plugin, in this case WooCommerce.
I am building a custom block to add a youtube-video as a background-video that autoplays and infinite loops when you visit the site. To make this happen the user needs to get the video-link and playlist-link (for the loop) and put it into the 2 Richtext input fields I created in the block. Once that is done the video will start playing alredy in the backend to get a better view on how it will look on the site. Now when you save the Block the code will be generated on the frontend as expected but as soon as you refresh the backend page the block will be broken and the following message will be displayed in the console:
All my posts have a custom field named date-start-custom. The value of the custom field is in the date format YYYY-MM-DD HH:MM (e.g: 2021-06-15 14:30), and I want to only list posts that has a date later than the current date.