Word Version by Ideeclic REQUIRES UPDATING Nov 17 2009

raspgiantsneckServers

Dec 9, 2013 (3 years and 8 months ago)

137 views

DOCUMENT:

Maintenance
Manual


PREPARED BY:

Idéeclic Inc.


FOR:

FNTC/NRT

Team

Attention: Sue Hanley

1200


100 Park Royal South

Vancouver, BC


DELIVERED:

November

17
, 2009









2

122
222
12

2

TABLE
OF CONTENTS

TABLE OF CONTENTS

................................
................................
................................
.

2

PROJECT DESCRIPTION

................................
................................
..............................

3

ASSUMPTI
ONS, CONSTRAINTS, DEPENDENCIES

................................
............................

4

MAJOR ISSUES / MITIGATION STRATEGIES

................................
................................
...

7

DETAILED APPLICATION

................................
................................
.............................

9

DETAILED TECHNICAL SOLUTION

................................
................................
..............

17



3

122
222
12

3

PROJECT DESCRIPTION

SHORT DESCRIPTION

The best
practices informational portal
will be built using a CMS called Dr
u
pal
1
. Drupal is an open
-
source
software packag
e that allows an individual or a community of users to easily publish, manage and organize
a wide variety of content on a website.


ASSOCIATED DOCUMENTA
TION



FNTC/NRT / NRT BC First Nations Internet Portal / PHASE 1


R
e
quirements Definition and
Project Sco
pe Document


December 2008



The Conceptual Manual and its Appendi
c
es

DEFINITIONS, ACRONYM
S AND ABBREVIATIONS


See the
C
onceptual Manual

CONTRIBUTORS / ROLES


Jean
-
Baptiste Minchelli:
Project Lead / Project Manager

Abdoulaye Siby: Technical Lead

Bruno Lafer
rière, Technical Assistance (Programmer)







1

http://drupal.org/



4

122
222
12

4

ASSUMPTIONS, CONSTRA
INTS, DEPENDENCIES


OVERALL ASSUMPTIONS

1.

The website will be built using PHP/MYSQL and ba
sed on the CMS Drupal version 6
(see

http://drupal.org/
)

2.

The following

Web
browsers are known to work well with Drupal core and support all of its features:



Internet Explorer 6.x and later



Firefox 2.x and later



Opera 7 and later



Safari 1.x and later



Camino 1.x and later



Google Chrome
1.x and later


TECHNICAL ASSUMPTION
S

Drup
al core and core modules respect W3C and WAI standards. (see “Standards” for more information)

The server must use PHP 5.2+ and MySQL 5+.

LINUX



A
web
hosting service based on Linux

WEB SERVER



Apache 2.x



The following
Apache
m
odules

are installed
:
mod_rewr
ite
, PHP (installed as module)

PHP SCRIPTING LANGUA
GE



PHP version 5.2.x



5

122
222
12

5



The following PHP extensions are installed:
MYSQLI,
XML, XSL, GD




PHP memory: 64Mb or more



PHP directives:

o

register_gl
obals
: off

o

session.save_handler
: user

o

error_reporting set to E_ALL & ~E_NOTICE

o

safe_mode
: off

o

session.cache_limiter: nocache

o

AllowOverride
is not set to

None

DATABASE SERVER



M
ySQL 4.1 or higher



Database Access Right
:
SELECT, INSERT, UPDATE, DELETE, CREATE, DROP, INDEX,
A
L
TER

SCHEDULED TASKS (CRO
N JOBS)


We assume that a functional task scheduler is

available for the portal

E
-
MAIL SUBSYSTEM

We assume that a functional e
-
mail subsystem is available. Whether it is provided by the web hosting
provider or by the client’s organization, the e
-
mail subsystem must accept to relay all e
-
mail messages sent
fr
om the Portal’s domain name without a challenge/request authentication involving a username and/or a
password.

The server provided by Ideeclic will run a fully working Enterprise Linux (Centos) operating system that will
provide a working e
-
mail subsystem.




6

122
222
12

6

DEPENDENCIES / CONST
RAINTS

The project is based on the Drupal technology. The website will be dependant of the functionalities,
stability and performance of Drupal.

Idéeclic will not modify the core of Drupal. This can limit
some functions or increase t
heir complexity
.

In addition to the Drupal CMS, this project depends on:



The web hosting service: Ideeclic’s web hosting services have been chosen by the NRT / FNTC;



The email server availability: Ideeclic’s web hosting services provides access to a mail s
erver;



