Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
I am not sure where to put this. There is no easy-access place to let whomever manages the repositories to know and https://www.drupal.org/support does not have an appropriate entry. So I am putting it here in hopes that somebody who knows more than I do can possibly either pass this along, or let me know if I am doing something wrong.
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
I've installed a Drupal Site using the Mayo-Theme.
Making minor core uprades easier I installed Drush on in a global installation:
wget http://files.drush.org/drush.phar
php drush.phar core-status
mv drush.phar /usr/local/bin/drush
drush init
drush vset --exact maintenance_mode 1
drush cache-clear all
Didn't do what they should do, so I set my Drupal Installation in Maintenance Mode manualy in the backend, after I cleared cache manualy.
I recently taken on the responsibility for a website and do not know the ftp details which makes any real update impossible. I have done everything I could but there is the previous person who worked on the website is not reachable by any means.
I would love to migrate from D6 directly to D8 except that we use Forena Reports extensively throughout my client's site and there doesn't seem to be an intent to advance Forena Reports to D8. It is a wonderful module for integrating ad-hock SQL queries into beautiful web pages.
Does anyone know of plans to advance the module to D8? Are there any alternatives that do not require custom module creation?
I am trying to migrate to D7 from a D6 site which has several custom tables and tens of thousands of documents referenced in a table named "files". The D6 database has 254 tables while the migrated D7 database now has 510 tables. It turns out that each of the fields (columns) in the D6 custom tables have been turned into their own individual table. This seems preposterous to me and will prevent me from providing .csv files of each table to my client who analyses the content offline.