Jump to content

opentype

Clients
  • Joined

  • Last visited

Everything posted by opentype

  1. opentype replied to Luis_angel's post in a topic in Feedback
    Even the existing “additional” apps (Pages, Blogs, Gallery, Downloads, Commerce) only get minor improvements every 1,5 to 2 years. IPS doesn’t have the resources to add another full-fledged app with the required functionality and if you look at which sites use Invision Community, only a fraction even has a use for an LMS. So it just doesn’t work. I am seeing paths to possible compromises though. For example: if Pages databases were coming to Clubs, clubs could be sold or offered for free as a “course” you sign up for—with all the lessons added as Pages database records, plus course forums, course calendar and so on. It still wouldn’t have all the bells and whistles of a LMS, but it could be a good solution for many and be fully native to Invision Community.
  2. opentype replied to Everade's post in a topic in Feedback
    PNG works fine on the web for a limited number of use cases like logos and other graphics. It was always bad for regular web content like pictures with a lot of information in them. Either huge files (PNG24) or very lossy (PNG8)—especially when processed through the regular web image libraries, which don’t do much optimization. So yeah, going from PNG to WebP will make a huge difference — but only in this very specific scenario of yours. One problem with WebP is that a cross-browser support only came very recently with Apple’s Big Sur OS. Before that and without a fallback solution in place, a WebP image would not render at all on millions of Apple devices (or very old Windows machines) and that continues to be the case for some time, since of course not everyone uses the latest operating system. When you weigh the pros (slightly smaller with slightly better image quality) and cons (might not show at all), the situation is only shifting slowly to the pro side. I agree with Joel by the way: the most important fix would be to allow WebP uploads—even if the delivery remains in a legacy format.
  3. JSON is just a way to store and exchange data—any data. It’s not meant for anything specific, like RSS is. So you likely always need a custom solution to map the external data structure to a suitable local structure, which in the case of Pages database is also custom in the sense that it can contain any number of fields of various types.
  4. It just needs to be uploaded as an attachment for the specific topic. It won’t work for images that are just embedded in the posts. The plugin only reads attachments.
  5. It will work for every topic that has an attachment – old or new. But social networks might cache older images if the link was shared before. So it might take some time to see the new og:image.
  6. What you ask for is already possible. You just need to be sure to turn reviews off or it will override the setting for leaving a rating. And yeah, the settings are a little scattered and category permissions sometimes confuse admins.
  7. It seams to be a problem of your default theme. I switched to “dark” and then the OG:image is set correctly. As an explanation: Theme hooks need be attached to a certain HTML code. In the specific case it’s: <div class="ipsClearfix"> … in the topic template, called via: #elClubContainer > div.ipsClearfix But if your theme designer changed or removed that code, then the hook will not be executed. You might pass on this information to your theme designer and maybe he adds that code back for you.
  8. Yes. That’s why it is not marked as compatible.
  9. As is explained in the screenshot you posted, you can use any name from FontAwesome 4.7. https://fontawesome.com/v4.7.0/icons/ “mask” is not on there.
  10. Well, no. Technically, the line-spacing stays the same. But your first post has three paragraphs and paragraphs, as a structural unit of the text, get additional spacing. There is an ACP setting called “Return Key Behavior”, which turns off the use of independent paragraphs, but I strongly suggest not to change that. There is no good reason to make forum posts in a typewriter-kinda-way in 2021. Proper structuring of the text is the best option. With CSS changes, one can also change the paragraph padding/margins, so the structure stays the same but the additional paragraph spacing is not used anymore.
  11. Custom CSS classes need to be whitelisted in the ACP. It’s an editor option. I am not sure the background task for the bb code will honour that option though. I am actually surprised to see your custom bb codes touched at all. Can’t remember that being the case when I upgraded a long time ago.
  12. I moved the content from my installation instruction PDFs to the “Addition Information” tab of each product. https://invisioncommunity.com/files/file/9544-pages-superdirectory/
  13. No, there is no way around that. Keep in mind that the plugin just reads RSS feeds, which also just provide a limited number of entries.
  14. opentype replied to TDBF's post in a topic in Feedback
    The topic mixes a few issues. I agree that “starting a checkout” should not create an invoice. Clicking the final “buy now” should. That’s when the sale is being made and that’s when the buyer can be charged through the invoice. (Note that this is unrelated from saving the basket and anything like that.) It’s not just a matter of practicality. It’s also a quite serious legal issue. If I ever get audited by our local tax department, I will have a lot of explaining to do about the non-consecutive invoice numbers I actually declare. The normal and expected procedure would be that each invoice number identifies an actual transaction with a payment and that “missing numbers” are an exception, where the invoice actually got cancelled and of course that needs a proof as well. With the current system, the tax department will likely assume that I didn’t properly declare the income for all these invoices and they might require evidence for what happened to each and every invoice number that I didn’t actually declare as income.
  15. You should be able to download the file from the Change Log section here on product page of the website.
  16. It’s intentional and mentioned on the product page.
  17. That won’t change. It’s the standard Pages paradigm. Listing view – Display view. It makes most sense for most databases, including voting databases, e.g. “movie title and some key facts“ on listing view and “full description + comments“ et cetera on display view. The display view can also be shown with whatever template you want. Changing the title links can be done by customizing the template though. Already possible and meant this way. You decide what fields you put in the listing view. Check the option to show “meta info”. The content field can be turned off as with any Pages database. (Make it not required. Remove permissions.) It’s both controlled through settings.
  18. Read the product page again, where the options and settings are explained.
  19. No, there is no option to change this. Again, it’s an IPS feature, meant to save space on mobile and my template just makes use of it. Have a look at this very topic you are writing in. It is doing exactly the same:
  20. Of course. The boxes going to the edge is intentional. That’s a feature IPS added to their theme in a recent version.
  21. opentype replied to opentype's post in a topic in Marketplace
    Yes. It’s in the plugin settings:
  22. It works like every database relationship field. In fact, this should work even if you deactivate SuperReviews. You link an entry in the review database: And then it should show on the review record page: And if cross-links are activated, it will show on the record in the foreign database for the entries being reviewed:
  23. The settings on the screenshots look correct. As soon as you add a car link to one of the review entries, it should appear on the car page.
  24. opentype replied to opentype's post in a topic in Marketplace
    Yes, that is intentional. If there is no dedicated image for the article, there is no point in wasting so much space on the article page. In the listing view, the space is used with or without an article image, so the fallback image makes more sense there.