No known problems
Tips and tricks
This page will be a dumping ground for small tips on improving your profiles with Advanced Profile Kit.
#470004: User avatar via CCK imagefield - Not complete but some good ideas there.
http://drupal.org/node/578900#comment-2174250 - Setting some parts of the profile private.
Installing Auto Admin
This handbook page is part of the documentation for the Auto Admin module.
With drush
Simply do:
$ drush dl autoadmin schema
$ drush enable autoadminManual
- Download the .tar.gz files from the project pages of Auto Admin and Schema modules.
- Extract into the "sites/all/modules" folder.
- Browse to the administration page and enable the modules.
Migrate from Nodewords 6.x-1.6 to 6.x-1.7
Hey,
I recently experienced problems from updateing to a new version of nodewords and removing the nodewords_by_path module. Looks like the format in the DB for nodewords table has changed to the serialized format. The old meta information was still in the database, but it was not recognisible since the format was plain.
So I made a quick script to port the meta tags (abstract, copyright, keywords and description) from one format to another:
Create a page with PHP content and write the following: (it's recommended to backup the database first)
<?php
// PHP Code
$result = db_query("SELECT * FROM nodewords n WHERE ( n.name='copyright' OR n.name='abstract' OR n.name='keywords' OR n.name='description' ) AND n.content NOT LIKE 'a:%{%}';");
while ($item = db_fetch_object($result)) {
unset($new_content);
$new_content = array('value' => $item->content);
$data = array(
'mtid' => $item->mtid,
'name' => $item->name,
'content' => serialize($new_content) // looks like drupal_write_record() doesn't serialize this, so I do it manually
);
drupal_write_record('nodewords', $data, 'mtid');
}
?>Display node types of cck content fields on permission page
I have run into the problem, that on the permissions page after having created dozens of content types and with many cck fields, which sometimes are shared by some types, i find it difficult to determine which field belongs to which node type. I knew I had to theme the permissions page. Which is what i did. To get a better overview of your content_permissions section put this in your template.php:
Lucene field types
Lucene indexes are composed of atomic documents. Each document is divided into named fields which either have content that can be searched or data that can retrieved. Before storing data into a field, it is important to determine which field type best fits the nature of the content being indexed. It is also best practice to avoid having to retrieve large amounts of data from the index itself. The Search Lucene Content module implements this practice by indexing most data using the UnStored field type. When searches match content in these fields, only the matching node ID is retrieved from the index, and the search results are populated with data from the database. This allows us to make use of Drupal's APIs without having to re-implement them on the Lucene layer. All available field types are listed below:
devdaily.com - technical support for open source users
Introduction
This is a brief case study describing the motivations and experiences of porting the devdaily.com website to use Drupal (Drupal 6 as of the time of this writing).
About devdaily.com
devdaily.com provides tutorials for users and developers of Open Source software. First created back in 1998, the devdaily.com website has been a one-man operation since its inception.
From 1998 through early 2009, approximately 1,200 blog posts and other tutorials were created. The total number of blog and tutorial pages is approximately 2,000, and there are over 50,000 other static pages on the site.
In early 2009 alexa.com showed the "traffic rank" for devdaily.com as around 70,000 -- making devdaily roughly the 70,000th most popular site on the internet.
The blog engine used was based on Java code I (Alvin Alexander) first created back in 2000, and have been making updates to since that time. In the spring of 2009 I realized I was spending as much time writing code to add new features to the blog as I was spending time writing new tutorials -- and I knew I needed to do something else.
