User login
Quick Help
SVN Commit Log
License Informaiton
SOPAC, Locum, and Insurge are made freely available under the GNU Public License v3
Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution 3.0 License
Search
New forum topics
Recent comments
- Re:
4 weeks 1 day ago - thanks, very helpful info for
4 weeks 3 days ago - great article
4 weeks 3 days ago - It's indeed a good post
4 weeks 4 days ago - info
6 weeks 19 hours ago - UGG Boots Clearance
UGGS
7 weeks 4 days ago - Can't go to http://sopac/catalog
19 weeks 4 days ago - VMware Workstation or Server?
1 year 29 weeks ago - Did you create a file called
1 year 31 weeks ago - Sort of. We're using the
1 year 37 weeks ago



That's all going to go into the project specific documentation that i haven't done yet :)
SOPAC blocks should be available to you in /admin/build/block to activate and place as you see fit, is that not the case?
The catalog form can be called from anywhere (and any node) by calling the print sopac_search_form() function. In our case, the catalog page is a view that calls it in the header like so:
print sopac_search_form('both');
'both' in this case meaning both basic and advanced forms.
Yep, the blocks are available, just need to figure out which paths to display on.
Thanks for the search form info. Are you using the views module to display that? (Haven't used the views module yet)
SOPAC doesn't really address block placement, since it assumes you know best where they should go :)
Yes, we're using views very extensively on our site.
BTW, here is a small module function I wrote to manage our blocks. I call it in the block configuration itself using the PHP input filter:
Nice, I'll have to check that out.
Oh, and I figured out the paths were already in the block configs, but I needed to go in and change them to "Show only on the listed pages".