OXIESEC PANEL

Name	Size	Modified	Perms
📁 ..	-	09/06/2025 12:29:47 PM	rwxr-xr-x
📄 comment-generate.feature	905 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 comment-list.feature	1.04 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 comment-meta.feature	2.33 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 comment-recount.feature	877 bytes	05/14/2024 01:45:25 PM	rw-r--r--
📄 comment.feature	13.17 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 menu-item.feature	7.68 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 menu-location.feature	1.88 KB	05/14/2024 01:45:25 PM	rw-r--r--
📄 menu.feature	2.05 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 network-meta.feature	418 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 option-get-autoload.feature	826 bytes	05/14/2024 01:45:25 PM	rw-r--r--
📄 option-list.feature	5.89 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 option-pluck-patch.feature	7.73 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 option-set-autoload.feature	1.96 KB	05/14/2024 01:45:25 PM	rw-r--r--
📄 option.feature	8.17 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 post-create-duplicate.feature	2.79 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 post-generate.feature	5.71 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 post-meta-clean-duplicates.feature	1.67 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 post-meta.feature	14.7 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 post-term.feature	5.37 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 post-type.feature	1.46 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 post-url-to-id.feature	564 bytes	05/14/2024 01:45:25 PM	rw-r--r--
📄 post.feature	16.49 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 signup.feature	5.52 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 site-create.feature	3.36 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 site-empty.feature	4.2 KB	05/14/2024 01:45:25 PM	rw-r--r--
📄 site-generate.feature	3.38 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 site-meta.feature	864 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 site-option-pluck-patch.feature	6.83 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 site-option.feature	3.64 KB	05/14/2024 01:45:25 PM	rw-r--r--
📄 site.feature	20.81 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 taxonomy.feature	5.6 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 term-generate.feature	810 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 term-meta.feature	849 bytes	03/20/2024 11:17:27 AM	rw-r--r--
📄 term-migrate.feature	2.97 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 term-recount.feature	1.6 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 term.feature	8 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 user-application-password.feature	10.26 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 user-generate.feature	1.05 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 user-import-csv.feature	5.32 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 user-list.feature	1.09 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 user-meta.feature	7.31 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 user-reset-password.feature	2.12 KB	03/20/2024 11:17:27 AM	rw-r--r--
📄 user-session.feature	944 bytes	09/06/2025 12:29:47 PM	rw-r--r--
📄 user-term.feature	2.82 KB	09/06/2025 12:29:47 PM	rw-r--r--
📄 user.feature	20.52 KB	09/06/2025 12:29:47 PM	rw-r--r--

Editing: site.feature

Feature: Manage sites in a multisite installation

Scenario: Create a site
    Given a WP multisite install

When I try `wp site create --slug=first --network_id=1000`
    Then STDERR should contain:
      """
      Network with id 1000 does not exist.
      """
    And STDOUT should be empty
    And the return code should be 1

Scenario: Create a subdomain site
    Given a WP multisite subdomain install

When I run `wp site create --slug=first`
    Then STDOUT should not be empty

When I run `wp site list --fields=blog_id,url`
    Then STDOUT should be a table containing rows:
      | blog_id | url                       |
      | 1       | https://example.com/       |
      | 2       | http://first.example.com/ |

When I run `wp site list --format=ids`
    Then STDOUT should be:
      """
      1 2
      """

When I run `wp site list --site_id=2 --format=ids`
    Then STDOUT should be empty

When I run `wp --url=first.example.com option get home`
    Then STDOUT should be:
      """
      http://first.example.com
      """

Scenario: Delete a site by id
    Given a WP multisite subdirectory install

When I run `wp site create --slug=first --porcelain`
    Then STDOUT should be a number
    And save STDOUT as {SITE_ID}
    And I run `wp site list --site__in={SITE_ID} --field=url | sed -e's,^\(.*\)://.*,\1,g'`
    And save STDOUT as {SCHEME}

When I run `wp site list --fields=blog_id,url`
    Then STDOUT should be a table containing rows:
      | blog_id | url                           |
      | 1       | https://example.com/          |
      | 2       | {SCHEME}://example.com/first/ |

When I run `wp site list --field=url`
    Then STDOUT should be:
      """
      https://example.com/
      {SCHEME}://example.com/first/
      """

When I try `wp site delete 1`
    Then STDERR should be:
      """
      Error: You cannot delete the root site.
      """
    And STDOUT should be empty
    And the return code should be 1

When I run `wp site delete {SITE_ID} --yes`
    Then STDOUT should be:
      """
      Success: The site at '{SCHEME}://example.com/first/' was deleted.
      """

When I try the previous command again
    Then the return code should be 1

Scenario: Filter site list
    Given a WP multisite install

