[chaley]

Originally Posted by ldolse

Thanks so much!!

You are welcome. Thanks for the feedback.

[*]Library name is hard-coded to CBH Library (simple enough to change in the code myself)

This is in the template, yes? I added a new configuration variable, $config['page_title'], to set what is printed there.

[*]1.1.2 is not actually linked on your Calibre page

Is now. As is 0.1.3 (more later)

[*]The installation instructions recommended using absolute paths, but in two cases I had to use relative paths - $config['smarty_web_dir'] (used your original relative example), and $config['smarty'] (had to use '../libs' - an absolute server path, e.g. /home/userid/public_html/libs did not work, though the same absolute path style worked for other directives

Surprising, but as long as it works, fine. I changed the INSTALL file to not push full paths so hard.

[*]The directions don't mention that a 'templates_c' directory must be created, though it is mentioned rather generically that this directory must be created for each application in the actual Smarty install docs - I had to create that in my temp directory in order for the app to work (though I think I could have stuck it in the Calibre_PHP directory as well).

Actually, you don't need a tempates_c directory. I don't have one. The code is set up to use smarty_templates_c, which is mentioned in INSTALL. Were you required to create the file? Perhaps for the smarty tests.

Trying to figure out how to use the $config['restrict_display_to'] right now. I want to use a negative tag search, e.g. not tags:"=Nopub" in normal Calibre search terms.

I broke searching quite badly when I added :true and :false tests. I (hope I) have fixed the problems. See version 0.1.3.

Some search documentation might be useful.

Supported search value tests are:

• values are bare words (no quotes & no spaces) or multiple words surrounded by quotes. Examples: foo, "foo bar"
• field names are calibre's field names, followed by a colon, such as series:
• contains searches. A bare word or field:word. The test will be true of the field contains the word.
• equal searches. =word or field:=word
• regular expressions. ~expression or ~/expression', with our without a field prefix

Supported expressions are:

• and: value_test and value_test. An 'and' test has priority over an or test. For example, 'series:foo and tag:bar or author:james' is equivalent to ('series:foo and tag:bar) or author:james'
• value_test value_test: equivalent to value_test and value_test
• or: value_test or value_test
• not: not value_test. The not keyword has the highest priority. For example, 'not a and b' is equivalent to '(not a) and b'
• parenthesized expressions: ( expression )

Example: series:="fu manchu" or authors:james

Notes:

• if quoted expressions are showing as \"....\" (and not working), then turn off PHP's magic quotes feature in your .htaccess using
  

  php_flag magic_quotes_gpc Off

• the server is (for the moment) picky about field names. For example, you must say 'tags', not 'tag', and 'authors', not 'author'. Use the value that calibre shows as the search term when you hover the mouse on a column heading.