Why is the additional theme directory still /wp/wp-content/themes instead of /content/themes ? about wordpress-skeleton HOT 9 CLOSED

This registers the wp core wp-content/themes directory as an ADDITIONAL theme directory, so you have access to your themes in /content/themes as well as the themes that come with WP in /wp/wp-content/themes

These two lines in wp-config.php change the default content directory so you need to register the /wp/wp-content/themes one to keep core themes:

define( 'WP_CONTENT_DIR', dirname( __FILE__ ) . '/content' );
define( 'WP_CONTENT_URL', 'http://' . $_SERVER['HTTP_HOST'] . '/content' );

from wordpress-skeleton.

I'm aware that it's additional (see the title).

But nothing in that directory can be edited, because it's a git submodule.

from wordpress-skeleton.

This is so that the themes included with WordPress are available. Without this, a default installation will break due to the lack of twentytwelve/twentythirteen.

from wordpress-skeleton.

Didn't realize that the default WP themes would still be used with something like this.
Why else the custom /content content directory ?
It's not like you can use this with an existing WP installation, so that you can keep using the themes which were already in use.
No one uses the default themes as is. All WP sites doing this would have the same images, icons, css, etc.
To me, this looks more for end users and not for theme developers. My misunderstanding.

I usually ignore the default WP themes by changing the default theme to the one I'm going to design+develop by adding the following to wp-config.php. (I changed the directory to /content so it matches this repo.)

define('WP_CONTENT_DIR', $_SERVER['DOCUMENT_ROOT'] . '/content');
define('WP_CONTENT_URL', 'http://' . $_SERVER['HTTP_HOST'] . '/content');
define('WP_DEFAULT_THEME', 'my-custom-theme-directory-name-here');

I guess this is not for me. Too bad.

from wordpress-skeleton.

You may not be using the bundled themes, but you may be using child themes that depend on them. If you don't want the bubdled themes available, just comment out that line.

from wordpress-skeleton.

That's a possibility.
Although I think, haven't tried it of course, that that would cause an uncommitted local change, and I would not be able to pull changes from this repo until I resolved this conflict.

from wordpress-skeleton.

It's not really intended for you to use this repo in perpetuity. I mean, adding plugins to your repo would also cause it to diverge. It's more of a WordPress repo "starter".

from wordpress-skeleton.

OK, I understand. It's not what I'm looking for. Too bad.

from wordpress-skeleton.

@RobertinoValue I ended up cloned this repo and then ignored the files & directories below. It's much more usable for my needs when I go to launch another site. Everyone has different needs so just make it do what makes sense for your project. You don't have to leave it exactly the way it came.

/config.php
/content/upgrade/*
/content/uploads/*
/content/themes/*
/content/plugins/*

from wordpress-skeleton.