[theme-reviewers] Admin Panel Frameworks and "Unique Callback Slugs"

[Abhik Biswas]

@Chip,
The third namespace is for the function to retrieve values from options
table.
I am planning a *theme enhancer* plugin for my themes and integrate the
plugin's options panel with the theme's. If I use theme slug namespace for
the function that retrieves the values, the plugin won't work (at least
with the setup I have in mind) for all the themes. I'd then have to
manually edit all the files and bundle the plugin with the theme (which is
too much extra work for each theme).

@Devin,
Thanks pal, I know I can change the options name. But, that's not what I
want.




On Fri, May 24, 2013 at 8:41 PM, Devin Price <devin at wptheming.com> wrote:

> Hi Abhik.  The Options Framework saves two sets of options.
>
> 1)  One is for the framework itself, so that it knows which option set the
> theme uses, which version it is, etc.  You could customize the framework to
> change this if you like, but it would create extra work to keep the
> framework in sync as new versions come out.
>
> 2)  The other option is where the actual theme options are stored.  These
> are saved as the theme name itself in the options table (by default),
> though you can easily customize this to be whatever you like.  You can see
> in my latest theme I manually set this to be "visual-theme" in options.php:
> https://github.com/devinsays/**visual/blob/master/inc/**options.php<https://github.com/devinsays/visual/blob/master/inc/options.php>
>
> Devin Price
> WP Theming Inc. <http://www.wptheming.com>
> Twitter: @devinsays <http://twitter.com/devinsays>
>
>
> ______________________________**_________________
> theme-reviewers mailing list
> theme-reviewers at lists.**wordpress.org<theme-reviewers at lists.wordpress.org>
> http://lists.wordpress.org/**mailman/listinfo/theme-**reviewers<http://lists.wordpress.org/mailman/listinfo/theme-reviewers>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20130524/1ccd36ac/attachment.html>