Fuzbolero .'s Library tagged cms →  View Popular

go to Packt Publishing's Open Source CMS Award Web site before October 30 and cast your vote in the following categories:



• Hall of Fame
• Best Open Source PHP CMS

Use an indent of 2 spaces, with no tabs.

Lines should have no trailing whitespace at the end.

Files should be formatted with \n as the line ending (Unix line endings), not \r\n (Windows line endings).

Create forms that submit a search to an external search engine, like Google, Yahoo!, Wikipedia, Last.fm or any other engine that uses query strings for form submissions (GET). External Search comes with predefined settings for a lot of common search engines in the following categories:



• Dictionaries and encyclopediae
• General Search sites
• Media
• Programming



If you would like a form for a search engine that isn't predefined, you can enter its settings at the External Search administration page.

Available Modules




There are many modules that provide some sort of slideshow / rotator functionality.



• Dynamic display block - Enables you to create and present blocks of content in a dynamic way. Uses the jQuery Cycle Plug-in.
• Views Rotator - a Views style plugin using the Cycle jQuery plugin with a small number of options for controlling transition behaviour.
• Views Cycle - a Views style plugin using the Cycle jQuery plugin, with an option for tabs, several transition effect options and other transition behavior settings.
• Views Slideshow - a Views style plugin using its own JavaScript for the rotation, also including a tabs option and a small number of transition behavior options. The Drupal 6 (dev) version is an extensible API that allows other cycles, rotators, and carousels to plug into the module, so they don't need to recreate the Views functionality.
• Views Slideshow: ImageFlow - offers an ImageFlow option to Views Slideshow, similar to Apple's CoverFlow.
• Slideshow Creator - adds an input format filter to allow you to add slideshow creation code to the body of a node. This module has been deprecated
• Featured Content Slider - select nodes based on content type and create up to 3 blocks of featured content.
• Slider - create a "slider" content type with a multi-value nodereference field to create carousel-style sliders of the referenced nodes.
• EasySlider - create a list-style view with a block display and the view results are displayed in a carousel style slider.
• Node Carousel - create carousels of nodes based on nodequeue or custom values using a hook in your own module.
• Views Carousel - a Views style plugin using the jCarousel jQuery plugin for the rotation, suitable for e.g. a scrollable thumbnail viewer.

The node access system determines who can do what to which nodes.

In determining access rights for a node, node_access() first checks
whether the user has the "administer nodes" permission. Such users have
unrestricted access to all nodes. Then the node module's hook_access()
is called, and a TRUE or FALSE return value will grant or deny access.
This allows, for example, the blog module to always grant access to the
blog author, and for the book module to always deny editing access to
PHP pages.

