Gopisathya

1. Features and field collection has some issues. When you upgrade field collection from field_collection 7.x-1.0-beta7 to field_collection 7.x-1.0-beta8, field collection add index to field collection fields.So feature will show overridden state. Line 88 Line 88 'cardinality' => -1, 'cardinality' => -1, 'field_name' => 'field_sit_test', 'field_name' => 'field_sit_test', + 'indexes' => array( + 'revision_id' => array( + 0 => 'revision_id', + ), + ), 'module' => 'field_collection', 'module' => 'field_collection', 'settings' => array( 'settings' => array( Solution: Recreate the feature and update. https://www.drupal.org/node/2248943 htt...

http://localhost:81/drupal30/article/node/1.xml http://localhost:81/drupal30/article/node/1.json article => end point node => resource 1=> argument .xml => response format .json => response format example response: {"vid":"1","uid":"1","title":"Test article","log":"","status":"1","comment":"2","promote":"1","sticky":"0","nid":"1","type":"article","language":"und","created":"1406884421","changed":"1406898936","tnid":"0","translate":"0","revision_timestamp":"1406898936","revision_uid":"1","body":{"und":[{"value":"Test article","summary":"","format":"filt...

Global Redirect searches for an alias of the current URL and does a 301 redirects to it if found. This prevents content from being displayed on multiple urls when the path module is enabled. Displaying duplicate content at multiple url's can cause a loss of search engine site ranking Checks the current URL for an alias and does a 301 redirect to it if it is not being used. Checks the current URL for a trailing slash, removes it if present and repeats check 1 with the new request. Checks if the current URL is the same as the site_frontpage and redirects to the frontpage if there is a match. Checks if the Clean URLs feature is enabled and then checks the current URL is being accessed using the clean method rather than the 'unclean' method. Checks access to the URL. If the user does not have access to the path, then no redirects are done. This helps avoid exposing private aliased node's. Make sure the case of the URL being accessed is the same as the one ...

1. my site is at http://www.mainsite.com 2. I want to create a subsite at http://www.mainsite.com/jp 3. I want to maintain the same users, sessions, roles for all my sub sites 4. I want to maintain same database for all my main site and subsites procedure: 1. Back up your database first 2. Rename all your tables to en_tablename (english is one of my site) 3. Rename following tables to shared_tablename (as we are going to share users, sessions, roles, auth common to all sub sites) users, sessions, role, authmap example: shared_users, shared_sessions... 4. Create tables for sub site (you need to create duplicate of all tables with sub site prefix. jp_tablename for example) example: jp_variable 5. create a folder mainsite.com.jp at sites/ folder 6. You can create following sub folders inside mainsite.com.jp/ files/ modules/ themes/ tmp/ You can use default/files folder if you dont want for every sub site. 7. Copy the default/settings.php to sites/mainsite...