Correct way to inject columns
Since I have a multisite setup, I was storing the AC table views with local storage (PHP files) so that there’d be just 1 centrally-accessible version for all the sites. Then because I have a suite of plugins, I was modifying the stored AC PHP files to add a custom filter that I could use to inject columns from other plugins. That was working fine before, but I see now that AC has overwritten all my table view files (even though they were set to writable = false) “baking-in” the columns that were supposed to be dynamically injected by my filter.
What’s the correct Admin Columns way to inject a column into a PHP-stored table view? I don’t see an AC hook that is obvious for that purpose OR is there a way of preventing AC from overwriting my customized locally-stored table view PHP files?
Thank you for your feedback. Since version 7 was a major update and columns needed adjustments to keep functioning correctly, we decided to update local storage files with the patch as well, even if they are set to read-only.
Could you share a bit more about the changes you made in your PHP files? That will help me better advise you for your specific use case. Please also send an example of a local storage file. You can email it to support@admincolumns.com, and I’ll be happy to assist you further there.
By the way, if you’re adding a third-party column (not related to Admin Columns), you can use the default WordPress hook to register the column. Our plugin persists columns with priority 200, so if you use a higher priority, you can override the persisted column configuration.
You must be logged in to reply to this topic.