Closed (fixed)
Project:
Frequently Asked Questions
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
4 Jan 2012 at 21:04 UTC
Updated:
22 Sep 2015 at 15:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
nancydruDid you look at the project page?
Comment #2
macmladen commentedI did and I found that I can make alias.
But I also looked at code and found that it is hard coded.
I belive that it should be possible to change path in settings or in menu like with other modules. Not a two seconds job but not too complicated either and some need it esp those building in non english language.
I've just changed module with
sed -i "s/faq-page/myfaq/g" faq.module(use anything you like instead ofmyfaq) and it works fine, but as Drupaler, I'd like it more to be done in settings.Comment #3
Steven Brown commentedSo first off you should never alter a module like that. If you personally want to fix the situation you should either create a patch or wait for someone that does. Also, you say "like other modules" perhaps you should list out another module that does this but "correctly".
Comment #4
macmladen commentedI do not want to alter module this way, it is just a quick hack to get it easily work on my site, nothing more than that and I enclosed what I did for both developers and users that can find it valuable.
That was more a question on if the path is hard-coded or it could be changed some other way and if it is hard coded then my suggestion is that it should not be. I needed it localised but maybe some would want it other way in english as well. The ability to change it could enable other case scenario usage, perhaps.
Comment #5
Steven Brown commentedThe way to use a different path the "faq-page" is to alias the page. This is how FAQ has always been, so far it's worked out pretty well. Hope this helps.
Comment #6
macmladen commentedDear developer(s), I'm glad you made this module and I'm thankfull that you did. My remark was just a support question (in case I was missing something obvious). While the case was as it is, design by decision, I've just suggested a path for improvement and this is what community is all about. And while
aliasis a sort of solution, it would be nicer (and not too complicated either) to have it in field on settings page. Just a suggestion, nothing more. Thanks for your time answering.Comment #7
Steven Brown commentedI'm not sure if Stella designed the FAQ module the way she did for a reason or if she didn't think about the menu path being based off a setting in the FAQ module. Either way I think it's an interesting idea. Wouldn't mind implementing it, after running it by Stella.
Moving this to postponed until further conversation with Stella :)
Comment #8
fenda commentedAny update regarding this? I'd be very willing to test a patch if needed.
Comment #9
stella commentedmarking as D7 stable release blocker
Comment #10
ryan.ryan commented:-/ yea, a hard-coded path is tough. In my use case, the faq is specific to a department in the organization. So a /faq path doesn't fit the structure.
Comment #11
Steven Brown commentedSorry for the year later response. I was put on a big project and still going.
Since time has paste our latest version is RC2. I will set this version to RC2 and check that the issue still exists in the latest version.
Comment #12
Steven Brown commentedCheck the latest version and this does not exist yet. Moving the version to dev. I will be working on this ASAP.
Comment #13
Steven Brown commentedHere is my first patch for this issue. Please review. Also note this is for the dev version of the module.
Comment #14
sirchaox1224 commentedThanks, FatGuy! That patch worked perfectly for me.
Eight months later and this option is still not incorporated into the FAQ module... :(
Comment #15
bisonbleu commentedPatch in #13 works. Thanks @FatGuyLaughing.
WARNING: BEFORE CHANGING THE DEFAULT PATH, if you have menu-items in your main menu whose path are built on the default path e.g. faq-page/[tid] these items will be DELETED when the path is updated. This also applies to the Views supplied by the module. To avoid this:
admin/config/content/faqand changefaq-pageto e.g. faq123So, if you setup a large FAQ menu tree, this patch is a double-edge sword with no handle! Be very careful.
If you have a single page FAQ, then you don't need to worry to much about this since only one menu item is required.
My 2¢: a better version of this patch would be one that issues a warning before a new path can be set.
Comment #16
sanchiz commentedComment #17
podarokdue to #15
Comment #18
paravibe commentedComment #19
paravibe commentedComment #21
paravibe commentedOops, here is correct patch )
Comment #22
paravibe commentedTest
Comment #23
paravibe commentedComment #24
alex liannoy commentedLooks great.
Comment #25
alex liannoy commentedComment #26
podarokthanks, merged