URL Structure for files

17 posts in this topic

Posted

Would their be any possibility in future so that we can get rid of /forum/files/ in every download link?

Example:


http://fearless-assassins.com/forum/files/file/374-enemy-territory-auto-pk3-cleaner/



Link would clearly look nice if their is no /forum/files/ in it.

Share this post


Link to post
Share on other sites

Posted

The /forum/ part would be because your forum is in a /forum/ directory.

Share this post


Link to post
Share on other sites

Posted

Yes, but its not a forum. Its a file directory.

Share this post


Link to post
Share on other sites

Posted

But why we need /files/ too? Even /forum/file/ could work nicely?

Share this post


Link to post
Share on other sites

Posted

The URL can be broken down into specific parts.

/forum/
This is this directory the IP.Board / IP.Downloads files are contained in. This is not controlled by IPB. If your installation is in the root of your domain, this would not be present.

/files/
This determines the application we are using. In this case, we need to specify that we are routing the request to IP.Downloads.

/file/
This determines what part of IP.Downloads we are viewing. In this instance, we're viewing a file.

/374-enemy-territory-auto-pk3-cleaner/
This determines what specific file we are viewing.

All parts of the URL serve a specific purpose to ensure we are routing the user to the correct location. :smile:

Share this post


Link to post
Share on other sites

Posted

You can edit the URL template file to change "files" and/or "file" to something else, but the three segments are needed to route properly as Ryan said.

Share this post


Link to post
Share on other sites

Posted

/forum/


This is this directory the IP.Board / IP.Downloads files are contained in. This is not controlled by IPB. If your installation is in the root of your domain, this would not be present.


This seems because you consider IPB to be the core. Which is the case if you look at the code. But from a users perspective, the forum is not the core.
It makes a lot of sense to have base urls like this:
domain.tld/forum
domain.tld/downloads or domain.tld/files
domain.tld/gallery
etc.

It would add value to IPS if this would become possible.
This provides a logical url structure that end users can comprehend.

/files/


This determines the application we are using. In this case, we need to specify that we are routing the request to IP.Downloads.


See above.

/file/


This determines what part of IP.Downloads we are viewing. In this instance, we're viewing a file.


What other parts can be viewed?
It seems to me that it would be beneficial to end users if admins are able to disable this part of the url. It serves no purpose for the end user and it reduces keyword density in the url.

Share this post


Link to post
Share on other sites

Posted


This seems because you consider IPB to be the core. Which is the case if you look at the code. But from a users perspective, the forum is not the core.


It makes a lot of sense to have base urls like this:


domain.tld/forum


domain.tld/downloads or domain.tld/files


domain.tld/gallery


etc.



It would add value to IPS if this would become possible.


This provides a logical url structure that end users can comprehend.




See above




IP.Downloads requires IP.Board to run. So, from a technical stand-point, the forums are indeed the core. If you store everything in the root, you can change the default application to load any of the applications first if none are specified. Clients can submit a ticket if they require assistance doing this, of course.


What other parts can be viewed?


It seems to me that it would be beneficial to end users if admins are able to disable this part of the url. It serves no purpose for the end user and it reduces keyword density in the url.




Categories of files, submission forms, etc.

I'm not saying it can't be changed in a future version, or discounting the validity of the request or anything like that... just explaining the way it is right now and the function that is performed by each segment of the URL. :smile:

Share this post


Link to post
Share on other sites

Posted

I'm not saying it can't be changed in a future version, or discounting the validity of the request or anything like that... just explaining the way it is right now and the function that is performed by each segment of the URL. :smile:


Yes, I see how it works that way from a technical standpoint. I really think it should work to suit the end user experience as well as SEO.

Share this post


Link to post
Share on other sites

Posted

If you install into the root of the domain, you have

domain.tld/files
domain.tld/blog
domain.tld/gallery
domain.tld/topic/xxxxxxx
domain.tld/forum/xxxxxx


