- This topic has 15 replies, 4 voices, and was last updated 7 years, 6 months ago by
.
-
Posts
-
upgraded my theme to the pro version and now all links to the gallery are broken. have created a new test gallery and doesn’t work either. here is .htaccess
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} !^facebook [NC]
RewriteCond %{HTTP_REFERER} !^$
RewriteCond %{HTTP_REFERER} !^http(s)?
/(.*)facebook.com [NC]RewriteCond %{HTTP_USER_AGENT} !^Pinterest [NC]
RewriteCond %{HTTP_REFERER} !(wp-admin) [NC]
RewriteCond %{HTTP_REFERER} !^http(s)?
/stjamesage.com [NC]RewriteCond %{REMOTE_ADDR} !(127.0.0.1|localhost|
:1)RewriteRule .* http://127.0.0.1 [L]
</IfModule>
stjamesage.com
The main gallery page is giving a 404 error or the images of a gallery?
Can you go to your pages menu and see the “Photo Gallery” page being there? Can you access that page at all from the front-end by clicking on the “view” link from the pages list?
Does this theme have some kind of built in gallery functionality?
If you post a link to your photo gallery page, it will be easier for us to see what it is doing.
nothing found?
[https://stjamesage.com/photogallery/]
have 10 sub galleries under the main and they get the 404 but the main gallery says Not Found
Before you updated the theme did all galleries work?
Have you checked if those pages exist in the wordpress “Pages” menu?
What is your wordpress permalink setting?
yes and the pages are there with photos attached but do not display when “view” is clicked
permalink set to post name
I reverted back to the free version to make sure it was working correctly. everything worked fine and have since changed back to the Pro theme and it is not working again
When you are running the “free” and “pro” themes; is the .htaccess file EXACTLY the same, or different?
pro theme
# BEGIN GD-SSL
<IfModule mod_rewrite.c>
Options +FollowSymLinks
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP_USER_AGENT} ^(.+)$
RewriteCond %{SERVER_NAME} ^stjamesage.com$
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]
Header add Strict-Transport-Security “max-age=300”
</IfModule>
# END GD-SSL
# 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
free theme
# BEGIN GD-SSL
<IfModule mod_rewrite.c>
Options +FollowSymLinks
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteCond %{HTTP_USER_AGENT} ^(.+)$
RewriteCond %{SERVER_NAME} ^stjamesage.com$
RewriteRule .* https://%{SERVER_NAME}%{REQUEST_URI} [R=301,L]
Header add Strict-Transport-Security “max-age=300”
</IfModule>
# END GD-SSL
# 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
from /home/siteftpname/html/.htaccess
I don’t know if this htaccess file content is causing the problem but I do know for sure that you should ONLY have one of the following block in that file:
# BEGIN WordPress
......
# END WordPressSomehow the theme is getting confused and polluting your htaccess file with multiple copies of the same directive. That can have some ramifications. So maybe you should cleanup the htaccess file just to make sure it is not contributing to the issue.
- You must be logged in to reply to this topic.