Thread: Problem with template functions and library maintenance
View Single Post
Old 03-11-2017, 04:42 PM   #7
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,449
Karma: 8012886
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by BetterRed View Post
@chaley - should that also fix the issue that comes up in this this thread ==>> Column to show mags. that are NOT in any virtual Libraries

Seems vaguely similar, the workaround is do library switches or a restart.

BR
I don't see why this change would fix anything related to this problem. The fix specifically reloads custom template functions after a check library.

NB: I tried creating a new custom column, "column built from other columns, behaves like tags" with the template {:'virtual_libraries()'}. It is a totally new column using a never-before-used lookup name. I had to restart to see the column at all, and after that it worked fine with no "recursion" error message. I also tried changing the template for an existing custom column and had no problems. I don't know why others are seeing the error. I suspect that people are reusing lookup names, something that is known to be problematic, but that is at best a suspicion.
chaley is offline   Reply With Quote