Hi

Order ID 4001, Joomla version 1.5.9, JoomSEF version 3.2.10

I'm having trouble defining some URLs.

For some reason not all the SEF URLs are showing up in the 'Show All Redirects' JoomSEF menu, which means I can't then update the URL.

How do I locate where the URL is being created and how do I update it to a new URL?

thanks for your help.

Nick

Hello,

if the URL is created it should be visible there. Most likely, your JoomSEF is not activated then from some reason? Or it does not have permissions to store to the DB. (try to check the FAQ regarding SQL errors) Also make sure you have error reporting on, so you can see error messages if there are any.

Hi jan

thanks for the response.

I've double checked and Artio is working perfectly for 95% of our URLs, there are just a few that aren't showing anywhere. This shows the permissions for the DB are there, so it shouldn't have any trouble with this.

I had an article that i'd defined the URL as 'products.html', but then needed to change the way this was handled.
I wanted to create a 301 re-direct to 'hardcovers.html' instead, so I deleted the URL for products.html and created a 301 re-direct.
I also deleted the Article as I no longer needed it.
Now when I go to 'products.html' I get an ugly 404 message, not one displayed in my sites template.
I've checked the 301 redirect section of ARTIO, and the URL is definitely correct, so I don't understand why it's not re-directing. It seems something in Joomla/ARTIO is still trying to display the deleted article instead of doing the 301 redirect.

I've also searched through my whole database for 'products.html' and it doesn't appear anywhere.
I've even manually searched through the jos_redirection table and it's not there.
Where are the URLs stored? How do I fix this?

BTW, how do I turn on error reporting?
I've enabled the debugging in Global Configuration, is this what you're referring to?

thanks
Nick

Hi,

I think I've worked it out.

The cache was turned on, so the 'products.html' URL had been cached which is why it was still trying to reach that page.
Turning the cache off now has the redirect working correctly.

Nick