If node module does not intervene (returns NULL), then the
node_access table is used to determine access. All node access
modules are queried using hook_node_grants() to assemble a list of
"grant IDs" for the user. This list is compared against the table.
If any row contains the node ID in question (or 0, which stands for "all
nodes"), one of the grant IDs returned, and a value of TRUE for the
operation in question, then access is granted. Note that this table is a
list of grants; any matching row is sufficient to grant access to the
node.

In node listings, the process above is followed except that
hook_access() is not called on each node for performance reasons and for
proper functioning of the pager system. When adding a node listing to your
module, be sure to use db_rewrite_sql() to add
the appropriate clauses to your query for access checks.

To see how to write a node access module of your own, see
node_access_example.module.

In early 2009, The American Society of Media Photographers (ASMP) embarked on a website redevelopment project with Context, a web development firm based just outside of Philadelphia.

With over 7,000 members and an expansive website consisting of hundreds of pages ranging from informational tutorials to event registration to their national "Find a Photographer" service, the ASMP had quite a project in front of them, and were looking for guidance in determining which system would be able to meet their requirements.

After reviewing the ASMP's 11 page request-for-proposal and the wonderfully clean and organized designs provided by Chicago's Grillo Group, Context decided that Drupal was the only CMS that would make the project practical.

SportBusiness Group is the world's leading supplier of information, media and B2B marketing services to the sports industry and, with its network of partners and agents, assists companies from all over the globe in achieving their business goals.

The latest incarnation (site version 11, 3rd Drupal version) of the Sportbusiness.com website has finally brought us into the world of Drupal 6. We initially moved the site over to Drupal almost 3 years ago (back in the Drupal 4.7 days) after months of data conversion from a proprietry Oracle-based CMS. We've never looked back. The upgrade to Drupal 6 has just finished; the site has been redesigned and several major changes have been implemented.

Getting up to 10,000 page impressions a day certainly doesn't make this a high-traffic site by comparison to some of the other sites we have at Electric Word plc (parent company to SportBusiness), but the visitors to the site demand equally high levels of quality and content. This was something we had to maintain from previous releases.

Installation profiles allow easy installation and configuration of a pre-defined set of modules. For example, the Drupal.org testing profile allows a user to quickly set up a site that approximates drupal.org, which is useful for testing. The biggest usability limitation of the current system is that all of the modules required by the installation profile must be downloaded and placed in the correct directories separately. Instead of being a one step process to get a new site up and running, end users must download the installation profile, read the documentation (if it even exists!) to find the list of other things to download, and so on.

With some work, the packaging scripts that come with Project module and which create all of the releases on drupal.org could be modified to automatically gather Drupal core and all the contributed modules needed for a particular install profile, and place them in a single archive file for download. This would greatly improve the usability of installation profiles, and make it much easier for Drupal site builders to get started with a Drupal installation tailored for a specific type of website.

In version 5, Drupal added Installation Profiles (sometimes also confusingly called distribution profiles) to its list of features. An installation profile is basically nothing more than a list of required modules and a variety of configuration code which gets performed during installation to give Drupal a bit more oomph out of the box.

A "distribution" of Drupal is one or more installation profiles included with Drupal itself and all of the required modules. Distributions can either be offered as a convenience to site builders by bundling together frequently used components, such as Acquia Drupal, or they can be used to offer a version of Drupal specifically targeted to a unique use case, such as Open Publish. Dries has some heavy things to think about for anyone interested in getting into the distribution business, so I'll pause for a moment while you go and read that link.

Back? Great! So you've decided you want to share your ultimate Drupal site for whatever reason, and you want to do it in the fastest way possible. Then this article is for you!

Step 4: Remove settings.php.

Not a lot of fun to send your database credentials out into the world. Check for any other sensitive files that might be lying around too, like SSL certificate keys, .htpasswd files, and the like.

Want to create a front page that's styled differently from the rest of your site? Perhaps you need a separate admin theme? Or how about a login page which only shows the login block and nothing else? With a little PHP knowledge these problems are easy to solve.

Note: You must be using the PHPTemplate theme engine for your theme. An easy way to determine this is by looking for files ending in .tpl.php within your site's theme folder. PHPTemplate is compatible with Drupal 4.6 and up. As a matter of fact, it's the default theme engine for Drupal 4.7 since it combines the best of both worlds for designers and programmers. Designers get an easy way to manipulate HTML lightly sprinkled with PHP variables for dynamic content, and developers get a fast rendering template system that's a snap to extend. Here's what a template looks like using PHPTemplate.

While at Drupalcamp Copenhagen I got into a few conversations about Drupal aha! moments, particularly around theming. After trying to talk in the abstract about the things that finally "clicked" for me when I was learning Drupal, I offered to write it up with some specifics. So, for my Danish buddies and any other curious Drupalers, these are my two biggest aha! moments that accelerated my Drupal theming ninja skills: "getting" the theme system and working with forms. I've already written about modifying forms and since "getting the theme system" is a big chunk, I'm going to focus just on that moment in this article.

Now "getting" the theme system could mean a lot of things, and what I mean is that once I understood what Drupal does by default and the way it expects me to override that, a lot of things fell into place for me. Instead of trying to control the firehose at full blast, I could see where the spigot was and how to turn the water down. I actually had this realization at a Lullabot workshop, back before I became a 'bot. It came about because I was formally introduced to PHPtemplate engine. In Drupal 5, which was current at the time, this was through a tour of the phptemplate.engine file. In Drupal 6 PHPtemplate is tied more closely to core and so in this article I'm going to be looking at theme.inc. For me, this was probably the biggest aha! moment I've ever had with Drupal. I'm not going to try to explain the whole Drupal theme system. There is a great guide on Drupal.org, as well as a few theme books out there, that do a good job of covering the big picture and the nitty-gritty details. We even have two videos that walk you through the wonders of theming. Here, I just want to talk about the little nuggets that happened to tie things together for me.

Similar



• Take control of your Drupal theme
• Drupal Theming: The Code Behind the Videos
• Podcast 74: Drupal Design Round Table
• Drupal Podcast No. 55: John Albin Wilkins and the Zen Theme
• Imagecache Example: User Profile Pictures