186 posts
  • Has been part of the Envato Community for over 4 years
  • Has sold $75,000+ on Envato Market and is now an Elite Author
  • Has collected 100+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+4 more
Artillegence says

If we save through get_option there is a limit , saving in database table removes that problem and the slider can be use in multiple places , You cant have that if slider is created for a post only. Another alternative would be custom posts but it depends on author. For page builder same concept applies as templates can be reused again.

11 posts Performance Experts
  • Has referred 1+ members
  • Has sold $75,000+ on Envato Market and is now an Elite Author
  • Has collected 1+ items on Envato Market
  • Elite Author: Sold more than $75,000 on Envato Market
+3 more
JoNa says

If we save through get_option there is a limit, saving in database table removes that problem and the slider can be use in multiple places , You cant have that if slider is created for a post only. Another alternative would be custom posts but it depends on author. For page builder same concept applies as templates can be reused again.

It is true that add_option/update_option has a limit, but a very high limit of 2^32 bytes, which is 4 GB of data, that’s a lot! :)

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

Awesome! I really hope that the CDATA requirement will be removed or revised in this update, see my previous message in case you accidentally missed it.

I did see it, thanks :) Feel free to edit this last post to remove the old message ;)

7 posts
  • Has been part of the Envato Community for over 4 years
  • Has collected 1+ items on Envato Market
  • Sells items exclusively on Envato Market
  • Located in Serbia
WPCanyon says

No reason to make your own tables for anything.

619 posts
  • Has been part of the Envato Community for over 3 years
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Sells items exclusively on Envato Market
ChapterThemes says


It is mainly used for sliders and page builders .
Ok, that makes sense. I can see why page builders might need this. Sliders though, I’m not sure why you wouldn’t just use a custom post type?

For my review theme i created a rating system with an similar backend interface like comments. Except it’s a whole separate system with his own tables. Different types of reviews could have their own criteria. Now it could be the case that different review types share the same criteria name in their list of criterias.

So, i’ve studied automation technlogy regarding to databases and there’s one thing you must always try to avoid when using databases: Data redundancy. This means it’s best to create multiple tables, separate values and link to eachother.

In my case it meant that i created 3 separate tables:

- ratingmeta: holds every single criteria from all review types and gives them an idea.

- ratings: hold the general data such as user info etc.

- ratingvalues: hold every rating input and links them to the appropiate ratingmeta ID and general rating id.

This is way better than using things like custom post types to save ratings with custom meta etc. and sure way better than using options. Imagine the custom post type and custom meta mess this would be.

Also, using the wpdb class and extra tables for such a rating feature is WAY faster than using al sorts of meta querie contructions when using CPT’s.

Now, i agree that this sort of thing should be in a plugin.

But just to let you know, that there could be plenty of reasons to put things in separate tables. Specially if you want ‘good practice’.

619 posts
  • Has been part of the Envato Community for over 3 years
  • Has sold $10,000+ on Envato Market
  • Has collected 10+ items on Envato Market
  • Sells items exclusively on Envato Market
ChapterThemes says

If we save through get_option there is a limit , saving in database table removes that problem and the slider can be use in multiple places , You cant have that if slider is created for a post only. Another alternative would be custom posts but it depends on author. For page builder same concept applies as templates can be reused again.

Sliders should be CPT’s if you ask me. Even pagebuilders could use CPT, also to re-use the same data elsewhere. Posts can get loaded everywehere with native functions.

5 posts
  • Has referred 10+ members
  • Has collected 10+ items on Envato Market
  • Sells items exclusively on Envato Market
  • Located in United Kingdom
+1 more
Barn2Media says

Just to clarify the license situation, I assume the term Item in the license refers to both the theme and any bundled plugins as a whole? Therefore, clause 9 in the Regular License…

Although you can modify the Item and therefore delete unwanted components before creating your single End Product, you can’t extract and use a single component of an Item on a stand-alone basis.

...would mean that using a theme-bundled plugin (e.g. to provide shortcodes in that theme) should not be used with another theme (e.g. another theme purchased on TF), as that would be using a single component of the Item on a stand-alone basis?

138 posts
  • Has referred 1+ members
  • Has sold $40,000+ on Envato Market
  • Had an item featured in an Envato Bundle
  • Has collected 1+ items on Envato Market
+3 more
BonfireThemes says

I did see it, thanks :)

Hopefully I won’t start a trend here, but I’m crossing my fingers you guys saw this too, and that get_post_thumbnail will be under the exceptions. Many thanks :)

Another thing to point out is the required use of get_post_thumbnail..

What if a theme only needs to echo the thumbnail url, and not the complete <img src="url" />? If something like this is used to get the url only: <?php $image_id = get_post_thumbnail_id(); $image_url = wp_get_attachment_image_src($image_id,'large', true); echo $image_url[0]; ?>

.. then Theme Check will say get_post_thumbnail is not used… Unless someone knows a better way to do the above, this should probably be under the exceptions as well.

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

Just to clarify the license situation, I assume the term Item in the license refers to both the theme and any bundled plugins as a whole? Therefore, clause 9 in the Regular License…

...

...would mean that using a theme-bundled plugin (e.g. to provide shortcodes in that theme) should not be used with another theme (e.g. another theme purchased on TF), as that would be using a single component of the Item on a stand-alone basis?

As far as I’m aware, when referring to the “item”, we’re referring to the entire contents of the main ZIP file downloaded from ThemeForest (excluding anything that must be distributed under its own pre-existing license).


Hopefully I won’t start a trend here, but I’m crossing my fingers you guys saw this too, and that get_post_thumbnail will be under the exceptions. Many thanks :)

I hope you’re not starting a trend too ;)

I’ve read every single post in this thread, so it’s safe to assume I’ve seen your question. If it’s not answered in the update when posted, you’re welcome to ask me again then.

366 posts WordPress Guy
  • Has referred 1+ members
  • Has sold $100+ on Envato Market
  • Has collected 50+ items on Envato Market
  • Member of the Envato Team
+5 more
Japh Envato team says

For my review theme i created a rating system with an similar backend interface like comments. Except it’s a whole separate system with his own tables. Different types of reviews could have their own criteria. Now it could be the case that different review types share the same criteria name in their list of criterias.

This makes sense to me. Agreed.


Sliders should be CPT’s if you ask me.

Agreed also.

by
by
by
by
by
by