There are no custom urls/redirects in JomSEF.

After enable Jomsef the atricle title(alias) display two times in Url
/krebs-kohlenhydratarme-ernaehrung/krebs-kohlenhydratarme-ernaehrung

That it is what i meant with duplicates :)

It´s very strange for me why i get now different urls with the component ...

Regards

crunky wrote:


This issue is only with core-menu links zu articles ...

... sorry for spamming ... But I'm a little bit more clever now :)

So the "duplicate-issue" was my thinking issue. Set extensions -> content -> "Add Menu Title to URL" to no fixed it.

Next step was there "Add categories to URL" set to "All Categories", now i had long urls again in Jreviews :)
In "Exclude categories from article links" i excluded the categories i doesn´t want to have in Joomla-urls!

So i have yet 1-2 categories i can´t exclude because it will destroy jreviews structure ...


The issue i have yet , the Jreviews Extension-Parameter doesn´t have effekt ... if i exclude anything there like e. g. category or criteria it will also be displayed in url ... what am I doing wrong?

The parameters in JReviews should work. Please check the JoomSEF's URLs Manager and try deleting the JReviews SEF URL that isn't affected by your parameters settings, so it can be recreated from scratch.
If that doesn't help, please post an example of such SEF URL and it's corresponding Real non-SEF URL from JoomSEF's URLs Manager.

Hy,

thanks, i will try this in the next days...

But i´ve two more issues...

1. In Jomsocial users can´t open the PM from other users ... The link on subjekt have no effekt.
I can disable the SEF in url manager, but then the the urls are joomla core :( is it possible to change only these links to "joomla default SEF router" ?

2. In Jreviews Addon Paidlistings, the confirm-site after an order generate an 404 page
Is it possible to fix this?

Thanks

1. It's currently not possible to use default Joomla router with only some URLs. But we already have a report of messaging not working correctly in JomSocial with our extension, so we'll fix it soon.

2. We'll check the addon functionality, but since it is paid, we'll need to ask for a development license, so it can take some time.