You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When linking to WordPress tables (posts, metadata, etc), you need the database prefix ('wp_', etc) before the table name. There is currently no way to write a prefix-agnostic deploy file. It should be possible to have some kind of templating variable in the place of the prefix and have that be interpreted by the dbdeploy script. As of now, if you are linking up to any non-dewdrop tables, you need to manually edit the dbdeploy file for every different database.
The text was updated successfully, but these errors were encountered:
When linking to WordPress tables (posts, metadata, etc), you need the database prefix ('wp_', etc) before the table name. There is currently no way to write a prefix-agnostic deploy file. It should be possible to have some kind of templating variable in the place of the prefix and have that be interpreted by the dbdeploy script. As of now, if you are linking up to any non-dewdrop tables, you need to manually edit the dbdeploy file for every different database.
The text was updated successfully, but these errors were encountered: