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. In your test, the file is being refetched from the server/host but for most end users the file will be cached in the user's browser after their first visit. This means that on every page load after the first, the font file does not need to be redownloaded or reprocessed. Like everything in development, it's a trade off. This approach tends to be more efficient than multiple separate images, for instance. They may download in parallel, but will consume more storage space (and subsequently require more "management") and bandwidth. We feel our current approach is presently the best solution, but as Rikki said we will continue evaluating and if (when) a better solution becomes mainstream we will certainly use it.
  2. That error happens if you reach the page to crop your profile photo, but don't have any profile photo stored. We'd recommend submitting a ticket if you require assistance. And this highlights the problem with having a generic database of error codes and messages. It can't really (typically at least) tell you the problem or how to solve it. Often it requires a human to intervene and determine the issue, and in cases where the error handling is just flat out insufficient, we try to improve the error messages to make them clearer and more actionable.
  3. Just a few points from me... 1) In my POV it is far better for you to create individual topics for individual requests. It is rare that we spend time reviewing large "how about all of these things" topics because frankly it's difficult and time consuming. We can and do, however, flag individual requests for follow up on our side quite often. 2) We absolutely DO base our changes off of requests clients have made. They may not be requests YOU have made, but why would we (as a business) spend time implementing things no one wants? That's just illogical. It's important to remember that we get feedback from many different sources (this forum being but one of them) and you may simply not be aware of common things we hear about from other avenues. 3) We'll be sticking with PHP for 5.0.
  4. You should visit Customization > Themes in the AdminCP, click the dropdown next to your theme and go to Manage Resources. Upload the font here, and then take the replacement tag (which generates the URL) and use that in your custom.css. Your solution is fine and will work, but the above method will benefit from using our storage handling system properly. i.e. if you move your theme resources to S3 for performance reasons, your font would be moved as well, and the CSS file would automatically update to reflect the new URL.
  5. Blocks will cache, but we're talking somewhere around 30-300 seconds typically, not a week. My best recommendation is to submit a ticket.
  6. That worked? Because this looks like a broken query: $sql="update ibf_forums_posts set post = replace(post, '".$name."', 'Nickname You Want'";
  7. Are you accounting for block caching (widgets are cached for a period of time and so the same image would be shown to everyone while the block is cached)? This is not specific to the "random gallery image" block but really to any block.
  8. Doesn't really answer my question, however. I can go to any site and post someone's name...that's not the same as retaining records of a user unnecessarily. But anyways, I'm not going to get drawn into a legal debate about GDPR right now. 😛
  9. What happens (or should happen) exactly if I visit a random forum on the internet right now and post about "Jibeji"? Is the site liable to remove that? Is that "personally identifying information"?
  10. I looked, and while interesting - exactly 0% of our clients (who have usage reporting enabled) have this installed, so it doesn't really make much sense to invest time in developing integration for the new library. Hopefully that changes in due course and we can revisit this.
  11. Ever since its first release, the REST API built into the Invision Community software has proven to be a very powerful and well-received feature. We love seeing what our clients and modification authors are able to do with the level of integration afforded to them through this capability, and so it is only natural that we have looked to expand the functionality in our upcoming 4.4 release. Poll Support Beginning with 4.4, you will now be able to create and update polls for both topics and blog entries through the REST API. Of course, modification authors can use this new endpoint. Warn Reasons You will also now be able to manage warn reasons through the REST API. This includes fetching a list of reasons, as well as fetching an individual reason, creating warn reasons, updating existing warn reasons, and deleting warn reasons. Event Venues Event venues can now be listed and individual venues fetched through the REST API, and you can now add, update and delete event venues through the REST API. Member Notifications You can now retrieve a list of notifications for a specific member through the REST API, useful if you were to attempt to recreate the notifications menu on a third party website (for example). Warning Users The REST API will now expose the warnings a user has received through a new endpoint. Additionally, you can fetch individual warnings, issue new warnings, undo and/or delete issued warnings, and acknowledge warnings through the REST API. If you are building a site wrapper around your community, you can leverage this functionality to ensure that users are unable to post elsewhere on your site if they have unacknowledged warnings within the community (and also to provide them with a way to acknowledge those warnings right on your site). The REST API Reference Node permissions Beginning with 4.4, you will now be able to set the permissions for a node when adding or updating it through the REST API (for example, you can now adjust the permissions for a forum or a downloads category through the REST API). Many clients noticed that while they could create new nodes through the API, the nodes would be unusable until an administrator manually went in and specified the permissions, so this change can eliminate this extra step in many situations. Event filtering You will now also be able to filter the events you pull through the Calendar REST API endpoints by start and end date (e.g. so you can show events within a specific time frame, such as the current week), and you can now also specify to sort the events returned by the event start date or the event end date. Clubs And finally, for those who leverage clubs on their communities, we have built in full REST API support for clubs. You can list all clubs, return a specific club, create new clubs, update existing clubs, and delete clubs through the REST API. Further, you can list all members in a club, add a specific member to a specific club, remove a member from a club, fetch the content types available for use within a club (i.e. so you can determine which applications are installed and have club support on a given site), fetch the nodes (displayed as tabs/sections within a club) created within a club, and delete nodes from a club. Important behind the scenes steps, such as generating invoices for members requesting to join paid clubs, are all handled automatically for you when using the REST API. We believe these changes will help clients better integrate with our software and open up new possibilities with their websites. Would you like us to add any other endpoints? Let us know in the comments below!
  12. If you require support or assistance, I would encourage you to post in the appropriate peer feedback forum or submit a ticket. This area is more intended for suggestions for future changes in the software. 🙂
  13. bfarber

    reCAPTCHA v3

    reCAPTCHA3 was only released a couple weeks ago. It is indeed something we will look into closer, although I can't promise any specific version target for inclusion.
  14. Yes, of course we see our own feedback forums. 😉
  15. You can use the live meta tag editor to do this. From the AdminCP visit System > Site Promotion > Search Engine Optimization > Meta Tags (tab)
  16. We use Instagram's oembed endpoint. You can test their URLs yourself here: https://api.instagram.com/oembed/?url=https://www.instagram.com/coryrichards/ ^ Doesn't work Example working URL: https://api.instagram.com/oembed/?url=http://instagr.am/p/fA9uwTtkSN/ We don't control which Instagram URLs Instagram will support with their oembed endpoint I'm afraid.
  17. Are we talking capital latin characters, or capital letters in another language?
  18. Look through our community here - is og:title missing on any of our pages? I don't believe so, certainly not on the index page. We haven't uploaded a default sharer image, so og:image will only be set when appropriate.
  19. og:title should not be missing on any page whatsoever. If it is, I suspect that might be an issue with a custom theme. og:image will be present on every single page so long as you upload a default image (edit your theme and visit the Logos tab to upload a default social sharer image, which will be overridden when there is a more specific or appropriate image throughout the site). Twitter cards themselves have been implemented, but naturally it will depend on the context of each individual page which tags are produced.
  20. Until you realize that search results can contain results from all different apps, which can have different moderation permission configurations and options (e.g. you can't "move" a status update). While this doesn't make the request insurmountable, there's actually a lot more to it than just slapping up some checkboxes and calling it a day in reality.
  21. Well, you have options depending upon your comfort level. The simplest solution for most of our clients is to create a PNG image twice the size of your logo (as @Joy Rex just alluded to) and upload that as your logo in the theme. You may or may not need to tinker with some size settings or CSS to ensure the logo displays at the height you want. If you're comfortable with CSS and HTML (and our theme manager), you could upload separate regular and 2x sized images using the Manage Theme Resources tool, and then manually reference them in the template correctly (using srcset and sizes attributes). Or if you understand SVGs well enough, you could upload those and reference those in the template as well, just the same. Basically you have two routes: The easy route is to just upload a logo image using the built in uploader The longer route that gives you more control is to manually upload your files to the manage resources page, and then adjust the logo template accordingly
  22. Just to be clear, the SVG mention in the blog entry relates specifically to the Safari Mask Icon, not the theme header/logo. A custom theme can add custom theme options, including the ability to upload an SVG logo.
  23. Who remembers the earlier days of the internet? Back when you popped your logo at the top left of your site and you were largely done? Invision Community has continually developed to account for all the new services that have been built during our 16 years. We now have social media sharing images, favicons and more to consider. Invision Community 4.4 also adds mobile application icons, Safari mask icons and data for an application manifest. Handling of these logos and icons was a prime candidate for improvement in 4.4. Moving our current options Step one for improving our handling of these images was to move our current options out of themes and to allow them to be managed suite-wide from a single area. You can still upload a logo image per-theme (which shows in the header area), but the rest of the options have now been relocated to a new area: Customization > Appearance > Icons & Logos. Adding new options After giving favicon and share logo management its own dedicated area, we took a look at enhancing the configuration options made available through the interface without requiring theme template edits. Multiple share logos You can now upload multiple share logos. If you elect to upload more than one share logo, Facebook and similar sites will generally either show a carousel to allow you to choose which logo to use when sharing, or simply use the first image referenced. Application icons You can now upload an image to represent your website which will be used to generate the "home screen" icons for iPhones and Androids automatically. Uploading a single image will result in several different copies of the image (in different dimensions) being generated, and mobile devices will automatically choose the best option from the list as needed. Safari mask icon You can also now upload a Safari Mask icon, which is used to represent your website in certain areas on Apple computers (such as on the "touchbar" of certain keyboards). This image must be an SVG image with a transparent background, and all vectors must be 100% black. Additionally, you can specify the mask color which is used to offset your image when necessary (e.g. to represent it as "selected" or "active"). Application manifest In order for devices to support the application icons that you upload, a file known as a web manifest must be generated and delivered to the browser. This now happens automatically, using details and icons specified in the AdminCP. Certain details, however, can be configured explicitly from the Icons & Logos page: Short name This is a short name to represent your site in areas with limited screen space, such as below your application icon on a mobile phone home screen. Site name This is the name of the site. The "Website name" setting is automatically used if you do not explicitly override it when configuring the manifest. Description A short description of your site Theme color You can choose a (single) color to represent the general theme of the site. This color may be used by devices in areas such as the address bar background. Background color You can also choose a (single) color to use as the background color for your site when the application is launched from a shortcut saved to the user's device home screen. Display mode Finally, you can specify the display mode your site should launch in. For our more astute designers and developers, you may have already realized that generating the manifest file lays the groundwork for future PWA (Progressive Web App) development and support. Additionally, some Android devices will automatically prompt users to add your website to their home screen now that a manifest file is generated by the site. Oh, and for the sake of completeness, we also generate the special browserconfig.xml file that Microsoft products (including Microsoft Edge, Internet Explorer, X-Box, and Microsoft-based mobile devices) look for when pinning sites and generating live tiles. There are no additional configuration options for this file - everything is automatically generated from the aforementioned options. The end result? Your community can now better convey, automatically, certain details to the myriad of devices out there that may be accessing your site, and you now have much better control over those details. You can more easily fine-tune the "little things" that help paint a complete picture of your web presence, and the groundwork has been laid for bigger and better things in the future as standardization and adoption of PWA functionality improves. This blog is part of our series introducing new features for Invision Community 4.4.
  24. This is something we want to look into closer in a future release.
  25. As has been alluded to, there is no dedicated "print X" (i.e. "print topic") option anymore. Instead, we apply print styles to the page and you can print directly from your browser. If the page is still too heavy for your liking, you can further tweak the print CSS using custom.css in your theme.
×
×
  • Create New...