Giving WordPress Its Own Directory

  • Resolved Basil Hendroff

    (@basilh)


    2 years, 11 months ago

    Hi,

    It’s not clear to me in this WP article, specifically the section .htaccess modification, what it refers to? Is it referring to separate versions of WP, site content or both? If it’s both, should it not be associated with Method I in the article? The way this section is presented, it seems to be a sub-heading of Method II. If it’s not both, which is it referring to content or WP? The way it’s written, it seems to be about WP. Wouldn’t annual content versions be of more interest?

    The section as it’s written is ambiguous and confusing. Can you please clarify the intent?

    • This topic was modified 2 years, 11 months ago by Yui.

    The page I need help with: [log in to see the link]

Viewing 7 replies - 1 through 7 (of 7 total)
  • George Hotelling

    (@revgeorge)

    2 years, 11 months ago

    That .htaccess code is for if you want to redirect people from the root (top level) directory into a WordPress installation in a subdirectory. For example, if you had WordPress installed at https://example.com/blog/ and you wanted people who visited https://example.com/ to be redirected to /blog/, that .htaccess code would take you to the subdirectory.

    The situation with annual installations of WordPress that is mentioned in the documentation is just an example of one way that code could be used.

    Thread Starter Basil Hendroff

    (@basilh)

    2 years, 11 months ago

    @revgeorge Thanks for responding. I agree, but I’m still confused probably because of the way the article is written. Let me rephrase using your example.

    In Method I, the address in the browser will be unchanged https://example.com, but the rewrite references the WP installation in /blog.

    What’s unclear about Method 2 is that it talks about WP core files being relocated to /blog. Does this suggest that the WP installation is now split into core and non-core (i.e. wp-content) files with the core files being moved to /blog while wp-content remains in root? Or is ‘core’ used loosely and the intent is that the whole WP installation is still moved to /blog?

    If I assume the WP installation is not split, but is moved to /blog, then if I follow the instruction, it appears I login to the site at https://example.com/blog, but visitors still access the site at https://example.com. There’s no visible redirection for visitiors Is this the expected behaviour?

    Thread Starter Basil Hendroff

    (@basilh)

    2 years, 11 months ago

    After lot’s of googling, I’ve started to get my head around this article. I still believe the way the article is written, sections of it are misleading and ambiguous. I suspect that this has occurred because the article has been cobbled together from a variety of sources over a long period of time. This is evident from the inconsistent use of the English language in various sections.

    I’ve identified three areas that could be improved:
    1. Moving a Root install to its own directory
    This section is misleading. What’s impacted is the WordPress Address URL, not the Site Address URL. The site is still accessed at https://example.com. What changes between method I and II is that WordPress is accessed at https://example.com (Method I) or https://example.com/subdir (Method II).
    2. Method II (With URL change)
    Here’s an instance where Google backfires. A search reveals there are many opinions on what constitutes WP core files. The intent of the articles is that core means the whole WP installation. I believe the best way to address this is to remove the word ‘core’ from this section.
    3. .htaccess modification
    The heading level and the placement of this section suggests that it is related to Method II. In fact, it appears to be more closely aligned to Method I.

    Apart from the identified issues, the article is full of spelling and grammatical errors.

    Moderator Yui

    (@fierevere)

    永子

    2 years, 11 months ago

    @basilh

    I have forwarded this topic link to docs team,

    atachibana

    I’d like to ask someone to re-write this page as Basil suggests. As a memorandum, I create the issue in the HelpHub repository.
    https://github.com/WordPress/HelpHub/issues/330

    You can watch and collaborate on GitHub

    Thread Starter Basil Hendroff

    (@basilh)

    2 years, 11 months ago

    Thanks Yui!

    At the bottom of every WP article there is a section titled Was this article helpful? How could it be improved? with the note:

    Feedback you send to us will go only to the folks who maintain documentation. They may reach out in case there are questions or would like to follow up feedback. But that too will stay behind the scenes.

    I’ve used that to alert the doc team, but now I’m aware of the HelpHub, is it better to raise an issue there instead, or doesn’t it matter?

    PS I’m warming to the idea of the HelpHub. The issue I find with submitting feedback through the WP article is that the feedback disappears into a black hole, whereas with the HelpHub, I can track the issue.

    Moderator Yui

    (@fierevere)

    永子

    2 years, 11 months ago

    I have quoted answer from doc’s team.
    It is better to follow in GitHub or you may want to discuss it on Slack as well.

    Channel is #docs

    To use that channel you need a Slack account. You can obtain one via these instructions.

    Slack

    Thread Starter Basil Hendroff

    (@basilh)

    2 years, 11 months ago

    Thanks, Yui!

Viewing 7 replies - 1 through 7 (of 7 total)
  • The topic ‘Giving WordPress Its Own Directory’ is closed to new replies.