Hi, I have a problem, that e. g. when using Kunena extension, Artio is creating the following SEF URLS in the database for each post:

category/test-post/moderate.html index.php?option=com_kunena&catid=10&do=moderate&func=post&Itemid=148
werbung/test-post/moderatethread.html index.php?option=com_kunena&catid=10&do=moderatethread&func=post&Itemid=148
category/test-post/quote.html index.php?option=com_kunena&catid=10&do=quote&func=post&Itemid=148
category/test-post/reply.html index.php?option=com_kunena&catid=10&do=reply&func=post&Itemid=148
category/test-post/report.html index.php?option=com_kunena&catid=10&func=report&Itemid=148
category/test-post/sticky.html index.php?option=com_kunena&catid=10&do=sticky&func=post&Itemid=148
category/test-post/subscribe.html index.php?option=com_kunena&catid=10&do=subscribe&func=post&id=5452&Itemid=148

But I do only want to have the post itself in the database, not all of the clicking options. So for reply, report etc. there shouldn't be any built SEF URL in the data base, as this directly increases tenfold the database entries for each post.

So I tried to exclude these URLs from SEF generation by adding "func=post;func=report"
1. to extension --> kunena --> common --> Custom non-SEF variables
2. to extension --> kunena --> common --> Do not SEF URLs matching regular expression

But still these SEF URLs are generated, and are stored in the database, so what is wrong?
It would be very helpful to get your feedback.

Best regards

Payon

Hi,
You should use the second option, Do not SEF URLs matching regular expression, but you need to create a regular expression correctly, for example:

You can find many guides on using regular expressions on the internet.

Thanks a lot for the answer. I will try this option