WordPress Theme Options - Portfolio

partnuz said
I totally agree but this is what users want and we can’t do anything about it except to give them what they want.

theres nothing wrong with giving users what they want, but its simple enough to pack a plugin with the theme or use something like TGM

OrganicBeeMedia said

partnuz said
I totally agree but this is what users want and we can’t do anything about it except to give them what they want.

theres nothing wrong with giving users what they want, but its simple enough to pack a plugin with the theme or use something like TGM

+1

Let’s just stab each other with knives

There are some problems with plugin approach: 1. Plugins update requires additional work for user. 2. Additional queries to db. 3. Relying on third-party plugins may limit flexibility when developing new features

partnuz said
There are some problems with plugin approach: 1. Plugins update requires additional work for user. 2. Additional queries to db. 3. Relying on third-party plugins may limit flexibility when developing new features

1. Very true but it’s best to get users used to using plugins because it prevents them from getting locked into a particular theme.

2. Not true at all. There is zero difference between code in a plugin and code in a theme.

3. Then build it as a plugin yourself.

mordauk said

partnuz said
There are some problems with plugin approach: 1. Plugins update requires additional work for user. 2. Additional queries to db. 3. Relying on third-party plugins may limit flexibility when developing new features

1. Very true but it’s best to get users used to using plugins because it prevents them from getting locked into a particular theme.

2. Not true at all. There is zero difference between code in a plugin and code in a theme.

3. Then build it as a plugin yourself.

Ad.2 I meant that most options frameworks store data in a single db option instead of few. Plugins require separate db options thus causing additional queries.

partnuz said
Ad.2 I meant that most options frameworks store data in a single db option instead of few. Plugins require separate db options thus causing additional queries.

The options are still stored in the same DB table and with the way that the WordPress database functions (such as get_option()) work, you actually aren’t querying the database each time. Post meta works the same way: each time you use get_post_meta(), you’re not actually querying the database with each function call.