
-
Invision Community 5.0.5 Beta 1 Released
It's safe to ignore this.
-
class loading system , a bug?
Ask him if he has declared the $multitons variable in the classes;) /** * @brief Multiton Store */ protected static $multitons;
-
Working on SSO, Can't Find Page/Module
I guess because the module doesn’t exist, that said, you really shouldn’t put your custom code into the core application , why aren’t you creating your own application with its own modules and controllers ?
-
Invision Community 5.0.4 Upgrade Breaks my Website
Based on the error it sounds like not all files were overwritten. Was this an upgrade via the ACP, or did you manually upload the files to your server? If the later, I would just try it again.
-
I no longer see the helpful tab in forums since 5.0.4 update.
There is an upgrade step which should enable it for all groups, let me test this.
-
-
Problem with tags
We have an open bugreport for this.
-
Undefined function
Changed Status to Not a bug
-
Undefined function
This function doesn't exist in IC5 anymore.
-
Event cover photo not present in API
I have created an internal suggestion mentioning this because it sounds like an oversight. The REST response for downloads app files contains the primary image, cms records too, so it would be just logical to also include it for blog entries and calendar events.
-
Event cover photo not present in API
That's correct, the cover photo isn't included (yet) into the REST API response
-
Topic Feed showing in all forums instead of selected forum only
The forum selector is for the content which should be shown, not where it should appear
-
Welcome page.
You can use the page for both! Use blocks from the ACP ( ACP => PAges => BLocks) to contol the visibility via permissions, so that one set of blocks is visible to only guests and the other to members)
-
%s at %s in date
Seems that your translation isn’t up2date.
-
Followers don't appear in profile
Matt literally fixed this few minutes ago.
-
Report API fails with a fatal error if the content has already been reported
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.