When I run `wp site list --field=url --blog_id=2`
    Then STDOUT should be:
      """
      {SCHEME}://example.com/first/
      """

Scenario: Filter site list by user
    Given a WP multisite install

When I run `wp site create --slug=first --porcelain`
    Then STDOUT should be a number
    And save STDOUT as {SITE_ID}
    And I run `wp site list --blog_id={SITE_ID} --field=url`
    And save STDOUT as {SITE_URL}

When I run `wp user create newuser newuser@example.com --porcelain --url={SITE_URL}`
    Then STDOUT should be a number
    And save STDOUT as {USER_ID}
    And I run `wp user get {USER_ID} --field=user_login`
    And save STDOUT as {USER_LOGIN}

When I run `wp site list --field=url --site_user={USER_LOGIN}`
    Then STDOUT should be:
      """
      {SITE_URL}
      """

When I try `wp site list --site_user=invalid_user`
    Then the return code should be 1
    And STDERR should be:
      """
      Error: Invalid user ID, email or login: 'invalid_user'
      """

When I run `wp user remove-role {USER_LOGIN} --url={SITE_URL}`
    Then STDOUT should contain:
      """
      Success: Removed
      """

When I run `wp site list --field=url --site_user={USER_LOGIN}`
    Then STDOUT should be empty

Scenario: Delete a site by slug
    Given a WP multisite install

When I run `wp site create --slug=first`
    Then STDOUT should contain:
      """
      Success: Site 2 created: http
      """
    And STDOUT should contain:
      """
      ://example.com/first/
      """

When I run `wp site delete --slug=first --yes`
    Then STDOUT should contain:
      """
      ://example.com/first/' was deleted.
      """

When I try the previous command again
    Then the return code should be 1

When I run `wp site create --slug=42`
    Then STDOUT should contain:
      """
      Success: Site 3 created: http
      """
    And STDOUT should contain:
      """
      ://example.com/42/
      """

When I run `wp site delete --slug=42 --yes`
    Then STDOUT should contain:
      """
      ://example.com/42/' was deleted.
      """

When I try the previous command again
    Then STDERR should contain:
      """
      Error: Could not find site with slug '42'.
      """
    And the return code should be 1

Scenario: Archive a site by a numeric slug
    Given a WP multisite install

When I run `wp site create --slug=42`
    Then STDOUT should contain:
      """
      Success: Site 2 created: http
      """
    And STDOUT should contain:
      """
      ://example.com/42/
      """

When I run `wp site archive --slug=42`
    Then STDOUT should contain:
      """
      Success: Site 2 archived.
      """

When I try `wp site archive --slug=43`
    Then STDERR should contain:
      """
      Error: Could not find site with slug '43'.
      """
    And the return code should be 1

Scenario: Get site info
    Given a WP multisite install

When I run `wp site url {SITE_ID}`
    Then STDOUT should be:
      """
      {SCHEME}://example.com/first/
      """

When I run `wp site create --slug=second --porcelain`
    Then STDOUT should be a number
    And save STDOUT as {SECOND_ID}
    And I run `wp site list --site__in={SECOND_ID} --field=url | sed -e's,^\(.*\)://.*,\1,g'`
    And save STDOUT as {SECOND_SCHEME}

When I run `wp site url {SECOND_ID} {SITE_ID}`
    Then STDOUT should be:
      """
      {SECOND_SCHEME}://example.com/second/
      {SCHEME}://example.com/first/
      """

Scenario: Not providing a site ID or slug when running an update blog status command should throw an error
    Given a WP multisite install

When I try `wp site private`
    Then the return code should be 1
    And STDERR should be:
      """
      Error: Please specify one or more IDs of sites, or pass the slug for a single site using --slug.
      """
    And STDOUT should be empty

Scenario: Site IDs or a slug can be provided, but not both.
    Given a WP multisite install
    And I run `wp site create --slug=first --porcelain`

When I try `wp site private 1 --slug=first`
    Then the return code should be 1
    And STDERR should be:
      """
      Error: Please specify one or more IDs of sites, or pass the slug for a single site using --slug.
      """

Scenario: Errors for an invalid slug
    Given a WP multisite install

When I try `wp site private --slug=first`
    Then the return code should be 1
    And STDERR should be:
      """
      Error: Could not find site with slug 'first'.
      """

Scenario: Archive/unarchive a site
    Given a WP multisite install
    And I run `wp site create --slug=first --porcelain`
    And save STDOUT as {FIRST_SITE}
    And I run `wp site create --slug=second --porcelain`
    And save STDOUT as {SECOND_SITE}

