Changes Not Displaying On Front End/Browser Tab Says Page Not Found
-
Hello, I’m having a slight problem with my website. For some reason on my shop page. I am not able to display the changes made on my website and the website tab displays “page not found”.
Fixes I have tried:
- Browser Cache
- Wrong URL
- Clear Your Cdn Cache
- Clear WordPress cache
Now I am guessing I have a coding problem but am not quite sure. Perhaps someone can give me a proper explanation.
The page I need help with: [log in to see the link]
-
The same
BEGIN AIRLIFT
AddDefaultCharset utf8
AddType text/html .html_gzip AddEncoding gzip .html_gzip
RewriteEngine On RewriteBase / RewriteCond %{HTTPS} on [OR] RewriteCond %{SERVER_PORT} ^443$ [OR] RewriteCond %{HTTP:X-Forwarded-Proto} https RewriteRule .* - [E=SO_SECURE:-https] RewriteCond %{HTTP:Accept-Encoding} gzip RewriteRule .* - [E=SO_ENCODE:gzip] RewriteCond %{REQUEST_METHOD} GET RewriteCond %{QUERY_STRING} ="" RewriteCond %{HTTP:Cookie} !(wordpress_logged_in|wp-postpass_|wptouch_switch_toggle|comment_author_|comment_author_email_) [NC] RewriteCond %{REQUEST_URI} !^(/(.+/)?feed/?|/(index.php/)?wp-json(/.|$))$ [NC] RewriteCond %{HTTP_USER_AGENT} !^(facebookexternalhit). [NC] RewriteCond "%{DOCUMENT_ROOT}/wp-content/cache/airlift/%{HTTP_HOST}%{REQUEST_URI}/index%{ENV:SO_SECURE}.html%{ENV:SO_ENCODE}" -f RewriteRule .* "%{DOCUMENT_ROOT}/wp-content/cache/airlift/%{HTTP_HOST}%{REQUEST_URI}/index%{ENV:SO_SECURE}.html%{ENV:SO_ENCODE}" [L] END AIRLIFT BEGIN LSCACHE LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block!
RewriteEngine on
CacheLookup on
RewriteRule .* - [E=Cache-Control:no-autoflush]
RewriteRule .litespeed_conf.dat - [F,L] marker ASYNC start
RewriteCond %{REQUEST_URI} /wp-admin/admin-ajax.php
RewriteCond %{QUERY_STRING} action=async_litespeed
RewriteRule .* - [E=noabort:1] marker ASYNC end marker CACHE RESOURCE start
RewriteRule wp-content/./[^/](responsive|css|js|dynamic|loader|fonts).php - [E=cache-control:max-age=3600] marker CACHE RESOURCE end marker DROPQS start
CacheKeyModify -qs:fbclid
CacheKeyModify -qs:gclid
CacheKeyModify -qs:utm*
CacheKeyModify -qs:_ga marker DROPQS end LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! END LSCACHE BEGIN NON_LSCACHE LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! marker BROWSER CACHE start
ExpiresActive on
ExpiresByType application/pdf A31557600
ExpiresByType image/x-icon A31557600
ExpiresByType image/vnd.microsoft.icon A31557600
ExpiresByType image/svg+xml A31557600
ExpiresByType image/jpg A31557600
ExpiresByType image/jpeg A31557600
ExpiresByType image/png A31557600
ExpiresByType image/gif A31557600
ExpiresByType image/webp A31557600
ExpiresByType video/ogg A31557600
ExpiresByType audio/ogg A31557600
ExpiresByType video/mp4 A31557600
ExpiresByType video/webm A31557600
ExpiresByType text/css A31557600
ExpiresByType text/javascript A31557600
ExpiresByType application/javascript A31557600
ExpiresByType application/x-javascript A31557600
ExpiresByType application/x-font-ttf A31557600
ExpiresByType application/x-font-woff A31557600
ExpiresByType application/font-woff A31557600
ExpiresByType application/font-woff2 A31557600
ExpiresByType application/vnd.ms-fontobject A31557600
ExpiresByType font/ttf A31557600
ExpiresByType font/otf A31557600
ExpiresByType font/woff A31557600
ExpiresByType font/woff2 A31557600 marker BROWSER CACHE end LITESPEED WP CACHE PLUGIN - Do not edit the contents of this block! END NON_LSCACHE BEGIN WordPress The directives (lines) between "BEGIN WordPress" and "END WordPress" are dynamically generated, and should only be modified via WordPress filters. Any changes to the directives between these markers will be overwritten.
RewriteEngine On RewriteRule .* - [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index.php$ - [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] END WordPress Wordfence WAF
php_value auto_prepend_file '/home/u831126664/domains/bunker41.com/public_html/wordfence-waf.php'difference is the wordpress section. Instead of it looking like this:
BEGIN WordPress The directives (lines) between “BEGIN WordPress” and “END WordPress” are dynamically generated, and should only be modified via WordPress filters. Any changes to the directives between these markers will be overwritten.
RewriteEngine On RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L] END WordPress
It now looks likes this:
BEGIN WordPress
The directives (lines) between “BEGIN WordPress” and “END WordPress” are dynamically generated, and should only be modified via WordPress filters. Any changes to the directives between these markers will be overwritten.
RewriteEngine On RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase / RewriteRule ^index.php$ – [L] RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule . /index.php [L]
END WordPress
That’s still a problem. Those all need to be on separate lines.
RewriteEngine On
is a directive,RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}]
is a directive, andRewriteBase /?
is a directive.RewriteEngine On RewriteRule .* – [E=HTTP_AUTHORIZATION:%{HTTP:Authorization}] RewriteBase /?
is not a directive, hence your problem. And so on for the rest of it.Please consult the example and try again: https://developer.www.ads-software.com/advanced-administration/server/web-server/httpd/#basic-wp
Yes, I’m aware. Each code is on a separate line on the actual .htaccess file, but on here when I copied and pasted the code on here it appeared the way you see above, but I assure you on the actual .htaccess file, each line of code is on a separate line.
It still does not fix the original problem though.
- This reply was modified 2 months ago by WebGuru1.
Ok, as long as it’s correct in the .htaccess file.
Does everything work properly under the Twenty Twenty-Four theme?
If you can install plugins, install Health Check. On the troubleshooting tab, you can click the button to deactivate all plugins and change the theme for you while you’re still logged in without affecting normal visitors to your site.
Okay, just tried the 2 fixes you suggested. Unfortunately, the problem still persists.
Would you happen to know of any other fixes?
Not really, no. I’ve asked some friends to take a look.
Are you using a caching plugin? If so, which?
Sorry for the late reply, but I’ve found a reasonable solution to fix this problem. I appreciate the help. I’m now closing this topic.
Would you mind sharing the solution here? I’m very curious. ??
- You must be logged in to reply to this topic.