In answer to your question, the FAQ package could be modified to include categories/subcategories for questions, making it similar to the "Categories" module. However, this can cause conflicts with the "Category" module if "path" is used (I found this out when I built an image gallery module for my own site). But, having said that, the conflict is easily resolvable with a slight modification to the controller for the "Category" module.
Customizing the module to suit your requirements will require a small donation (which can be made by clicking the "Donate" button at http://www.fido-x.net/index.php?route=i ... ion/donate
). PM me if you would like the customization done.
but are compatible with 1.2.9.
NOT compatible with 1.2.9
1.2.9 use DB PREFIX in all db query
I received an error installing your module on OC 1.2.9
had to rewrite
I understand where you're coming from (I hadn't looked at the code in the "model" in 1.2.9 before releasing these modules - my bad, I hadn't fully tested them on 1.2.9). This issue will be addressed in the next release. However, it should be noted, that this is not really a DB_PREFIX - it's more of a table prefix, since it is not the database that is prefixed, it is the tables within the database that are prefixed. As for the compatibility issue - if you are not using database prefixes, the modules will work with 1.2.9.
allsop wrote:First, thanks for the modules. But I'm having a problem with the FAQ module. I have followed all of the install instructions to the letter. When I get to the Admin section and select "Admin–>Configuration–>Users–>User Group" and then click the edit link in the action column for the "Top Administrator", tick the checkboxes for "catalog/faq" in both the "Access" and "Modify" lists, then click the "Save" button; I get a "Forbidden" page in my browser. That's it. Can't go any further.
Any ideas would be appreciated.
Does the user you logged in as have the necessary permissions to modify the "Top Administrator"? If you do have the necessary permissions, it may have something to do with ownership or permissions of the files themselves. I haven't come across this problem myself, so I'm not sure how to resolve it.