When I run `wp site archive {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} archived.
      """

When I run `wp site list --fields=blog_id,archived`
    Then STDOUT should be a table containing rows:
      | blog_id      | archived |
      | {FIRST_SITE} | 1        |

When I try `wp site archive {FIRST_SITE} {SECOND_SITE}`
    Then STDERR should be:
      """
      Warning: Site {FIRST_SITE} already archived.
      """
    And STDOUT should be:
      """
      Success: Site {SECOND_SITE} archived.
      """
    And the return code should be 0

When I run `wp site list --fields=blog_id,archived`
    Then STDOUT should be a table containing rows:
      | blog_id      | archived |
      | {FIRST_SITE} | 1        |

When I run `wp site unarchive {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} unarchived.
      """

When I run `wp site list --fields=blog_id,archived`
    Then STDOUT should be a table containing rows:
      | blog_id      | archived |
      | {FIRST_SITE} | 0        |

When I try `wp site archive 1`
    Then STDERR should be:
      """
      Warning: You are not allowed to change the main site.
      """
    And STDOUT should be empty
    And the return code should be 0

Scenario: Activate/deactivate a site
    Given a WP multisite install
    And I run `wp site create --slug=first --porcelain`
    And save STDOUT as {FIRST_SITE}
    And I run `wp site create --slug=second --porcelain`
    And save STDOUT as {SECOND_SITE}

When I run `wp site deactivate {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} deactivated.
      """

When I run `wp site list --fields=blog_id,deleted`
    Then STDOUT should be a table containing rows:
      | blog_id      | deleted |
      | {FIRST_SITE} | 1       |

When I try `wp site deactivate {FIRST_SITE} {SECOND_SITE}`
    Then STDERR should be:
      """
      Warning: Site {FIRST_SITE} already deactivated.
      """
    And STDOUT should be:
      """
      Success: Site {SECOND_SITE} deactivated.
      """
    And the return code should be 0

When I run `wp site list --fields=blog_id,deleted`
    Then STDOUT should be a table containing rows:
      | blog_id      | deleted |
      | {FIRST_SITE} | 1       |

When I run `wp site activate {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} activated.
      """

When I run `wp site list --fields=blog_id,deleted`
    Then STDOUT should be a table containing rows:
      | blog_id      | deleted |
      | {FIRST_SITE} | 0       |

When I try `wp site deactivate 1`
    Then STDERR should be:
      """
      Warning: You are not allowed to change the main site.
      """
    And STDOUT should be empty
    And the return code should be 0

Scenario: Mark/remove a site from spam
    Given a WP multisite install
    And I run `wp site create --slug=first --porcelain`
    And save STDOUT as {FIRST_SITE}
    And I run `wp site create --slug=second --porcelain`
    And save STDOUT as {SECOND_SITE}

When I run `wp site spam {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} marked as spam.
      """

When I run `wp site list --fields=blog_id,spam`
    Then STDOUT should be a table containing rows:
      | blog_id      | spam |
      | {FIRST_SITE} | 1    |

When I try `wp site spam {FIRST_SITE} {SECOND_SITE}`
    Then STDERR should be:
      """
      Warning: Site {FIRST_SITE} already marked as spam.
      """
    And STDOUT should be:
      """
      Success: Site {SECOND_SITE} marked as spam.
      """
    And the return code should be 0

When I run `wp site list --fields=blog_id,spam`
    Then STDOUT should be a table containing rows:
      | blog_id      | spam |
      | {FIRST_SITE} | 1    |

When I run `wp site unspam {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} removed from spam.
      """

When I run `wp site list --fields=blog_id,spam`
    Then STDOUT should be a table containing rows:
      | blog_id      | spam |
      | {FIRST_SITE} | 0    |

When I try `wp site spam 1`
    Then STDERR should be:
      """
      Warning: You are not allowed to change the main site.
      """
    And STDOUT should be empty
    And the return code should be 0

Scenario: Mark/remove a site as mature
    Given a WP multisite install
    And I run `wp site create --slug=first --porcelain`
    And save STDOUT as {FIRST_SITE}
    And I run `wp site create --slug=second --porcelain`
    And save STDOUT as {SECOND_SITE}

When I run `wp site mature {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} marked as mature.
      """

When I run `wp site list --fields=blog_id,mature`
    Then STDOUT should be a table containing rows:
      | blog_id      | mature |
      | {FIRST_SITE} | 1    |

When I try `wp site mature {FIRST_SITE} {SECOND_SITE}`
    Then STDERR should be:
      """
      Warning: Site {FIRST_SITE} already marked as mature.
      """
    And STDOUT should be:
      """
      Success: Site {SECOND_SITE} marked as mature.
      """
    And the return code should be 0

When I run `wp site list --fields=blog_id,mature`
    Then STDOUT should be a table containing rows:
      | blog_id      | mature |
      | {FIRST_SITE} | 1    |

When I run `wp site unmature {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} marked as unmature.
      """

When I run `wp site list --fields=blog_id,mature`
    Then STDOUT should be a table containing rows:
      | blog_id      | mature |
      | {FIRST_SITE} | 0    |

When I try `wp site unmature 1`
    Then STDERR should be:
      """
      Warning: You are not allowed to change the main site.
      """
    And STDOUT should be empty
    And the return code should be 0

Scenario: Set/Unset a site as public
    Given a WP multisite install
    And I run `wp site create --slug=first --porcelain`
    And save STDOUT as {FIRST_SITE}
    And I run `wp site create --slug=second --porcelain`
    And save STDOUT as {SECOND_SITE}

When I run `wp site private {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} marked as private.
      """

