The Instant View Editor uses a three-column layout, so you really want to use it on a desktop screen that's wide enough. Sorry for the inconvenience.

Back to the main page »

Original

Preview

Link Preview

Issue #2

You can keep the pagination.
Accepted by admin
Mykhailo Komendant
TL;DR -
RULES_TOO_SLOW error caused by @inline function - is a template problem?


----
Just want to ask, if the site responds to the request of each page for more than 2 (5, 10) seconds, then this is a template problem?

How about caching content that obtained using the @inline function?

Combining articles divided into several pages, I use this issues as reference:
https://instantview.telegram.org/contest/takvim.com.tr/template19/issue1/
https://instantview.telegram.org/contest/indosport.com/template36/issue2/

And about RULES_TOO_SLOW error:
https://instantview.telegram.org/contest/aksam.com.tr/template26/issue1/

As I understand, in my case error caused by following line of code:
@inline: $nav//iframe

@inline make each request one by one (doesnt matter if I inline each frame in @map/@while loop, or use @inline on all frames at the same time), and if site responds too slow, we get such error in IV. Once when all subpages of article is cached (after 1-2 reloads), template will succefully generate IV
Declined by admin
Type of issue
IV not generated for target page
Reported
Mar 27, 2019