Posted December 17, 2024Dec 17 Hello. Since last update we have had 37 log entries of: "TypeError: Cannot assign string to property IPS\Dispatcher\_Front::$currentPage of type ?int (0) #0 /datadrive/forum/system/Dispatcher/Dispatcher.php(110): IPS\Dispatcher\_Front->init() #1 /datadrive/forum/index.php(13): IPS\_Dispatcher::i() #2 {main}"
December 17, 2024Dec 17 Pleas visit the support area in your ACP and apple the patch which will resolve this issue.
December 22, 2024Dec 22 Author Just did the update and will monitor. In the mean time please see attached for latest error.
December 23, 2024Dec 23 Author 1) Getting multiple log errors, please see attached. 2) Separately, running htop on server backend it shows high CPU usage with apache2. What is the recommenced server CPU number for running a medium sized forum?
December 23, 2024Dec 23 Community Expert Have you removed any content recently or third party applications? We would need to look further into this for you, however the access details on file appear to be incorrect or missing. Could you please update these details by visiting your client area, selecting the relevant purchase, then clicking "Review/Update Access Information" under the "Stored Access Information" section. We look forward to further assisting you.
December 23, 2024Dec 23 Author Have not made changes recently... Stored access information has been updated for you. Thank you
December 23, 2024Dec 23 Community Expert Unfortunately, a display name was provided rather than an email address which your community login requires.
December 23, 2024Dec 23 Community Expert Unfortunately, the email/password combo are incorrect. Please be sure to test the credentials before providing 🙂
December 26, 2024Dec 26 Author On 12/23/2024 at 1:16 PM, Jim M said: Unfortunately, the email/password combo are incorrect. Please be sure to test the credentials before providing 🙂 It should be working now. Sorry about that.
December 26, 2024Dec 26 Community Expert Thank you for updating that. Unfortunately, while I see this in your logs, I do not see this happening in real time. So either this was a temporary issue or has resolved itself.
