I have used jUpgrade to migrate my site from Joomla 1.5.26 to 2.5. I also installed a new copy of K2 in the 2.5 installation.

Some of my menu items which point to K2 items produce 404 errors.

I have ensured their permissions are set to Public.

If I create a new menu entry pointing to a K2 item, it also produces a 404 error.

How can I resolve this?

*bump*

Can you send a link to your site, which produces the 404 error?

Thanks Mohamed.

Home URL is www.melvilletenniscentre.com.au/

Try clicking on Junior Tennis on the right.

Regards,
Steve.

Have you tried to check with the SEF urls disabled?

I think this maybe caused by differences in the item/category ids while you are migrating from J1.5, although this is strange because you said the error occures for new menu items as well!

I turned SEF URLs off, and the problem remains.

Hello Steven,

Your page produces a Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects. which is a server related issue. Make sure you haven't forgotten any old code in your .htaccess file.
You can always try again with a new .htaccess file.

The server is using a default .htaccess file.

I noticed that the server has a hard time displaying the 404 error page. Perhaps a byproduct of this is a 310 error code?

How would I fix the server not being able to display a proper 404?

Provided that you are using the latest version of K2,
I would first turn the redirect plugin off and see what happens then if I were you.

From that point I would experiment by turning off any additional extensions or plugins I've installed.
That way you can find which extension is causing the issue.

If none of these work for you, you should open a ticket with your hosting provider.

If I disabled the redirect plugin, and click on the problem navigation item, I'm taken to the URL:
www.melvilletenniscentre.com.au/login?return=aHR0cDovL3d3dy5tZWx2aWxsZXRlbm5pc2NlbnRyZS5jb20uYXUvanVuaW9yLXRlbm5pczI=

This page displays a "item not found" message, and asks me to login.

This is similar behaviour to when the migrated content had not yet had permissions set to Public.

Maybe the 404 page does not have Public permission? Where do I check this?