The cron task scheduler availability: Task schedulers are provided with Ideeclic’s hosting plans




7

122
222
12

7

MAJOR ISSUES / MITIG
ATION STRATEGIES

ISSUE #

DESCRIPTION

IMPACT
LEVEL

RISK
LEVEL

STATUS

MITIGATION
STRATEGY

1.


We are dependant on
Drupal and community
developers modules

Medium

Low

Open

For the
development of
the site: apply
patches to
Drupal as
required &
choose only
stable modules

whenever
possible
.

2.


The Drupal search
engine usually searches
the entire site

Low

Low

Open

Idéeclic is
developing
custom
module
to allow specific
section
searches.

3.


WYSIWYG editors can
give strange results if the
user pastes
formatted

contents directly from
applications such as MS
Word (i.e. tables).

Low

Medium

Open

Limit highly
formatted
content when
copy/pasting
inside
the
WYSIWYG
editor

4.


Drupal can be CPU and
memory
intensive
.

Medium

Medium

Open

Idéeclic will
stress test the
application on
the live server
and during the
BUILD phase.

5.


Due to

the particular
needs of the Portal, a few
modules a still in the
developmen
t phase

(not
officially declared stable)

or only available in
previous Drupal versions
.

Medium

High

Open

Idéeclic
will port
the given old
versions to
Drupal 6 and
we will test the
modules that
are still in
development
stage to ensure
that they a
re

suitable

for
production
.

6.


Web
Hosting

Service

Low

Low

Closed

P
rovided by
Ideeclic



8

122
222
12

8

7.


E
-
Mail Server

Low

Low

Closed

P
rovided with
Ideeclic’s
hosting services

8.


Task Scheduler

Low

Low

Closed

Provided with
Ideeclic’s
hosting services



9

122
222
12

9

DETAILED APPLICATION

REQUIRED FUN
CTIONALITIES / KEY D
ELIVERABLES

LANGUAGE

The
interfaces of the Portal are delivered in
English only.

However, the content created with the CMS can
be English, French.

CONTENT VETTING

Content vetting will be performed by the moderation module.

URL

C
ustom co
ntent type

(URL), URL listing (views)

MEMBER
S

REGISTRATION

The profile module will extend the Drupal core user forms to include all the fields from the MEMBER
content type (See the content matrix)

ACCESS PERMISSIONS M
ANAGEMENT

The Drupal build
-
in
permissio
n system will be used in order to create the require permissions groups for
the portal:



Public (built
-
in Anonymous
),



Basic Member (built
-
in Authenticated),



Community of Practice Member,



Organizations Administrator,



Administrator.

MINI SITES

Mini Sites wil
l be created u
sing the organic group modules. They will use several content types:



10

122
222
12

10



A group node to serve as home page for the Mini Site



A group page that can be used to create pages inside the Mini Site



Image Gallery



Job Postings

The og_panel module will b
e used in order to allow the Mini Site’s owner to create new pages

Mini Sites will use the built
-
in Drupal RSS feature. And the document upload feature of the portal (see
below)

MINI SITES DIRECTORY

LISTING

Module(s): views, organic group

This is a view wi
th an organic group filter.

PAGE CREATION/MODIFI
CATION

Module(s): taxonomy
, fckeditor

Dependant Module(s):
taxonomy_breadcrumb

The built
-
in Drupal node type will be extended as a Generic type with additional fields: Section, Tags
.

A
structured
taxonomy
tre
e
will be created
with the taxonomy module

to allow pages to
be assigned a
specific site section.

T
he rich text

field
s

will use fckeditor.

PHOTO GALLERIES

Module(s): View, Finder, views_gallery

Dependant Module(s): ImageField, Nodereference_url

The global
image gallery will
show
all photos in the database with a view.

We will
base this
feature
on a user contributed solution described at
:

http://www.lullabot.com/articles/photo
-
galleries
-
views
-
attach



11

122
222
12

11

DOCUMENT UPLOAD WITH

METADATA SUPPORT

Module(s): Upload,

Nodereference, CCK, Taxonomy

This feature will use a custom content type to make it possible to upload documents
, enter associated
metadata, place them in different sections of the Portal and assign tags to them. The tags will allow to
group similar documents
in the same section
for a better browsing experience.

LINKS TO GOOGLE MAPS

Module(s): Google map embed

We wi
ll use Google Map Embed to enter data about the location we want to represent. It is basically
entering the same information that you would enter in the search box on that page:

http://maps.google.com/

SEARCH ENGINE

