Woredpress.com Quick Reference Guide:
- How o create front-page <Home>
- Click Pages -> Add New in your Dashboard.
- Title this page “Home” (you can, of course, name it whatever you like).
- Type the content you want displayed on the front page of your blog and publish it.
- Write another new page.
- Title this page “Posts” (Or “blog” if you want sitename.com/blog)
- You don’t need to type content, because it won’t be displayed. Publish the page.
- Click Settings -> Reading on the left menu in your Dashboard.
- You will see the following options. Set yours to look like this:
After making these changes, posts will no longer show on the front page of your blog. The static page “Home” will show there. Visitors will need to click on the link to “Posts” page to see your posts.
- Custom Menu
- How to open menu link in new window
- Formatting Text
- Page jumping Top Bottom Anchor
- Adding meta tags
Free wordpress.com does not have an option to add meta tags, to disable page caching
meta http-equiv="cache-control”" content="max-age=0″ meta http-equiv="cache-control" content="no-cache" meta http-equiv="expires" content="Sat, 01 Sep 2001 00:00:00 GMT" meta http-equiv="pragma" content="no-cache"
Sometime you want to force the cache on one particular page\request.
You can do that by holding the “Ctrl” key while clicking reload or F5.
To disable page caching permanently in FireFox:
- Open a new window or tab in Firefox.
- Type about:config in the address bar
- Search for “cache” in the search bar and look for network.http.use-cache in the filtered results.
- Double-click it will toggle it from “true” to “false”. Default should be “true”.
1. why does Firefox keep putting sites in https
Now finding that Firefox automatically redirects its URL to an https address causing http mixed content not to display.
set the Boolean pref browser.urlbar.autoFill to false (did not solve the issue)
set the Boolean pref browser.urlbar.autoFill.typed to false (did not solve the issue)
set the Boolean pref security.mixed_content.block_active_content to false (solved the issue). But mind you, this will make your Firefox browser a little less secure!
2. Completely disable “this plugin is vulnerable and should be updated”
set the Boolean pref extensions.blocklist.enabled to false (true by default)
A warning: Turning this option to false lowers the security of your browser – not only will it stop checking for plugin vulnerabilities but Firefox will not prevent you from installing known malicious extensions that could hijack your browser or do any number of other nasty things.