Template: Sticky

This is a sticky post.

There are a few things to verify:

  • The sticky post should be distinctly recognizable in some way in comparison to normal posts. You can style the .sticky class if you are using the post_class() function to generate your post classes, which is a best practice.
  • They should show at the very top of the blog index page, even though they could be several posts back chronologically.
  • They should still show up again in their chronologically correct postion in time, but without the sticky indicator.
  • If you have a plugin or widget that lists popular posts or comments, make sure that this sticky post is not always at the top of those lists unless it really is popular.

Markup: Title With Special Characters

Putting special characters in the title should have no adverse effect on the layout or functionality.

Special characters in the post title have been known to cause issues with JavaScript when it is minified, especially in the admin when editing the post itself (ie. issues with metaboxes, media upload, etc.).

Latin Character Tests

This is a test to see if the fonts used in this theme support basic Latin characters.

! # $ % & ( ) *
+ , . / 0 1 2 3 4
5 6 7 8 9 : ; > = <
? @ A B C D E F G H
I J K L M N O P Q R
S T U V W X Y Z [
] ^ _ ` a b c d e f
g h i j k l m n o p
q r s t u v w x y z
{ | } ~

Markup: Title With Markup

Verify that:

  • The post title renders the word “with” in italics and the word “markup” in bold.
  • The post title markup should be removed from the browser window / tab.

Add images to pages

  • Jesus
  • Stations of the cross
  • Mysteries of Rosary
    • Glorious
    • Joyful
    • Sorrowful
    • Luminious
  • Churches
  • Holy Land
  • Saints

changed .htacess

Securing wp-includes

A second layer of protection can be added where scripts are generally not intended to be accessed by any user. One way to do that is to block those scripts using mod_rewrite in the .htaccess file. Note: to ensure the code below is not overwritten by WordPress, place it outside the # BEGIN WordPress and # END WordPress tags in the .htaccess file. WordPress can overwrite anything between these tags.

# Block the include-only files.
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^wp-admin/includes/ - [F,L]
RewriteRule !^wp-includes/ - [S=3]
RewriteRule ^wp-includes/[^/]+\.php$ - [F,L]
RewriteRule ^wp-includes/js/tinymce/langs/.+\.php - [F,L]
RewriteRule ^wp-includes/theme-compat/ - [F,L]
</IfModule>

 


use jetpack locally

added use jetpack locally plugin. this lets jetpack to run with private ip.  don’t want this plugin in production or we want it disabled.


Edge Case: Nested And Mixed Lists

Nested and mixed lists are an interesting beast. It’s a corner case to make sure that

  • Lists within lists do not break the ordered list numbering order
  • Your list styles go deep enough.

Ordered – Unordered – Ordered

  1. ordered item
  2. ordered item
    • unordered
    • unordered
      1. ordered item
      2. ordered item
  3. ordered item
  4. ordered item

Ordered – Unordered – Unordered

  1. ordered item
  2. ordered item
    • unordered
    • unordered
      • unordered item
      • unordered item
  3. ordered item
  4. ordered item

Unordered – Ordered – Unordered

  • unordered item
  • unordered item
    1. ordered
    2. ordered
      • unordered item
      • unordered item
  • unordered item
  • unordered item

Unordered – Unordered – Ordered

  • unordered item
  • unordered item
    • unordered
    • unordered
      1. ordered item
      2. ordered item
  • unordered item
  • unordered item