I’ve added several new images to my carousel that was working perfectly and still rotates fine but the “Next” and “Previous” links have stopped working. I cannot find what the cause could be - the “Carousel next” and Carousel prev" code blocks look OK and the div tag referencing the carousel1 id is intact. Anyone know where I should look or what to look for to see what I broke? There are over 130 images in this carousel so the next and previous function is important and should be fixed. Here’s the URL to the page: https://nittanyleathernecks.com/slider_archived_test.html (images won’t display but you can review the code via “View Page Source”).
@SureWeb
Thanks for your advice - I removed the second instance of the JS but that did not resolve the issue. Seems the hyperlink area is not working… normally when I scroll over the area shown, my mouse cursor turns into the hand indicating the area is a link. This no longer works so I think whatever code delineates this as an image link is broken. Any ideas how I can repair this?
Link to the site is no longer working
I gave up trying to figure what the problem was and simply remade the page… so it is working now. Thanks @Printninja for checking though… if anyone, you probably would have found what was causing the issue.
Thanks Randy, I do enjoy doing detective work on websites 
Great to hear… I have another issue to solve. Perhaps you can Sherlock this one? This htacess code should redirect from an old site on http://hlaa-centralpa.biz.tc to the new site on https://rjrwebz.com/hlaa but doesn’t work. Any ideas what’s wrong with the code?
**
RewriteEngine On
RewriteCond %{SERVER_PORT} 80
RewriteCond %{HTTP_HOST} ^(www.)?rjrwebz.com/hlaa.com
RewriteRule ^(.*)$ https://rjrwebz.com/hlaa/$1 [R,L]
**
The redirect seems to work fine for me.
Yes the redirect works but only because I’ve added a URL redirect to the index page via a meta tag along with a JS script as insurance. This works but it does flash the old page for split second before the redirect opens the index page on the new site - which won’t happen if I can get the htacess to work and remove the redirect meta tag and the JS. Do you see anything noticeably wrong with the code I’ve written for the htacess file?
Honestly, I don’t see any significant mistakes - this is just because I’m not really able to read code of that kind. The one I’m used to use does not specify any URL (which might be wrong - but working though):
RewriteEngine On
RewriteCond %{HTTPS} !=on
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]
Might that be of help?
Cheers
Thomas
@Thomas This “Rewrite Rule” is for converting a non secure request (http) into a secured one (https).
When the request is already using https, the condition is not valid/match and this rule is going to be ignored and is not in affect!
Ah - I see @Marf now the big difference and what @randyrie is after. Thanks for this explanation.
Cheers
Thomas
Your condition is wrong, the request on the old host is not going to be and contain “rjrwebz.com/hlaa.com”.
Use something like this (not tested).
RewriteEngine on
RewriteCond %{HTTP_HOST} ^(.*)hlaa-centralpa.biz.tc
RewriteRule ^(.*)$ https://rjrwebz.com/hlaa/$1 [R,L]
This is matching when the requested host is hlaa-centralpa.biz.tc (with any subdomain).
And it’s always better to specify, the reason for the redirect.
If the redirect is permanent, use 301.
RewriteRule ^(.*)$ https://rjrwebz.com/hlaa/$1 [R=301,L]
If the redirect is temporary, use 302.
RewriteRule ^(.*)$ https://rjrwebz.com/hlaa/$1 [R=302,L]
You’ve all exceeded my knowledge on the subject. I’ve only modified an htaccess file once in my life, and I just followed instructions I was given.
Anytime I need to redirect an old domain to a new one, I do it through the domain registrar’s DNS settings page.
Thank @Marf for your explanation. Last night, I ultimately went with a simple, single
**Redirect 301 “/” “https://www.rjrwebz.com/hlaa/” **
line in the htacess file which works perfectly. I do not know or understand what the [R=301,L] part means or does so I’ve omitted it.