Charles
Forum Replies Created
-
Well, in case anyone comes across this, I found the problem.
I have my sites setup on my host like this:
public_html/example1/wordpress
public_html/example2/wordpress
public_html/example3/wordpressI was trying to pull up example1.com, where the wordpress files are installed at example1.com/wordpress.
The problem was I accidentally uploaded an old index.php file in the root of public_html. So it was public_html/index.php. And that was screwing my site up. So…the moral of the story is….be careful where you place files!
Also, I have another site on this Bluehost account setup the same way and it works just fine.
Forum: Fixing WordPress
In reply to: Custom Rewrite Slug not workingOkay, after trying some changes, I CAN change the custom slog on the custom post type…
BUT not to the way I’d ideally like it. If I change it to a simple sinlge word, I’m fine.
1) If I change it to “some/thing” (two words separated by a slash, it doesn’t work. Is it possible to use a slash in custom slugs? I’d like to do this to give the illusion the paricular posts is under a particular general directory.
2) If a slash doesn’t work in this format, is there a way to make the post name show up in the URL after a variable name. This one is complicated.
I’m using Advanced Custom Fields and one of my custom fields for each Type B post is a Relationship field, which associates each Type B post with it’s corresponding Type A custom post type post. Say, for axample, I have a Corolla post, that is then associated with the Type A post, which in this case would be Toyota. So I’d want the URL to be example.com/toyota/corolla. Is something like this possible?
Forum: Plugins
In reply to: [Custom Post Type UI] Custom Rewrite Slug not workingOkay, after trying some changes, I CAN change the custom slog on the custom post type…
BUT not to the way I’d ideally like it. If I change it to a simple sinlge word, I’m fine.
1) If I change it to “some/thing” (two words separated by a slash, it doesn’t work. Is it possible to use a slash in custom slugs? I’d like to do this to give the illusion the paricular posts is under a particular general directory.
2) If a slash doesn’t work in this format, is there a way to make the post name show up in the URL after a variable name. This one is complicated.
I’m using Advanced Custom Fields and one of my custom fields for each Type B post is a Relationship field, which associates each Type B post with it’s corresponding Type A custom post type post. Say, for axample, I have a Corolla post, that is then associated with the Type A post, which in this case would be Toyota. So I’d want the URL to be example.com/toyota/corolla. Is something like this possible?
Forum: Fixing WordPress
In reply to: Changing the wp-content folder name on a local MAMP installationTried simply putting in “/localhost:8888/” but that’s not cutting it for the DIR.
It seems what I want is just a filtered version of the get_post_link. I just can’t find any examples that illustrate this, a way to pull up that archive, limited to posts that match certain criteria.
Forum: Networking WordPress
In reply to: Six questions about multisite setup (subdomains)Oh okay, so once any admin logs in to any site, he/she has access to the entire network of sites (unless otherwise specified).
Also, as far as installing WP Multisite in its own directory, are you sure that doesn’t work? It looks like as of version 3.5, Multisite supports that sort of setup.
Forum: Networking WordPress
In reply to: Six questions about multisite setup (subdomains)Ahh, now that helps out. I didn’t know you can’t install WP in its own directory and then not have subdomains. That’s a shame.
As for those couple tricky ones, I’ll try to explain a bit more.
1) Say I have a regular, single WP site at example.com. Then I turn it into a multisite network. So now I have example.com, and site1.example.com, site2.example.com, etc.
The original single WP site I had at example.com….how do I access the WP administration for just that one particular site. It seems if I go to example.com/wp-login.php (as I did before the conversion), I’d then access the super admin for all sites. Or, once I convert to multisite. do I have to assign that original site to a subdomain, like original.example.com?
2) I was thinking…what if I have site1.example.com, site2.example.com, site3.example.com as apart of a multisite network. Then on site2 I decide I’d like a bunch of related sites to it, another network–could I launch a network within a network? But it seems like the answer is no, and that I should then install a new, fresh multisite network at the domain site2.example.com and run with that.
Forum: Fixing WordPress
In reply to: Primary nav menuIt’s possible, it’s all a matter of customizing the CSS. Right now the main body has a white background, as does the menu. In order to see water at the very top of the site, the main content container could be pushed down a bit with something like
.site-container {margin-top:50px;}Ahh okay, cool. I just wasn’t sure if I was missing something bigger there, but really it’s mostly an issue of convenience. Still….thanks for your work on this plugin! I love it.
Oh that’s not actually what I was getting at, but you raise an interesting point as well.
For clarification, I’ll distinguish betweeen method 1 and method 2.
METHOD 1: In the CPT UI plugin, when you go to add a new CPT (or edit one), at the bottom there are advanced options. At the bottom of those, there are checkboxes for built-in taxonomies — they include the usual categories, tags, and whatever custom ones you’ve created.
METHOD 2: BUT ALSO, when you create a new taxonomy, you have the option to check a box that will attach that new taxonomy to a particular post type.
It seems as if both methods accomplish the task of linking a custon taxonomy to a custon post type. My question is why are there two different ways of doing the same thing.
After clicking around a bit, I see one difference between the two. When linking a taxonomy to a CPT in method 1, that taxonomy also then shows up in the admin columns (when you view all posts in your post type in a table). Buf if you attach a taxonomy to a CPT using method 2, that taxonomy isn’t a part of that admin columns view.
Are there any other differences? Or any other compelling reasons to use one method over the other, or both?