Jump to content

Ryan Ashbrook

Invision Community Team
  • Posts

    12,669
  • Joined

  • Days Won

    13

 Content Type 

Downloads

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Development Blog

Deprecation Tracker

Providers Directory

Forums

Events

Store

Gallery

Everything posted by Ryan Ashbrook

  1. Unfortunately, this is not possible at this time.
  2. There is no way to prevent that cookie from being set, because it is being set by PHP itself (we use the built-in PHP session handling with a custom handler to push them to the database). You should be able to configure your Cloudfront distribution to ignore that particular cookie for caching purposes, however, though this is unfortunately not something we can assist with.
  3. Unfortunately, no - the problem actually lies within CKEditor itself. We have reported the issue to them (multiple times, actually) however they have never resolved the problem.
  4. Zapier can likely do this: https://zapier.com/apps/discord/integrations/invision-community
  5. Yes, this comes standard as a part of the 4.7.1 update. 🙂
  6. We're aware of this issue and working on resolving it.
  7. Go to your Admin CP, click the bell in the top right, then click Notification Settings on the top right of the menu. On that page, look for this section, and select either "Yes - once until addressed" or "Yes - every occurrence", depending on your preference.
  8. Hmm... I'll make a note of this. InnoDB is always preferred because it uses row level locking, rather than table level locking like MyISAM. I see forums_posts is in the MyISAM column when that's probably the most important table (outside of core_search_index) to be InnoDB.
  9. A fix for this will be included in 4.7.2.
  10. A fix for this will be included in 4.7.2.
  11. In addition to that, instead of using \IPS\Session\Front::i(); for external scripts you should use \IPS\Dispatcher\External::i();
  12. You would likely have better control over things like this if you place your S3 bucket behind a Cloudfront distribution. It's a bit complex, but you can achieve some very specific caching situations.
  13. That is a legacy column that is no longer used since the latest versions of IPS4 use the password_hash function. That column is still referenced, however, if a user has not logged in since an upgrade from IPB3, so the system can update the password hash to the new version.
  14. For what it's worth, the current application and module is already loaded by the dispatcher (as mentioned by CodingJungle), so it won't reload it - it would just use the existing data already in memory. Additionally, applications and modules are cached in the data store so loading them on the fly should have very little effect on performance.
  15. As Marc mentioned, this is likely an out of date theme. Specifically, the forums > topics > topic template. If you open that template in your theme, click the Variables button and make sure it looks like this: $topic, $comments, $question=NULL, $votes=array(), $nextUnread=NULL, $pagination=NULL, $topicVotes=array()
  16. Your community is appearing online for me, currently. What specifically are you seeing? We did have a brief outage earlier that has since been resolved. You can see the current status (and subscribe for future notifications) at https://status.invisioncommunity.com
  17. Only Forums, Blogs, and custom fields in certain areas support Polls at this time.
  18. Yes, that is legitimate code used by Facebook Pixel. You can learn more about that here. It's harmless, and doesn't actually show on the site itself unless you specifically enable it. Since you appear to be using template disk caching (which is why you found that in a file in the uploads directory), if you delete the file then it will simply automatically regenerate.
  19. This is kind of a difficult scenario - technically, they are in fact two different pages (and you can see this when you look at the View a category button on the right, above the entry list). The first one is the overall blog, which would show every single entry. The second is viewing a specific category within that blog, which would only show entries in that specific category. If that user posted another entry within that blog, but in a different category, the issue would resolve itself because the first link would show both entries, whereas the second would continue to show just the one. So then you have the opposite problem, in this scenario, with the canonical link pointing to the root blog while viewing a category, instead of pointing to the category itself.
  20. If you click the link to Recount, it will give you the option to do either that individual member, or all members.
  21. At the end of the day, I'm not sure it really matters, so whichever you feel is best will work fine.
  22. The only table that would have been created during upgrade would have been the calendar_events table - and technically, it wasn't actually created but rather renamed from the old cal_events table for the Calendar application. I am unsure of the other two tables - the first one looks like a third party application, and the second one looks to have been a copy of the posts table (which was renamed to forums_posts). Searching through both IPS4 and IP.Board 3, and there is no reference at all to any "posts2" table. Regardless of where they came from, it is fine to simply change them to InnoDB.
×
×
  • Create New...