Jump to content

13.

Members
  • Posts

    1,194
  • Joined

  • Days Won

    5

 Content Type 

Profiles

Downloads

IPS4 Providers

Release Notes

IPS4 Guides

IPS4 Developer Documentation

Invision Community Blog

Forums

Store

Everything posted by 13.

  1. Yes, make it optional with the ability to upload the custom sound.
  2. It would be better to use the native method everywhere and fallback to the JS-based method only when needed, so the majority of users of modern browsers won't experience problems just because of a minority of technically backward Apple browsers. It's very easy because native lazy loading works perfectly fine when used with JS-based method at the same time.
  3. OpenSearch is the Elasticsearch alternative with open source and Apache 2.0 Licence. https://opensearch.org
  4. When we paste URLs in the editor, some of them are automatically handled as a link, for example: https://www.google.com/ But it does not work if the domain is IDN, e.g.: https://xn--90adahrqfmec.xn--p1ai/ The expected behavior is conversion to link like this: https://гемоглобин.рф But it simply does not work here, even though there is a clear indication of the HTTPS protocol.
  5. @idioteque, explain your problem in more detail.
  6. For me, it is not important which editor to use, but how exactly it will be customized by IPS. The main thing I hope for is that IPS won't carry over all the same bugs that they added to the current editor and haven't been fixing for years. Such as the complete inability to delete mentions in mobile Chrome, for example: 1620649541089.mp4 As well as get rid of additional overcomplications, such as replacing existing editor functions. For example, fast and easy URL embedding on clumsy and slow: 👍 👎
  7. .htaccess rule for all xml and json files: <FilesMatch "\.(xml|json)$"> Order Deny,Allow Deny from all </FilesMatch>
  8. It's still not fixed even in 4.6.x 😞 https://invisioncommunity.com/applications/core/data/versions.json https://invisioncommunity.com/applications/core/data/theme.xml
  9. I wonder why image extensions are hardcoded instead of option in ACP? It would be great to have this as an option, so everyone who cares about modern image formats could add them there without any code.
  10. Some time ago, I described how I solved this problem for one of my communities.
  11. Better not just Amazon, but also (at least) FFmpeg.
  12. I also would love to see here an option to display these messages to all users but without mentioning the exact moderator, who performed the action. I.e., groups with permissions will see: %username% changed the title from "ABC" to "123" %username% moved %n% messages to the %topic% While ordinary users will see: Moderator changed the title from "ABC" to "123" Moderator moved %n% messages to the %topic% Where %username% is the username and Moderator is just text.
  13. It looks like one important question was missed in the off-topic messages flow:
  14. Check if this problem exists in the default theme. If it reproduces even there, then submit a ticket with a bug report (ticket) in your client area.
  15. You (IPS) can load polyfills only when they are needed and don't waste the traffic for the majority of browsers.
  16. Also, I would love to see limits for the number of reactions of the specific types given to one user within some defined period, i.e.: Maximum number of positive reactions allowed to give per user [value] per [period] Maximum number of negative reactions allowed to give per user [value] per [period]
  17. The easiest way to filter all ancient browsers from the IE epoch is just checking if CSS or CSS.supports are missed, because it present in all modern browsers and Edge 12+. if (typeof(CSS) === "undefined" || typeof(CSS.supports) === "undefined") { // Here you can do whatever you want to the visitors with ancient browsers from the IE epoch console.log('Your browser is out of date'); }
  18. It looks like CSS Custom Properties currently are not used, so it would be easier to create correct checks if IPS tell us which exactly features not supported in older browsers they used in 4.5+.
  19. For IPS 4.4, changed this: <li><a class='ipsType_blendLinks' href='{$comment->item()->url()->setQueryString( array( 'do' => 'findComment', 'comment' => $comment->$idField ) )}' data-ipsTooltip title='{lang="share_this_post"}' data-ipsMenu data-ipsMenu-closeOnClick='false' id='elSharePost_{$comment->$idField}' data-role='shareComment'><i class='fa fa-share-alt'></i></a></li> to this: <li><a class='ipsType_blendLinks' href='{$comment->item()->url()->setQueryString( array( 'do' => 'findComment', 'comment' => $comment->$idField ) )}' data-ipsTooltip title='{lang="share_this_post"}' data-ipsMenu data-ipsMenu-closeOnClick='false' id='elSharePost_{$comment->$idField}' data-role='shareComment'>#{$comment->$idField} <i class='fa fa-share-alt'></i></a></li> In this template:
  20. Actually not only IE but all browsers which do not support modern features like CSS Custom Properties, etc. Sticking to IE in these checks is a bad idea.
×
×
  • Create New...