Contest - Instant View

Processed Issues6

This page shows a list of issues for tw2sl.com that were approved or declined by our admins.

Template #1 å	Issue #1 Jun 3, 2017	Pavel T. Service area (contact form) Accepted by admin This page must not generate an IV in accordance to 2.2 of Perfect Template Checklist: https://instantview.telegram.org/checklist#2-2-pages-that-require-significant-interaction
Template #2 Pavel T.	Issue #1 Jun 6, 2017	Deleted Account 1.1. Pages with static article-like content (Documentation) Accepted by admin
Template #6 Dinozaur	Issue #1 Jun 13, 2017	Pavel T. Trashy seo-text with duplicates of title/meta which exists in every article Dinozaur Trashy or not - it's not up to you. This text is contained in the original, so it should be displayed. Declined by admin
Template #6 Dinozaur	Issue #2 Jun 14, 2017	Pavel T. I repeat my previous issue with comments: this parts containing SEO trash exists in EVERY article and, i think, generated automatically by SEO-widgets. They're NOT parts of main article text. Main article text is wrapped in one more <div> like on many arabic sites. In my template all articles work correct without these trashy parts. Dinozaur I repeat my previous answear: Trashy or not - it's not up to you. This text is contained in the original, so it should be displayed. and They ARE parts of main article text. Open your eyes! Stop trying cheat me and Telegram's administrators. Declined by admin Agreed with creator. Seems to be a normal text.
Template #6 Dinozaur	Issue #3 Jun 15, 2017	Pavel T. Missed captions Accepted by admin
Template #11 Dinozaur	Issue #1 Jun 18, 2017	Pavel T. 404 page Dinozaur This is not tw2sl.com/404.html page The error message is the text of the article itself. Declined by admin Declined by admin We think that generating IVs for these pages is optional. Both template 11 and template 12 handle them in an acceptable way. We plan on adding protection for IVs of pages that suddenly stop being accessible or start returning significantly less data than before. Both T11 and T12 would work well for this page when this protection is added. T12's solution would've been preferable if these pages became periodically unavailable and then came back, but our research so far shows that they stay unavailable once pulled.