Aug 23rd, 2011, 6:52 PM
Hey Russell,
No, but I wouldn't worry too much in this case. The API mostly just contains functions that are for common use; I didn't think people would need this function - go right ahead and use it, I doubt it will be changing for a long, long time.
For the filter settings function, that's fine too; however, that's more likely to change. That's the problem with referencing core functions: there's no guarantee they won't change. I wish I could, but I can't!
For assigning a View to a client, all you need is for (a) the View to have Public / Private access type and (b) to insert a brand new row in the ft_client_views table (account_id, view_id). You might want to just write a separate function to handle that, rather than using any of the Core code.
Good luck! Let me know how it goes.
- Ben
Quote:...but this isn't exposed in the API.
No, but I wouldn't worry too much in this case. The API mostly just contains functions that are for common use; I didn't think people would need this function - go right ahead and use it, I doubt it will be changing for a long, long time.
For the filter settings function, that's fine too; however, that's more likely to change. That's the problem with referencing core functions: there's no guarantee they won't change. I wish I could, but I can't!
For assigning a View to a client, all you need is for (a) the View to have Public / Private access type and (b) to insert a brand new row in the ft_client_views table (account_id, view_id). You might want to just write a separate function to handle that, rather than using any of the Core code.
Good luck! Let me know how it goes.
- Ben