Questions about the Profile FAQ module (and a comment regarding 'forms')

researchcooperative
@researchcooperative
9 years ago
694 posts
This week I tried entering a FAQ item without success.

The module is active and has been allocated to the Quota used by the profile.

After clicking on the plus sign, I get a FAQ form and can "create new entry".

I made a new entry, but seeing no category options in the category dropdown list I did not choose any category. Consequently the FAQ was not published, though it remained in the system ready for further modification.

While playing around with this, I found that the "new value" box in fact means "add new category". There is no question box on the form to get an explanation of this.

After adding a category title, and saving the changes, my first FAQ question was at last published. From this it appears that FAQ questions must be organised into categories in order to be published. That's OK, but it would be nice if this could be clearly stated.

Can the FAQ form language be changed by JR to make the form more self-explanatory?

Can the Profile FAQ module be given documentation to explain any other tricks to using it? (I did a search in documentation, and found nothing on this module).

As an all areas where forms are provided, it would be nice if we could design the FAQ form for a specific profile or quota, without this changing the default form seen in other profiles or quotas.

When changing the FAQ form itself, by adding a new field for example, it would be enormously convenient for administrators to be given a drop-down option list such as:

1. Apply this FAQ form as default for all Profile FAQ forms
2. Apply this FAQ form as default for profiles in the present Quota
3. Apply this FAQ form only to the present profile

I imagine that options 2 or 3 would be most useful for most networks, if they were available. Unfortunately, it seems we currently have no options, and only option 1 exists (as far as I can see).

Presumably options 2 and 3 can be achieved through labour-intensive backend coding, case-by-case, but I'm hoping for an easy-to-use solution for non-coding administrators.



--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)

updated by @researchcooperative: 07/24/15 12:14:33AM
douglas
@douglas
9 years ago
2,790 posts
I've got this module updated in the Marketplace that has the help setup for the category field and it is now set to required, it is needed to keep your FAQ's organized. Update via your ACP > Core > Marketplace > System Updates and let me know if you see any issues.

You can modify the language strings through the ACP > Profiles > Profile FAQ > Language tab.

As far as the updates you've suggested, I'll see if they can be done, but there are no plans at this time to update this module. It would be low on our priority list at the moment.


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos
researchcooperative
@researchcooperative
9 years ago
694 posts
Thanks for that! I agree that the categorization is useful.

Is it possible to install a JR module (e.g. the FAQ module) more than once, by relabelling the module?

That way, it might be possible to set up the FAQ form in one way for one quota, and in another way for another quota.

And then, if I set up a quota for a single profile, with the module assigned to that quota and profile, I can have a profile-specific FAQ form that does not affect the FAQ form in other quotas and their profiles.

Just a thought.

It might be a rather heavy-handed way of solving the problem, in terms of use of server space.


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
douglas
@douglas
9 years ago
2,790 posts
It is not as easy as just renaming the module, there are functions that have to be named a certain way in order for modules to work. You'll want to check out the Module Development docs here:

https://www.jamroom.net/the-jamroom-network/documentation/development

That being said, you could use the jrFAQ module as a guide to create a module to suite your needs.

Or, there is also the Aparna module, which allows you to create custom modules and then add any new/extra fields via the form designer, which will also allow you to show certain fields to certain quotas.

Aparna Module Docs:
https://www.jamroom.net/the-jamroom-network/documentation/modules/853/aparna

And you can download the module via your ACP > Core > Marketplace

Hope this helps!


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos
researchcooperative
@researchcooperative
9 years ago
694 posts
I doubt I will get to developing alternative FAQ forms myself, but need to understand how this might be achieved.

In the present case, I need a FAQ for the network, and the default FAQ system is fine for that. It appears on the network profile page which I am using as an operational center for the network, in its own quota.

Where I need an independent FAQ form is for "Special Members" who I hope will eventually be able to set up Marketplace tools, and sell their services. As a business shopfront, the profile of a special member will need a FAQ that has categories that make it easy for the seller to explain to prospective customers how to carry out transactions.

I have not completely thought this through, but just see it as a likely case where an independent FAQ form would be useful (along with an independent profile form, as the profiles of Special Members will need different fields than those of regular or normal members).

Thanks


--
PJ Matthews, Kyoto
Migrated from Ning 2.0. Now at Jamroom 6 beta and using Jamroom Hosting for The Research Cooperative (researchcooperative.org)
gary.moncrieff
gary.moncrieff
@garymoncrieff
9 years ago
865 posts
Could you not use the documentation module as the site wide help and keep faq's for the other requirement?
peter.matthews
peter.matthews
@petermatthews
9 years ago
2 posts
That might be better.

Documentation is what websites are often actually providing (or needing) rather than responses to frequent questions.

Thanks.