Jump to content

bfarber

Clients
  • Posts

    163,911
  • Joined

  • Days Won

    346

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Projects

Release Notes v5

Invision Community 5 Bug Tracker

Forums

Events

Store

Gallery

Everything posted by bfarber

  1. What is your recommendation for the caching period?
  2. Manifests were introduced in our last major release. There haven't been any feature change announcements for our next release yet.
  3. We don't comment on every suggestion - I don't have any specific comments right now, no.
  4. https://web.dev/native-lazy-loading Admittedly I haven't tested it, I was going directly by the documentation on the very website you linked to. Perhaps this sentence means prior to 76 you had to enable the flags, and if so that's great that it's out "stable" now. Still, if no other browsers support the functionality, and Chrome only began supporting this functionality 13 days ago, it's probably worth giving the feature some time to mature before jumping on it. ;)
  5. I'm not sure I know how to answer that. For the editor, when you paste a link in that we know an oembed endpoint can handle, we send it to that endpoint, and then generally embed the content that the endpoint returns. Look at the "html" property of this JSON object for instance - it has the full HTML to embed: https://api.instagram.com/oembed/?url=http://instagr.am/p/fA9uwTtkSN/
  6. It's only a beta feature (i.e. it's hidden behind a special flag you have to manually enable) in Chrome 76, which was released 13 days ago. I think we need to give a little time for this to mature first, but definitely when it does I think moving to natively supported browser functionality where possible would make sense.
  7. It should be noted that for the most part the site should validate fine out of the box. It's possible third party plugins or applications may not validate, or old content stored prior to upgrading or content imported via RSS may not validate, but generally the site should validate fine.
  8. No, you haven't. Search engines do not require a meta description tag in order to index a page - they never have, and over the years have only de-emphasized the importance of this tag, not relied upon it more heavily. Now, of course, it's possible that topics are not being indexed but should be in random cases and we can take a look at that, but I can unequivocally tell you that it is not because there isn't a meta description tag on the second page of a topic. We can take a look - thanks for bringing this up. 🙂
  9. But that's not what was asked, and the post is very misleading. Either way, the status of the original inquiry has not changed. But many clients do in fact use Adsense. I'll leave you to draw your own conclusions, however adsense does not need to log in to your site to display ads to logged in users - it needs to log in to your site if you display ads in areas where only logged in users can access. That is an important and material difference to the discussion. In other words, if you only display ads in areas that are accessible to guests (whether you display ads to guests, logged in members, or both), then you do not need to try to get the adsense crawler to log in to your site.
  10. I understand that....but that's not what the previous post said, so I responded to clarify.
  11. There is no off-the-shelf solution for SAML. In terms of setting it up, I assume you mean the integration on the community side and not the front end SAML instance itself. If that assumption is correct, without using a ready-made solution yes, it is quite a "pain" to add integration for SAML into the software unless you're very familiar with how SAML works and/or enjoy reading about the nitty gritty details of protocols. There is no guide for setting up SAML; it's not something you are able to do without custom code.
  12. You can display ads to logged in members, however if Adsense requires that a page be guest-viewable in order for ads to display there, then any pages which guests are unable to view would not be able to display ads. Some sites lock everything down and only logged in users can access basically anything. Some sites are pretty much wide open, guests just can't post. There's a lot of variation in how a site can be configured, so it's hard to give a one size fits all answer.
  13. I'll just note, we do also have an OpenID Connect solution, in addition to SAML, so if that is a preference you can also inquire with our sales department about OpenID Connect instead.
  14. Yeah, I would say that if you already have a PHP script written to output the data from your custom database table, just include that script using the template plugin mentioned above. That'll be easier than converting the code into our framework (unless your goal was learning how to use our framework).
  15. Elasticsearch will provide vastly superior search results, however it is a remote service so your community will need to make HTTP requests to it in order to index the content, and to fetch the search results. That said, the searching is faster than MySQL particularly for larger data sets. Generally speaking, if you get to a million or two posts, you should probably switch over to ElasticSearch. Before that point, you would really just need to try it out and see if you prefer it or not. If you have a really fast server and a relatively smaller site, you may find that local MySQL searches are sufficient, and perform faster, than a remote service.
  16. It's probable we will revisit the meta tags in an upcoming release, but can't say for certain when or if we'll implement exactly as outlined here.
  17. I can only say that this is on an internal suggestions tracker and is being considered for a future release.
  18. I don't think that's what the page is suggesting. I think it's merely pointing out the developer resources available to you simply by signing in with your Apple ID. Based on the documentation I've seen so far, it appears you will indeed need to be a part of their developer program (i.e. pay $99 per year) in order to use the "Sign in with Apple" feature they are releasing.
  19. The majority of reports we get were along the lines of "I can't click the Quote/Edit/Options links below this post". We'd investigate and find that Grammarly had inserted a large div into the post which was basically sitting on top of those links, making them unclickable. The issue mostly manifested when editing posts which had quotes in them, but this was not a sole factor. In any event, as we have no control over Grammarly's behavior or CKEditor's behavior in this context, the best we could do to prevent issues for our clients was to prevent Grammarly from inspecting the post content. You can still of course use their standalone app to write up posts, and then copy/paste those posts into the editor afterwards.
  20. Grammarly and CKEditor do not play well, and we received several bug reports about the same issue(s) related to how Grammarly modifies the DOM within an editor. In short = yes, there was an issue (or a couple of very related issues), and there was no way for us to resolve this outside of disabling Grammarly in the editor. It may return when we reach a point where we can upgrade to CKEditor 5. It is my understanding that the CKEditor devs and the Grammarly devs are working together on maximum compatibility, but won't be backporting that to CKEditor 4.
  21. Unless I'm misunderstanding, you can already use any CDN you wish. You set up where to store the files in the file configuration area, and then you can enter a custom URL (so you could store the files on a subdomain which your CDN sits in front of, and then set the custom URL routed through the CDN however your chosen CDN requires). We use CloudFront with our Community In The Cloud offerings, however the code is not specific to CloudFront.
  22. As it happens, this is on an internal discussion tracklist - but there's nothing else to report right now. I can't say if support will be included in any specific upcoming release yet.
  23. https://searchengineland.com/google-explains-crawl-budget-means-webmasters-267597 https://webmasters.googleblog.com/2017/01/what-crawl-budget-means-for-googlebot.html I'm afraid, it's not "nonsense". Google has a limited number of resources they can dedicate to each site, and they do just that. Posts do not represent a separate page and in fact the canonical URL that is embedded into the page points back to the topic (which is included in the sitemap).
  24. The more pages you send to Google to crawl, the more pages Google has to split its resources over. Google will have a finite "crawl budget" for your site - how much resources it will spend crawling your site. If you send Google a ton of links to crawl that are low quality, you ultimately take resources away from Google crawling your higher quality content. You will find that as usual, it's quality over quantity. You are incorrect about profiles not being included in the sitemap (there is an option to toggle it off in the AdminCP - make sure it's enabled). Example: https://invisioncommunity.com/sitemap.php?file=sitemap_profiles_1
  25. constants.php <?php define( 'NEXUS_TEST_GATEWAYS', true );
×
×
  • Create New...