When I run `wp site list --fields=blog_id,public`
    Then STDOUT should be a table containing rows:
      | blog_id      | public |
      | {FIRST_SITE} | 0    |

When I try `wp site private {FIRST_SITE} {SECOND_SITE}`
    Then STDERR should be:
      """
      Warning: Site {FIRST_SITE} already marked as private.
      """
    And STDOUT should be:
      """
      Success: Site {SECOND_SITE} marked as private.
      """
    And the return code should be 0

When I run `wp site list --fields=blog_id,public`
    Then STDOUT should be a table containing rows:
      | blog_id      | public |
      | {FIRST_SITE} | 0    |

When I run `wp site public {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} marked as public.
      """

When I run `wp site list --fields=blog_id,public`
    Then STDOUT should be a table containing rows:
      | blog_id      | public |
      | {FIRST_SITE} | 1    |

When I try `wp site private 1`
    Then STDERR should be:
      """
      Warning: You are not allowed to change the main site.
      """
    And STDOUT should be empty
    And the return code should be 0

Scenario: Permit CLI operations against archived and suspended sites
    Given a WP multisite install
    And I run `wp site create --slug=first --porcelain`
    And save STDOUT as {FIRST_SITE}

When I run `wp site archive {FIRST_SITE}`
    Then STDOUT should be:
      """
      Success: Site {FIRST_SITE} archived.
      """

When I run `wp --url=example.com/first option get home`
    Then STDOUT should contain:
      """
      ://example.com/first
      """

Scenario: Create site with title containing slash
    Given a WP multisite install
    And I run `wp site create --slug=mysite --title="My\Site"`
    Then STDOUT should not be empty

When I run `wp option get blogname --url=example.com/mysite`
    Then STDOUT should be:
      """
      My\Site
      """

Scenario: Activate/deactivate a site by slug
    Given a WP multisite install

When I run `wp site deactivate --slug=first`
    Then STDOUT should contain:
      """
      Success: Site 2 deactivated.
      """

When I try `wp site deactivate --slug=first`
    Then STDERR should be:
      """
      Warning: Site 2 already deactivated.
      """

When I run `wp site activate --slug=first`
    Then STDOUT should be:
      """
      Success: Site 2 activated.
      """

Scenario: Archive/unarchive a site by slug
    Given a WP multisite install

When I run `wp site archive --slug=first`
    Then STDOUT should contain:
      """
      Success: Site 2 archived.
      """

When I try `wp site archive --slug=first`
    Then STDERR should be:
      """
      Warning: Site 2 already archived.
      """

When I run `wp site unarchive --slug=first`
    Then STDOUT should be:
      """
      Success: Site 2 unarchived.
      """

Scenario: Mark/remove a site by slug from spam
    Given a WP multisite install

When I run `wp site spam --slug=first`
    Then STDOUT should contain:
      """
      Success: Site 2 marked as spam.
      """

When I try `wp site spam --slug=first`
    Then STDERR should be:
      """
      Warning: Site 2 already marked as spam.
      """

When I run `wp site unspam --slug=first`
    Then STDOUT should be:
      """
      Success: Site 2 removed from spam.
      """

Scenario: Mark/remove a site by slug as mature
    Given a WP multisite install

When I run `wp site mature --slug=first`
    Then STDOUT should contain:
      """
      Success: Site 2 marked as mature.
      """

When I try `wp site mature --slug=first`
    Then STDERR should be:
      """
      Warning: Site 2 already marked as mature.
      """

When I run `wp site unmature --slug=first`
    Then STDOUT should be:
      """
      Success: Site 2 marked as unmature.
      """

Scenario: Set/Unset a site by slug as public
    Given a WP multisite install

When I run `wp site private --slug=first`
    Then STDOUT should contain:
      """
      Success: Site 2 marked as private.
      """

When I try `wp site private --slug=first`
    Then STDERR should be:
      """
      Warning: Site 2 already marked as private.
      """

When I run `wp site public --slug=first`
    Then STDOUT should be:
      """
      Success: Site 2 marked as public.
      """