Skip to content
Snippets Groups Projects
Select Git revision
  • issue-752
  • develop
  • master default
  • issue-677
  • issue-677-original-with-migrate
  • issue-716
  • issue-654
  • issue-732
  • issue-737
  • issue-735
  • issue-707
  • issue-706
  • issue-705
  • issue-703
  • issue-696
  • issue-690
  • issue-675
  • issue-670
  • issue-635
  • issue-404
  • 7.19
  • 2012-04-18
  • 2012-04-03
  • 2012-04-02
  • 2012-03-01
  • 2012-02-07
  • 20120207
  • 2012-01-13
  • 2012-01-12
  • 2011-12-16
  • 2011-12-05
  • 2011-11-17
  • 2011-11-14
  • 2011-11-08.2
  • 2011-11-08
  • 2011-11-01
  • 2011-10-27
  • 2011-10-06
  • 2011-10-03
  • 2011-09-19
40 results
Compare
Forked from UNL Information Services / UNL-CMS
223 commits behind the upstream repository.
Name Last commit Last update
includes
misc
modules
profiles
scripts
sites
themes
vendor
.gitignore
.gitmodules
.htaccess-subsite-map.txt.sample
.htaccess.sample
CHANGELOG.txt
COPYRIGHT.txt
HOW-TO-CONTRIBUTE.md
INSTALL.mysql.txt
INSTALL.pgsql.txt
INSTALL.sqlite.txt
INSTALL.txt
LICENSE.txt
MAINTAINERS.txt
README.md
UPGRADE.txt
authorize.php
cron.php
example.robots.txt
index.php
install.php
rewrite.php
rewrite_miss.php
update.php
web.config
xmlrpc.php
README.md

Requirements:

Get Started:

In this example the web root is /Library/WebServer/Documents and Apache runs as _www - modify the instructions below according to your setup

  • Fork UNL-Information-Services/UNL-CMS and clone your fork into /Library/WebServer/Documents/workspace/UNL-CMS

  • Create a local database (example name: unlcms)

  • From /Library/WebServer/Documents/workspace/UNL-CMS run:

    git submodule init git submodule update

  • Create this file in your home directory with a name like resetunlcms.sh

    echo 'Resetting UNL-CMS... Get ready for action!'

    mysqldump -uYOURUSERNAME -pYOURPASS --add-drop-table --no-data unlcms | grep ^DROP | mysql -uYOURUSERNAME -pYOURPASS unlcms echo 'unlcms database emptied....'

    cd /Library/WebServer/Documents/workspace/UNL-CMS/sites/default rm -rf files rm settings.php mkdir files chown _www files cp default.settings.php settings.php chown _www settings.php

    cd /Library/WebServer/Documents/workspace/UNL-CMS/sites sudo rm -rf localhost.* sudo rm -rf MYDEVMACHINE.unl.edu.* sudo rm -rf unl.edu.* sudo rm sites.php cp example.sites.php sites.php

    echo 'Resetting .htaccess' cd /Library/WebServer/Documents/workspace/UNL-CMS sudo rm .htaccess cp .htaccess.sample .htaccess sudo chown YOURUSER .htaccess sed -i "" 's/# RewriteBase /drupal//RewriteBase /workspace/UNL-CMS//' ".htaccess"

    echo 'Done.' echo 'Note: If you want clean urls you need to look at the .htaccess file where it says "Allow public files to be accessed without the sites/<site_dir>/files prefix"';

  • Run that script. (Can also be run whenever you want to reset your dev environment.)

    sudo sh ~/resetunlcms.sh

  • Go to http://localhost/workspace/UNL-CMS and go through the install process

Install Issues:

  • Can't create a new site with Drush/UNL Cron if pdo_pgsql is enabled

    If pdo_pgsql is enabled on the php install that is running drush/unl cron then it will fail without modification. Adding the following junk values for pgsql solves the problem at line 414 (D7.10) of install_run_task inside install.core.inc

          $form_state['values']['pgsql']['username'] = 'xxxx'; //add this
      $form_state['values']['pgsql']['database'] = 'xxxx'; //add this
      drupal_form_submit($function, $form_state); //existing code
      $errors = form_get_errors(); //existing code

