lvca-blocks.js glitch report

[Olivier Langlois]

It doesn’t seem to cause any problem but I have found the following that looks suspect…

//LVCA_Block class – each ajax block uses a object of this class for requests
LVCA_Block = function (blockId) {

var self = this;

var $blockElem = $(‘#’ + blockId).eq(0);

self.blockId = blockId;
self.query = $blockElem.data(‘query’);
self.settings = $blockElem.data(‘settings’);
self.blockType = self.settings[‘block_type’];
self.currentPage = $blockElem.data(‘current’);
self.filterTaxonomy = $blockElem.data(‘filter-term’);
self.filterTerm = $blockElem.data(‘filter-taxonomy’);

self.filterTaxonomy is set with filter-term and
self.filterTerm is set with filter-taxonomy…

[Raghavendra]

I have done the fix for the next update. Yes you are right – it does not cause any harm right now since the value is not being set initially. It is set only when the user clicks on the filters and then it gets corrected with the right values. Thanks for catching this.

[Author]

Posts