Postings by Peter Kokot update 2019-05

Hello webmasters,

I was requested to write email here (apologies for missing that sooner
but my last email didn't get responses because the constant
discussions are probably too time consuming for everyone in their busy
lives so no problem basically, I understand).

There are few adjustments taking place on the PHP bugs tracker -
application level at the moment.

Two main things are currently being worked on:
1.) Bugs categories (a.k.a. - PHP version selection


This was brought by the pull request to include PHP 7.4 branch and to
remove the old one:
<a href="" title=""></a>

Couple of questions about PHP versions selection when reporting a bug:
<a href="" title=""></a>

Q1: Currently, there are listed also the so called "snaps" which were
once used via Today this is not working anymore.
However, there are Windows snapshots.

Dependency injection container for


following previous discussions about the template engine, OOP,
modernizing application this one is about adding a
minimalistic dependency injection container.

Pull request is in preparation [1]

Short intro:
What are dependencies and what is dependency injection is briefly
described in the attached docs file in the pull request and in
numerous articles and blog posts around the community.

I really can't imagine a PHP application written in OOP without a
dependency injection container these days anymore. template layer


Current template system in code is integrated in front
controllers (index.php...) and some separate template files. It
contains several helper functions with globals usage and mixes HTML
with PHP code logic.

Stale branches for web/pecl repository

Hello, there are 3 so called stale branches that got stuck:
<a href="" title=""></a>

The "maint":
<a href="" title=""></a>
and "old_auth":
<a href="" title=""></a>
which are both already fully integrated in the web/pecl master branch.

Should we remove these two from the Git repository?

I'm about to recheck the "next" branch soon:
<a href="" title=""></a>
It seems that a complete site redesign was being done and then moving
to pickleweb but as I imagine the entire project is too complicated
for creating a separate bra download proxy script


a question about the site that might be stopping server upgrades.

The extension download URL endpoint is:
<a href="" title=""></a>

This is a PHP proxy download script that do some checks and outputs
non standard header for Apache webserver and mod_xsendfile to offer a
direct file download as it was a static file. That way there is very
little performance overhead and option that request goes through a PHP

However, this mod_xsendfile isn't maintained anymore.

PHP version upgrade on


worth noting that the web application
<a href="" title=""></a> has been adjusted to work on PHP
7.2 and even 7.3 already.

There are some warnings and notices thrown by some outdated PEAR code
here and there (part of the PEAR core package that comes with a system
PHP installation on the server) but nothing that would stop app from

Regenerate REST XML files on

there is an issue with some XML files for REST api on that
haven't been updated in a period of a week and include few releases.

The script needed to be run on the server to regenerate the
XML files is located at:
This script regenerates the XML files from the database into the location
set by the environment variable PEAR_REST_DIR or in the config here:
<a href="" title=""></a>

If someone is so kind to help us out here.

Thank you.