Your comments
Hi everyone!
As I said in my previous post, we investigated this issue and found that the "Insticator" code was part of a beta test for the paid recommendations program and was implemented on a handful of sites. This code has been removed from these sites for now, while we ask the vendor to look into the issue and while we perform some further investigating ourselves. We actually do not have any confirmation that there was a bad ad on their network, nonetheless they have blocked the URL in question.
Also, prior to placing this code on these beta sites, someone at the site, usually on the advertising side, was notified and provided permission to move forward with the test.
Viruses, malware, and "bad ads" that cause mobile redirects and other situations are rare, but they can unfortunately happen and are usually very hard to track down.
We are also looking into other techniques and technologies that may be useful to help reduce these types of issues.
If you see this happening in the future, and you can reproduce it, please submit a ticket to our Customer Support staff with the URL of the page where it happened, the resulting landing page URL and any information you have about the ad (such as a screenshot, HTML source code, etc.) and we will see if we can reproduce it locally. If we are able to determine further where the redirect source might be, we can notify our partners of the URL so the issue can be addressed.
As a side note, Greg, are you still having issues?
Right now we offer “infinity summary” mode… where it is the headline and summary of the article, not the whole article which is what you're asking about.
The problem is that it has to be done with 100% JavaScript, and our templates are quite complex that this becomes difficult. We actually (like 2 weeks ago) just had a meeting about this… we are thinking we could provide really super simple pages and then build them up over time.
For example… we wouldn't have a photo gallery slideshow at the top (to start, anyway). We probably wouldn't have metering and/or subscription at launch. And there may be some ad tech that we would leave off.
What do you think of that idea?
Also, I've been hearing from some partners that they would prefer a "load more" infinity scroll instead of true infinity. That way you can reach the footer if desired.
I just wanted to post something really quickly to update you that we have been investigating the details on this and found that the Insticator code was part of a beta test through our paid recommendations program. It has been disabled as we look at whether or not it was involved and so forth. I will have more info in the morning!
Hi Robert!
I did respond to your email as well, but I will add some information here as well so that others can have it as a reference.
NOTE: We have a temporary "fallback" mode that we can enable on your site if you are worried about your icons. This mode will run Font Awesome 4 CSS and classes temporarily in case you (or we) need to make updates. Then, we turn off the "fallback" mode which will switch you back to Font Awesome 5. Please submit a Customer Support ticket if you think there will be an issue.
Firstly, there is more information in this link:
A few important things to note:
- We are not using ALL icons - only a subset, so we can keep the library as small as possible. If you need us to add an icon (we've had a few requests already), just let us know and we can evaluate it.
- For now we are only including some of the branding library, some solid and some regular. We don't use the "light" icons so those are not included at this time. The link above has links to lists of every icon we offer, and as we add more we will add them to those lists.
- Note that we are doing our own namespace for tnt-[name] as shown in the example in the link. This way it will be easier for us to make changes in the future.
- Styling for the FA5 icons will use the tnt-* prefix as well. Example: tnt-2x, tnt-fw, tnt-layers.
Let me know if anyone has questions or if you need more information!
Correct... the idea behind the summary field is that you can use it to override a bad truncated summary, because it is cut off awkwardly or because it is too short.
We have been consulted about the initiative as part of our Google partnership and as part of our AMP integration, but aren't yet part of the beta.
We do have Single Sign-in available now through oAuth 2.0. Here is a page on how to do this: https://help.bloxcms.com/knowledge-base/applications/settings/users/federated_authentication/article_ec11c076-fab5-11e6-b45b-ef23752afc52.html
So, once authenticated, you can log into the BLOX front-end with no sign-in as long as you're signed in to Google.
(We have Facebook authentication as well, which is popular.)
The /app directory should allow http or https as long as you are calling that from the original code. You would need to ensure that the reference in the code is actually pointing to https however. Protocol-less will also work, but these days we recommend just doing straight secure always, regardless of whether or not your site is secure.
In other words, if your website is asking for an image in the /app directory, it needs to say:
<img src="https://example.com/app/images/image.jpg">
instead of:
<img src="http://example.com/app/images/image.jpg">
If you're doing this already and it isn't working - please let me a link (you can create a job ticket also) so we can look.
Hi again Elizabeth!
Where you able to get this working? If the original issue was "Can't fetch feed." or something like that, I just saw a post that Amazon may now be accepting Let's Encrypt certificates, so this problem may be fixed.
Customer support service by UserEcho
