...
Almost there... ctools needs to be updated:
While at it, we will also update panels and panels_style-pack modules too--
Let's see how it looks now by going to the home page:
Still some errors... maybe clearing cache of the system might help... so logging in:
This is a familiar error!! From our experience with the Wx portal migration, we know the root cause of this error:
The CONF file is not configured correctly!!
Give Apache a boot--
service httpd restart
Starting a fresh session with a new browser and try logging in:
OKAY.... this is also a "previously encountered" error... let's update Rules module and see how it behaves after that...
After uploading the update to the rules module onto the RHEL7, untar it:
tar -zxvf rules-7.x-2.12.tar.gz
and after it's untar'd, we remove the tar.gz file to keep things tidy:
rm -rf rules-7.x-2.12.tar.gz
Let's run Drupal's update process as before and see where it stands now...
Still the ctools errors... but remember, we want to login and clear cache.... so go back to Firefox and try logging in again...
SUCCESS!!
Let's clear cache and see what happens with respect to the ctools errors...
okay, we still see the same ctools related errors... but ALSO a new one:
At least, this is easy to fix:
sudo su -
cd default/
ls -alt
chown -R apache:apache files/
ls -alt
Clear cache and reload the home page...
Still some ctools related errors...... (further) research time!
Let's update the nodeaccess module & then run the Drupal's update process
cd modules/
rm -rf nodeaccess/
tar -zxvf nodeaccess-7.x-1.8.tar.gz
rm -rf nodeaccess-7.x-1.8.tar.gz
After clearing cache and reloading the home page: still the same ctools error on the home page :-/
Let's update the Mail System module... and reload the home page after clearing cache
Nope... still same errors!
Breakthrough!
Checkout this post on the Drupal site, where the user explains what could be the cause... upon checking the currently live (RHEL6) OEM Portal, we see that the home screen config is explicitly calling a file
Let's fix that—along with any other hard-linked calls, clear cache, and reload the home page to see if that solves—
SUCCESSSSSSSS!!!!!!!!!!!!!
Let's check again.... but this time, we will log out, log back in (fresh session) and see if there are any errors on the home page:
