eLeXeM

I was wondering ?? – any news re this?

Cheers – LX

this appears to be resolved by now.

good to know there’d be another way of tackling this ??
+ cheers for responding.
Best – LX

found a solution with the hoster in the meantime. had to use their own internal server naming, not the external domain. Cheers + sorry
LX

• This reply was modified 5 years, 8 months ago by eLeXeM.

Thank you very much, Daniele;
I’ll give it a test at the earliest chance I get;
might be on or after the weekend, tho;
bit tied up the next couple days.

Thanks either way already ??

Cheers + ttys – LX

hey,
any ETA on when we can expect the fix?

that is weird.
Did you run page loads monitoring the waterfall?

I’m sincerely sorry I can’t be of better help, Daniele :/ I tried to describe it as best I could.

Perhaps the difference becomes spottable if you install Glossary on a fresh WordPress and choose to opt out of Freemius on that, and then have a look at the page performance waterfall/s when saving a post or a page. That’s where it hit me.

:/ #hth – best – lx

(as to the other bit : “blc” is > Broken Link Checker)

Either way, tho’ – all of those calls related to freemius are taking ridiculous amounts of time + I’m still unclear why they have to occur at all, where opted out.

?? ciao, Daniele (@mte90);
well, do you consider it an issue that your plugin doubles the response time of those calls in question? (see above

switching off Glossary, however, cut the response-time by half (while over 3 seconds is still utterly inacceptable) : https://snag.gy/jBYXJw.jpg

)

#metoo ;-P

Hello, @webfactory –
yeah ?? it came through and it appears to be working very nicely.

Thanks a ton for addressing this! I was right giving you that 5-star-review.
Terrific!
Cheers – LX ??

Hello @svovaf + thank you for getting back to me re this.

• ackowledged re the identifcation of calls from the backend.
• interestingly, looking at HTTP-API-calls, Query Monitor states “No HTTP API calls.” Which confuses me, tho; because:
• right now, all 3 potential offenders are off, so what would possibly cause lines calling admin-ajax with your admin identifier?

The remaining 3 lines showing the bogging string gave some more clues, hovering over the “initiator” bit. Aside from generic / core pointers

• the first 2 point to something named “blcDoWork” – I’ll have to identify to which component this belongs
• the second one to permalink_manager_duplicate_check of Permalink Manager; I’ll switch this off for just another eliminiation step; but this is actually indispensible (we’re even running the Pro version).
  Result: This test left only one line behind, the one belonging to “blcDoWork”, totalling 2.26s delay. Hmm. Now I’m even more confused. Because Permalink Manager didn’t even surface in the initial search for the string (see first post). Perhaps @mbis can add some more insight re this detail?

In the meantime, I’ll go try find out what this “blcDoWork” is + where it originates.

Cheers –

nice ?? looking forward to it.

Cheers – LX

will the missing templates issue be mended with an update anytime soon? Cheers – LX