Limitations

• To support data entry, a table must have a primary key or a unique index.
• Managing media items requires the user to be logged in with an active WordPress account that has the necessary permissions.
• When activated, the plugin creates a repository in your WordPress database. If the plugin is network-activated on a multisite installation, a repository is created for every site. For sites added later, the repository must be created manually (Plugin Settings > Repository).
• WP Data Access uses plugin tables prefixed with $wpdb->prefix. If you change the WordPress database table prefix after installation, you must also update the prefix for the WP Data Access tables accordingly.
• There is a limit on the file size for imports. The maximum file size depends on your server configuration. You can solve this issue by increasing the import file size limit.

Legacy Tools

The following known limitations apply to the legacy tools.

• To support bulk actions, a table must have a primary key or a unique index.
• If you add list tables or data entry forms to your web pages, you might encounter a 404 error if your column names conflict with reserved terms, your theme's parameters, or those of other plugins. Solution: Rename the column. Example: Rename column name to person_name.
• Features that rely on AJAX are not available when the Blue Host plugin is enabled, as it generally blocks all AJAX requests. Disabling the Blue Host plugin resolves this issue.
• To make date columns searchable in the Search Builder, ensure your WordPress date format is defined as "Y-m-d". Other date formats are not supported.
• Search functionality for a table added via the [wpdadiehard] shortcode does not work when the page is set as a static homepage.