IMPORTANT: the code and documentation related to these modules are still experimental and should not be used in production enviroment.
The new version of Patterns provides the changes to offer compatibility with the new Patterns Server and Patterns Client modules (to be released soon), whose aim is to act as a hub for sharing Patterns files among Drupal users.The key attributes we aimed for are simplicity and security.
Given these goals, two addons to share patterns based on DrupalToDrupal and exchange information between clients and servers is being built. The client extension ensures transfer through a secure, encrypted channel where user credentials are verified each time an attempt to post patterns files is made. This way, a 1 to 1 association between patterns creator, patterns users and statistics can be generated.
Currently, the procedure to upload patterns is twofold: Patterns can be pushed to a user-specified server from the UI or via the Drupal drush utility.
A public Patterns Server will be released at drupal-patterns.org, but using the Patterns Server module anyone can set up his/her own server.
Uniform Server Drupal 7 Setup (Verbose)
An explicit guide to setting up an easy Drupal development environment utilizing the Uniform Server. “The Uniform Server is a WAMP package that allows you to run a server on any MS Windows OS based computer. It is small and mobile to download or move around and can also be used or setup as a production/live server.” http://www.uniformserver.com/
In case of difficulty:
The Uniform Server + Drupal 7 Installation Step-By-Step
Download the Uniform Server (version Coral 8.1.2) (Not the latest version; because Drupal needs PHP 5.3.10 and the latest is PHP 5.4.4 etc.)
Double-click Coral_8_1_2.exe (the self-extracting file for Uniform Server, it will create a folder in the same directory called "UniServer").
Move the UniServer folder and its contents to where you want your application and new Drupal sites to reside:
(typically Users/(your name)/Sites/UniServer)
or E:/UniServer (on a RAM stick or SD card)
Drupal works on any web server with PHP support.
Apache is the most commonly used web server for Drupal. Drupal will work on Apache 2.x hosted on UNIX/Linux, OS X, or Windows.
The majority of Drupal development and deployment is done on Apache, so there is more community experience and testing performed on Apache than on other web servers. Drupal 7 and 6 will likely work on Apache 1.3.
You can use the Apache 'mod_rewrite' extension to allow for clean URLs.
The Apache Virtualhost configuration must contain the directive
AllowOverride All to allow Drupal's .htaccess file to be used.
Nginx is a commonly used web server that focuses on high concurrency, performance and low memory usage.
Drupal will work on Nginx legacy versions (0.7.x, 0.8.x, 1.0.x), stable 1.2.x versions, and development 1.3.x versions hosted on UNIX/Linux, OS X, or Windows. Nginx is a popular alternative to Apache, so there is also significant community experience and testing performed on Nginx.
For information on enabling clean URLs, see Clean URLs with NGINX.
Microsoft IISRead more
Submitted content ends up with garbage quotes and backslashes : \"\\ "\\\\ etc. A magic_quotes_gpc issue
When saving content (through pretty much any form) that contains either single or double quotes, the data that lands in the system is the "escaped" version of those characters.
Re-saving the save content again can multiply the problem by repeatedly re-escaping the escaped stuff and you end up with strings like
<a href=\"\\"\\\\"\\\\\\\\"\\... !!
The PHP magic_quotes_gpc value has to be off. And it's not. Really. Even though your phpinfo may say it is!
Drupal PHP system requirements for server setup recommend/require it be off - but if not, Drupal tries to work around the problem.
Drupal would prefer magic quotes to be off globally. But when taking form submissions, it checks that flag. If it finds magic quotes are in fact on, it repairs the form input appropriately and carries on.
That usually worked - until recently.
The Drupal .htaccess file tries to disable the magic_quotes_gpc flag at runtime, but this is not allowed by all configurations and all versions of PHP.
Magic quotes is being deprecated and support for it is going away. Control of it may be troublesome.
As the title states, I've installed the module under 3 system configurations :
- Debian 6 / PHP 5.3 / Virtualmin on a private server
- Ubuntu 10.04 LTS / PHP 5.3 on a development workstation
- Ubuntu 12.04 LTS / PHP 5.4 on a development workstation
Downloadprogress beind installed by PECL, the first step is to install pecl. In both distributions it's included in the php-pear package. So :
sudo apt-get install php-pear
In the two operational configurations, the package was already installed ; as a basic component in the Ubuntu WS and as part of Virtualmin auto-installation on the Debian server.
At this stage, pecl is installed but it will need to compile the downloadprogress module as a step of the installation process. So more resources are needed before pecl can be invoked.
sudo apt-get install php5-dev
Accept the required dependeces and let apt-get do it's job.
Ubuntu 12.04 (LTS):
build-essentialis another required package, otherwise the install will fail:
sudo apt-get install build-essential
Then pecl can be invoked :
sudo pecl install uploadprogress