WordPress DK Forum Topic: Mit seneste blogpost redirecter til forsiden

WordPress DK Forum Topic: Mit seneste blogpost redirecter til forsiden http://wp-danmark.dk/forum/topic/mit-seneste-blogpost-redirecter-til-forsiden-3 WordPress DK Forum Topic: Mit seneste blogpost redirecter til forsiden da-DK Sun, 25 Oct 2026 17:14:56 +0000 http://bbpress.org/?v=1.0.1 <![CDATA[Søg]]> q http://wp-danmark.dk/forum/search.php AntonAKH om "Mit seneste blogpost redirecter til forsiden" http://wp-danmark.dk/forum/topic/mit-seneste-blogpost-redirecter-til-forsiden-3#post-59509 man, 27 okt 2014 16:02:36 +0000 AntonAKH 59509@http://wp-danmark.dk/forum/ Hej alle, Jeg står med et problem der er ved at drive mig til vanvid, og kan ikke få hjælp det hostingfirma jeg har mit website hos. Det som er problemstillingen er, at når jeg trykker på det seneste blogindlæg (link <a href="http://antonhoelstad.dk/bedste-plugins-social-synlighed-wordpress/">her</a>) bliver jeg 301-redirected til forsiden. Den har gjort det med alle blogindlæg jeg har udgivet, og det altid det nyeste som har denne problemstilling. Jeg har prøvet at deaktivere alle plugins, sætte min .htaccess tilbage til standard, ændret i permalinkstrukturen – og jeg er løbet tør for idéer. Har forsøgt at Google mig frem til en mulighed, men kan ikke finde andre med det samme problem som mig. Hvis du skal prøve at få den samme fejl, så gå på forsiden <a href="http://antonhoelstad.dk/">her</a> og tryk på det seneste blogindlæg i bunden, som lige nu er ”De bedste plugins for social synlighed til Wordpress”. Det er et problem jeg har haft fra starten af installationen mener jeg, men at det er noget som er gået væk og kommet igen over nogle gange. Meebox som jeg hoster det hos siger at det ikke er noget fra deres ende af der fejler, og at jeg må spørge nogle wordpress guruer – og det gør jeg så her! Jeg har brugt nogle plugins til at beskytte mit website og lave hastighedsoptimering, herunder iThemes Security og W3 Total Cache. Her er min .htaccess-fil: <code># BEGIN iThemes Security # BEGIN Tweaks # Rules to block access to WordPress specific files <files .htaccess> Order allow,deny Deny from all </files> <files readme.html> Order allow,deny Deny from all </files> <files readme.txt> Order allow,deny Deny from all </files> <files install.php> Order allow,deny Deny from all </files> <files wp-config.php> Order allow,deny Deny from all </files> # Rules to disable XML-RPC <files xmlrpc.php> Order allow,deny Deny from all </files> # Rules to disable directory browsing Options -Indexes <IfModule mod_rewrite.c> RewriteEngine On # Rules to protect wp-includes RewriteRule ^wp-admin/includes/ - [F] RewriteRule !^wp-includes/ - [S=3] RewriteCond %{SCRIPT_FILENAME} !^(.*)wp-includes/ms-files.php RewriteRule ^wp-includes/[^/]+\.php$ - [F] RewriteRule ^wp-includes/js/tinymce/langs/.+\.php - [F] RewriteRule ^wp-includes/theme-compat/ - [F] # Rules to prevent php execution in uploads RewriteRule ^(.*)/uploads/(.*).php(.?) - [F] # Rules to block suspicious URIs RewriteCond %{QUERY_STRING} \.\.\/ [NC,OR] RewriteCond %{QUERY_STRING} ^.*\.(bash|git|hg|log|svn|swp|cvs) [NC,OR] RewriteCond %{QUERY_STRING} etc/passwd [NC,OR] RewriteCond %{QUERY_STRING} boot\.ini [NC,OR] RewriteCond %{QUERY_STRING} ftp\: [NC,OR] RewriteCond %{QUERY_STRING} http\: [NC,OR] RewriteCond %{QUERY_STRING} https\: [NC,OR] RewriteCond %{QUERY_STRING} (\<|%3C).*script.*(\>|%3E) [NC,OR] RewriteCond %{QUERY_STRING} mosConfig_[a-zA-Z_]{1,21}(=|%3D) [NC,OR] RewriteCond %{QUERY_STRING} base64_encode.*$.*$ [NC,OR] RewriteCond %{QUERY_STRING} ^.*(\[|\]|$|$|<|>|ê|"|;|\?|\*|=$).* [NC,OR] RewriteCond %{QUERY_STRING} ^.*("|'|<|>|\|{||).* [NC,OR] RewriteCond %{QUERY_STRING} ^.*(%24&x).* [NC,OR] RewriteCond %{QUERY_STRING} ^.*(127\.0).* [NC,OR] RewriteCond %{QUERY_STRING} ^.*(globals|encode|localhost|loopback).* [NC,OR] RewriteCond %{QUERY_STRING} ^.*(request|concat|insert|union|declare).* [NC] RewriteCond %{QUERY_STRING} !^loggedout=true RewriteCond %{QUERY_STRING} !^action=jetpack-sso RewriteCond %{QUERY_STRING} !^action=rp RewriteCond %{HTTP_COOKIE} !^.*wordpress_logged_in_.*$ RewriteCond %{HTTP_REFERER} !^http://maps\.googleapis\.com(.*)$ RewriteRule ^(.*)$ - [F] # Rules to block foreign characters in URLs RewriteCond %{QUERY_STRING} ^.*(%0|%A|%B|%C|%D|%E|%F).* [NC] RewriteRule ^(.*)$ - [F] </IfModule> # END Tweaks # END iThemes Security # BEGIN W3TC Browser Cache <IfModule mod_deflate.c> <IfModule mod_headers.c> Header append Vary User-Agent env=!dont-vary </IfModule> AddOutputFilterByType DEFLATE text/css text/x-component application/x-javascript application/javascript text/javascript text/x-js text/html text/richtext image/svg+xml text/plain text/xsd text/xsl text/xml image/x-icon application/json <IfModule mod_mime.c> # DEFLATE by extension AddOutputFilter DEFLATE js css htm html xml </IfModule> </IfModule> # END W3TC Browser Cache # BULLETPROOF .51.1 >>>>>>> SECURE .HTACCESS # If you edit the BULLETPROOF .51.1 >>>>>>> SECURE .HTACCESS text above # you will see error messages on the BPS Security Status page # BPS is reading the version number in the htaccess file to validate checks # If you would like to change what is displayed above you # will need to edit the BPS /includes/functions.php file to match your changes # If you update your WordPress Permalinks the code between BEGIN WordPress and # END WordPress is replaced by WP htaccess code. # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress # This removes all of the BPS security code and replaces it with just the default WP htaccess code # To restore this file use BPS Restore or activate BulletProof Mode for your Root folder again. # BEGIN W3TC Page Cache core <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteCond %{HTTP:Accept-Encoding} gzip RewriteRule .* - [E=W3TC_ENC:_gzip] RewriteCond %{HTTP_COOKIE} w3tc_preview [NC] RewriteRule .* - [E=W3TC_PREVIEW:_preview] RewriteCond %{REQUEST_METHOD} !=POST RewriteCond %{QUERY_STRING} ="" RewriteCond %{REQUEST_URI} \/$ RewriteCond %{HTTP_COOKIE} !(comment_author|wp\-postpass|w3tc_logged_out|wordpress_logged_in|wptouch_switch_toggle) [NC] RewriteCond "%{DOCUMENT_ROOT}/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}" -f RewriteRule .* "/wp-content/cache/page_enhanced/%{HTTP_HOST}/%{REQUEST_URI}/_index%{ENV:W3TC_PREVIEW}.html%{ENV:W3TC_ENC}" [L] </IfModule> # END W3TC Page Cache core # BEGIN WordPress <IfModule mod_rewrite.c> RewriteEngine On RewriteBase / RewriteRule ^index\.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] </IfModule> # END WordPress # BLOCK HOTLINKING TO IMAGES # To Test that your Hotlinking protection is working visit <a href="http://altlab.com/htaccess_tutorial.html" rel="nofollow">http://altlab.com/htaccess_tutorial.html</a> #RewriteEngine On #RewriteCond %{HTTP_REFERER} !^https?://(www\.)?add-your-domain-here\.com [NC] #RewriteCond %{HTTP_REFERER} !^$ #RewriteRule .*\.(jpeg|jpg|gif|bmp|png)$ - [F] # FORBID COMMENT SPAMMERS ACCESS TO YOUR wp-comments-post.php FILE # This is a better approach to blocking Comment Spammers so that you do not # accidentally block good traffic to your website. You can add additional # Comment Spammer IP addresses on a case by case basis below. # Searchable Database of known Comment Spammers <a href="http://www.stopforumspam.com/" rel="nofollow">http://www.stopforumspam.com/</a> <FilesMatch "^(wp-comments-post\.php)"> Order Allow,Deny Deny from 46.119.35. Deny from 46.119.45. Deny from 91.236.74. Deny from 93.182.147. Deny from 93.182.187. Deny from 94.27.72. Deny from 94.27.75. Deny from 94.27.76. Deny from 193.105.210. Deny from 195.43.128. Deny from 198.144.105. Deny from 199.15.234. Allow from all </FilesMatch> # BLOCK MORE BAD BOTS RIPPERS AND OFFLINE BROWSERS # If you would like to block more bad bots you can get a blacklist from # <a href="http://perishablepress.com/press/2007/06/28/ultimate-htaccess-blacklist/" rel="nofollow">http://perishablepress.com/press/2007/06/28/ultimate-htaccess-blacklist/</a> # You should monitor your site very closely for at least a week if you add a bad bots list # to see if any website traffic problems or other problems occur. # Copy and paste your bad bots user agent code list directly below.</code> Jeg håber virkelig at nogen af jer kan hjælpe mig! Tusind tak på forhånd.