Meta Box

Thank you Peter. Your reply left me in doubt on several aspects so I asked ChatGPT and this is what it had to say (I think it might be useful to other members).

-----

"Handling the transition of posts from ONLINE to OFFLINE in a Custom Post Type (CPT) involves several considerations. Let's address your questions step by step:

1. Taxonomy or Custom Field (CF)?
For your use case, a taxonomy seems more suitable since it's designed for grouping and categorizing content. In this scenario, a taxonomy with two terms (ONLINE and OFFLINE) would allow you to easily filter and query posts based on their status.

(@Peter: I'm surprised your reply both because your article comparing CF and taxonomy explictly says:
- Do you need to browse posts by value? NO => CF | YES => Taxonomy
- Do you need to filter by the value? NO => CF | YES => Taxonomy
- Do you need to manage (add, edit, remove) the values? NO => CF | YES => Taxonomy
Link: https://metabox.io/custom-fields-vs-custom-taxonomies/)

2. Using the Same Taxonomy for Multiple CPTs
Yes, it's absolutely fine to use the same taxonomy across multiple CPTs. Taxonomies are meant to be flexible and can be shared among different post types without interference.

3. SEO Considerations - 404 or Redirect
In terms of SEO, it's generally better to avoid 404 errors for content that has been intentionally removed or set to OFFLINE. A 301 redirect would be more user-friendly and can help retain SEO value by directing users and search engines to relevant content. However, the decision depends on your specific use case and how you want to handle the user experience.

4. How to Display a 404 Error
If you decide to go with the 404 approach, switching the post to draft mode in the WordPress back office is one way to achieve this. Drafted posts are not publicly accessible, and attempting to access them would result in a 404 error.

5. Filtering Published/Draft Status in Archive Pages
Yes, you can filter posts based on their published status. In your archive page queries, you can specify that only published posts should be displayed. For example, in a typical WP_Query or get_posts() call, you can include the 'post_status' parameter 'post_status' => 'publish'.
This ensures that only published posts are retrieved.

In summary, using a taxonomy for the ONLINE/OFFLINE status seems like a reasonable choice. The decision between a 404 error and a redirect depends on your specific UX goals. Combining taxonomies with proper post status queries in your template files will help you achieve the desired functionality on the front end."

Thank you Peter.

Just to be sure, I didn't say all the CF are common to all posts of the CPT (only some).
Would it still work?

Otherwise, another option would be to simply change the value directly in the database with some magic formula (that I don't have... yet). What do you think?

Thank you Long. I hope my suggestions regarding #1 #3 #4 #5 #6 won't fall through :-).

Regarding Gridbuilder, here is what the dev Loic told me:

There is no integration with FB Favorite Posts.
It is however possible to use this shortcode in a card:
[mbfp-button id="{{ post.id }}" class="custom_class" add="add_text" added="added_text" show_count="true"]

As for #2, where am I supposed to paste the code snippet you gave me? And is it still needed if I do what Loic said above?

Here is the file I mentioned above.

Thank you Long! 🙂

Using Oxygen Builder, should I put it in a snippet in Advanced Scripts or Code Snippets?

Thank you Anh and Long, I have a better understanding of the situation now.

If I follow your suggestion for storing the lyrics, it is going to take me a lot of time to do it manually, so it got me thinking.

I bought WP All Import a year ago but haven't put it to use yet.
When I contacted the support of the plugin to know if I could use WP All Import to import the content of all my custom fields/posts, they said:

If you're using regular custom post types and regular custom fields (i.e. the postmeta WordPress table), you should be able to import into the majority of Meta Box fields using these instructions: https://www.wpallimport.com/documentation/custom-fields/theme-plugin-fields/.

For more complex fields, or if you're using the custom tables option to store meta fields in a custom table, you'd have to write custom code that uses our API to import the data: https://www.wpallimport.com/documentation/advanced/action-reference/.

This leads me to the following questions:
1- does Meta Box use the postmeta WordPress table by default?
2- if so, does that mean that I can use WP All Import to import any type of custom field for my CPT (including the lyrics even if they have different sizes / numbers of timecode/lyrics pairs)?
3- as for styling the lyrics, I guess I need to add two classes (one for the timecode, another for the lyrics). Would you show me a screenshot of how to do it wfor a cloneable group with two subfield texts?

Best,

Laurent

It looks like your solution works manually. What if we want Meta Box to output the correct size automatically?