Jewelsnorth
Forum Replies Created
-
Forum: Themes and Templates
In reply to: Sidebar on job board themeI’ve edited the stylesheet and when I add something to the #sidebar block above, I can get the sidebar to appear in the container. If I move the get_sidebar routine elsewhere in the stylesheet, the sidebar appears above or below the main content. I’ve tried playing with the clear and float lines as well.
I’m a newbie to CSS. The theme seems to allow sidebars, but they’re turned off. Has anyone used else used the same theme with sidebars?
Forum: Fixing WordPress
In reply to: Redirecting 404 errors to 410Hmm, I’m wondering if it might work to use a Post Expiration plugin to move the posts into a new category after a period of X days. Then set the sitemap to Noindex that category.
It would require a bit more processing on the server side, but would that cause the old links to drop from the search engines when they’re next crawled?
Forum: Fixing WordPress
In reply to: Redirecting 404 errors to 410If I set a post to draft it turns into a 404, would it still they remain indexed by search engines and generate errors?
Forum: Fixing WordPress
In reply to: Redirecting 404 errors to 410t31os_, that makes sense. 🙂 I wasn’t thinking about WordPress intuitively knowing which should be 404s vs. 410s, but rather simply assuming that any 404 should be a 410.
The board will have job posts that get stale after a certain date. I don’t want to leave the posts archived because job seekers get frustrated looking finding outdated entries. Likewise, deleting everything old and leaving 404s would only be accepted by search engines for just so long before I’d be penalized.
Where I’m going I’d be thinking of using a hacked together “404-type page” for 410 redirects so I can still give readers a list of similar options…. if I can get the 410 redirect working that is.
Forum: Fixing WordPress
In reply to: Redirecting 404 errors to 410I’m not sure either. The .htaccess exerpt I got from someone else and wasn’t necessarily applicable to a WordPress environment.
What I’d like to occur is that instead of getting a 404 error for any posts are deleted, can a 410 error be generated (and ideally the request redirected to a custom 410 page or even index.php).
Is this possible?
Edited to add: Someone on another forum unfamiliar with WP mentioned that
because articles are generated dynamically, the !-f test (which checks if the file actually exists on the hard drive) will always be false (or true, if it is looking for the article-creating file).
The workaround might be to hack the error document that is being served. You can alter the file so that if the request is for a deleted article, it sends a 410 error message instead of a 404 message.
Does this seem reasonable and what might this look like?
Forum: Fixing WordPress
In reply to: Redirecting 404 errors to 410I tried this (without the error document which I haven’t added yet):
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{LA-U:REQUEST_FILENAME} !-f
RewriteCond %{LA-U:REQUEST_FILENAME} !-d
RewriteRule (.*) – [G]
</IfModule>
# END WordPresbut it called the rewrite rules before the request is mapped to the file system to the value contained in REQUEST_FILENAME is the same as REQUEST_URI. This always fails and gives me a 410 for all the pages/posts except for index.php.
Forum: Fixing WordPress
In reply to: Redirecting 404 errors to 410If I could get the 410 error to work in the .htaccess, I’d add a another statement: ErrorDocument 410 /410.php