Invision Community 4: SEO, prepare for v5 and dormant account notifications Matt November 11, 2024Nov 11
Posted March 21Mar 21 Hello,I wanted to configure a "Sponsorship" field on the registration form, but it didn't work.And I can no longer create the field I created.
March 21Mar 21 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.
Friday at 07:36 PM5 days Author 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.Glad to have shed light on this technical issue so that it can benefit the community and the stability of v5.Waiting for the next update, good luck to you!
8 hours ago8 hr Author 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.Hi Marc,I don't know if this can help you;Because of this technical issue, my members, from any group, no longer had access to the entire site.I poked around a bit, and I had to delete what I had created (the profile_step_title_1).Except that via the admin panel, I got an error.So I decided to do it via the database.I deleted the value in core_profile_step, but it still appeared in the admin panel, and my members still couldn't access the site, even after clearing the cache.I then deleted the core_profile_step table and went to the admin panel, support, to automatically correct the problem in the database (with the missing table).Since then, the profile_step_title_1 has been successfully deleted, and the bugs have disappeared.
2 hours ago2 hr That would indeed resolve it. Thank you for letting us know you have this resolved, and we do have a bug report in for this to get the cause resolved