content page will not open

[ronc]

Hi Guys:

Doing an upgrade of store on 1.0.8.4 Start by going to modules content to uninstall GDPR. Content page returns page isn't working http ERROR 500. Downloaded 1.0.8.4 did clean setup and still get the same error. Reran all SQL from 1.0.8.0 which I had updated from the day before.
Server running php 8.3 dropped back to 8.1 and returned with no resolve.
Found database collation was utf8mb3 updated to utf8mb4 still no solution.
Error log is the same in the clean install as in the live install

Error log:
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of database_core::query($sql, $resultmode = MYSQLI_STORE_RESULT) should either be compatible with mysqli::query(string $query, int $result_mode = MYSQLI_STORE_RESULT): mysqli_result|bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.1/database_core.php on line 61
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of mysql_session::open($save_path, $session_name) should either be compatible with SessionHandler::open(string $path, string $name): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.3/mysql_session.php on line 27
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of mysql_session::close() should either be compatible with SessionHandler::close(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.3/mysql_session.php on line 15
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of mysql_session::read($key) should either be compatible with SessionHandler::read(string $id): string|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.3/mysql_session.php on line 31
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of mysql_session::write($key, $value) should either be compatible with SessionHandler::write(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.3/mysql_session.php on line 47
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of mysql_session::destroy($key) should either be compatible with SessionHandler::destroy(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.3/mysql_session.php on line 19
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of mysql_session::gc($maxlifetime) should either be compatible with SessionHandler::gc(int $max_lifetime): int|false, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.3/mysql_session.php on line 23
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of mysql_session::validateId($key) should either be compatible with SessionUpdateTimestampHandlerInterface::validateId(string $id): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.3/mysql_session.php on line 42
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Return type of mysql_session::updateTimestamp($key, $ignore) should either be compatible with SessionUpdateTimestampHandlerInterface::updateTimestamp(string $id, string $data): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in .../includes/system/versioned/1.0.8.3/mysql_session.php on line 38
[22-Sep-2025 17:06:08 Europe/London] PHP Deprecated: Creation of dynamic property messageStack::$messages is deprecated in .../includes/system/versioned/1.0.5.1/message_stack.php on line 23

Thanking you in advance for whatever help you can provide

Ron

[BrockleyJohn]

You will get deprecated notices running 1.0.8.4 on php 8.anything but as long as they aren't displayed it won't give you a problem. I've just checked 8.3 on a clean install of 1.0.8.4

You need to find the actual error which is causing the 500 return. Typically it's the last line in the error log, unless it's a public site.
If it's not written to the php error log you should check the apache error log and see if that tells you. If you're on cpanel, it's in the Metrics section labelled Errors.

[ronc]

Thanks BrockleyJohn

I would just keep upgrading but it says I need to uninstall the GDPR

Here is the last line of the error log in cpanel.

[Mon Sep 22 07:09:03.500660 2025] [autoindex:error] [pid 3304533:tid 3305459] [client 192.88.135.34:7280] AH01276: Cannot serve directory .../ext/: No matching DirectoryIndex (index.html.var,index.htm,index.html,index.xhtml,index.wml,index.perl,index.pl,index.plx,index.ppl,index.cgi,index.jsp,index.js,index.jp,index.php4,index.php3,index.php,index.phtml,index.shtml,default.htm,default.html,home.htm,index.php5,Default.html,Default.htm,home.html,welcome.html) found, and server-generated directory index forbidden by Options directive

[ronc]

Hi Guys:

Thanks for all the help. Searched the forum for every instance of 500 and found the cure.

see viewtopic.php?p=5159#p5159

Ron