eliteone
-
Posts
114 -
Joined
-
Last visited
Content Type
Downloads
Release Notes
IPS4 Guides
IPS4 Developer Documentation
Invision Community Blog
Development Blog
Deprecation Tracker
Providers Directory
Forums
Events
Store
Gallery
Everything posted by eliteone
-
Sorry to leave you hanging. Fixed it with your latest version. Thanks
-
Update: I was able to get it working once I fixed the colocation issue. All good now 🙂
-
I had to disable it to upgrade to PHP 8.0. It still works if you keep your forum on PHP 7.4 at least it does for me.
-
Was able to alter colocation via phpmyadmin. I'll switch it over and see how it does.
-
Ran the checker as told. This is the result. Not sure why some of the database collocation is on the wrong one. Tried to get the converter from the link but it's not a valid link. Thing is this site has been current and working fine until I ran the 4.7 upgrade. I then tried to switch the PHP per the recommendation.
-
Where would I get the colocation converter?
-
Disabled 3rd party items and set it to 8.0 again and I get this now. I get this when trying to access the admin panel after switching it with the 3rd party stuff off.
-
Just updated site to version 4.7 and it recommended I update to PHP 8.0 from PHP Version 7.4.29 that is currently running. when I switch it to PHP 8.0 the forum fails to load. UnityHQ Community Forum is the site. When I check for errors in the logs nothing shows up. Site comes back online when I revert it back to version 7.4.29. Anyone have any ideas as to what could be the issue?
-
Following. Mine are missing from my forum.
-
Having the same issue of it not working after upgrading forum from 4.4 to 4.5.
-
It was an issue with my host. Got it sorted out.
-
First off thank you for this great addon. Since I updated it to version 1.7.0 I get an error when I try to add a new block to the portal. Not Acceptable An appropriate representation of the requested resource /Unityhq/forums/y*************/ could not be found on this server. (blocked out path for obvious reasons ) Additionally, a 406 Not Acceptable error was encountered while trying to use an ErrorDocument to handle the request. Any ideas on what could be causing this?
