-Press Release-

Ten years ago today, the Trinity Desktop Environment (TDE) saw the release
of its first version (3.5.11). Lot of things have happened since that day
but TDE has continued to grow and flourish throughout the years. Today the
project is healthier than ever, with dedicated self-hosted servers,
regular releases, modern collaboration tools and a vibrant community of
users and enthusiasts.

Hello All,

Your Drupal site has been updated today for one or more of the following:

- Drupal core - Highly critical - Remote Code Execution
https://www.drupal.org/sa-core-2019-003

- Font Awesome Icons - Critical - Remote Code Execution
https://www.drupal.org/sa-contrib-2019-025

Hi All,

If you’re on D8, core and probably a few modules will be updated tomorrow.  If
you’re on D7, most likely several modules will be updated.  Full Security
Announcement is below (but it really doesn’t say much, not that it should for
those self-same security implications).

As a FYI:  Wednesdays are generally the day of the week Drupal updates are
released.  The 3rd Wednesday of a month is usually when the majority of
Drupal security updates occur.

Hi All,

Two things

> 1)

Servers srv03 and srv04 have had routine maintenance of a major upgrade to their Apache web server software.

All primary domains have passed IDA’s QC. But, as with any software upgrade, please do you client QC(s) to verify any unique functionality you might have.

> 2)

At this time IDA is also taking request to move sites to either of these servers. If you want to move your site(s) closer to your users’ localities, these servers are located at:

Hi All,

Your Drupal 7 site has been updated today for:

[Security-news] Views - Moderately Critical - Access Bypass - DRUPAL-SA-CONTRIB-2017-068
https://www.drupal.org/node/2902604

[Security-news] Views refresh - Moderately Critical - Access Bypass – DRUPAL-SA-CONTRIB-2017-069
https://www.drupal.org/node/2902606

Hi All,

Your Drupal 7 site has been updated today for:

[Security-news] Drupal Core - Multiple Vulnerabilities - SA-CORE-2017-003
https://www.drupal.org/SA-CORE-2017-003

While this individual security issue should not effect many sites, we apply
all security releases immediately to address as best as possible as yet
undiscovered security issues.

Problem: Your PHP max execution time was exceeded and PHP quits.

Solution: Extend PHP's Runtime Configuration max_execution_time.

For security reasons try changing max_execution_time to 60 seconds first, then longer if you need it.

* Also, you'll need to change the pathing I've used as appropriate for you site / system.

# Drupal Solution Details #

First we need to play, "Where's php.ini?"

I occasionally have to deal with shared hosting. Which I'll admit, I'm not real happy about as I generally have to install a bunch of my default tools, most of which then have to be 'fixed' to work on [insert cheap hosting firm's name]'s concept of security.

As I just did this (again), here is the 'patch' for drush to make it 'play nice.'

Summary Procedure

Copy php.ini to a drush usable location and edit for your problems.

Detailed Procedure

The Error:

I'll fully admit Drupal has one crappy user administration interface. And, since I get quite a few of the "can you find info about this user?" requests, which take so little time I can't bill for them :), I've expanded on the Drupal Post installation support question:

Search for username in Users list?
https://www.drupal.org/node/744628

and created a custom view to help out my customers.

In the better late than never, I've finally gotten around to publishing it . . .