Check-in: How is Composr running on PHP 8?

Hello everyone,

I'd like to check in with you and ask how Composr (10.0.47) is running on PHP 8? Are you getting any more deprecation notices or errors anywhere? Theoretically, v10 should be almost fully PHP-8 compatible by now.

Your input will be greatly appreciated.

They've all disappeared for me Patrick on PHP 8.3.3.

I'll drop a note back should any popup going forward.

Function utf8_encode() is deprecated in /sources/global3.php on line 946

str_replace(): Passing null to parameter #2 ($replace) of type array|string is deprecated in /sources/crud_module.php on line 717

Uncaught TypeError: array_keys(): Argument #1 ($array) must be of type array, null given in /sources/comcode.php:260

Adam Edington said

Function utf8_encode() is deprecated in /sources/global3.php on line 946

str_replace(): Passing null to parameter #2 ($replace) of type array|string is deprecated in /sources/crud_module.php on line 717

Uncaught TypeError: array_keys(): Argument #1 ($array) must be of type array, null given in /sources/comcode.php:260

From “Post #9,848”, 14th April 2024, 11:10 pm

Thank you, but can you provide more context? What were you doing in each of these errors?

The 2nd one was when I deleted a forum. The other 2 are from the Composr errorlog and I don't recall noticing them on the website.

Sounds good. I added a tracker issue under your name for it.

I just finished alpha2, so I'll be switching over to v10 now and resolving pending issues reported for 10.0.47. Should have a 10.0.48 patch out in a week or two.

Greetings,

In reply to Patrick's OP I'm indeed  - suddenly as of about 5 days ago - getting no fewer than 75 "deprectated" messages displayed above my site's header image on all pages, all of them stating:

Deprecated: Creation of dynamic property Tempcode::$is_empty is deprecated in /home2/under283/public_html/uptcom/sources/tempcode.php on line 1930

Plus, below the header image, a single different message:

Deprecated: Creation of dynamic property Breadcrumb_substitution_loader::$substitution_current_match_key is deprecated in /home2/under283/public_html/uptcom/sources/breadcrumbs.php on line 157

Interestingly (and to me inexplicably) these display only to Super-admins, and thankfully not to users in other usergroups. Nonetheless from my administrator's practical standpoint they're a total pain and I'm anxious to banish them from my sight. Lamentably I haven't figured out a way to do that selectively using CSS "display:none;" via (I'm presuming) GLOBAL_HTML_WRAP.tpl in a way that avoids eliminating the entire contents of the website body as well. I'd be mighty grateful to anyone able and willing to advise me as to how to accomplish that!

In addition, there have arisen (so far as I can tell, in tandem with the above) a variety of other persisting display-related faults which I'll list on the offchance that they're also attributable to PHP 8 incompatibilities/ deprecations:

• My Site Tree is now displaying 35 undefined items (i.e., fake page-links) labelled "n/a" across my Welcome and Site zones - and 5 of them display as not within any zone at all!. On clicking any of these in the Sitemap Editor, the following error message is presented (in an overlay):

An error occurred when loading this screen onto the web browser. You are being notified of this as you are staff. If you believe this is a bug in Composr, please contact the developers with full details. More details are available in your browser's error console. The error was:

129: Uncaught TypeError: Cannot read properties of null (reading 'getAttribute')
https://understanding-piano-technique.com/uptcom/data/script.php?script=tree_list&theme=admin&keep_theme=admin
 

• The contents of "Edit Menu"pages fails (except for the title, showing the name of the menu concerned) to display on selecting a menu via the Menu Management page's list or via the icon accompanying each menu on displayed pages - meaning, of course, that i have no accessible means of editing any of them. I've tested the relevant menu-editing templates in preview mode, and found them to display normally. Hence I can only assume that something code-related must be ignoring or voiding their INCLUDE tempcode directives on opening the editing screen.
• As of my viewing the auto-generated "A to Z index" page for one of my custom catalogues earlier today, all of my pages are displaying a persistent global message stating: 

A symbol is missing: OCF. This usually happens when Comcode is written without placing template/PHP code within a code tag.

These are the issues I've noted as yet; should I encounter further ones I'll report them in a subsequent post in this topic.

My main concern, naturally, is establishing what I need to do in order to fix the above issues! Can anyone advise me, please?


 

RichT Thank you for replying.

Some of these deprecation issues have already been resolved in Composr v10 (at least they should be), so my guess is you do not have the latest version of v10. To confirm, what version do you have according to your Admin Zone Dashboard? We'll proceed from there after knowing that.

Many thanks for your reply, Patrick!

My apologies for failing to disclose which version of Composr I'm running (or rather, had been before reading your reply)  - namely 10.0.43.

Prompted by your reply's substance and implications, I just upgraded to 10.0.47 - and bingo! All of the behaviours I reported above are no longer in evidence.

So, to refer to your topic's original question, I'm delighted to be confirming 10.0.47's successful resolution of PHP v8-caused misbehaviours!

Boundless thanks to you all at ocProducts for all your continual work releasing upgrades that fix all such circumstantially arising issues!

Richard.
 

Glad to hear your site is working well again. Yeah we resolved a majority of PHP 8 issues in 10.0.45 - 10.0.47 .

As a side note just for your FYI, ocProducts no longer exists; Chris closed it down as his life circumstances changed (for the better, but unfortunately that means he has much less time for Composr). So we're just called core developers now.

Currently the development of Composr is being performed mainly by me via PDStig, LLC, and funded by Chris personally. The hope is, especially once v11 reaches stable, others come forward with the desire to help develop and maintain Composr, as Composr is no longer (and will no longer be) backed by any company.