Hacks of Core:

  • includes/bootstrap.inc

    • function drupal_settings_initialize(). UNL change: include a "global" settings file that applies to all sites.

    • function conf_path(). UNL change: Add $default_domains array support for sites.php to list which domains are ok to use with 'unl.edu.*' site_dirs. If no $default_domains array is defined in sites.php, this code will do nothing.

    • Fix so that drupal_serve_page_from_cache() won't override a cached Vary header. http://drupal.org/node/1321086

  • rewrite.php

    This custom file is used to allow public files to be accessed without the sites/<site_dir>/files prefix.

  • sites/sites.php

    Added support for $default_domains array. See conf_path() in includes/bootstrap.inc

  • sites/example.sites.php

    Added an example of the $default_domains array. Added the stub record needed for creating site aliases.

  • modules/image/image.field.inc

Hacks of Contrib modules:

#DRUPAL 7 README

CONTENTS OF THIS FILE

  • About Drupal
  • Configuration and features
  • Installation profiles
  • Appearance
  • Developing for Drupal

ABOUT DRUPAL

Drupal is an open source content management platform supporting a variety of websites ranging from personal weblogs to large community-driven websites. For more information, see the Drupal website at http://drupal.org/, and join the Drupal community at http://drupal.org/community.

Legal information about Drupal:

  • Know your rights when using Drupal: See LICENSE.txt in the same directory as this document.
  • Learn about the Drupal trademark and logo policy: http://drupal.com/trademark

CONFIGURATION AND FEATURES

Drupal core (what you get when you download and extract a drupal-x.y.tar.gz or drupal-x.y.zip file from http://drupal.org/project/drupal) has what you need to get started with your website. It includes several modules (extensions that add functionality) for common website features, such as managing content, user accounts, image uploading, and search. Core comes with many options that allow site-specific configuration. In addition to the core modules, there are thousands of contributed modules (for functionality not included with Drupal core) available for download.

More about configuration:

  • Install, upgrade, and maintain Drupal: See INSTALL.txt and UPGRADE.txt in the same directory as this document.
  • Learn about how to use Drupal to create your site: http://drupal.org/documentation
  • Download contributed modules to sites/all/modules to extend Drupal's functionality: http://drupal.org/project/modules
  • See also: "Developing for Drupal" for writing your own modules, below.

INSTALLATION PROFILES

Installation profiles define additional steps (such as enabling modules, defining content types, etc.) that run after the base installation provided by core when Drupal is first installed. There are two basic installation profiles provided with Drupal core.

Installation profiles from the Drupal community modify the installation process to provide a website for a specific use case, such as a CMS for media publishers, a web-based project tracking tool, or a full-fledged CRM for non-profit organizations raising money and accepting donations. They can be distributed as bare installation profiles or as "distributions". Distributions include Drupal core, the installation profile, and all other required extensions, such as contributed and custom modules, themes, and third-party libraries. Bare installation profiles require you to download Drupal Core and the required extensions separately; place the downloaded profile in the /profiles directory before you start the installation process. Note that the contents of this directory may be overwritten during updates of Drupal core; it is advised to keep code backups or use a version control system.

Additionally, modules and themes may be placed inside subdirectories in a specific installation profile such as profiles/your_site_profile/modules and profiles/your_site_profile/themes respectively to restrict their usage to only sites that were installed with that specific profile.

More about installation profiles and distributions:

APPEARANCE

In Drupal, the appearance of your site is set by the theme (themes are extensions that set fonts, colors, and layout). Drupal core comes with several themes. More themes are available for download, and you can also create your own custom theme.

More about themes:

DEVELOPING FOR DRUPAL

Drupal contains an extensive API that allows you to add to and modify the functionality of your site. The API consists of "hooks", which allow modules to react to system events and customize Drupal's behavior, and functions that standardize common operations such as database queries and form generation. The flexible hook architecture means that you should never need to directly modify the files that come with Drupal core to achieve the functionality you want; instead, functionality modifications take the form of modules.

When you need new functionality for your Drupal site, search for existing contributed modules. If you find a module that matches except for a bug or an additional needed feature, change the module and contribute your improvements back to the project in the form of a "patch". Create new custom modules only when nothing existing comes close to what you need.

More about developing: