HOW TO CONTRIBUTE TO THE DISTRICT 9650 WEB SITE

Error message

  • Deprecated function: Return type of DatabaseStatementBase::execute($args = [], $options = []) should either be compatible with PDOStatement::execute(?array $params = null): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2244 of /home2/yogikbh/public_html/rotary/drupal_7/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::current() should either be compatible with Iterator::current(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home2/yogikbh/public_html/rotary/drupal_7/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::next() should either be compatible with Iterator::next(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home2/yogikbh/public_html/rotary/drupal_7/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::key() should either be compatible with Iterator::key(): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home2/yogikbh/public_html/rotary/drupal_7/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::valid() should either be compatible with Iterator::valid(): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home2/yogikbh/public_html/rotary/drupal_7/includes/database/database.inc).
  • Deprecated function: Return type of DatabaseStatementEmpty::rewind() should either be compatible with Iterator::rewind(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in require_once() (line 2346 of /home2/yogikbh/public_html/rotary/drupal_7/includes/database/database.inc).
  • Deprecated function: strlen(): Passing null to parameter #1 ($string) of type string is deprecated in drupal_random_bytes() (line 2268 of /home2/yogikbh/public_html/rotary/drupal_7/includes/bootstrap.inc).
  • Deprecated function: Return type of DateObject::__wakeup() should either be compatible with DateTime::__wakeup(): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include_once() (line 158 of /home2/yogikbh/public_html/rotary/drupal_7/sites/all/modules/date/date_api/date_api.module).
  • Deprecated function: Return type of DateObject::format($format, $force = false) should either be compatible with DateTime::format(string $format): string, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include_once() (line 158 of /home2/yogikbh/public_html/rotary/drupal_7/sites/all/modules/date/date_api/date_api.module).
  • Deprecated function: Return type of DateObject::setTimezone($tz, $force = false) should either be compatible with DateTime::setTimezone(DateTimeZone $timezone): DateTime, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include_once() (line 158 of /home2/yogikbh/public_html/rotary/drupal_7/sites/all/modules/date/date_api/date_api.module).
  • Deprecated function: rtrim(): Passing null to parameter #1 ($string) of type string is deprecated in url() (line 2349 of /home2/yogikbh/public_html/rotary/drupal_7/includes/common.inc).
  • Deprecated function: strpos(): Passing null to parameter #1 ($haystack) of type string is deprecated in url_is_external() (line 2393 of /home2/yogikbh/public_html/rotary/drupal_7/includes/common.inc).
  • Deprecated function: str_replace(): Passing null to parameter #3 ($subject) of type array|string is deprecated in url_is_external() (line 2395 of /home2/yogikbh/public_html/rotary/drupal_7/includes/common.inc).
  • Deprecated function: ltrim(): Passing null to parameter #1 ($string) of type string is deprecated in url() (line 2311 of /home2/yogikbh/public_html/rotary/drupal_7/includes/common.inc).

CASUAL CONTRIBUTIONS OR AMENDMENTS

Fill in the AMEND WEB PAGE FORM and email to webmaster

ACCESS TO CONTENT MANAGEMENT SYSTEMS

Access is from the My Account link on the Home page of the web site.

The district website has 2 different types of access. 

1. DISTRICT CONTACT DATABASE - Available for all registered members of Distict 9650 Rotary.

2. WEB PAGE EDITORS AND CONTRIBUTORS LOGIN - Available for any interested members who wish to contribute to the District Web Site

It is here you request access to become an editor of the web site content. Other features are Upload content, files, photos etc.
 

HOW TO BECOME AN EDITOR / CONTRIBUTOR

1. USER NAME: This is the name that will show up on all your contributions. It is best not to make it so cryptic that no one could guess who you are.
2. Email the webmaster Bruce Hemmett with the following details requesting to become a contributor to the District 9650 include your USER NAME. Copy the following text into your email.

Dear Webmaster

 I would like to become a contributor to the Rotary District 9650 web site.

MY NAME IS:

MY EMAIL IS:

MY ROTARY CLUB IS:

USER NAME IS:

You will be sent a confirmation email with a link to create your password.  Your password should contains at least eight characters. It should include numbers, punctuation, and both upper and lowercase letters. e.g. Grocho#36 (It may take a few days for the confirmation email to be sent)

PREFERRED BROWSER

To successfully edit content we strongly recommend you use Mozilla Firefox as your browser. For some reason other browsers cause unexpected behavior when editing content.

THE ROLE OF AN EDITOR

Add a new page to the website.

Submit an article or story.

Add comments to an existing page.

Add photos to the District Photo Gallery

The first step is to apply to become a  contributor / editor. See How to become a contributor

Create content:

Blog entry

DGs_News 

Used by current DG for weekly / personal blogs.

Event

Events have a date field and are automatically added to the calender. 

Forum topic

Page

Panel

Story

A blog entry is a single post to an online journal, or blog.

DG's News blog. The most recent will be displayed on the Home Page. Other published pages will be listed on the DG's News summary page.

Events have a start date and an optional end date as well as a teaser and a body. They can be extended by other modules, too.

A forum topic is the initial post to a new discussion thread within a forum.

A page, similar in form to a story, is a simple method for creating and displaying information that rarely changes, such as an "About us" section of a website. By default, a page entry does not allow visitor comments and is not featured on the site's initial home page.

A panel layout broken up into rows and columns. ( PS Please do not use this option - Only for the very advanced users)

A story, similar in form to a page, is ideal for creating and displaying content that informs or engages website visitors. Press releases, site announcements, and informal blog-like entries may all be created with a story entry. By default, a story entry is automatically featured on the site's initial home page, and provides the ability to post comments.

Publishing documents on the District Web Site

We accept the following document formats. (.doc, .pdf, .xls,)

pdf -  Portable Document Format (PDF) is an open standard for document exchange originally created by Abode. Free pdf writers are readily available here.

doc - Word documents - should be saved as Word 97-2003 Document (*.doc) - This is the most universal version that can be opened by older as well as the latest versions of work. Newer versions of Word save as (*.docx). Unfortunately .docx cannot be opened by older versions of Word.

xls - Excel spreadsheets.

PLEASE REPLACE SPACES IN FILE NAMES WITH _ or - (i.e. underschore or dash). Having file names with spaces in its name can causes erattic behaviour when it comes time for the file to be downladed. So instead ot nameing a file "Upload this file.doc" - name it as "Upload_this_file.doc"

File Upload Locations

Files should be uploaded into the appropriate folders.
Documents: root/file/subfolder
Images: root/image/subfolder
Where subfolder is the area that is most appropriate for the particular file topic. If in doubt search for files or images of a similar subject matter and save the file in that subfolder. e.g. root/file/... subfolders could be /Newsletter, /Manuals   or root/image/... subfolders could be /2013-14  or /2014-15 etc to represent the current year

If the file or image is expected to be only valid for the current year then use the folder format -  /2021-22 etc.