Jump to content

opentype

Clients
  • Posts

    9,933
  • Joined

  • Last visited

  • Days Won

    137

 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 opentype

  1. You can tell Google to not index images through the robots.txt.
  2. Turn on the group setting to moderate new posts from new members and approve them manually. Automatic methods to detect spam will always be limited.
  3. It looks like you are accidentally using Apple’s Reading View. https://www.makeuseof.com/how-to-use-reader-view-in-safari/
  4. There is a short registration confirmation email. You can just change the language string “email_reg_complete” in the translation settings and turn it into a welcome message. That’s what I do.
  5. Yes. You probably don’t see it because you are looking at your own records, which you can’t react to.
  6. It’s also a database/category level permission. Also, pay attention to the difference between reviews and ratings. Only one system can be active at a time.
  7. Articles (aka Pages databases) have ratings. I use it all the time.
  8. opentype

    IC5: Theme Tools

    Real-world example: for my many Pages databases, the output of the database relationship field as comma-separated list is usually insufficient, so I would replace what’s in cms -> front -> global -> basicRelationship and add record images, grid views and so on. How would I do that now? From what I understand from the article, I would only be able to add stuff at dedicated locations, not replace anything.
  9. Plain text. I’m still surprised this isn’t the default with the IPS suite, even though it is everywhere else. You can’t paste color text in Facebook, Twitter and so on. It would only cause issues – as it does in Invision Community.
  10. Again, it goes on a listing page. The database front-page mode is not that. Categories are not relevant.
  11. You need to drag the filter widget on a database listing page. That’s what this setting is for. It can’t be tied to the badge display itself without custom coding.
  12. It’s also required for proper invoicing in many jurisdictions. So, I doubt that will be touched/removed.
  13. How do you define “new user”? A recently created account or an account created AFTER the terms were changed. The latter should certainly not be forced on an acceptance page again. They already accept the terms during registration. But once you force an acceptance after a change of the terms, all existent users will have to accept the terms. That would be working as intended. It also doesn’t matter that you try to save the terms again and this time don’t choose that option. You still have the pending acceptance from the first time. This has nothing to do with UX choices. It’s a legal requirement. The Terms of Service are a legally binding agreement and substantial changes need to be agreed upon. You can’t just make silent changes. That is why this intrusive process is necessary.
  14. The solution for the “phone problem” is to reduce the size allowed for attachments. On top of that, compression settings for uploads are also available. That covers almost every use case. Very few people would need to mess around with additional options to convert the existing content.
  15. But then you would manually have to feature and unfeature records to show them as new. The better options would be to use a custom field to create your custom badge(s). Here is a tutorial for a multi-badge setup from one field: https://www.opentype.space/superdocs/ips-community-tips/pages/multi-color-select-box-badges-with-pages-r16/
  16. Just for the sake of completeness: the official solution is … Turn on “Moderate new records” in the database settings Assign an “author group” to the users Change the database permissions to allow “add record” for this group
  17. It always worked like that in 4.x. I usually avoid using default values for fields because of this behaviour. I’m sure it’s all “working as intended”, just not exactly what a user (or even admin) would expect. Suggestions: show the actual number of filtered items don’t pre-select default field values (which are useful in the record form and during record creation) in the filter widget. (Clover’s point 3 is just a side-effect of point 2.)
  18. No. But it’s impossible to say what is going on based on just this screenshot. In fact, it’s not even a problem if the user has already validated their account and keeps clicking the validation link. Then getting that message would be expected and there would be no “issue” to fix.
  19. The error doesn’t point to a specific problem. You would need to narrow down the cause first. Could be a problem with the email links (changed by the mail provider?). Could be a caching issue. Could be admin interference (where accounts are approved before the user does it). Could be the links are simply clicked multiple times …
  20. It would require customization of the feed template. A Pages record reply is treated like a forum reply, which also doesn’t repeat the attachments posted to the original post.
  21. You can do that with the Pages app. Or just blocks, where you hide content from guests and show your blocks to guests only. There is even a “Guest Signup Widget” included with the software. It may not exactly do what you want, but it is made for the purpose you ask about.
  22. Put “register” in the search bar. The specific one should be popupRegisterTemplate.
  23. They have to reset their password and need to know their email address.
  24. Not much space in blocks, so it uses a reduced reaction counter there.
  25. Some nice ideas there. I’m not a fan of minimizing the user info in the topic view though. The personal touch of clearly seeing who you are interacting with is getting more important these days, not less. If anything, this view should only be triggered if there is not enough space, not in full desktop view. As a typographer, the example screenshot is painful to look at. 3 posts with just one or two lines each that are waaaaaaaay too long for comfortable reading. This was always a problem with a default IPS installations but now it was made worse, not better. If the user info remains to the side, it also improves the readability of the post content.
×
×
  • Create New...