Jump to content

Marc

Invision Community Team
  • Posts

    15,909
  • Joined

  • Last visited

  • Days Won

    277

 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. If you are having issues with the files being downloaded automatically, you need to download a full set of files and upload these to your server, then run the upgrade
  2. Because you are using the processed name of the item that is used on the page, not the original file name.
  3. If you upload a fresh set of files from your client area, it should correct this. If not, this is the bypass Add this to a constants.php file. Its important you remove this after the upgrade <?php define('UPGRADE_MD5_CHECK', false);
  4. You are searching for the thumbnail there, and not the original image. Example:- something.png.4a45406aa3adedeb508fc7c996e044b7.png Thats the thumbnail for something.png
  5. Sorry to ask, but I have to. Have you checked the permissions?
  6. You would need to ensure your usergroup has the "Can use HTML" option switched on.
  7. That is the standard offline page you are seeing. They have simply added it to the offline message, using the "Source" option to add the html there
  8. Is it something whereby you are just looking to change the text? Im asking as you could just change the language string on your language pack to do this
  9. See if you see this again now you have rid of the other 2 problems. It may well be related
  10. Thank you for letting us know. I saw similar on mine, which is why I asked which cache worked. I have logged that as a bug, even if the initial issue isnt actually a bug there
  11. As with the other items, please clear browser cache and site cache and try this again
  12. 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
  13. 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/
  14. 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
  15. 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.
  16. As mentioned by my colleague, these are in a different place for the signatures, although I understand how that could be confusing.
  17. 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?
  18. 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.
  19. 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.
  20. Unless categories are used. If they are, then this becomes a setting per category
  21. 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!):
×
×
  • Create New...