lygren
Member
Hmm, ran the import, but did not help much... For example, this URL; https://avforum.no/forum/index.php?...nger-med-alcons-post1883425.html&#post1883425, is still coming up with a "not found" error... Hmm...
That URL will never ever work.Hmm, ran the import, but did not help much... For example, this URL; https://avforum.no/forum/index.php?...nger-med-alcons-post1883425.html&#post1883425, is still coming up with a "not found" error... Hmm...
.htaccess
file or a nginx.conf
file that is intercepting that URL and redirecting it to the broken URL you posted. Do note that I am not able to assist you with fixing that issue, as it is not an issue with this mod.Unfortunately I have no experience with nginx so I have nothing to offer, sorry...we have still not been able to figure this issue out... Main problem now is that the serves uses nginx and not apache it seems? So @DragonByte Tech; would you happen to have a tip on someone that can help us out with the server side redirect issue we seem to be unable to sort out (@Nginx that is). You can send me your suggestion via PM if you have any...![]()
It's handled automatically after you run the importer I highlighted earlier. You don't have to do any manual configuration.OK, got it. The server supplier has now activated apache on www and port 80 for testing purposes... Just to be sure; the "export" file I am creating using your add-on is the file I am supposed to be using in the XenForo redirect add-on, right?
Oh, no don't select the log table from this mod. That's only created because it's a requirement, the table is empty.Yes, I have run your importer, but it does output a new redirect table, so my question is if I am to select this redirect table instead of the original one that was used during the original migration. If not, that´s fine, I´ll just leave the old redirect table in XenForos redirect add-on...
That is the exact same URL posted twice.Sorry to bother you again... We have alternated from nginx to apache now to try to more easily identify and fix the issue through .htaccess.
Now threads are not redirected like before at least, for example:
Native: https://avforum.no/forum/av-rom-kon...inger-med-alcons-post1324194.html#post1324194
Actual: https://avforum.no/forum/av-rom-kon...inger-med-alcons-post1324194.html#post1324194
So, for some reason, even now without that intercepting issue on nginx we´re not able to get that redirect script to work... I know this is an unsupported add-on, but I just wanted to ask again if you would happen to have any inputs...
In that case I have no idea, sorry. It works fine for others and for ourselves.Yeah, as to show that nothing is done with it, neither a server side redirect or the XenForo redirect / DragonByte fix redirect...![]()
I still don't have any idea, it's not going to change in another 2 hours from now, sorry.So, the old URL´s that are not rewritten by the DragonByte SEO does work, for example this one: http://avforum.no/forum/showthread.php?t=34945. So, that means the XenForo redirect works. Any idea how we can tweak your add-on to support our DragonByte URL´s?? Did we add some customisation that hinders your script from properly rewriting them and as such activating the XenForo redirect script?
I just clicked it, and it works. But yes, that does look like a thread URL rewritten by DBSEO.Just a quick question; hope you can take the time to respond - is this URL "DragonBye SEO" rewritten? http://avforum.no/forum/digitale-projektorer/104414-infocus-in76-hdmi-signal.html
We use essential cookies to make this site work, and optional cookies to enhance your experience.