Not entirely sure about this one. The only time I've ever used this is if the clean URL check failed (say mod_rewrite not enabled when setting up a new localhost), or sometimes moving a site between servers and running into .htaccess issues etc., so feels like a developer task, but it also crowds the admin/config/development area with something you hopefully never, ever have to visit.

CommentFileSizeAuthor
clean-urls.patch7.23 KBcatch

Comments

Bojhan’s picture

I don't think this is a particular good solution, it is only 1 field isn't it? I'd rather relocate it under something, then keep this as its own.

catch’s picture

I'd prefer that as well, but no idea where to put it.

dries’s picture

Personally, configuring the clean URL doesn't feel like 'Development'. It is in no way related to coding.

Bojhan’s picture

What about moving it under URL aliases?

webchick’s picture

Yeah, whatever category we create for Path module, Path Redirect, Global Redirect, etc. this should go under as well.

"Development" doesn't feel like a good fit, IMO.

catch’s picture

Title: Move clean URL settings to admin/config/development » Move clean URLs somewhere out of the way
Status: Needs review » Active

Path module should go to admin/structure/path IMO.

We can't make it a tab on url aliases, because path module is optional, and this setting isn't. However a tab /somewhere/ would be good.

webchick’s picture

Well, I was thinking something more like "SEO". I'm not sure about an entire category related to that, but it is a big component of most websites, and there are quite a few of the top 50 modules that could fit into something like this (Pathauto, Google Analytics, Nodewords, XML Sitemap, Global Redirect).

naxoc’s picture

Clean urls are now in "Search and Metadata" on the configuration page. I guess this issue is solved?

marcingy’s picture

Status: Active » Closed (fixed)