I am using 7.5.9 and latest url tracker. I have setup as follows one admin website and one front end site. The admin has website and backoffice access the front end site does not have backend access.
When I create a new redirect on the admin website on the admin front end the redirect works fine. On the front end site the url redirect does nothing.
This is for existing pages and I am forcing the redirect. Both instances share the same database so I would assume it would work on both? When I create redirect where the url is not an existing page then that works fine on both instances.
I was hoping it was going to be simple, like the URL Tracker wasn't installed on the front-end instance, but you said it works for pages which don't exist :(
I know you said you're running the latest version, but just to clarify, that is 3.14.1.? There was an issue with 3.14.0 which caused force redirects to break.
Honestly, I'm a bit stumped. I don't know the plugin well enough I'm afraid. All I can suggest is enable logging, and hopefully that will narrow down as to why it isn't redirecting.
You'll be looking for log entries that start with UrlTracker HttpModule |
urlTracker:forcedRedirectCacheTimeoutEnabled
boolean(false)
Set to true to cache forced redirects for a period of time. Setting this to true will enable forced redirect updates and additions to propagate to all servers in a multi-server environment.
to true. Still not joy with forced redirects in multi server environment. So it works fine on the server which is admin and has backoffice access which is where i create the redirect. However on frontend server it just loads up the existing url and does not redirect. I am guessing because for the newly created item it is looking for it in the cache? When you app pool recycle on the frontend server then it works.
Looking the source code UrlTrackerRepository.ReloadForcedRedirectsCache method it resets the LastForcedRedirectCacheRefreshTime to latest date however it only does it for the server it is running on.
Shared db issue
I am using 7.5.9 and latest url tracker. I have setup as follows one admin website and one front end site. The admin has website and backoffice access the front end site does not have backend access.
When I create a new redirect on the admin website on the admin front end the redirect works fine. On the front end site the url redirect does nothing.
This is for existing pages and I am forcing the redirect. Both instances share the same database so I would assume it would work on both? When I create redirect where the url is not an existing page then that works fine on both instances.
Any ideas?
Regards
Ismail
Hi Ismail,
I was hoping it was going to be simple, like the URL Tracker wasn't installed on the front-end instance, but you said it works for pages which don't exist :(
I know you said you're running the latest version, but just to clarify, that is 3.14.1.? There was an issue with 3.14.0 which caused force redirects to break.
Honestly, I'm a bit stumped. I don't know the plugin well enough I'm afraid. All I can suggest is enable logging, and hopefully that will narrow down as to why it isn't redirecting.
You'll be looking for log entries that start with
UrlTracker HttpModule |Daniel,
I installed via nuget and version is 3.14.1 and its installed on both servers. I will turn on more logging see if that helps.
Regards
Ismail
Acutally looking at the docs https://github.com/kipusoep/UrlTracker#urltrackerenablelogging
The option
urlTracker:forcedRedirectCacheTimeoutEnabled boolean(false) Set to true to cache forced redirects for a period of time. Setting this to true will enable forced redirect updates and additions to propagate to all servers in a multi-server environment.
May be i need to set it to true?
Will give that a go
You know, that's probably it 😂
As mentioned, I'm not familiar enough with the plugin yet.
Let me know how you get on though!
Ok so I have set that parameter,
to true. Still not joy with forced redirects in multi server environment. So it works fine on the server which is admin and has backoffice access which is where i create the redirect. However on frontend server it just loads up the existing url and does not redirect. I am guessing because for the newly created item it is looking for it in the cache? When you app pool recycle on the frontend server then it works.
Looking the source code UrlTrackerRepository.ReloadForcedRedirectsCache method it resets the LastForcedRedirectCacheRefreshTime to latest date however it only does it for the server it is running on.
Regards
Ismail
Hi Ismail,
I wish I could help you, but unfortunately I have no experience with multi-server environments, and I wouldn't even know where to begin!
Does the timeout need reducing at all?
My best advice to you, is to create a pull request (the current setup actually came from another PR)
It would be great to see if anyone else has the URL Tracker on a multi-server environment though, I wouldn't want to break it for those!
Cool have lowered the cache time and that works. many thanks for your help
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.