Ever since we opened up the beta of Mergebot to our lovely early adopters before Christmas, we have been working hard to make a dent in the list of limitations of the beta. The limitations were necessary to get Mergebot out the door, but initial feedback from our testers confirmed our thoughts that these limitations need to be lifted sooner rather than later. Plugin Integration
Brad previously described how Mergebot needs to know certain information about a plugin, to ensure all data is merged correctly. This information ensures that any new table row, which is assigned a new ID when created, is deployed correctly and its new ID is used in all other queries that reference this new ID.
This information is stored in a schema JSON file, and as a quick recap, it can contain the following definitions:
The primary key columns for any custom tables
Columns in custom tables that are foreign key relationships to other tables
Key / value relationship data stored in meta tables (postmeta, options, usermeta) that contain IDs we want to replace on deployment
Attributes in shortcodes that contain IDs we want to replace on deployment
IDs stored in content columns, like the Posts table’s post_content
Source: https://managewp.org/articles/14281/mergebot-beta-update-plugin-integrations-and-query-selection
source https://williechiu40.wordpress.com/2017/01/26/mergebot-beta-update-plugin-integrations-and-query-selection/
No comments:
Post a Comment