16 posts
  • Bought between 1 and 9 items
  • Brazil
  • Exclusive Author
  • Has been a member for 4-5 years
theux says

^ well the point of having CPTs inside a plugin is that user can access the data when he/she changes theme.

Yes and no. You still can have your CPTs inside a plugin and make them tied to your theme. Just because your CPT is a plugin, it doesn’t mean that it will work plug and play on other themes. If the intention in having CPT in plugins is to ‘protect the buyers’; Envato will really need to review all themes and make sure that the authors don’t tie the CPTs to their theme in someway.

900 posts
  • Sold between 1 000 and 5 000 dollars
  • Most Wanted Bounty Winner
  • Has been a member for 5-6 years
  • Referred between 1 and 9 users
  • Microlancer Beta Tester
  • Serbia
  • Exclusive Author
aleluja says

They don’t have to be plug’n’play but the content must be accessible (in the dashboard) when the theme is changed.

395 posts
  • Elite Author
  • Bought between 10 and 49 items
  • Exclusive Author
  • Sold between 100 000 and 250 000 dollars
  • Has been a member for 2-3 years
  • Microlancer Beta Tester
  • Grew a moustache for the Envato Movember competition
  • Referred between 10 and 49 users
  • United Kingdom
Jaynesh says

If the theme uses standard naming conventions for the custom post types, then the data should be available when switching themes.

For example, if you have a custom post type for portfolios, all themes should use the same naming conventions for this custom post type. Therefore no plugin should be required.

900 posts
  • Sold between 1 000 and 5 000 dollars
  • Most Wanted Bounty Winner
  • Has been a member for 5-6 years
  • Referred between 1 and 9 users
  • Microlancer Beta Tester
  • Serbia
  • Exclusive Author
aleluja says

So it’s up to guessing without control? What’s so big deal to put CPT in a plugin?

395 posts
  • Elite Author
  • Bought between 10 and 49 items
  • Exclusive Author
  • Sold between 100 000 and 250 000 dollars
  • Has been a member for 2-3 years
  • Microlancer Beta Tester
  • Grew a moustache for the Envato Movember competition
  • Referred between 10 and 49 users
  • United Kingdom
Jaynesh says

So it’s up to guessing without control? What’s so big deal to put CPT in a plugin?

Let’s say the Portfolio CPT now has to be put into a plugin. Now every user will need to install the plugin to use the CPT.

When the buyer switches themes, they will now have access to the data of the previous CPT. That is great but now the buyer will have to install ANOTHER plugin for another Portfolio CPT.

This makes the entire purpose of using plugin for CPT useless because it may not be tailored to another theme.

If all themes use the same naming convention for common CPT, that data will always be available when switching themes.

900 posts
  • Sold between 1 000 and 5 000 dollars
  • Most Wanted Bounty Winner
  • Has been a member for 5-6 years
  • Referred between 1 and 9 users
  • Microlancer Beta Tester
  • Serbia
  • Exclusive Author
aleluja says

Well until there are standards for the naming it should’t be let to luck. I (and themeforest and wordpress community) don’t want to take a risk between losing access to data and having everything work nicely. I agree it would be super-awesome but currently it’s just too risky.

395 posts
  • Elite Author
  • Bought between 10 and 49 items
  • Exclusive Author
  • Sold between 100 000 and 250 000 dollars
  • Has been a member for 2-3 years
  • Microlancer Beta Tester
  • Grew a moustache for the Envato Movember competition
  • Referred between 10 and 49 users
  • United Kingdom
Jaynesh says

Well until there are standards for the naming it should’t be let to luck. I (and themeforest and wordpress community) don’t want to take a risk between losing access to data and having everything work nicely. I agree it would be super-awesome but currently it’s just too risky.

Nothing is left to luck here. If TF can enforce plugins they can enforce standards for naming.

108 posts
  • Exclusive Author
  • Sold between 10 000 and 50 000 dollars
  • United Kingdom
  • Most Wanted Bounty Winner
  • Microlancer Beta Tester
  • Referred between 1 and 9 users
  • Bought between 1 and 9 items
  • Has been a member for 1-2 years
designedbydash says


Well until there are standards for the naming it should’t be let to luck. I (and themeforest and wordpress community) don’t want to take a risk between losing access to data and having everything work nicely. I agree it would be super-awesome but currently it’s just too risky.
Nothing is left to luck here. If TF can enforce plugins they can enforce standards for naming.

I believe the idea is that themes in future should play nicely with all WP themes, including ones from WP.org and other sites. Therefore enforcing a naming convention wouldn’t work for obvious reasons.

2 posts
  • Bought between 10 and 49 items
  • Exclusive Author
  • Has been a member for 4-5 years
  • Spain
rodz says



Well until there are standards for the naming it should’t be let to luck. I (and themeforest and wordpress community) don’t want to take a risk between losing access to data and having everything work nicely. I agree it would be super-awesome but currently it’s just too risky.
Nothing is left to luck here. If TF can enforce plugins they can enforce standards for naming.
I believe the idea is that themes in future should play nicely with all WP themes, including ones from WP.org and other sites. Therefore enforcing a naming convention wouldn’t work for obvious reasons.

Having a standard naming convention for CPTs is a discussion that until now haven’t reached any consensus in WP community (as far as I know). Although leading developers are all for it.

ThemeForest is in a position where she could take the lead.

The biggest problem I see is that each theme can take a different approach when handling Custom Fields and Meta Boxes. But, as long as it is not serialized data, after switching themes, the user should be able to access the previous data in the default Custom Fields meta box.

A couple of discussions at [wp-hackers] and a great quote
Basically a plugin using Custom Post Types should follow Postel’s Law: “be conservative in what you do, be liberal in what you accept from others”
http://wordpress-hackers.1065353.n5.nabble.com/Custom-Post-Types-and-pending-incompatibilities-td24661i20.html#a24674
http://wordpress-hackers.1065353.n5.nabble.com/Community-conventions-for-custom-post-types-td39285.html#a39313
576 posts
  • Bought between 1 and 9 items
  • Exclusive Author
  • Has been a member for 3-4 years
  • Sold between 10 000 and 50 000 dollars
ChapterThemes says

Naming your functions ( in a proper way ofcourse ) and post types should always be left free for everyone.

CPT naming has nothing to do with good theme compatibility for plugin based options and features. If i call a CPT ‘portfolio’ or ‘mygreatpcptxue’, the plugin still has to work perfectly on different themes.

by
by
by
by
by
by