More or less, it sounds like this is what you're after? You simply need to install to the root of the domain.

Share this post


Link to post
Share on other sites

Posted

The optimal file structure that I'm after would be:
domain.tld/files/filename
domain.tld/blog/blogname
domain.tld/gallery/imagename
domain.tld/forum/threadname
domain.tld/news/articlename
domain.tld/tracker/issuename
domain.tld/database/entryname
domain.tld/documents/documentname
domain.tld/video/videotitle

Tigratrus and AlexJ like this

Share this post


Link to post
Share on other sites

Posted

ditto, im not fan of the uncessary url,
http://www.site.com/forum/files/file/
could be
http://www.site.com/...s/categoryname/
or www.site.com/forum/files/filename
www.site.com/forum/filename
im not sure if that would be any issue since i had vbseo with the downloadsII addon on my vbulletin and i had no such issue with that. so it could be implement similar way what vbseo has done.
if theres filename with same name then just have a feature which will just rename filename-copy and the original filename to avoid conflicts
heres the demo http://www.minatica....ds/134-Audacity

just allow us to edit our own customized seo structure

Tigratrus likes this

Share this post


Link to post
Share on other sites

Posted


The optimal file structure that I'm after would be:


domain.tld/files/filename


domain.tld/blog/blogname


domain.tld/gallery/imagename


domain.tld/forum/threadname


domain.tld/news/articlename


domain.tld/tracker/issuename


domain.tld/database/entryname


domain.tld/documents/documentname


domain.tld/video/videotitle




^^^^^
This.

James

Share this post


Link to post
Share on other sites

Posted


You can edit the URL template file to change "files" and/or "file" to something else, but the three segments are needed to route properly as Ryan said.



Can anyone clarify the location for making these changes?

Thanks!

James

Share this post


Link to post
Share on other sites

Posted



Can anyone clarify the location for making these changes?



Thanks!



James


Don't have it in front of me but from memory...

/admin/application_addons/ips/downloads/extensions/furltemplates.php
Tigratrus likes this

Share this post


Link to post
Share on other sites

Posted


Don't have it in front of me but from memory...



/admin/application_addons/ips/downloads/extensions/furltemplates.php



You're a Lady (?) and a scholar. :)

Egads... so "files" is actually hardcoded into that furltemplates.php in like 15 places? Seriously?
I'd think that the names used for the apps in the url would be... Well... abstracted a bit more so that they could be easily changed.

My wife's mainly design and CSS focused, but I'm guessing that even Susan would find that a bit odd.

Dare I hope that this will be looked at for the upcoming shift to the "community" platform?

Seriously, IMO the entire URL structure functionality should be pulled out into a core section where you can craft a cohesive url scheme for the entire site without having to go diving into php edits for each and every app. That will then get stepped on next upgrade and TRASH your SERPS in the process.

Maybe the IP.SEO app should be expanded and made a core app so that all path/rout SEO url functionality can be handed over to it?

James

Share this post


Link to post
Share on other sites

Posted


You're a Lady (?) and a scholar. :smile:



Egads... so "files" is actually hardcoded into that furltemplates.php in like 15 places? Seriously?


I'd think that the names used for the apps in the url would be... Well... abstracted a bit more so that they could be easily changed.



My wife's mainly design and CSS focused, but I'm guessing that even Susan would find that a bit odd.



Dare I hope that this will be looked at for the upcoming shift to the "community" platform?



Seriously, IMO the entire URL structure functionality should be pulled out into a core section where you can craft a cohesive url scheme for the entire site without having to go diving into php edits for each and every app. That will then get stepped on next upgrade and TRASH your SERPS in the process.



Maybe the IP.SEO app should be expanded and made a core app so that all path/rout SEO url functionality can be handed over to it?



James


Those are definitely things you should post in the main feedback board so that it gets more attention. I agree on all points really. Custom URLs would be a pretty great move by IPS.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Who's Browsing   0 members

    No registered users viewing this page.