Module(s): Search, Views, Finder

The glo
bal search engine will be based on the built
-
in search modules.

The Boolean search will be handled directly by Drupal. The CCK field that must be searched will be
configured in CCK in order to be included in the search result.

Views will be used to render
specific search results other than the global search result.

The search engine will be customized in order to be able to see search results that are not accessible to
the user.

SITE MAP

Module(s): site_map

See the conceptual manual for more information abo
ut the Site .

HELP/FAQ

Generic Contents

CONTACT US

Module(s):
Built
-
in Drupal contact module



12

122
222
12

12

Since the built
-
in contact module does not provide all the required fields for the Portal, the webform module
will be used instead.

SOCIAL BOOKMARKING

Module(s):
Addtoany

The
Addtoany
module will be used in order to allow Generic content pages to be shared through
Share
link
, Digg and
del
i
cious

networks
. Please visit
http://digg.com
,
http://delicio
us.com

and
http://linkedin.com

for more information about them and their data managment mechanisms,

SOCIAL NETWORKING

Static links to Facebook, Twitter and YouTube placed directly inside

Drupal a block
.


RSS FEEDS

Drupa
l’s built
-
in RSS feature will be used in order to generate feeds wherever possible if necessary.

COMMENTING

Module(s): comment, moderation


The built
-
in comment module will be used. The configuration of the permission system will determine if
content vetti
ng should be done with new comments depending on the access privileges of the author of the
comment.

COMMUNITIES OF PRACT
ICES

Module(s):
organic group
, moderation
,

og_block_visibility
,

og_calendar,

og_event,

og_forum,

og_menu

COMMUNITIES OF PRACT
ICES NOTIF
ICATIONS

Module(s): notification
, messaging

The notification module will be
configured to allow subscription for relevant content type.

COMMUNITIES OF PRACT
ICES LISTING

Module(s): view, organic group



13

122
222
12

13

This module will require extensive customization because

by default, private group cannot be listed at all.

Refer to the conceptual manual for more information

on the Community of Practice related features
.

FORUMS

The built
-
in forum module will be used.

C
OMMUN
I
CATION
TOOLS

Hard link to communications tools will

be provided in a Drupal block.

EVENT CALENDAR

Module(s): calendar
, view
s
, event

EVENT REGISTRATION

Module(s): signup, signup_pay, simple_paypal

Ideeclic
has finished porting this module to
to Drupal 6. This module is required
whenever
Paypal payment
shoul
d be collected on some registrations. The module
has
be
en

customized so it can accept a Paypal
account specific to the event

instead of a unique global Paypal account for the Portal
.

The Paypal payment
gateway supports all major credit cards and more. For
more information about the payment methods
supported by the Paypal framework, please visit
http://paypal.com
.

JOB BOARD

Module(s): view
s
, cck

The job search engine will be implemented with the views. That will no prevent t
he global search engine
from finding job posting.

NEWS

Module(s): view
s
, cck



14

122
222
12

14

SECURITY HIGHLIGHTS

MEMBERS

In order to register, a person must provide a valid email address. A confi
r
mation email will be sent to that
address. The message will contain a link
that the person must click in order to activate the profile. This will
help pr
e
vent automatic registration by bots.

USER CONTRIBUTIONS

Only
registered Portal M
embers will be able to
submit content on the Portal. The type of content and
whether or not conte
nt vetting will be required for a Portal Member group is outlined in the
Permission and
security

ta
ble

in the conceptual manual
.

DOCUMENT TYPES

It is recommended that we limit the types of document that can be uploaded into the CMS to avoid
pote
n
tial virus
es
. The content matrix will specify the allowed content types

that are safer and more suitable
in each situation
.

Some document types like
PDF a more «

secure

». But
just as long as not anyone can upload documents
(or that you trust people who do perform
uploads) it should be fine to allow other types such as Word
doc
u
ments (*.doc), PowerPoint documents (*.ppt).

DOCUMENT SIZE

For the accepted content types, another limitation must be applied to the size of the resource being
u
p
loaded. For instance, the hei
ght and width of an image file should be keep within some boundaries
depending on the context in which the image will be used (Member’s picture, photo gallery images, an
o
r
ganization’s logo …)

The decision to specify a document size must be done by the Por
tal Administrator based on the usage
pattern of Portal members.

By default, we will set this limit at 8M
B per file and a total of 40MB per user.
These settings can later be changed if necessary.

ONLINE PAYMENTS

Although online paymen
ts

will be initiated on

the Portal

