Jump to content

Marc

Invision Community Team
  • Posts

    15,659
  • Joined

  • Last visited

  • Days Won

    274

 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 Marc

  1. As with the other items, please clear browser cache and site cache and try this again
  2. Please could you clear your browser cache and try it again? Im having no issues this end, and I suspect you may be having cache issues from prior to the upgrade. Also please try clearing cache in the admin CP. If either of those work, let us know which. If the above doesnt, let me know which browser and OS you are on
  3. We do not provide 3rd party language pack or application support unfortunately. It would be worth taking a look through the providers area here, where people advertise their sites and services https://invisioncommunity.com/third-party/providers-directory/
  4. Glad to hear you managed to solve that one. I know there can be issues with that and some ad types such as google ads, so it may be what was causing the conflict
  5. Sorry, I think you misunderstood what I was saying there. It being present is because you are not using categories. That is correct. If you started using categories, that setting would disappear, and instead be available per category.
  6. As mentioned by my colleague, these are in a different place for the signatures, although I understand how that could be confusing.
  7. Sorry, its not clear what you are asking here. Please could you clarify? Are you asking for these to be wysiwyg editors, or asking to be able to post html?
  8. Again, I agree this has perhaps taken longer than it should have to fix, and I have chased this up for you, as per a few messages above there. I'm honestly not sure what else you would like to achieve from this, other than acknowledgement that it has taken a while (is has) and action taken to resolve the issue (we have). If there is something more you would like me to assist you with, please let me know.
  9. Software can occasionally have bugs—this is an inherent part of development. There was no dispute that the bug has been present for some time and needs attention. I completely agree, and I have followed up on it for you. In fact, we are hoping that it will be resolved in the next release. However you asked if v4 has been forgotten about, given we are working on v5. This is clearly not the case. Bugs are prioritized based on several factors, including the upcoming release, available resources, the impact on the software, the number of users affected, and more. Unfortunately, there’s no straightforward answer I can give, as it really depends on situation at the time, and the bugs themselves. With regard financial loss. The software is provided "as-is", as per your end user agreement. We has logged a bug report, as per above, and you have also acknowledged there is a bug within that particular area that is causing you issues. Until we state this is rectified, this would still be the case.
  10. Unless categories are used. If they are, then this becomes a setting per category
  11. I can chase this up, however It would be worth looking at just how many bugs have been fixed within that year you mention. While I completely understand you chasing the bug in question given the length of time, I feel that saying we have forgotten about v4 in that time is a little unfair. Since the date this bug was added, there has been 4.7.15, 4.7.16, 4.7.17, 4.7.18, and we are currently working on 4.7.19. For context, you have looked at one bug here and decided 4 has been dismissed, but discounted all of this (and this is in addition to 15 alphas!):
  12. Thank you for bringing this issue to our attention! I can confirm this should be further reviewed and I have logged an internal bug report for our development team to investigate and address as necessary, in a future maintenance release.
  13. There is no way in which to do this at present. Please bear in mind that items added as feedback are not necessarily items that will definitely be changed.
  14. Its certainly something we would usually try to avoid. So this certainly isnt something we would see as being the norm
  15. That would certainly be a good start if you are having issues. Also if you are on a later release of PHP, it may be you need to upgrade your site to the latest
  16. This is very likely, yes
  17. As mentioned by Adriano there, thats not something in which can be changed
  18. You mention this has not been switched on for a long time, and also mention chatroom there. We havent run chat for a very very long time, so that will not work. In terms of the site itself, do you know what version its on? You can chance an address used in the conf_global.php file. The site doesnt have any concern as to what IP that address is using (although the address itself may be an IP if doing something on local of course)
  19. Give it a moment, and should be back to normal.
  20. Glad to hear thats now working. I will certainly pass on the information though
  21. Yes please. Add this within the notes area of your client area. Not here
×
×
  • Create New...