Menu Content

Support

> Forums, FAQs & Paid Support
Welcome, Guest
Username Password: Remember me

Finding out an Article's SEF URL
(1 viewing) (1) Guest
Support forum for users using free edition of JoomSEF 3 (Joomla 1.5 compatible). These forums are mainly for mutual help between users.

Please note that due to our capacity limitations, we do not monitor these forums regularly.
  • Page:
  • 1

TOPIC: Finding out an Article's SEF URL

Finding out an Article's SEF URL 14 years, 4 months ago #9543

I'm somewhat new to JoomSEF and SEF URL's in general, and was wondering if there is an easy way in Joomla 1.5 to find an article's SEF URL.

Today I created an uncategorized (i.e. static content) article, and wanted to get the JoomSEF URL for the article so that I could hard-code it into a custom HTML module on our front page.

I ended up having to go into Joomla Admin --> JoomSEF and filter by keyword, search through the results and find the SEF URL for that article that was generated by JoomSEF.

I was just thinking that there has to be a better way to find out the SEF URL for an article...?

Perhaps there is and I just don't know about it, but I was hoping someone out there has some advice.

Thanks!

Re:Finding out an Article's SEF URL 14 years, 4 months ago #9550

  • jaku
There are 2 ways to find out the SEF URL:
1. at frontend, when navigating to the artilce
2. in backend in Components / JoomSEF / Manage URLs (this has advanced filtering including regular expressions support)

Re:Finding out an Article's SEF URL 14 years, 4 months ago #9554

Thanks for the response.

I was afraid of that.

A lot of times I create a new piece of content that I'm not putting on a menu or that I will eventually need to hard code the link into a custom html page, so it makes it difficult to guess what SEF URL JoomSEF will generate for that particular article.

It would be great if there was some way to click on a buttoon or look at the document properties and get the answer to "What is the JoomSEF URL for this article?"

Having to go to the back end is a little extra work, but oh wel....


Thanks!
  • Page:
  • 1
User Login Empty