(see event registration)
, the online payments will be
handled by Paypal. The only payment related information kept in the database will be:



15

122
222
12

15



The buyer’s email addresses (the signup address and the Paypal address)



The buyer’s full name provided o
n the signup form



The payment transaction number



The amount paid

STANDARDS

DOCUMENTATION STANDA
RDS

This document will be updated during the project to become the Maintenance Manual.

NAMING CONVENTIONS



File names:
ISO 9660 level 2 (32 characters)



Uniform Re
source Locators (URL): URL rewriting will be activated in order to produce search
engine friendly URLs. URLs will look like the followings:

o

http://<portal_domain>/<module>/<node_id>

o

Examples:



http://first
nationportal.com/node/6



http://firstnationportal.com/og



http://drupal_sandbox/sites/default/files/lipsum.txt


PROGRAMMING STANDARD
S

All
HTML code created by Idéeclic will be:



XHTML compliant.



Respect WAI standards Level A (priority 1):

http://www.w3.org/WAI/WCAG1A
-
Conformance
.



Valid W3C:

http
://validator.w3.org/
.

The Drupal 6 core is also XHTML and W3C compliant.

Idéeclic can not guaranty standards validation inside the existing 3
rd

party contributed modules.



16

122
222
12

16

Here
are
the
3
rd

party contributed

modules
used in this project:

The full list is av
ailable on the Portal at the address
http://fnbc.info/admin/build/modules




CCK
-

http://drupal.org/project/cck



Views
-

http://drupal.org/project/views



FCKEditor
-

http://drupal.org/project/fckeditor



Event

-

http://drupal.org/project/event



Calendar (calendar
-
6.
x
-
2.2
)

-

http://drupal.org/project/calendar




Moderation

(moderation
-

6.x
-
1.4
)
-

http://drupal.org/project/moderation



Organic Groups and related modules

o

Organic Groups (og
-
6.x
-
2.0
)

-

http://drupal.org/project/og

o

OG Block Visibility

(
og_b
lock_visibility
)

-

http://drupal.org/project/og_block_visibility


o

OG Calendar (og_calendar
-
6.x
-
1.0
)

-

http://drupal.org/project/og_calendar

o

OG Contact (
og_contact
)

-

http://drupal.org/project/og_contact


o

OG Event (og_event
-
6.x
-
1.x
-
dev
)

-

http://drupal.org/project/og_event

o

OG Forum (og_fo
rum
-
6.x
-
2.0
-
rc4
)

-

http://drupal.org/project/og_forum

o

OG Menu

(og_menu)

-

http://drupal.org/project/og_menu

o

OG Panels

(og_panels)

-

http://drupal.org/project/og_panels




Signup

-

http://drupal.org/project/signup




Signup confirm e
-
mail

-

http://drupal.org/project/signup



Simple Paypal (simple_paypal
-
6.x
-
1.x
-
dev)
-

http://drupal.org/project/simple_paypal



Warning

(warning
-
6.x
-
1.x
-
dev)

-

http://drupal.org/project/warning




Google Maps Embed (6.x
-
1.2)



Content Access (6.x
-
1.2)



Ad (6.x
-
2.1)





17

122
222
12

17

DETAILED TECHNICAL S
OLUTION

TECHNICAL ARCHITECTU
RE & ENVIRONMENTS

LIVE SERVERS INFRAST
RUCTURE AND ARCHITEC
TURE



CPU:
AMD Phenom II X3 2.6Ghz



RAM:
2GB



Hard Drive:
3
0GB



Bandwidth: 100Mbps, 3000GB/Month



Administration: cPanel/WHM Internal



Enterprise Linux (CentOS)




MySQL.
5.0.
81



PHP.
5.2.9

At the end of the project, CDs or DVDs will be handed o
ff to NRT / FTNC. The medium will content backup
of all the files and database content as well as the original working version of the graphical design
elements. Although the hosting service is
configured

by Ideeclic, the
service and
servers are provided, r
un,
and physically managed by iWeb

(
http://iweb.ca
)

The guarantees that comes with the hosting plan are (
http://iweb.com/about
-
us/legal/
) :



100% Network and Power Uptime



Hardw
are replacement in less than 4 hours



Lowest price guarantee


STAGING AND
DEVELOPMENT SERVERS
INFRASTRUCTURE AND A
RCHITECTURE

iWeb Shared Hosting at
http://
fnbc.info
/




18

122
222
12

18

DATA MANAGEMENT PLAN

DATA ARCHIVING AND S
TORAGE

