[Olivier Langlois]

I just tested with 5.4.7. It now works fine. thank you

[Olivier Langlois]

Raghavendra, you are right. The problem occurs only in my specific setup…

[Olivier Langlois]

if I disable fancybox totally by doing

initLightbox: function ($blockElem) {} in lvca-blocks.js

the problem goes away.

It seems that fancybox doesn’t like this statement at all
$(responseObj.data).appendTo($blockElem.find(‘.lvca-block-inner’));

in _doAjaxBlockProcessResponse() function

Let me say again that I am not happy at all to have stumble into that shitty problem. As a paying customer, I shouldn’t have to waste time doing this debugging.

I feel that you have failed in your testing duty with this release, please be more careful about that…

[Olivier Langlois]

I’m a bit upset… The AJAX called is done when I click on the ‘load_more’ button. Server returns the next page data fine but instead of being appended as it used to… The Grid HTML is totally wipped out and I have a big empty fancybox overlay.

This fancybox stuff that I have no idea what it is for has obviously hasn’t been tested well.

[Olivier Langlois]

Ok guilty code is has been changed from:

wp_trim_words(wp_strip_all_tags(strip_shortcodes($excerpt)), $excerpt_count, ‘…’);

to

do_shortcode(force_balance_tags(html_entity_decode(wp_trim_words(htmlentities($excerpt), $excerpt_count, ‘…’))));

So I can report you that the the new code generate ugly output…

[Olivier Langlois]

I’m all good no rush. I already have the fix!

[Olivier Langlois]

Raghavendra, ok. I had the chance to check the fix. It works like a charm. I’m so happy that you did took a look. I didn’t notice that no post was visible on mobile view (ouch!). That one slipped from away from my attention.

[Olivier Langlois]

Raghavendra, ok sure. I will test tonight and report back here the result.

Greetings,

[Olivier Langlois]

It was with firefox 57

[Olivier Langlois]

https://olivierhealthtips.com/blog-posts/

but it contain the fix. I guess that if you change the CSS dynamically to what it was, you might be able to trigger the problem.

[Olivier Langlois]

This is a neat rounding error. If I change the following in lvca-frontend.css

.lvca-gapless-grid .lvca-fourcol {
width: calc(33.3333333333%);
float: left;
margin-left: 0px; }

to

.lvca-gapless-grid .lvca-fourcol {
width: calc(33.33333%);
float: left;
margin-left: 0px; }

my problem goes away

[Olivier Langlois]

Ok that is the best that I can do. I know nothing about NEAT or SASS

the div lvca-block-column lvca-fourcol
On 1.7.5: 386.65px wide
On 1.8.0: 386.667px wide

The problem is that lvca-block-column width multiplied 3 times exceed by 1 pixel the width of the container. lvca_block_inner which is 1160 px wide.

lvca_block_inner is in a bootstrap framework container (1170px)

I think that you have all you need to know to do your job and make a fix.

thank you

[Olivier Langlois]

Ok, I have noticed something that might explain the problem. According to firefox Inspection tool

On 1.7.5 and 1.8.0, lvca_container is 1140 pixel wide.

However

the div lvca-block-column lvca-fourcol (Why fourcol if I have configure to have 3 cols??)
On 1.7.5: 386.65px wide
On 1.8.0: 386.667px wide

[Olivier Langlois]

Hi Raghavendra,

I finally did have a chance to investigate a little bit more this problem.
1. I have turn off Autooptimize: No improvement
2. I have the following CSS tweak that I have commented out to rule out possible interference:
.lvca-portfolio-wrap .lvca-portfolio .lvca-portfolio-item .hentry {
padding: 10px;
border: 1px solid #dfdfdf;
border-radius: 5px;
background: #fff;
}

.lvca-portfolio-wrap .lvca-portfolio .lvca-portfolio-item .entry-title {
font-size: 26px;
line-height: 28px;
}

.lvca-portfolio-wrap .lvca-portfolio .lvca-portfolio-item .lvca-project-image .lvca-image-info .lvca-terms a {
display: none!important;
}

.entry-summary p {
font-size: 18px;
line-height: 28px;
}

No change. Still have the weid behavior.

3. I will try with your custom CSS suggestion and I will also give 1.8.1 a try…

and report back here if it helps.

In the meantime, This is javascript code that is responsible for what I have. Any idea which function is taking the decision to change the column number from 3 to 2?

[Olivier Langlois]

Allright. I see that you have cut in half the size of LVCA update_info by removing 1 duplicate changelog.

You are maybe right that LVCA isn’t responsible.

It did just turn on a red light that the function taking an unreasonable amount of time set_site_transient() update a record in the DB table wp_options with a 36KB long field where a single entry was 13K (LVCA one) whereas most of the others are all smaller than 500 bytes.

I did retest this afternoon with the changelog duplicate instance removal (now your entry takes ~7KB) and the function is even few seconds longer than yesterday…

[Author]

Posts