I would love to be able to do this, when supporting customers on the forum there is often the same images that the support guys need to use in replies, ideally I want to have an extra option in the list for Support Content which can be accessed by anyone in the support group.
I am coding something up and have got the option up and I can make that only show for support staff but I am kind of stuck at that point.
Is there something i can replace the red bits with here to make the content in a specific media manager folder to appear?
I always get this when i try to upgrade.
" Error: An older copy of Tracker's files still exist, please remove the /home/community/test.community.fortherecord.com/docs/admin/applications_addon/ips/tracker/ folder before continuing. "
i copied over the IF UPDATING FROM 2-1-0 Beta 3 OR EARLIER so i assumed this was all i had to do
EDIT- I did the obvious and just deleted the tracker folder mentioned and it all seems OK.. should everythign be good?
I already have no departments specified, however clients tend to them complain about ''there is no department to select when i try to submit a ticket" what i would like is to disable the support tab altogether, there doesnt appear to be a way to do this without hacking the code. I have already changed the contact us link via the skin to point to our actual contact us page..
My bad, it seems some dumb ass added a sales department, deleted and now all is good, although it would be nice to only allow the support section for specific groups rather than limiting them by departments.
So does sphinx not work with IP.Content? I was actually looking at implementing it as the current search is rather useless.
Not trying to be rude or anything but I agree with csm "the IPS Community Suite works with Sphinx" or even "The IPS Community Suite has built-in first-rate support for Sphinx" implies that the entire community suite works with Sphinx, not just some parts.
I spent about half an hour searching for how to implement sphinx to find this post that says IP.content won't work with it. Now i am not trying to split hairs, but wording can be critically important and this post saved me hours of implementing something that seems like it isn't going to work.