Database: MySQL

DATABASE (OR OTHER D
ATA STORAGE) MANAGEM
ENT PLAN



Cron tasks will be properly setup in order to allow Drupal to perform regular database
maintenance task periodically



A checklist will be provided in order to perform a regular database backu
p (performed by the
Portal Administrator).



A daily and a weekly backup solution will be provided by Ideeclic. The server will generate a daily
backup that will be stored

on

the server itself. Then, on a weekly basis, a backup archive will be
automatically
sent to
Ideeclic’s FTP server available to the client.

DATA VOLUMES / DATA
LOAD

A
basic
Drupal web site require
s

roughly 50MB
.

File storage capacity
10
GB
.

The capacity of 10GB

is based on estimates and

will be adjustable in the future to suit the Portal’s
needs.

Bandwidth: 1000GB per month

Connection Speed:
10
0
mb
ps


COMPONENTS

List all components, key functions and configurations

PAGE / CONTENT TYPES

Alphabetical list of content types used in this project.

The full list is available on the Portal at the add
ress
http://fnbc.info/admin/content/types




ADVERTISEMENT



COMMENT



19

122
222
12

19



COP



COURSE



COURSE LISTING



EVENT



FORUM TOPIC



GALLERY



GENERIC



GENERIC LISTING



HOMEPAGE



IM APPLICATION



IM APPLICATION LISTING



JOB



LANDING P
AGE



LINK LISTING



NEWS



FIRST NATIONS ORGANIZATION



ORGANIZATION LISTING



PAGE



PHOTO



RESOURCE



SITE



SLIDE SHOW



SUBJECT AREA LISTING



URL



20

122
222
12

20


CONTENT MANAGEMENT

The Content Management is being taken care of by the Drupal CMS.

WORKFLOW

C
ONTENT
V
ETTING

The moderation

module will content the content creation workflow whenever content vetting is required.

The author of the content will submit it. Then the administrator will use the moderation features to accept or
refuse the submitted content. The following content are
subject to vetting:



New URL submitted for the Portal



New Communities of Practices

A
CCESSING A
C
OMMUNITY OF
P
RACTICE

Accessing a Community of Practice will require the following steps:



The requester clicks on the link to request access;



The requested is pre
sented with a form where (s)he can enter a justification message to be sent
with the access request;



The owner of the Community of Practice will receive a notification email and will take the
necessary action by following the instructions in the email.

P
AY
ING FOR A PAID EVENT

REGISTRATION



The visitor displays the event, whishes to register and click on the paid registration link (or button);



The visitor will be presented with a registration for that (s)he can fill out;



After submitting the form, the visitor

will be taken to the Paypal site in order to proceed with the
payment;



After a successful payment, the visitor will be taken back to the Portal where the registration data
will be updated to reflect the successful payment.



21

122
222
12

21



If the customer had chosen to pa
y using a non
-
automated method (check, wire transfer …)
or if
the Paypal payment did not succeed, then
the registration status will show that a payment is
required.

USER MANAGEMENT


Groups

/ Roles

Permissions

P
UBLIC

(A
NONYMOUS USERS
)

B
ASIC
M
EMBER

C
OMMUNI
TY OF
P
RACTICE
M
EMBER

O
RGANIZATION
A
DMINSTRATORS


DEVELOPMENT TOOLS



PHPMyAdmin



Dreamweaver



Netbeans



SVN

TESTS



Before install
ing

a new module, we will check the

stability and different issues;



Each
feature

and section of the
Portal

will be tested by
Ideecl
ic and selected
users;



Stress tests will be do
ne to simulate concurrent users;



The file
/document

upload will be tested;



The access rights of the uploaded files will be verified;



A final test will be done whe
n the live server will be setup;



Sample content a
nd stress test content will be used in order to verify the effectiveness of the
security filters that prevent contributor to perform HTML or Code Injection
(see

http://en.wikipedia.org/wiki/Code_i
njection
)
;



22

122
222
12

22



Different scenario will be simulated in a real situation in order to ensure that the Portal is able to
effectively send outbound e
-
mail whenever required (notifications, confirmations, contact forms …)



Various tests will be performed in order t
o verify and confirm the know limits of the Portal. For
instance, the maximum length of the menu items’ titles that can be used before affecting the
Portal’
s design;



Ideeclic will ensure that even in the absence of content in some or all sections, the Port
al will still
have a friendly appearance
;



The “access denied” and “page not found” pages will be tested to ensure that they appear when
required and that they d
isplay the appropriate messages;



