Hahaha.  Yeah, that part I get.  :)

But I was somewhat hoping that this forum was also about allowing people to ask technical questions about the code, not just being a closed conversation between knowledgeable people about the next release/next big thing.

In the case of 14726, I would have thought the generated part of the Schema would contain the link item->biblio. But maybe
1) it's something that failed (so the bug is in the Schema generation)
2) it's something that must be coded (but why?)
3) it's too obvious, I'm just clueless... Which is somewhat an unsatisfying answer. :)

Thanks,

Philippe Blouin,
Responsable du développement informatique

Tél.  : (888) 604-2627
philippe.blo...@inlibro.com <mailto:philippe.blo...@inlibro.com>

inLibro | pour esprit libre | www.inLibro.com <http://www.inLibro.com>
On 08/27/2015 11:16 AM, Jonathan Druart wrote:
You know what's next, I won't explain you ;) (do, pay or wait)
What's the bug number?

2015-08-27 15:15 GMT+01:00 Philippe Blouin <philippe.blo...@inlibro.com>:
A bug has been filled.  What next?
Isn't it a good forum to ask "what happened"/"what's missing" ?

Philippe Blouin,
Responsable du développement informatique

Tél.  : (888) 604-2627
philippe.blo...@inlibro.com

inLibro | pour esprit libre | www.inLibro.com
On 08/25/2015 10:27 AM, Jonathan Druart wrote:

You can fill a bug report, it's a bug :)

2015-08-25 14:57 GMT+01:00 Philippe Blouin <philippe.blo...@inlibro.com>:

Simple question I'm sure, but there's this bug in circulation.tt that shows
I haven't played much with the new Schema structure:

(circulation.tt, line 672)
[% IF ( issue ) %]
     <div class="lastchecked">
         <p><strong>Checked out: </strong>[% issue.item.biblio.title %] ([%
issue.item.barcode %]). Due on [% issue.date_due | $KohaDates %]</p>
     </div>
[% END %]

This (in bold) never shows up.  The item.biblio link, well, it doesn't
exists in the Result::Item per my understanding.  Whatever I tried with
biblioitem(s) in between didn't pan either.

Suggestions would be appreciated.

(If this is indeed a bug and not a code 18, I'll be happy to do the
"paperwork" to file it in)

Thanks,
Blou




_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/



_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to