Jump to content

Marc

Invision Community Team
  • Posts

    15,996
  • Joined

  • Last visited

  • Days Won

    278

 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. Much will depend on the content it finds and the rules involved there.
  2. On reviewing your ticket, I see the issue was related to WAF on the server. Just adding this here as a follow up in case anyone comes across any similar issue, but glad to see the problem has been resolved
  3. No problem at all. Glad you have what you need 🙂
  4. This is a known issue when using elasticsearch, unfortuanetly. We are aware and working to find a solution.
  5. Our developers will need to take a closer look at this, and a ticket has therefore been created on your behalf. Someone will be in contact as soon as possible with an update
  6. An example if what I would need there. I have this from your pm now, thank you
  7. Please could you let me know which database?
  8. Please see the following guide, which shows how you would move your site
  9. If you have a fully working upgraded package, you should move all files and folders to the server, restore your database to the server, and change your conf_global.php file to suit
  10. Please update your details on file. We can then take a look at this for you. I am unable to replicate this on my own instance
  11. As mentioned aboce, you can change the URL within your client area. That however would not in any way cause the issue you are having. Check any caching you have running on your server, clear your browser cache, and double check for any redirects you may have set up. Also ensure you have edited your htaccess file if you have anything in there related directly to the URL.
  12. It would be "Link hover color" you are looking for under the text tab when editing your theme
  13. Yes, thats normal when an item is taking a long while to run
  14. Yes, that is correct. We do not support 3.x oin any way. Including the upgrader for it. While we fully appreciate your position and have been trying to assist here, you need to be aware its unsupported. Only once you are on 4.x would you be supported again. The issue you have is simply that you are trying to upgrade from software released over a decade ago. As said, I will loop in a colleague to see if its anything we can point you in the right direction of.
  15. I can move this over to our community support to see if anyone can assist, but the reality here is you are upgrading from a very old unsupported release. I will see if anyone knows what may be happening here, but you do have to bear this in mind
  16. I fully appreciate what you are saying there, and it does indeed not take that long usually. However, there have been multiple issues here. You first of all added the wrong site as the association here, so we were not trying to log into the correct site. Then the details you entered for the correct set were also incorrect. These items are for yourself to check, rather than ourselves. Your ticket was ready to be looked at by my colleague some 23 hours ago. We determined it was the wrong site some 22 hours ago, but the details were still incorrect. Had the above been entered correctly, we would have been looking at that straight away. Someone will be looking at this as soon as possible
  17. While we are much faster than that, support response can be up to 72 hours per terms of service. You have been answered quite a few times during that period, and unfortunately we are still unable to gain full access to assist.
  18. The first thing I would suggest doing here is checking your email error logs, in System>Settings>Email, to see if you are seeing any errors show up in there. Make sure you run a test on the email settings page, to see what happens when you test that. Also, have you contacted your email host regarding the issue?
  19. Please could you update all access details on file, and I can then take a look to see whats going on
  20. We have a ticket open with Apfelstrudel above, so will let you know the outcome of that once its resolved
  21. Looking at the code, it seems its actually intentional. However I will get a bug report logged so this can be looked at
  22. Your ticket has already been escalated. If you need to revert quickly, it would be best to revert to your backup taken prior to this process.
  23. Glad to see you managed to get the upgrade through. I would suggest getting your live one done and up to date now, so that you are in a better position for us to support you
  24. Ive flagged this for our developers so they can confirm
  25. We are aware its an issue, and it has actually been resolved in a future release
×
×
  • Create New...