If you have accidentally created a site, or are done with a site that you have created, we ask that you please delete any unused sites.
Ho to delete your site
Note: To delete a site you must be an administrator of the site. Contributors and Editors will not be able to perform this task.
From your site’s Dashboard navigate to the Tools tab.
once in the tools tab, navigate to the ‘Delete Site’ option below.
check the checkbox saying “I’m sure I want to permanently disable my site, and I am aware I can never get it back or use sites.temple.edu/[SiteSlug] again.”
Click the blue “Delete My Site Permanatley” Button.
You will be prompted with the following message
After seeing this message, you will receive an email where you will need to click the link to confirm the deletion of your site.
Temple University Sites allows a few ways to limit access to your content. Using password protection lets you require users to enter a password before viewing a particular post or page. This will allow you to distribute a password for a post or page to anyone on the Internet, regardless if they have an AccessNet username and password.
Note: This should not be your AccessNet password. You will need to give users this password to access a protected page, and you should never give anyone your AccessNet password.
To require users to login with their Temple AccessNet username and password please see Managing Site Privacy.
Post Visibility Settings
Once you publish a WordPress post (or Page), it is visible to the public (by default). In WordPress terms, this means a post with a Published status has a default visibility ofPublic, based on the settings in the Publish box of a Edit Post Screen.
WordPress also offers two less public options for your post’s Content Visibility. Clicking the “Edit” link next to Visibility: Public reveals three radio buttons:
Public is selected by default.
Checking Password protected reveals a text field for entering a password, that will be required to view that post. The password is limited to 20 characters. This should not be your AccessNet password. This will be a password you will distribute to all the users you want to view this post or page.
Checking Private makes your post visible only to your site’s Users with the role ofAdministrator or Editor.
Visibility Settings
In Gutenberg Editor
When you’re done editing the post’s visibility, click the “OK” button. You should now see your post’s new setting, e.g., Visibility: Password Protected.Remember: a setting change does not take effect until you click the “Publish” button (or “Update” if the post is already published.)
Finding or Changing a Password
Only an Administrator, Editor, or the post’s Author can change a post’s password or visibility setting. To do so, use the “Visibility: Edit” link again. These settings are also available using the post’s Quick Edit link in the All Posts Screen.
The Visibility “Edit” link (or “Quick Edit”) is also a good way to reveal a forgotten post password.
Password Protected Posts
Visibility: Password Protected
WordPress displays a password-protected post differently. It makes these changes to the post’s:
Title– Adds the text “Protected: ” before the post Title.
Excerpt– Instead of the post Excerpt, prints this text: “There is no excerpt because this is a protected post.”
Content– Instead of the post Content, prints a password form with this text: “This post is password protected. To view it please enter your password below:”
So, a password-protected post with a title of “My Post” would display like this:
Password Protecting Many Posts and Pages
WordPress stores this password in a browser cookie so readers don’t have to re-enter passwords if they visit the same page multiple times. Furthermore, if multiple posts use the same password, the reader will only have to enter the password once to access every post (see caveat below).
WordPress will only track one password at a time. Therefore, if two posts use two different passwords, entering the password for post A, then entering the password for post B means that revisiting post A (or any post which shares its password) will require the user to re-enter the password for post A.
Go to Settings->Reading in the admin area to manage your site visibility. Here are the available options:
Allow search engines to index this site
Discourage search engines from indexing this site
I would like my blog to be visible only to registered users of Temple University Sites
I would like my blog to be visible only to registered users I add to “Temple University Sites”
I would like “Temple University Sites” to be visible only to Admins.
Allow search engines to index this site
This setting will make your site open to the entire world. Search engines will be able to crawl your site and send users to your content.
Discourage search engines from indexing this site would like my blog to be visible only to registered users of Temple University Sites
This setting will still make your site open to the entire world, but it will tell search engines such as Google, Bing, and Yahoo! not to send users to your site. So, unless someone guesses your URL, the site is hidden from the world, but anyone with a link can still access your site. This is a good option to select while you are still building your site but are not ready for primetime.
I would like my blog to be visible only to registered users of Temple University Sites
This setting will make any user login with their Temple AccessNet username and password before accessing your site. No search engines or outside users will be able to see any content.
I would like my blog to be visible only to registered users I add to “Temple University Sites”
This is a good option for private group collaboration. Only users at Temple who you select will be able to login and view your site. No search engines or outside users will be able to see any content.
I would like “Temple University Sites” to be visible only to Admins
At this point, your site is completely locked down. No search engines or users will be able to see any content other than site administrators.
You must be logged in to post a comment.