I've been reading this tutorial ( https://metabox.io/bundle-metabox-plugin-create-customfields/) and following along on my computer. Allowing for various tweaks here and there it all works rather nicely. However Once I get to the end I do have a working custom plugin, but let's say I want to distribute this.
Do I need my plugin to install composer when it first installs in order to then get the metabox bits I need, and if so how is that done? This bit of information appears to have been missed from the tutorial.
Or is the ide that I keep a local copy of the plugin, update as and when metabox updates and then release a new version of plugin that has a vendor folder containing metabox?
You can use Git to create the release for the custom plugin, it also keeps up the vendor folder but removes some composer files that aren't needed to use in the release plugin.
Then on other sites, you can just pull the new update from that repository. Read more on this documentation https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
Thank you, that makes perfect sense.
Now that that's bit's clear may I carry on with a related question. I would like to create a custom plugin that I can apply to new sites as I create them, essentially a settings page for generic site settings so that I don't need to recreate them for each site I build.
1) I take it metabox settings pages are a form of custom post type and therefore get saved in the posts table, but the options fields associated with them are saved in the options table?
2)very specifically oxygen related (and for oxygen 3.9 + where metabox integration is built in). Will metabox fields that I add to my custom plugin be visible under the metabox tab when selectiong dynamic content to be added to oxygen elements or would one need to use rwmb_get_value() to retrive data from those custom plugin metabox fields?