CPTs should be in a plugin, template files should be in a theme. It does not matter that moving to another theme means that the CPTs will be displayed using index.php and single.php, the point is that there will be no data loss, which is the main point here.
This seems ok to me.
Soft Reject for the same issue.
Moving the custom post type to a plugin seems completely useless to me because :
a. You are forced to use another plugin
b. All those custom post type will NOT work properly on other themes.
So we’re forced to add another layer of complexity.
ps. I will also bundle Custom Post Type UI, thanks for the link
I use it for the last two years. I will never come back to any Adobe product
This is definitely NOT a quality theme.
Hi all ! I would like to partner with a really good graphic designer to raise the quality level of my themes. Currently i design & code all my themes but i realized i am more a coder than a designer so i would like to find some talent to partner with.
Post your portfolios here or send me a private message.
You can find my themes here : http://themeforest.net/user/mountainthemes/portfolio
It is “cool” but sublime text is better in my opinion.
Ah, i hate Adobe
I format the code manually in sublime text 2 and i don’t think it is time consuming
I have 3 github repos, one on my computer, one on an external hard drive and one on bitbucket. I use two branches, master and dev. i develop everything on dev and then i merge the branch on master just before the release.
I usually upload everything (obviously not the repo) via ftp with the sftp plugin of sublime text.