Drupal 7 - Update Modules

Updating Drupal 7 modules can be a more involved process than installing or removing modules. Follow the steps closely, as they are necessary to ensure the stability of your website.
To update a module that's used by your website:

Check for module-specific update instructions

First, check the module's project page "Read Documentation" link, as well as the instructions (for example, README.txt, INSTALL.txt, and UPGRADE.txt) that come with the module's installation file (tarball or zip)for any module-specific update instructions. This is typically necessary when updating modules that involve the usage of third party libraries. Be sure to read and understand all module specific requirements before proceeding with the updates.

Back up your database and files

Your website's database contains all of its content, as well as all of its settings and configuration. Though unlikely, any operation that modifies the database can be potentially damaging. Back up your website's files to ensure that you can revert back to the point when things were working. We highly recommend you back up your site before updating modules.

Put your site into Maintenance mode

From the Drupal Administration pages, go to /admin/config/development/maintenance and put the site into maintenance mode by selecting "Put site into maintenance mode".

Replace the module code with the updated version

You can use either of the following methods to update your module: manually updating the files or Drush.

Manually updating files

To replace the module's code with the new version, download a copy of the new module from the drupal.org project page, or use the link projected by the Update module from your site's update status report. Delete the entire outdated module's directory and upload the new one as if you were installing the module for the first time. If you don't delete the outdated module, Drupal may not reflect the update, and report an outdated module.

Drush

If you have the Drush module installed, you can also update your modules from the command line.
To update one or more modules using Drush run the following command from a command prompt, where [module] is the drupal.org project name of the module you want to update:

drush up [module]

If you have more than one module to update, add the additional module project names to the end of the command, separated by spaces. If you want to update all modules and the installed version of Drupal core, run the following:

drush up

Note: If you use Drush to update your module, you don't need to run update.php, allowing you to skip the next step in this process.

Run update.php

Update.php is a script that is used to update the database after modules, themes, or core have been updated or upgraded. A new version of a module may change the structure of the database; this script adjusts the database to fit the updated module. Since the database contains all of the content and the settings of your website, this is an essential step to ensure its continued operation.
If you are running multiple sites, you must run update.php on each site.

Launch the update.php file on your site using a web browser. This file is located in the same directory as Drupal itself, for example http://example.com/update.php

Performing updates requires admin privileges. The first account created on your site ("user 1") has the required privileges. If you do not have the proper privileges, you will see the following screen. Either sign in or follow the instructions on the page to perform the update.

After you're signed in with the proper privileges, you'll see this screen. Click the Select versions link to expand the section.

These dropdown lists contain database updates specified by modules you have installed. If you are not developing your own module or troubleshooting, you should leave them alone and just click Update. The correct items should already be selected by default — either “No updates available” if there have not been any database changes, or a number, which is simply an ID number of the database update being applied.

This next page may take time to load, as the server is modifying your database. This page displays any errors that may have occurred during the process. If none have occurred, your module updates are complete!

Turn off Maintenance mode

Put the site back online by visiting /admin/settings/site-maintenance and disabling maintenance mode.

If Drush is not responding check path, export PATH="$HOME/.composer/vendor/bin:$PATH"

DRUPAL - Update - Notice: Undefined index: distribution_name in drupal_install_profile_distribution_name()

Notice: Undefined index: distribution_name in drupal_install_profile_distribution_name()

To reproduce the issue

Open admin/modules.
At admin/reports/, open the Recent log messages, it will show the following notice:

Notice: Undefined index: distribution_name in drupal_install_profile_distribution_name() (line 207 of ...).

To solve

Adapt the table name if you use prefix and then execute the following SQL statement:

UPDATE `system` 
SET `status` = '1' 
WHERE `filename` = 'profiles/standard/standard.profile';

Ontario Job Posting Sites

https://www.kellyservices.ca/ca/careers/

Wherever your career takes you, Kelly has the connections and industry expertise to offer you the best jobs at the world’s leading companies. Let us help you achieve your career goals.

New Technology to Buy and Explore

https://walabot.com/

Developer

(formerly Pro)

$599

Includes Creator kit capabilities
Walabot Black Shell Case
Wider freqs. range (US)
High 3D resolution
18 antenna array
Imaging API
Raw signal data

Works on Linux, Windows and RPI

View Tech Specs (PDF)

Windows Server 2012: How to Add an Account to a Local Administrator Group

The new interactions on Server Manager as well as the next generation of administration interface may get you stuck on doing common administrative tasks which you have done quickly on Windows Server 2008. One of the tasks I have to do is add an account to the Local Administrator group. In this article, I will show you the step-by-step guidance on how to add an account to Local Administrator group. This article helps Windows Server 2012 beginning administrators facilitate server management as well as get Windows Server 2010 knowledge.

Open Server Manager. Click Tool in the right corner of Server Manager and then select Computer Management.

In the Computer Management windows, expand Local Users and Groups and select Groups. Double click on Administrators group.

In the Administrators Properties, click Add...In the Select Users, Computers, Service Accounts, or Groups windows, type the account you want to add to Local Administrator group and then click OK.

Click OK.

Note: If you are on the Domain Controller, you cannot find Local Users and Groups in the Computer Management. In the case you want to add any account to the local Administrator group on the domain controller machine, just open Active Directory Users and Computer.

You cannot open the BIM file. Reason: You are not an Administrator on the workspace database server

In Analysis Services tabular, the database administrator can make modifications to the model schema and can query all data in the model designer, reporting client, and SQL Server Management Studio. But cannot add or delete databases on the server, or grant administrator rights to other databases on the same server. That privilege belongs to server administrators alone. So if you want to open a model.bim file in SSDT and deploy it onto SSAS server, you need to be server admin.

Most of us might get this error message when we start to work on SSAS tabular model in client sides.

The solution is very straight forward but this can’t be solved by same login which is getting this error message. Contact the SQL Server administrator or use "sa" login and add your username under Sever administrators list in SSAS as shown below.

Ehsan Ullah

Home