The security logging capability of Drupal will be tested.

ROLLO
UT

To
deploy

the Portal

is a delicate process and increase in complexity after the first deployment.

Ideeclic will perform the following tasks:

For the system, the file system including the uploaded documents:



Migrating the Drupal core and contributed modu
les on the live server



Uploaded the contributed (uploaded) files to the live server



Resetting the permissions on the files on the live server



Configuring the cron scheduled tasks on the live server



Configuring the e
-
mail server

for the live server’s domain

For the Data



Exporting the database from the development server



Importing the database on the live server while keeping the database encoding format

Once
the Portal
deployed,
the processes described above cannot be simply redone. Great care must be
taken
in order to avoid breaking the links between the database and the physical files of the uploaded
resources (document, images …). Failure to do so will result in many orphan files or database entries that
will waste valuable disk space.



23

122
222
12

23

APPLICATION MAINTENA
NCE

This section is preliminary and will be updated for the Maintenance Manual.

DOMAINE NAMES

The domain names for the Portal are:



fnbc.info (http://fnbc.info)



firstnationsbc.info (http://firstnationsbc.info)

ADMIN ACCESS

The a
dmi
nistration

menu is located

here
at the following address




http://fnbc.info/admin


Quick login page



http://fnbc.info/user


DIRECTORIES STRUCTUR
E



The
Portal’s
theme is located in:
sites/default/themes/
fnb
c



Mini Sites themes will be located inside
sites/default/themes/
minisites/minisite_name



All 3
rd

parties modules and custom modules are in:
sites/all/modules/



Uploaded files are located here: sites/default/files

NAMESERVERS

The n
ame

servers
for the Portal a
re
:



DNS1:
my
.
privatedns.com



DNS2:
your
.
privatedns.com



24

122
222
12

24

I
WEB CPANEL
ADMINISTRATION
ACCESS



Address :
http://fnbc.info:2082




Username:
fnbc



Password:
ideeclic296$

FTP ACCESS



Address :
209.172.55.88



Username:
fnbc



Passwor
d:
ideeclic296$

AUTOMATIC TASKS

A Cron task needs to be created for the Drupal core. It is configured to run automatically each day.
However, for heavily used web site, the Cron task may require to be executed more often (e.g. every hour
or every 30 minut
e). During the execution of these tasks, Drupal also perform content indexing which is the
process of preparing the content for the search engine.

The entry for the cron task for Drupal is:

0 0 * * *
wget
-
O
-

-
q
-
t 1 http://fnb
c.info/cron.php

PATCHES APPL
IED TO DRUPAL

Some patch (code correction to the core or modules) had to be applied to
some 3rd Party modules in order
to ensure that the Portal functions
properly.
The patched modules are:

1.

og (Organic Groups): for CoP and Mini Site features.

2.

signup_pay: f
or paypal payments

3.

og_forum: for the forum feature inside the CoPs.

ADMIN EMAIL

The admin email address
es aliases can be created in cPanel and forwarded to any valid e
-
mail address.
For real e
-
mail accounts, an access to the
access email via the cpanel or
set
-
up the email account on


25

122
222
12

25

outlook.
The
re

are extensive documentation
s available as video tutorials inside the cPanel administration
Web interface that can be used for further advanced needs.

DATABASE



Serveur host name: localhost



Database name:
fnbc_porta
l



Database User: fnbc_dbuser



Database Password:
vHS!4u71hI6a

DRUPAL CORE & MODULE
S UPDATES

For the Drupal core and the third parties modules, whenever
vulnerabilities

are

discovered or whenever an
improved or better performing version is released, it might

be necessary to
upgrade the version of the
affect modules or the Drupal core used by the Portal.

The Portal is configured to check the availability of new versions of the installed elements on a daily basis.
If new updates are available, Drupal will displ
ay the information in the administration area as seen on the
screen capture.




26

122
222
12

26

IN SUCH CASE, ONLY A QUALIFIED DRUPAL

SPECIALIST SHOULD PROCEED WITH THE
FOLLOWING STEPS WITH INSTALLING THE NECESSARY UPDATE.

The following modules had to been customized duri
ng the creation of the Portal and should not be
upgrading without porting the customization to the new version. Failure to do so will result in the permanent
lost of the customizations. The modules are:



og



signup_pay



og_forum

BACKUP

Via the cPanel, g
oto Fi
les then Backups and then to Full Backup. Fill out information to have back up sent
anywhere you want. By default, back up is generated at the root of your
directory

structure






27