3118 posts
  • Sold between 5 000 and 10 000 dollars
  • United States
  • Bought between 10 and 49 items
  • Has been a member for 3-4 years
  • Exclusive Author
chrisakelley says

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

439 posts
  • Bought between 50 and 99 items
  • Europe
  • Exclusive Author
  • Has been a member for 2-3 years
  • Sold between 5 000 and 10 000 dollars
Pixelous says


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

308 posts
  • Attended a Community Meetup
  • Sold between 10 000 and 50 000 dollars
  • Exclusive Author
  • Bought between 10 and 49 items
  • Has been a member for 2-3 years
  • Referred between 10 and 49 users
SyamilMJ says

Let’s just stab each other with knives

152 posts
  • Exclusive Author
  • Has been a member for 4-5 years
partnuz says

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

730 posts
  • Elite Author
  • Attended a Community Meetup
  • Has been a member for 4-5 years
  • Sold between 100 000 and 250 000 dollars
  • Bought between 50 and 99 items
  • Exclusive Author
  • Most Wanted Bounty Winner
+2 more
mordauk says

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.

152 posts
  • Exclusive Author
  • Has been a member for 4-5 years
partnuz says


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.

730 posts
  • Elite Author
  • Attended a Community Meetup
  • Has been a member for 4-5 years
  • Sold between 100 000 and 250 000 dollars
  • Bought between 50 and 99 items
  • Exclusive Author
  • Most Wanted Bounty Winner
+2 more
mordauk says

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.

by
by
by
by
by
by