Drupal 7.x

A dear friend of our family and community has gone missing in Peru.
Time is of the essence in publicizing this and organizing search and rescue missions.

So far others have begun a facebook page at https://www.facebook.com/findcarlavalpeoz/ which gives some background on this. You may have seen some mass media coverage of it also.

I want to augment that page with a dedicated website. I have setup a primary site and did the initial install of Drupal 7

hello

How can I fix this problem? (stretch the toolbar;admin)

The photo link is at the bottom .

thx

picture_link

-- Sorted and nothing helpful came out of it so I deleted the question. 

He guys! Looking for some pointers on contextual filters. I have 3 seperate page display views set up to show the following taxonomy:

Vocabulary -"Parts"

• Parent term (Manufacturer)
  • "child" term (Category)
    • content ascribed to child term

View one: displays the Parent term manufacturers correctly with a path /Parts

View two: displays the "child" term categories correctly with a path /Parts/%

I'm running a Drupal 7 site on a shared hosting service. In order to allow me to do the conversion to 4 byte UTF-8, the hosting company can migrate the site from their MySQL 5.6 server to a MySQL 5.7 one.

However, before they proceed, they are asking me to "ensure if your applications are compatible with MySQL 5.7 as issues may arise if that is not the case."

I'm running a Commons (commons-7.x-3.46), Drupal 7.56.. I think it should be fine, but can't find a clear answer

Is there anything I should do before confirming the migration?

I just enabled HTTP/2 on my server. Status report states:

"File system: The directory sites/default/files is not writable... "

Also, in Performance > Bandwidth Optimization, both Aggregate CSS and JavaScript files is disabled.

NOTE: I have never changed my directory permissions. Default is and always has been 755 (for /default and /files).

NOTE 2: If I change permissions to 777 then error goes away and Bandwidth options are back. When I change back to 755 the issue returns.