Jump to content

Matt

Management
  • Posts

    70,143
  • Joined

  • Last visited

  • Days Won

    649

 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 Matt

  1. I've released a patch so that custom CSS in other areas, and also CSS that has been edited is now visible when editing a theme.
  2. I accept that the very few who make significant edits to our core CSS will find this change uncomfortable. The vast majority want to add or override existing CSS, so this change will not affect them. We want to get to a point where we can serve CSS from a single set of files via a CDN. We also want to overhaul and modernise our CSS for efficiency and enabling a more streamlined output from a better build process. These things do take time, and we have to take steps towards that goal, and drawing a line with 4.7.0 and asking that core CSS is not edited is the first step towards this. As a temporary measure, a template edit in core/front/global/includeCSS to remove the framework CSS and instead link to a separate directory of your own optimised CSS would enable you to carry on with your heavily optimised CSS. I can help you with this if you wanted to explore this.
  3. That's fair. I can add this to our development documentation. I'm working on an upgrade step to resolve this. 👍
  4. I don't understand what the issue is @Adlago? You can still edit and add custom CSS.
  5. As mentioned above, we would prefer that the core CSS is not edited, and instead that you use the custom/ folder(s) to add your custom CSS. This gives us the option in the future to serve all CSS from a single set of CSS files on a fast CDN. There is an issue with those that *have* edited core CSS files, and I'm working on an update to solve that.
  6. Custom theme? I do recall a mod or theme recently that used 'large' without quotes and it was treated as a constant and silently ignored previous to PHP 8. The word 'large' is not used in that default template for the userPhoto.
  7. As of 4.7.0, only true custom CSS files will show to discourage editing framework CSS. Have you edited framework CSS files in the past?
  8. This is a great question, so I asked it on Twitter to get some advice from some experienced community managers:
  9. I love how clean this looks @SjorsK
  10. I would say that bulk emails are very different from a targeted post-registration drip campaign but I appreciate that in your part of the world, companies are actively being handed fines for non-compliance while the rest of the world shrugs.
  11. My understanding is that you can send emails related to the service they signed up for. It's when you start sending them adverts for other services that you are on shaky ground. Sending a sequence of welcome emails and guidance how to use the community is fair, and I cannot see how this would be deemed "illegal". We work with brands in the EU who have whole departments dedicated to legal and they have no issue with a welcome email sequence.
  12. I don't really see what advantages the others have over CKEditor 5. Whichever we choose, there is a significant time investment to rewrite our plugins and parts of our uploader, etc.
  13. This is probably what we'll do.
  14. This is definitely very much on our minds. 🙂
  15. You can set the write permissions via constants: 'IPS_FOLDER_PERMISSION' => 0777, // Writeable folders 'FOLDER_PERMISSION_NO_WRITE' => 0755, // Non-writeable folders 'IPS_FILE_PERMISSION' => 0666, // Writeable files 'FILE_PERMISSION_NO_WRITE' => 0644, // Non-writeable files
  16. Hi Chris, I've opened a ticket for you. We'll take a look and see if we can see what is going on.
  17. This is fixed and will be in the next 4.7.0 release.
  18. Automated tools are very useful in helping you ensure your site is compliant and secure but sometimes they mark you down for things that just aren't a problem in the real world. We work with some of the world's biggest brands who often bring in third party security specialists and not once have we been asked to use this prefix. If you redirect your site from http to https then the impact is minimal. The blog linked above was written in 2017 when SSL was very much optional for most of the web, but now browsers really enforce SSL so it's less of a problem. The author and MDN note that not all browsers (including Safari and Firefox) support the prefix and will serve the cookie anyway making it a little pointless outside of an internal network where you can enforce which browsers can be used.
  19. Are you concerned about brute force log in attempts? We have built in protection for this as multiple failed attempts to log into a user account lock the account for 15 minutes.
  20. I believe CKEditor fixed this in their 4.18.1 version. Invision Community 4.6 uses 4.18.0. We have upgraded to 4.19 for Invision Community 4.7, so the issue should be resolved then.
  21. We have not tested extensively with MySQL 8. Our recommended version is 5.6 (MySQL went from 5.7 to 8). I suspect MySQL 8 is the issue here.
  22. I agree with checkout, but I'll need to think about /search as this would exclude the tag search results which have some SEO merit.
  23. It's worth using the browsers dev tools to check the console to see if it's an error loading a CSS file when this occurs.
  24. A fix is in review and should make it for the June release.
×
×
  • Create New...