ld-6.x-3.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"78eea5c9019d3a6ca7ea53923855b53826bab6edb4a9c7b71f30d4b75c21305c\";s:4:\"size\";s:11:\"98522148391\";s:8:\"filedate\";s:20:\"12942729371294272937\";s:0:\"\";s:0:\"\";}s:13:\"6.x-1.0-beta3\";a:21:{s:4:\"name\";s:23:\"filefield 6.x-1.0-beta3\";s:7:\"version\";s:13:\"6.x-1.0-beta3\";s:3:\"tag\";s:19:\"DRUPAL-6--1-0-BETA3\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/282502\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta3.tar.gz\";s:4:\"date\";s:10:\"1216052708\";s:6:\"mdhash\";s:32:\"16d7dc669271b9ded8d709a03f46a12e\";s:8:\"filesize\";s:5:\"36534\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta3.tar.gzhttp://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"16d7dc669271b9ded8d709a03f46a12edba795c2420cf8ba3145781577d8c975\";s:4:\"size\";s:10:\"3653447710\";s:8:\"filedate\";s:20:\"12160527081293231532\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:13:\"6.x-1.0-beta2\";a:21:{s:4:\"name\";s:23:\"filefield 6.x-1.0-beta2\";s:7:\"version\";s:13:\"6.x-1.0-beta2\";s:3:\"tag\";s:19:\"DRUPAL-6--1-0-BETA2\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/276520\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta2.tar.gz\";s:4:\"date\";s:10:\"1214786709\";s:6:\"mdhash\";s:32:\"337a36de008d2adba4e241700dfc7835\";s:8:\"filesize\";s:5:\"33771\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta2.tar.gzhttp://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"337a36de008d2adba4e241700dfc78357c31625f07129c0b1d3f86827632245f\";s:4:\"size\";s:10:\"3377145006\";s:8:\"filedate\";s:20:\"12147867091293231534\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:13:\"6.x-1.0-beta1\";a:21:{s:4:\"name\";s:23:\"filefield 6.x-1.0-beta1\";s:7:\"version\";s:13:\"6.x-1.0-beta1\";s:3:\"tag\";s:19:\"DRUPAL-6--1-0-BETA1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/276020\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta1.tar.gz\";s:4:\"date\";s:10:\"1214646309\";s:6:\"mdhash\";s:32:\"f55c8088212c8ef790128d672ea63d3c\";s:8:\"filesize\";s:5:\"30229\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta1.tar.gzhttp://ftp.drupal.org/files/projects/filefield-6.x-1.0-beta1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f55c8088212c8ef790128d672ea63d3c70d6fbde2cef47dc9e0f6d850b97ac3c\";s:4:\"size\";s:10:\"3022939591\";s:8:\"filedate\";s:20:\"12146463091293231529\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-1.0-alpha3\";a:21:{s:4:\"name\";s:24:\"filefield 6.x-1.0-alpha3\";s:7:\"version\";s:14:\"6.x-1.0-alpha3\";s:3:\"tag\";s:20:\"DRUPAL-6--1-0-ALPHA3\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/275237\";s:13:\"download_link\";s:68:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha3.tar.gz\";s:4:\"date\";s:10:\"1214484311\";s:6:\"mdhash\";s:32:\"35edea2e3c2d7586c9efe7bde7d89875\";s:8:\"filesize\";s:5:\"28409\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:133:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha3.tar.gzhttp://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"35edea2e3c2d7586c9efe7bde7d898753231c8e2d7f892eea850ca602391d777\";s:4:\"size\";s:10:\"2840937483\";s:8:\"filedate\";s:20:\"12144843111293231532\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:14:\"6.x-1.0-alpha2\";a:21:{s:4:\"name\";s:24:\"filefield 6.x-1.0-alpha2\";s:7:\"version\";s:14:\"6.x-1.0-alpha2\";s:3:\"tag\";s:20:\"DRUPAL-6--1-0-ALPHA2\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/274537\";s:13:\"download_link\";s:68:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha2.tar.gz\";s:4:\"date\";s:10:\"1214353208\";s:6:\"mdhash\";s:32:\"fad99b3ccc10d1c7185e05190c18b2e2\";s:8:\"filesize\";s:5:\"27684\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:133:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha2.tar.gzhttp://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"fad99b3ccc10d1c7185e05190c18b2e2f6daebe74f0e1c6e8d8de8332b3b5d77\";s:4:\"size\";s:10:\"2768436884\";s:8:\"filedate\";s:20:\"12143532081293231534\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-1.0-alpha1\";a:21:{s:4:\"name\";s:24:\"filefield 6.x-1.0-alpha1\";s:7:\"version\";s:14:\"6.x-1.0-alpha1\";s:3:\"tag\";s:20:\"DRUPAL-6--1-0-ALPHA1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/274307\";s:13:\"download_link\";s:68:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha1.tar.gz\";s:4:\"date\";s:10:\"1214320524\";s:6:\"mdhash\";s:32:\"71cd35da51661f17a066f68dc47ab471\";s:8:\"filesize\";s:5:\"26177\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:133:\"http://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha1.tar.gzhttp://ftp.drupal.org/files/projects/filefield-6.x-1.0-alpha1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"71cd35da51661f17a066f68dc47ab471079b2da68710b8213fafd75cfb671476\";s:4:\"size\";s:10:\"2617735314\";s:8:\"filedate\";s:20:\"12143205241293231530\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}}s:14:\"latest_version\";s:7:\"6.x-3.9\";s:11:\"recommended\";s:7:\"6.x-3.9\";s:6:\"status\";i:5;}s:9:\"jquery_ui\";a:23:{s:4:\"name\";s:9:\"jquery_ui\";s:4:\"info\";a:6:{s:4:\"name\";s:9:\"jQuery UI\";s:7:\"package\";s:14:\"User interface\";s:7:\"version\";s:7:\"6.x-1.4\";s:7:\"project\";s:9:\"jquery_ui\";s:9:\"datestamp\";s:10:\"1284001909\";s:16:\"_info_file_ctime\";i:1296890111;}s:9:\"datestamp\";s:10:\"1284001909\";s:8:\"includes\";a:1:{s:9:\"jquery_ui\";s:9:\"jQuery UI\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:7:\"6.x-1.4\";s:14:\"existing_major\";s:1:\"1\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:9:\"jQuery UI\";s:10:\"short_name\";s:9:\"jquery_ui\";s:10:\"dc:creator\";s:3:\"sun\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"1\";s:16:\"supported_majors\";s:1:\"1\";s:13:\"default_major\";s:1:\"1\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:35:\"http://drupal.org/project/jquery_ui\";s:8:\"releases\";a:6:{s:7:\"6.x-1.4\";a:20:{s:4:\"name\";s:17:\"jquery_ui 6.x-1.4\";s:7:\"version\";s:7:\"6.x-1.4\";s:3:\"tag\";s:13:\"DRUPAL-6--1-4\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/906160\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.4.tar.gz\";s:4:\"date\";s:10:\"1284001910\";s:6:\"mdhash\";s:32:\"ce29e1092687c0dc0e18be3879d0bf15\";s:8:\"filesize\";s:5:\"10416\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.4.tar.gzhttp://ftp.drupal.org/files/projects/jquery_ui-6.x-1.4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"ce29e1092687c0dc0e18be3879d0bf15bbd2c4068fb4e97d44312b403962a97f\";s:4:\"size\";s:10:\"1041612298\";s:8:\"filedate\";s:20:\"12840019101293232503\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.3\";a:20:{s:4:\"name\";s:17:\"jquery_ui 6.x-1.3\";s:7:\"version\";s:7:\"6.x-1.3\";s:3:\"tag\";s:13:\"DRUPAL-6--1-3\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/497608\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.3.tar.gz\";s:4:\"date\";s:10:\"1245556234\";s:6:\"mdhash\";s:32:\"af80047e75e0b5e89c0d62a43e29e207\";s:8:\"filesize\";s:4:\"9001\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.3.tar.gzhttp://ftp.drupal.org/files/projects/jquery_ui-6.x-1.3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"af80047e75e0b5e89c0d62a43e29e20760ded06d236ec8a7be06d44269a5c7da\";s:4:\"size\";s:9:\"900110653\";s:8:\"filedate\";s:20:\"12455562341293232502\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.2\";a:20:{s:4:\"name\";s:17:\"jquery_ui 6.x-1.2\";s:7:\"version\";s:7:\"6.x-1.2\";s:3:\"tag\";s:13:\"DRUPAL-6--1-2\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/274037\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.2.tar.gz\";s:4:\"date\";s:10:\"1214264715\";s:6:\"mdhash\";s:32:\"996e5e48017bd0d1d80949100cf6494d\";s:8:\"filesize\";s:4:\"8605\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.2.tar.gzhttp://ftp.drupal.org/files/projects/jquery_ui-6.x-1.2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"996e5e48017bd0d1d80949100cf6494d8b92f665aa6dcf67311afc8dd54dadfd\";s:4:\"size\";s:9:\"860510106\";s:8:\"filedate\";s:20:\"12142647151293232502\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.1\";a:20:{s:4:\"name\";s:17:\"jquery_ui 6.x-1.1\";s:7:\"version\";s:7:\"6.x-1.1\";s:3:\"tag\";s:13:\"DRUPAL-6--1-1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/263362\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.1.tar.gz\";s:4:\"date\";s:10:\"1211910015\";s:6:\"mdhash\";s:32:\"e3683abf5ea065988bdc090be3a0ae0f\";s:8:\"filesize\";s:4:\"8788\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.1.tar.gzhttp://ftp.drupal.org/files/projects/jquery_ui-6.x-1.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"e3683abf5ea065988bdc090be3a0ae0f96d2f8a4214320db8068b561b2234bfc\";s:4:\"size\";s:9:\"878810143\";s:8:\"filedate\";s:20:\"12119100151293232502\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.0\";a:17:{s:4:\"name\";s:17:\"jquery_ui 6.x-1.0\";s:7:\"version\";s:7:\"6.x-1.0\";s:3:\"tag\";s:13:\"DRUPAL-6--1-0\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1211855711\";s:6:\"mdhash\";s:32:\"8d1ee270a67ee80ab0c6a146d5449300\";s:8:\"filesize\";s:4:\"8765\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"8d1ee270a67ee80ab0c6a146d5449300\";s:4:\"size\";s:4:\"8765\";s:8:\"filedate\";s:10:\"1211855711\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:11:\"6.x-1.x-dev\";a:19:{s:4:\"name\";s:21:\"jquery_ui 6.x-1.x-dev\";s:7:\"version\";s:11:\"6.x-1.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/270704\";s:13:\"download_link\";s:65:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.x-dev.tar.gz\";s:4:\"date\";s:10:\"1289434353\";s:6:\"mdhash\";s:32:\"e56db64c85824686814945e3a9e9c244\";s:8:\"filesize\";s:5:\"11801\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:127:\"http://ftp.drupal.org/files/projects/jquery_ui-6.x-1.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/jquery_ui-6.x-1.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"e56db64c85824686814945e3a9e9c244bccaaf4a403621905630f85681befe77\";s:4:\"size\";s:10:\"1180115016\";s:8:\"filedate\";s:20:\"12894343531293250707\";s:0:\"\";s:0:\"\";}}s:14:\"latest_version\";s:7:\"6.x-1.4\";s:11:\"recommended\";s:7:\"6.x-1.4\";s:6:\"status\";i:5;}s:13:\"jquery_update\";a:24:{s:4:\"name\";s:13:\"jquery_update\";s:4:\"info\";a:6:{s:4:\"name\";s:13:\"jQuery Update\";s:7:\"package\";s:14:\"User Interface\";s:7:\"version\";s:7:\"6.x-1.1\";s:7:\"project\";s:13:\"jquery_update\";s:9:\"datestamp\";s:10:\"1214262616\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1214262616\";s:8:\"includes\";a:1:{s:13:\"jquery_update\";s:13:\"jQuery Update\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:7:\"6.x-1.1\";s:14:\"existing_major\";s:1:\"1\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:13:\"jQuery Update\";s:10:\"short_name\";s:13:\"jquery_update\";s:10:\"dc:creator\";s:5:\"jjeff\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"1\";s:16:\"supported_majors\";s:3:\"1,2\";s:13:\"default_major\";s:1:\"1\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:39:\"http://drupal.org/project/jquery_update\";s:8:\"releases\";a:5:{s:14:\"6.x-2.0-alpha1\";a:21:{s:4:\"name\";s:28:\"jquery_update 6.x-2.0-alpha1\";s:7:\"version\";s:14:\"6.x-2.0-alpha1\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/779956\";s:13:\"download_link\";s:72:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-2.0-alpha1.tar.gz\";s:4:\"date\";s:10:\"1272041111\";s:6:\"mdhash\";s:32:\"d10b6a09a2ed73bd342cc6104ed7f873\";s:8:\"filesize\";s:5:\"83646\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:141:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-2.0-alpha1.tar.gzhttp://ftp.drupal.org/files/projects/jquery_update-6.x-2.0-alpha1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"d10b6a09a2ed73bd342cc6104ed7f87343fa1641a82ba2b3cb16d9f507891e84\";s:4:\"size\";s:10:\"8364688006\";s:8:\"filedate\";s:20:\"12720411111293232507\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:11:\"6.x-2.x-dev\";a:20:{s:4:\"name\";s:25:\"jquery_update 6.x-2.x-dev\";s:7:\"version\";s:11:\"6.x-2.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/409588\";s:13:\"download_link\";s:69:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-2.x-dev.tar.gz\";s:4:\"date\";s:10:\"1284034331\";s:6:\"mdhash\";s:32:\"4db310b424a87d09e6fd721b3ea15a98\";s:8:\"filesize\";s:5:\"83770\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:135:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-2.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/jquery_update-6.x-2.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"4db310b424a87d09e6fd721b3ea15a98d94f8d965a9a4e8e2d2e28bfc4120a06\";s:4:\"size\";s:10:\"8377088117\";s:8:\"filedate\";s:20:\"12840343311293250708\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:7:\"6.x-1.1\";a:20:{s:4:\"name\";s:21:\"jquery_update 6.x-1.1\";s:7:\"version\";s:7:\"6.x-1.1\";s:3:\"tag\";s:13:\"DRUPAL-6--1-1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/274023\";s:13:\"download_link\";s:65:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-1.1.tar.gz\";s:4:\"date\";s:10:\"1214262616\";s:6:\"mdhash\";s:32:\"9cd3cb3977513fa21ef7ab47263e6224\";s:8:\"filesize\";s:5:\"74807\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:127:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-1.1.tar.gzhttp://ftp.drupal.org/files/projects/jquery_update-6.x-1.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"9cd3cb3977513fa21ef7ab47263e622418cc7e88538fb282f6862aed7e76ffbc\";s:4:\"size\";s:10:\"7480777859\";s:8:\"filedate\";s:20:\"12142626161293232507\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:7:\"6.x-1.0\";a:19:{s:4:\"name\";s:21:\"jquery_update 6.x-1.0\";s:7:\"version\";s:7:\"6.x-1.0\";s:3:\"tag\";s:13:\"DRUPAL-6--1-0\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/263065\";s:13:\"download_link\";s:65:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-1.0.tar.gz\";s:4:\"date\";s:10:\"1211856011\";s:6:\"mdhash\";s:32:\"ead5c2fb7cf73d45197b96e678356f81\";s:8:\"filesize\";s:5:\"37777\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:127:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-1.0.tar.gzhttp://ftp.drupal.org/files/projects/jquery_update-6.x-1.0.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"ead5c2fb7cf73d45197b96e678356f81587fedb7e88212402629b02daa5c9d9b\";s:4:\"size\";s:10:\"3777739405\";s:8:\"filedate\";s:20:\"12118560111293232507\";s:0:\"\";s:0:\"\";}s:11:\"6.x-1.x-dev\";a:19:{s:4:\"name\";s:25:\"jquery_update 6.x-1.x-dev\";s:7:\"version\";s:11:\"6.x-1.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/270693\";s:13:\"download_link\";s:69:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-1.x-dev.tar.gz\";s:4:\"date\";s:10:\"1278834678\";s:6:\"mdhash\";s:32:\"682349b9b6d0d4a118d74b4012af8a7f\";s:8:\"filesize\";s:5:\"74795\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:135:\"http://ftp.drupal.org/files/projects/jquery_update-6.x-1.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/jquery_update-6.x-1.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"682349b9b6d0d4a118d74b4012af8a7f82702b9be93cab617b535a5f1b242aa3\";s:4:\"size\";s:10:\"7479578324\";s:8:\"filedate\";s:20:\"12788346781293250708\";s:0:\"\";s:0:\"\";}}s:4:\"also\";a:1:{i:2;s:14:\"6.x-2.0-alpha1\";}s:14:\"latest_version\";s:7:\"6.x-1.1\";s:11:\"recommended\";s:7:\"6.x-1.1\";s:6:\"status\";i:5;}s:4:\"link\";a:23:{s:4:\"name\";s:4:\"link\";s:4:\"info\";a:6:{s:4:\"name\";s:4:\"Link\";s:7:\"package\";s:3:\"CCK\";s:7:\"version\";s:7:\"6.x-2.9\";s:7:\"project\";s:4:\"link\";s:9:\"datestamp\";s:10:\"1276539609\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1276539609\";s:8:\"includes\";a:1:{s:4:\"link\";s:4:\"Link\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:7:\"6.x-2.9\";s:14:\"existing_major\";s:1:\"2\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:4:\"Link\";s:10:\"short_name\";s:4:\"link\";s:10:\"dc:creator\";s:7:\"jcfiala\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"2\";s:16:\"supported_majors\";s:1:\"2\";s:13:\"default_major\";s:1:\"2\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:30:\"http://drupal.org/project/link\";s:8:\"releases\";a:18:{s:7:\"6.x-2.9\";a:20:{s:4:\"name\";s:12:\"link 6.x-2.9\";s:7:\"version\";s:7:\"6.x-2.9\";s:3:\"tag\";s:13:\"DRUPAL-6--2-9\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"9\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/827200\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/link-6.x-2.9.tar.gz\";s:4:\"date\";s:10:\"1276539609\";s:6:\"mdhash\";s:32:\"4ded032cae71f43174f70f70ecd57471\";s:8:\"filesize\";s:5:\"40597\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/link-6.x-2.9.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.9.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"4ded032cae71f43174f70f70ecd57471c7e38ec16194e3121352670f715ac71e\";s:4:\"size\";s:10:\"4059757572\";s:8:\"filedate\";s:20:\"12765396091293232641\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.8\";a:20:{s:4:\"name\";s:12:\"link 6.x-2.8\";s:7:\"version\";s:7:\"6.x-2.8\";s:3:\"tag\";s:13:\"DRUPAL-6--2-8\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"8\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/623932\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/link-6.x-2.8.tar.gz\";s:4:\"date\";s:10:\"1257394550\";s:6:\"mdhash\";s:32:\"54bf94310938c8000eb80c22464ba2d8\";s:8:\"filesize\";s:5:\"24911\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/link-6.x-2.8.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.8.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"54bf94310938c8000eb80c22464ba2d8df91dc6cf5bf83e91e21dd728f76dc9b\";s:4:\"size\";s:10:\"2491135180\";s:8:\"filedate\";s:20:\"12573945501293232639\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.7\";a:20:{s:4:\"name\";s:12:\"link 6.x-2.7\";s:7:\"version\";s:7:\"6.x-2.7\";s:3:\"tag\";s:13:\"DRUPAL-6--2-7\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"7\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/620668\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/link-6.x-2.7.tar.gz\";s:4:\"date\";s:10:\"1257135943\";s:6:\"mdhash\";s:32:\"960d3e01365529c1fcae95039e9e7dc9\";s:8:\"filesize\";s:5:\"24902\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/link-6.x-2.7.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.7.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"960d3e01365529c1fcae95039e9e7dc924552e3a024aee4e02f56b56c20e247a\";s:4:\"size\";s:10:\"2490235177\";s:8:\"filedate\";s:20:\"12571359431293232641\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:15:\"Security update\";}}}s:7:\"6.x-2.6\";a:20:{s:4:\"name\";s:12:\"link 6.x-2.6\";s:7:\"version\";s:7:\"6.x-2.6\";s:3:\"tag\";s:13:\"DRUPAL-6--2-6\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"6\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/512554\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/link-6.x-2.6.tar.gz\";s:4:\"date\";s:10:\"1246976471\";s:6:\"mdhash\";s:32:\"e9dbc3209f93f78ec14dd8a48c5fb8d6\";s:8:\"filesize\";s:5:\"22630\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/link-6.x-2.6.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.6.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"e9dbc3209f93f78ec14dd8a48c5fb8d6a770f3694d6a42f70b30793e410118f2\";s:4:\"size\";s:10:\"2263030599\";s:8:\"filedate\";s:20:\"12469764711293232640\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:13:\"6.x-2.6-beta3\";a:21:{s:4:\"name\";s:18:\"link 6.x-2.6-beta3\";s:7:\"version\";s:13:\"6.x-2.6-beta3\";s:3:\"tag\";s:19:\"DRUPAL-6--2-6-BETA3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"6\";s:13:\"version_extra\";s:5:\"beta3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/510266\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/link-6.x-2.6-beta3.tar.gz\";s:4:\"date\";s:10:\"1246734941\";s:6:\"mdhash\";s:32:\"16ad8ed0d366777bbaf02195dee4f010\";s:8:\"filesize\";s:5:\"22631\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/link-6.x-2.6-beta3.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.6-beta3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"16ad8ed0d366777bbaf02195dee4f0104d1b70539d38904fe43cde887fe91f66\";s:4:\"size\";s:10:\"2263130605\";s:8:\"filedate\";s:20:\"12467349411293232642\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.6-beta2\";a:21:{s:4:\"name\";s:18:\"link 6.x-2.6-beta2\";s:7:\"version\";s:13:\"6.x-2.6-beta2\";s:3:\"tag\";s:19:\"DRUPAL-6--2-6-BETA2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"6\";s:13:\"version_extra\";s:5:\"beta2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/507690\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/link-6.x-2.6-beta2.tar.gz\";s:4:\"date\";s:10:\"1246488355\";s:6:\"mdhash\";s:32:\"76db909e8b2621c9377bfd7060ba339a\";s:8:\"filesize\";s:5:\"23690\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/link-6.x-2.6-beta2.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.6-beta2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"76db909e8b2621c9377bfd7060ba339ae2ec80a3b9d2a662387d986afe7af9b8\";s:4:\"size\";s:10:\"2369031368\";s:8:\"filedate\";s:20:\"12464883551293232637\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.6-beta1\";a:21:{s:4:\"name\";s:18:\"link 6.x-2.6-beta1\";s:7:\"version\";s:13:\"6.x-2.6-beta1\";s:3:\"tag\";s:19:\"DRUPAL-6--2-6-BETA1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"6\";s:13:\"version_extra\";s:5:\"beta1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/438778\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/link-6.x-2.6-beta1.tar.gz\";s:4:\"date\";s:10:\"1240201545\";s:6:\"mdhash\";s:32:\"5c7795e16074a0368a50a454eba9ec7c\";s:8:\"filesize\";s:5:\"22117\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/link-6.x-2.6-beta1.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.6-beta1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"5c7795e16074a0368a50a454eba9ec7c9f3fff4e13f86172b8070996a5f1ec17\";s:4:\"size\";s:10:\"2211730003\";s:8:\"filedate\";s:20:\"12402015451293232640\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.5\";a:20:{s:4:\"name\";s:12:\"link 6.x-2.5\";s:7:\"version\";s:7:\"6.x-2.5\";s:3:\"tag\";s:13:\"DRUPAL-6--2-5\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"5\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/311640\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/link-6.x-2.5.tar.gz\";s:4:\"date\";s:10:\"1222062031\";s:6:\"mdhash\";s:32:\"152beeb2451a532e2f7123ba10cb1866\";s:8:\"filesize\";s:5:\"26255\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/link-6.x-2.5.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.5.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"152beeb2451a532e2f7123ba10cb18661e56b435a5e27c91d497f3f45f5bb854\";s:4:\"size\";s:10:\"2625537043\";s:8:\"filedate\";s:20:\"12220620311293232637\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.4\";a:20:{s:4:\"name\";s:12:\"link 6.x-2.4\";s:7:\"version\";s:7:\"6.x-2.4\";s:3:\"tag\";s:13:\"DRUPAL-6--2-4\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/311636\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/link-6.x-2.4.tar.gz\";s:4:\"date\";s:10:\"1222061435\";s:6:\"mdhash\";s:32:\"e038edae40617ed573c3cefb10caac3f\";s:8:\"filesize\";s:5:\"21682\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/link-6.x-2.4.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"e038edae40617ed573c3cefb10caac3f474ec3172a76e53bb1364b711dfeb52c\";s:4:\"size\";s:10:\"2168229417\";s:8:\"filedate\";s:20:\"12220614351293232640\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.3\";a:20:{s:4:\"name\";s:12:\"link 6.x-2.3\";s:7:\"version\";s:7:\"6.x-2.3\";s:3:\"tag\";s:13:\"DRUPAL-6--2-3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/276477\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/link-6.x-2.3.tar.gz\";s:4:\"date\";s:10:\"1214777711\";s:6:\"mdhash\";s:32:\"3fb0a05406086be6a1b65f320d431f34\";s:8:\"filesize\";s:5:\"20495\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/link-6.x-2.3.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"3fb0a05406086be6a1b65f320d431f347e163e6627ce422e477d233f1685814a\";s:4:\"size\";s:10:\"2049526258\";s:8:\"filedate\";s:20:\"12147777111293232638\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:9:\"6.x-2.3.1\";a:21:{s:4:\"name\";s:14:\"link 6.x-2.3.1\";s:7:\"version\";s:9:\"6.x-2.3.1\";s:3:\"tag\";s:15:\"DRUPAL-6--2-3-1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"3\";s:13:\"version_extra\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/284503\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/link-6.x-2.3.1.tar.gz\";s:4:\"date\";s:10:\"1216417210\";s:6:\"mdhash\";s:32:\"51be611f4b6325f0e62ae8da61a22fbc\";s:8:\"filesize\";s:5:\"20500\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/link-6.x-2.3.1.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.3.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"51be611f4b6325f0e62ae8da61a22fbcca8b6a47450e7c5d053719a8e436ee46\";s:4:\"size\";s:10:\"2050026261\";s:8:\"filedate\";s:20:\"12164172101293232640\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.2\";a:20:{s:4:\"name\";s:12:\"link 6.x-2.2\";s:7:\"version\";s:7:\"6.x-2.2\";s:3:\"tag\";s:13:\"DRUPAL-6--2-2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/267399\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/link-6.x-2.2.tar.gz\";s:4:\"date\";s:10:\"1212735317\";s:6:\"mdhash\";s:32:\"8856fc24bacd5198cffd46061541473b\";s:8:\"filesize\";s:5:\"18792\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/link-6.x-2.2.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"8856fc24bacd5198cffd46061541473becbe4bc7fc32affeeca9f3ca44c8c21f\";s:4:\"size\";s:10:\"1879223257\";s:8:\"filedate\";s:20:\"12127353171293232636\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.1-beta4\";a:21:{s:4:\"name\";s:18:\"link 6.x-2.1-beta4\";s:7:\"version\";s:13:\"6.x-2.1-beta4\";s:3:\"tag\";s:19:\"DRUPAL-6--2-1-beta4\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"1\";s:13:\"version_extra\";s:5:\"beta4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/249022\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/link-6.x-2.1-beta4.tar.gz\";s:4:\"date\";s:10:\"1208720713\";s:6:\"mdhash\";s:32:\"87ffef5ddba6eb90f4fdd2d135399358\";s:8:\"filesize\";s:5:\"16750\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/link-6.x-2.1-beta4.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.1-beta4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"87ffef5ddba6eb90f4fdd2d13539935839f46e0e9b1b428ade7224cc21e00110\";s:4:\"size\";s:10:\"1675020579\";s:8:\"filedate\";s:20:\"12087207131293232638\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.1-beta3\";a:21:{s:4:\"name\";s:18:\"link 6.x-2.1-beta3\";s:7:\"version\";s:13:\"6.x-2.1-beta3\";s:3:\"tag\";s:19:\"DRUPAL-6--2-1-beta3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"1\";s:13:\"version_extra\";s:5:\"beta3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/240740\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/link-6.x-2.1-beta3.tar.gz\";s:4:\"date\";s:10:\"1206952509\";s:6:\"mdhash\";s:32:\"26cbeb74c30390dba9dd3c97cf83166a\";s:8:\"filesize\";s:5:\"16777\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/link-6.x-2.1-beta3.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.1-beta3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"26cbeb74c30390dba9dd3c97cf83166ac9a3e01d5dab4c00462438dfce896d75\";s:4:\"size\";s:10:\"1677720618\";s:8:\"filedate\";s:20:\"12069525091293232640\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.1-beta2\";a:20:{s:4:\"name\";s:18:\"link 6.x-2.1-beta2\";s:7:\"version\";s:13:\"6.x-2.1-beta2\";s:3:\"tag\";s:19:\"DRUPAL-6--2-1-beta2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"1\";s:13:\"version_extra\";s:5:\"beta2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/240739\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/link-6.x-2.1-beta2.tar.gz\";s:4:\"date\";s:10:\"1206952509\";s:6:\"mdhash\";s:32:\"f34f19c3e9d862705d61e4cc1905ffd6\";s:8:\"filesize\";s:5:\"16786\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/link-6.x-2.1-beta2.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.1-beta2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f34f19c3e9d862705d61e4cc1905ffd62c2e54c206a3304df41c9b21f0a4e5ca\";s:4:\"size\";s:10:\"1678620623\";s:8:\"filedate\";s:20:\"12069525091293232636\";s:0:\"\";s:0:\"\";}s:13:\"6.x-2.1-beta1\";a:21:{s:4:\"name\";s:18:\"link 6.x-2.1-beta1\";s:7:\"version\";s:13:\"6.x-2.1-beta1\";s:3:\"tag\";s:19:\"DRUPAL-6--2-1-beta1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"1\";s:13:\"version_extra\";s:5:\"beta1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/240723\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/link-6.x-2.1-beta1.tar.gz\";s:4:\"date\";s:10:\"1206946811\";s:6:\"mdhash\";s:32:\"b2f0d3de0b8135053d8559d36dd41ff7\";s:8:\"filesize\";s:5:\"16773\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/link-6.x-2.1-beta1.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.1-beta1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"b2f0d3de0b8135053d8559d36dd41ff7e538bfb02894c6410f16a317929aa502\";s:4:\"size\";s:10:\"1677320625\";s:8:\"filedate\";s:20:\"12069468111293232638\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:11:\"6.x-2.x-dev\";a:19:{s:4:\"name\";s:16:\"link 6.x-2.x-dev\";s:7:\"version\";s:11:\"6.x-2.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/580990\";s:13:\"download_link\";s:60:\"http://ftp.drupal.org/files/projects/link-6.x-2.x-dev.tar.gz\";s:4:\"date\";s:10:\"1286842334\";s:6:\"mdhash\";s:32:\"52debba6190f7e58e1fdf74bd41582ec\";s:8:\"filesize\";s:5:\"40752\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:117:\"http://ftp.drupal.org/files/projects/link-6.x-2.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-2.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"52debba6190f7e58e1fdf74bd41582ec5808cc6a4cc269e3c706e9a4dea76f69\";s:4:\"size\";s:10:\"4075259137\";s:8:\"filedate\";s:20:\"12868423341293250746\";s:0:\"\";s:0:\"\";}s:11:\"6.x-1.x-dev\";a:19:{s:4:\"name\";s:16:\"link 6.x-1.x-dev\";s:7:\"version\";s:11:\"6.x-1.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/240722\";s:13:\"download_link\";s:60:\"http://ftp.drupal.org/files/projects/link-6.x-1.x-dev.tar.gz\";s:4:\"date\";s:10:\"1278834740\";s:6:\"mdhash\";s:32:\"928e74fb61f369ab6ec4a4a72c1302bb\";s:8:\"filesize\";s:5:\"23692\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:117:\"http://ftp.drupal.org/files/projects/link-6.x-1.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/link-6.x-1.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"928e74fb61f369ab6ec4a4a72c1302bbd52cd3a481f1e4be874b5a8a1f9d3469\";s:4:\"size\";s:10:\"2369231366\";s:8:\"filedate\";s:20:\"12788347401293250746\";s:0:\"\";s:0:\"\";}}s:14:\"latest_version\";s:7:\"6.x-2.9\";s:11:\"recommended\";s:7:\"6.x-2.9\";s:6:\"status\";i:5;}s:12:\"mobileplugin\";a:23:{s:4:\"name\";s:12:\"mobileplugin\";s:4:\"info\";a:6:{s:4:\"name\";s:13:\"Mobile Plugin\";s:7:\"package\";s:6:\"Mobile\";s:7:\"version\";s:7:\"6.x-2.0\";s:7:\"project\";s:12:\"mobileplugin\";s:9:\"datestamp\";s:10:\"1264526408\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1264526408\";s:8:\"includes\";a:1:{s:12:\"mobileplugin\";s:13:\"Mobile Plugin\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:7:\"6.x-2.0\";s:14:\"existing_major\";s:1:\"2\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:13:\"Mobile Plugin\";s:10:\"short_name\";s:12:\"mobileplugin\";s:10:\"dc:creator\";s:7:\"teemule\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"2\";s:16:\"supported_majors\";s:3:\"1,2\";s:13:\"default_major\";s:1:\"1\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:38:\"http://drupal.org/project/mobileplugin\";s:8:\"releases\";a:3:{s:7:\"6.x-2.0\";a:20:{s:4:\"name\";s:20:\"mobileplugin 6.x-2.0\";s:7:\"version\";s:7:\"6.x-2.0\";s:3:\"tag\";s:13:\"DRUPAL-6--2-0\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/695978\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/mobileplugin-6.x-2.0.tar.gz\";s:4:\"date\";s:10:\"1264526408\";s:6:\"mdhash\";s:32:\"0e1c0ca84b3b2d06008564b97d16e89f\";s:8:\"filesize\";s:5:\"24770\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/mobileplugin-6.x-2.0.tar.gzhttp://ftp.drupal.org/files/projects/mobileplugin-6.x-2.0.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"0e1c0ca84b3b2d06008564b97d16e89fbe1a8d1c467a27dd91566069b615baa0\";s:4:\"size\";s:10:\"2477028672\";s:8:\"filedate\";s:20:\"12645264081293232990\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:7:\"6.x-1.1\";a:20:{s:4:\"name\";s:20:\"mobileplugin 6.x-1.1\";s:7:\"version\";s:7:\"6.x-1.1\";s:3:\"tag\";s:13:\"DRUPAL-6--1-1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/473156\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/mobileplugin-6.x-1.1.tar.gz\";s:4:\"date\";s:10:\"1243343466\";s:6:\"mdhash\";s:32:\"c63ac042b00e102586ae58d1f277c3d0\";s:8:\"filesize\";s:6:\"780994\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/mobileplugin-6.x-1.1.tar.gzhttp://ftp.drupal.org/files/projects/mobileplugin-6.x-1.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"c63ac042b00e102586ae58d1f277c3d0bf3e5f61e0c4e0d3b3a09c38e2b14ea1\";s:4:\"size\";s:12:\"780994914565\";s:8:\"filedate\";s:20:\"12433434661293232995\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.0\";a:20:{s:4:\"name\";s:20:\"mobileplugin 6.x-1.0\";s:7:\"version\";s:7:\"6.x-1.0\";s:3:\"tag\";s:13:\"DRUPAL-6--1-0\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/472316\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/mobileplugin-6.x-1.0.tar.gz\";s:4:\"date\";s:10:\"1243268622\";s:6:\"mdhash\";s:32:\"b409347ab2065cc5a94e7b47e2783897\";s:8:\"filesize\";s:6:\"781038\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/mobileplugin-6.x-1.0.tar.gzhttp://ftp.drupal.org/files/projects/mobileplugin-6.x-1.0.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"b409347ab2065cc5a94e7b47e2783897dee1530e1f9f7fdaff0a1f64bb9a40f2\";s:4:\"size\";s:12:\"781038914646\";s:8:\"filedate\";s:20:\"12432686221293232991\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}}s:14:\"latest_version\";s:7:\"6.x-2.0\";s:11:\"recommended\";s:7:\"6.x-2.0\";s:6:\"status\";i:5;}s:10:\"multiblock\";a:23:{s:4:\"name\";s:10:\"multiblock\";s:4:\"info\";a:5:{s:4:\"name\";s:10:\"MultiBlock\";s:7:\"version\";s:7:\"6.x-1.3\";s:7:\"project\";s:10:\"multiblock\";s:9:\"datestamp\";s:10:\"1233076829\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1233076829\";s:8:\"includes\";a:1:{s:10:\"multiblock\";s:10:\"MultiBlock\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:7:\"6.x-1.3\";s:14:\"existing_major\";s:1:\"1\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:10:\"MultiBlock\";s:10:\"short_name\";s:10:\"multiblock\";s:10:\"dc:creator\";s:12:\"andrewlevine\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"1\";s:16:\"supported_majors\";s:1:\"1\";s:13:\"default_major\";s:1:\"1\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:36:\"http://drupal.org/project/multiblock\";s:8:\"releases\";a:4:{s:7:\"6.x-1.3\";a:20:{s:4:\"name\";s:18:\"multiblock 6.x-1.3\";s:7:\"version\";s:7:\"6.x-1.3\";s:3:\"tag\";s:13:\"DRUPAL-6--1-3\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/365059\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/multiblock-6.x-1.3.tar.gz\";s:4:\"date\";s:10:\"1233076829\";s:6:\"mdhash\";s:32:\"b4005140c80a1c7fb066686c2f9e49f7\";s:8:\"filesize\";s:5:\"11846\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/multiblock-6.x-1.3.tar.gzhttp://ftp.drupal.org/files/projects/multiblock-6.x-1.3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"b4005140c80a1c7fb066686c2f9e49f7119428b8e8a827a48ddcd5de60345223\";s:4:\"size\";s:10:\"1184613663\";s:8:\"filedate\";s:20:\"12330768291293233053\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.2\";a:20:{s:4:\"name\";s:18:\"multiblock 6.x-1.2\";s:7:\"version\";s:7:\"6.x-1.2\";s:3:\"tag\";s:13:\"DRUPAL-6--1-2\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/363830\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/multiblock-6.x-1.2.tar.gz\";s:4:\"date\";s:10:\"1232864728\";s:6:\"mdhash\";s:32:\"bc955f59b13982771becaa6cbb592aab\";s:8:\"filesize\";s:5:\"11836\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/multiblock-6.x-1.2.tar.gzhttp://ftp.drupal.org/files/projects/multiblock-6.x-1.2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"bc955f59b13982771becaa6cbb592aab818b512db4c0ed1b8d402f5c9b5f06b1\";s:4:\"size\";s:10:\"1183613665\";s:8:\"filedate\";s:20:\"12328647281293233052\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.1\";a:20:{s:4:\"name\";s:18:\"multiblock 6.x-1.1\";s:7:\"version\";s:7:\"6.x-1.1\";s:3:\"tag\";s:13:\"DRUPAL-6--1-1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/274042\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/multiblock-6.x-1.1.tar.gz\";s:4:\"date\";s:10:\"1214266810\";s:6:\"mdhash\";s:32:\"7463be3af5980fe208f07a9551657da4\";s:8:\"filesize\";s:5:\"10346\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/multiblock-6.x-1.1.tar.gzhttp://ftp.drupal.org/files/projects/multiblock-6.x-1.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"7463be3af5980fe208f07a9551657da4c54bb2b1a83a52a2fa504dd03192a591\";s:4:\"size\";s:10:\"1034611617\";s:8:\"filedate\";s:20:\"12142668101293233051\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:11:\"6.x-1.x-dev\";a:20:{s:4:\"name\";s:22:\"multiblock 6.x-1.x-dev\";s:7:\"version\";s:11:\"6.x-1.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/353802\";s:13:\"download_link\";s:66:\"http://ftp.drupal.org/files/projects/multiblock-6.x-1.x-dev.tar.gz\";s:4:\"date\";s:10:\"1278834938\";s:6:\"mdhash\";s:32:\"a4f74408ded7a75af69e98e46af8ebc1\";s:8:\"filesize\";s:5:\"12760\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:129:\"http://ftp.drupal.org/files/projects/multiblock-6.x-1.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/multiblock-6.x-1.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"a4f74408ded7a75af69e98e46af8ebc135d0ea55be49c76d9f1dad0746501ed9\";s:4:\"size\";s:10:\"1276015482\";s:8:\"filedate\";s:20:\"12788349381293250862\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}}s:14:\"latest_version\";s:7:\"6.x-1.3\";s:11:\"recommended\";s:7:\"6.x-1.3\";s:6:\"status\";i:5;}s:6:\"panels\";a:23:{s:4:\"name\";s:6:\"panels\";s:4:\"info\";a:6:{s:4:\"name\";s:6:\"Panels\";s:7:\"package\";s:6:\"Panels\";s:7:\"version\";s:7:\"6.x-3.9\";s:7:\"project\";s:6:\"panels\";s:9:\"datestamp\";s:10:\"1294876603\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1294876603\";s:8:\"includes\";a:4:{s:6:\"panels\";s:6:\"Panels\";s:10:\"panels_ipe\";s:22:\"Panels In-Place Editor\";s:11:\"panels_mini\";s:11:\"Mini panels\";s:11:\"panels_node\";s:11:\"Panel nodes\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:7:\"6.x-3.9\";s:14:\"existing_major\";s:1:\"3\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:6:\"Panels\";s:10:\"short_name\";s:6:\"panels\";s:10:\"dc:creator\";s:13:\"merlinofchaos\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"3\";s:16:\"supported_majors\";s:1:\"3\";s:13:\"default_major\";s:1:\"3\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:32:\"http://drupal.org/project/panels\";s:8:\"releases\";a:22:{s:7:\"6.x-3.9\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.9\";s:7:\"version\";s:7:\"6.x-3.9\";s:3:\"tag\";s:13:\"DRUPAL-6--3-9\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"9\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:30:\"http://drupal.org/node/1024918\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.9.tar.gz\";s:4:\"date\";s:10:\"1294876604\";s:6:\"mdhash\";s:32:\"d3ef48d1a615eb044267d9fb0013086f\";s:8:\"filesize\";s:6:\"398072\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.9.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.9.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"d3ef48d1a615eb044267d9fb0013086f1f32debc6a959c498639911beb3dd588\";s:4:\"size\";s:12:\"398072486342\";s:8:\"filedate\";s:20:\"12948766041294876604\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:9:\"Bug fixes\";i:1;s:15:\"Security update\";}}}s:7:\"6.x-3.8\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.8\";s:7:\"version\";s:7:\"6.x-3.8\";s:3:\"tag\";s:13:\"DRUPAL-6--3-8\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"8\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/957374\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.8.tar.gz\";s:4:\"date\";s:10:\"1288393847\";s:6:\"mdhash\";s:32:\"c0665430d5c5dda1b7080e174d1debad\";s:8:\"filesize\";s:6:\"397936\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.8.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.8.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"c0665430d5c5dda1b7080e174d1debad43fbc19a34627734d55305ab6ec61dc9\";s:4:\"size\";s:12:\"397936482146\";s:8:\"filedate\";s:20:\"12883938471293233707\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-3.7\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.7\";s:7:\"version\";s:7:\"6.x-3.7\";s:3:\"tag\";s:13:\"DRUPAL-6--3-7\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"7\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/865584\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.7.tar.gz\";s:4:\"date\";s:10:\"1280189119\";s:6:\"mdhash\";s:32:\"e3a45d1e4085e4dc7736f20de9d209f7\";s:8:\"filesize\";s:6:\"382477\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.7.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.7.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"e3a45d1e4085e4dc7736f20de9d209f7b6c0525810dc5207ba61216dec96829c\";s:4:\"size\";s:12:\"382477463206\";s:8:\"filedate\";s:20:\"12801891191293233702\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-3.5\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.5\";s:7:\"version\";s:7:\"6.x-3.5\";s:3:\"tag\";s:13:\"DRUPAL-6--3-5\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"5\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/812452\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.5.tar.gz\";s:4:\"date\";s:10:\"1275094509\";s:6:\"mdhash\";s:32:\"f713545b0a818271a43ffc10c9e192bd\";s:8:\"filesize\";s:6:\"348703\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.5.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.5.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f713545b0a818271a43ffc10c9e192bdc3aa4e5812bfcb50e1a931742656220e\";s:4:\"size\";s:12:\"348703418312\";s:8:\"filedate\";s:20:\"12750945091293233709\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-3.4\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.4\";s:7:\"version\";s:7:\"6.x-3.4\";s:3:\"tag\";s:13:\"DRUPAL-6--3-4\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/803916\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.4.tar.gz\";s:4:\"date\";s:10:\"1274320813\";s:6:\"mdhash\";s:32:\"6fc2170843269a05f65bc22155aa0d97\";s:8:\"filesize\";s:6:\"372024\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.4.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"6fc2170843269a05f65bc22155aa0d976b3abefe82b43c1d4b3506b6a9178c05\";s:4:\"size\";s:12:\"372024443420\";s:8:\"filedate\";s:20:\"12743208131293233715\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:3:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";i:2;s:15:\"Security update\";}}}s:7:\"6.x-3.3\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.3\";s:7:\"version\";s:7:\"6.x-3.3\";s:3:\"tag\";s:13:\"DRUPAL-6--3-3\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/701812\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.3.tar.gz\";s:4:\"date\";s:10:\"1265065814\";s:6:\"mdhash\";s:32:\"46285850574246604750def846433e05\";s:8:\"filesize\";s:6:\"348175\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.3.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"46285850574246604750def846433e0534a3c3587e26cc09bc8c543adb3751d6\";s:4:\"size\";s:12:\"348175394570\";s:8:\"filedate\";s:20:\"12650658141293233703\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-3.2\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.2\";s:7:\"version\";s:7:\"6.x-3.2\";s:3:\"tag\";s:13:\"DRUPAL-6--3-2\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/611096\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.2.tar.gz\";s:4:\"date\";s:10:\"1256162761\";s:6:\"mdhash\";s:32:\"9b7a53d7892f202bfb4463a5b4b7e7b7\";s:8:\"filesize\";s:6:\"336144\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.2.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"9b7a53d7892f202bfb4463a5b4b7e7b7aa16d34bc1e91e9199029257974f5fd4\";s:4:\"size\";s:12:\"336144382168\";s:8:\"filedate\";s:20:\"12561627611293233709\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-3.1\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.1\";s:7:\"version\";s:7:\"6.x-3.1\";s:3:\"tag\";s:13:\"DRUPAL-6--3-1\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/605840\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.1.tar.gz\";s:4:\"date\";s:10:\"1255638659\";s:6:\"mdhash\";s:32:\"3533d26f01302b98487f087fafb07580\";s:8:\"filesize\";s:6:\"335965\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.1.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"3533d26f01302b98487f087fafb075808627ee600027fb5a412d5dd13eb2c8f7\";s:4:\"size\";s:12:\"335965382009\";s:8:\"filedate\";s:20:\"12556386591293233698\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-3.0\";a:20:{s:4:\"name\";s:14:\"panels 6.x-3.0\";s:7:\"version\";s:7:\"6.x-3.0\";s:3:\"tag\";s:13:\"DRUPAL-6--3-0\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/554226\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0.tar.gz\";s:4:\"date\";s:10:\"1250724669\";s:6:\"mdhash\";s:32:\"2bfa7f119253533dcbefa100bf354b61\";s:8:\"filesize\";s:6:\"322329\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"2bfa7f119253533dcbefa100bf354b6126722c405fd69ac3820da6217262623e\";s:4:\"size\";s:12:\"322329368151\";s:8:\"filedate\";s:20:\"12507246691293233704\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-3.0-rc1\";a:21:{s:4:\"name\";s:18:\"panels 6.x-3.0-rc1\";s:7:\"version\";s:11:\"6.x-3.0-rc1\";s:3:\"tag\";s:17:\"DRUPAL-6--3-0-RC1\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/528134\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-rc1.tar.gz\";s:4:\"date\";s:10:\"1248309076\";s:6:\"mdhash\";s:32:\"e86ae024f95f29cf8e1ff9a52394982d\";s:8:\"filesize\";s:6:\"355424\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-rc1.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0-rc1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"e86ae024f95f29cf8e1ff9a52394982d5716c66e1ecf676327410025ea076aa8\";s:4:\"size\";s:12:\"355424401447\";s:8:\"filedate\";s:20:\"12483090761293233710\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-3.0-beta4\";a:21:{s:4:\"name\";s:20:\"panels 6.x-3.0-beta4\";s:7:\"version\";s:13:\"6.x-3.0-beta4\";s:3:\"tag\";s:19:\"DRUPAL-6--3-0-BETA4\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/517088\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-beta4.tar.gz\";s:4:\"date\";s:10:\"1247424051\";s:6:\"mdhash\";s:32:\"705d1347895ad47daed06cefb7d22ce3\";s:8:\"filesize\";s:6:\"337007\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-beta4.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0-beta4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"705d1347895ad47daed06cefb7d22ce351de3110bf6b60ff0d335d9501aec08d\";s:4:\"size\";s:12:\"337007381197\";s:8:\"filedate\";s:20:\"12474240511293233699\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:13:\"6.x-3.0-beta2\";a:21:{s:4:\"name\";s:20:\"panels 6.x-3.0-beta2\";s:7:\"version\";s:13:\"6.x-3.0-beta2\";s:3:\"tag\";s:19:\"DRUPAL-6--3-0-BETA2\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/468632\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-beta2.tar.gz\";s:4:\"date\";s:10:\"1242862539\";s:6:\"mdhash\";s:32:\"2e26b928b8c3de8d651fea7fd8e6d63d\";s:8:\"filesize\";s:6:\"339504\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-beta2.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0-beta2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"2e26b928b8c3de8d651fea7fd8e6d63dfa8a77788e2985f797db9a176aef663f\";s:4:\"size\";s:12:\"339504386343\";s:8:\"filedate\";s:20:\"12428625391293233705\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-3.0-beta1\";a:21:{s:4:\"name\";s:20:\"panels 6.x-3.0-beta1\";s:7:\"version\";s:13:\"6.x-3.0-beta1\";s:3:\"tag\";s:19:\"DRUPAL-6--3-0-BETA1\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/450240\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-beta1.tar.gz\";s:4:\"date\";s:10:\"1241139940\";s:6:\"mdhash\";s:32:\"403e3907c9b38ccf76b5281b6643861a\";s:8:\"filesize\";s:6:\"337251\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-beta1.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0-beta1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"403e3907c9b38ccf76b5281b6643861aa11bcc625f0d0498f344266a4bd43ce8\";s:4:\"size\";s:12:\"337251383797\";s:8:\"filedate\";s:20:\"12411399401293233711\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-3.0-alpha4\";a:21:{s:4:\"name\";s:21:\"panels 6.x-3.0-alpha4\";s:7:\"version\";s:14:\"6.x-3.0-alpha4\";s:3:\"tag\";s:20:\"DRUPAL-6--3-0-ALPHA4\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/421994\";s:13:\"download_link\";s:65:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha4.tar.gz\";s:4:\"date\";s:10:\"1238697971\";s:6:\"mdhash\";s:32:\"f27d2b25d17ce8f065e5dd432f8a1a86\";s:8:\"filesize\";s:6:\"367906\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:127:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha4.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f27d2b25d17ce8f065e5dd432f8a1a86b6f0b8cb0c78f8ddaa623f43adbe9c87\";s:4:\"size\";s:12:\"367906439336\";s:8:\"filedate\";s:20:\"12386979711293233699\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:14:\"6.x-3.0-alpha3\";a:21:{s:4:\"name\";s:21:\"panels 6.x-3.0-alpha3\";s:7:\"version\";s:14:\"6.x-3.0-alpha3\";s:3:\"tag\";s:20:\"DRUPAL-6--3-0-ALPHA3\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/418640\";s:13:\"download_link\";s:65:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha3.tar.gz\";s:4:\"date\";s:10:\"1238444751\";s:6:\"mdhash\";s:32:\"44693a0b993cfccb881c123d13a6f776\";s:8:\"filesize\";s:6:\"367243\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:127:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha3.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"44693a0b993cfccb881c123d13a6f77613a479dd505295d083fda381e4ba0776\";s:4:\"size\";s:12:\"367243438241\";s:8:\"filedate\";s:20:\"12384447511293233705\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-3.0-alpha2\";a:21:{s:4:\"name\";s:21:\"panels 6.x-3.0-alpha2\";s:7:\"version\";s:14:\"6.x-3.0-alpha2\";s:3:\"tag\";s:20:\"DRUPAL-6--3-0-ALPHA2\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/366425\";s:13:\"download_link\";s:65:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha2.tar.gz\";s:4:\"date\";s:10:\"1233270339\";s:6:\"mdhash\";s:32:\"5641b7a35fa62580b116c97d5408249e\";s:8:\"filesize\";s:6:\"354040\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:127:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha2.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"5641b7a35fa62580b116c97d5408249ed3c204012b139d936f37d4d6f56623c0\";s:4:\"size\";s:12:\"354040421335\";s:8:\"filedate\";s:20:\"12332703391293233711\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-3.0-alpha1\";a:21:{s:4:\"name\";s:21:\"panels 6.x-3.0-alpha1\";s:7:\"version\";s:14:\"6.x-3.0-alpha1\";s:3:\"tag\";s:20:\"DRUPAL-6--3-0-ALPHA1\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/352589\";s:13:\"download_link\";s:65:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha1.tar.gz\";s:4:\"date\";s:10:\"1230663323\";s:6:\"mdhash\";s:32:\"284d81a8550d65e1a4958e5c84ebba10\";s:8:\"filesize\";s:6:\"400176\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:127:\"http://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha1.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.0-alpha1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"284d81a8550d65e1a4958e5c84ebba10040989175ad697f53ef9f1ab77ddf930\";s:4:\"size\";s:12:\"400176511142\";s:8:\"filedate\";s:20:\"12306633231293233700\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:11:\"6.x-3.x-dev\";a:19:{s:4:\"name\";s:18:\"panels 6.x-3.x-dev\";s:7:\"version\";s:11:\"6.x-3.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--3\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/366922\";s:13:\"download_link\";s:62:\"http://ftp.drupal.org/files/projects/panels-6.x-3.x-dev.tar.gz\";s:4:\"date\";s:10:\"1295915226\";s:6:\"mdhash\";s:32:\"00844a93f5eb6ebeb72d4081c755ab88\";s:8:\"filesize\";s:6:\"398145\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:121:\"http://ftp.drupal.org/files/projects/panels-6.x-3.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/panels-6.x-3.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"00844a93f5eb6ebeb72d4081c755ab884f98877dbd8a43e647bf42b1a1156a23\";s:4:\"size\";s:12:\"398145486418\";s:8:\"filedate\";s:20:\"12959152261295915227\";s:0:\"\";s:0:\"\";}s:14:\"6.x-2.0-alpha3\";a:18:{s:4:\"name\";s:21:\"panels 6.x-2.0-alpha3\";s:7:\"version\";s:14:\"6.x-2.0-alpha3\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha3\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1230669628\";s:6:\"mdhash\";s:32:\"af08bf2c2b739341add3723b759a8d3c\";s:8:\"filesize\";s:6:\"418513\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"af08bf2c2b739341add3723b759a8d3c\";s:4:\"size\";s:6:\"418513\";s:8:\"filedate\";s:10:\"1230669628\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-2.0-alpha2\";a:18:{s:4:\"name\";s:21:\"panels 6.x-2.0-alpha2\";s:7:\"version\";s:14:\"6.x-2.0-alpha2\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha2\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1223825423\";s:6:\"mdhash\";s:32:\"84813abb46ea70be8ab09711edcc007e\";s:8:\"filesize\";s:6:\"399737\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"84813abb46ea70be8ab09711edcc007e\";s:4:\"size\";s:6:\"399737\";s:8:\"filedate\";s:10:\"1223825423\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-2.0-alpha1\";a:18:{s:4:\"name\";s:21:\"panels 6.x-2.0-alpha1\";s:7:\"version\";s:14:\"6.x-2.0-alpha1\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha1\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1220497215\";s:6:\"mdhash\";s:32:\"f06c1a814d13dd7becff85a9c7078e3e\";s:8:\"filesize\";s:6:\"356885\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"f06c1a814d13dd7becff85a9c7078e3e\";s:4:\"size\";s:6:\"356885\";s:8:\"filedate\";s:10:\"1220497215\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:11:\"6.x-2.x-dev\";a:16:{s:4:\"name\";s:18:\"panels 6.x-2.x-dev\";s:7:\"version\";s:11:\"6.x-2.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1234656855\";s:6:\"mdhash\";s:32:\"c1ff3908e47d5f4f9cfba6077cd8fb4a\";s:8:\"filesize\";s:6:\"416317\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"c1ff3908e47d5f4f9cfba6077cd8fb4a\";s:4:\"size\";s:6:\"416317\";s:8:\"filedate\";s:10:\"1234656855\";s:0:\"\";s:0:\"\";}}s:14:\"latest_version\";s:7:\"6.x-3.9\";s:11:\"recommended\";s:7:\"6.x-3.9\";s:6:\"status\";i:5;}s:11:\"panels_tabs\";a:23:{s:4:\"name\";s:11:\"panels_tabs\";s:4:\"info\";a:6:{s:4:\"name\";s:16:\"Tabs panel style\";s:7:\"package\";s:20:\"Panels style plugins\";s:7:\"version\";s:11:\"6.x-1.0-rc6\";s:7:\"project\";s:11:\"panels_tabs\";s:9:\"datestamp\";s:10:\"1286015464\";s:16:\"_info_file_ctime\";i:1296890116;}s:9:\"datestamp\";s:10:\"1286015464\";s:8:\"includes\";a:1:{s:11:\"panels_tabs\";s:16:\"Tabs panel style\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:11:\"6.x-1.0-rc6\";s:14:\"existing_major\";s:1:\"1\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:11:\"Panels Tabs\";s:10:\"short_name\";s:11:\"panels_tabs\";s:10:\"dc:creator\";s:9:\"smoothify\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"1\";s:16:\"supported_majors\";s:1:\"1\";s:13:\"default_major\";s:1:\"1\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:37:\"http://drupal.org/project/panels_tabs\";s:8:\"releases\";a:10:{s:11:\"6.x-1.0-rc6\";a:21:{s:4:\"name\";s:23:\"panels_tabs 6.x-1.0-rc6\";s:7:\"version\";s:11:\"6.x-1.0-rc6\";s:3:\"tag\";s:17:\"DRUPAL-6--1-0-RC6\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc6\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/929362\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc6.tar.gz\";s:4:\"date\";s:10:\"1286015464\";s:6:\"mdhash\";s:32:\"1256d58a59e13f176024dc6b129dccc7\";s:8:\"filesize\";s:5:\"10575\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc6.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc6.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"1256d58a59e13f176024dc6b129dccc77d637bd1a5c75924c615091561aecdb6\";s:4:\"size\";s:10:\"1057512762\";s:8:\"filedate\";s:20:\"12860154641293233720\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-1.0-rc5\";a:21:{s:4:\"name\";s:23:\"panels_tabs 6.x-1.0-rc5\";s:7:\"version\";s:11:\"6.x-1.0-rc5\";s:3:\"tag\";s:17:\"DRUPAL-6--1-0-RC5\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc5\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/907534\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc5.tar.gz\";s:4:\"date\";s:10:\"1284122508\";s:6:\"mdhash\";s:32:\"e1672a1bf0cd4e696796e13c893d801e\";s:8:\"filesize\";s:5:\"10560\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc5.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc5.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"e1672a1bf0cd4e696796e13c893d801e67ff2450feb8e32ac670f28db36ed23d\";s:4:\"size\";s:10:\"1056012700\";s:8:\"filedate\";s:20:\"12841225081293233719\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:11:\"6.x-1.0-rc4\";a:21:{s:4:\"name\";s:23:\"panels_tabs 6.x-1.0-rc4\";s:7:\"version\";s:11:\"6.x-1.0-rc4\";s:3:\"tag\";s:17:\"DRUPAL-6--1-0-RC4\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/881220\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc4.tar.gz\";s:4:\"date\";s:10:\"1281619592\";s:6:\"mdhash\";s:32:\"ffb30e3a9c86cf36fbe4cc652c6dc2be\";s:8:\"filesize\";s:5:\"10461\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc4.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"ffb30e3a9c86cf36fbe4cc652c6dc2be9a6e7c75590b016094596e2a813c42c2\";s:4:\"size\";s:10:\"1046112582\";s:8:\"filedate\";s:20:\"12816195921293233719\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-1.0-rc3\";a:21:{s:4:\"name\";s:23:\"panels_tabs 6.x-1.0-rc3\";s:7:\"version\";s:11:\"6.x-1.0-rc3\";s:3:\"tag\";s:17:\"DRUPAL-6--1-0-RC3\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/870000\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc3.tar.gz\";s:4:\"date\";s:10:\"1280529974\";s:6:\"mdhash\";s:32:\"d1052eb9fb5192b56771359a68fe1a03\";s:8:\"filesize\";s:5:\"10345\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc3.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"d1052eb9fb5192b56771359a68fe1a038072c0827a3d5b61cc510c87590985f9\";s:4:\"size\";s:10:\"1034512448\";s:8:\"filedate\";s:20:\"12805299741293233720\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-1.0-rc2\";a:21:{s:4:\"name\";s:23:\"panels_tabs 6.x-1.0-rc2\";s:7:\"version\";s:11:\"6.x-1.0-rc2\";s:3:\"tag\";s:17:\"DRUPAL-6--1-0-RC2\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/868982\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc2.tar.gz\";s:4:\"date\";s:10:\"1280439618\";s:6:\"mdhash\";s:32:\"252752e067405c1a1d94e9ef3252d686\";s:8:\"filesize\";s:5:\"10289\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc2.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"252752e067405c1a1d94e9ef3252d686b798220bbb35fce0f45ed92364de68be\";s:4:\"size\";s:10:\"1028912408\";s:8:\"filedate\";s:20:\"12804396181293233719\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-1.0-rc1\";a:20:{s:4:\"name\";s:23:\"panels_tabs 6.x-1.0-rc1\";s:7:\"version\";s:11:\"6.x-1.0-rc1\";s:3:\"tag\";s:17:\"DRUPAL-6--1-0-RC1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/867388\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc1.tar.gz\";s:4:\"date\";s:10:\"1280340016\";s:6:\"mdhash\";s:32:\"64edc246a0723dc49841dff658635ac8\";s:8:\"filesize\";s:5:\"10026\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc1.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-rc1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"64edc246a0723dc49841dff658635ac888bd27c886fb54e2192bf92786db8c14\";s:4:\"size\";s:10:\"1002611965\";s:8:\"filedate\";s:20:\"12803400161293233720\";s:0:\"\";s:0:\"\";}s:13:\"6.x-1.0-beta3\";a:21:{s:4:\"name\";s:25:\"panels_tabs 6.x-1.0-beta3\";s:7:\"version\";s:13:\"6.x-1.0-beta3\";s:3:\"tag\";s:19:\"DRUPAL-6--1-0-BETA3\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/816294\";s:13:\"download_link\";s:69:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta3.tar.gz\";s:4:\"date\";s:10:\"1275505517\";s:6:\"mdhash\";s:32:\"353bef8fc474faeb2102bd06c7122721\";s:8:\"filesize\";s:4:\"9604\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:135:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta3.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"353bef8fc474faeb2102bd06c712272160dbb3d31317f930c191575a2dee82c3\";s:4:\"size\";s:9:\"960411469\";s:8:\"filedate\";s:20:\"12755055171293233720\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-1.0-beta2\";a:20:{s:4:\"name\";s:25:\"panels_tabs 6.x-1.0-beta2\";s:7:\"version\";s:13:\"6.x-1.0-beta2\";s:3:\"tag\";s:19:\"DRUPAL-6--1-0-BETA2\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/807450\";s:13:\"download_link\";s:69:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta2.tar.gz\";s:4:\"date\";s:10:\"1274685010\";s:6:\"mdhash\";s:32:\"3bd477996d51e4528e5f5fc102c831c6\";s:8:\"filesize\";s:4:\"9702\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:135:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta2.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"3bd477996d51e4528e5f5fc102c831c618e523ee64c6c2a0ddde495869f9d442\";s:4:\"size\";s:9:\"970211633\";s:8:\"filedate\";s:20:\"12746850101293233719\";s:0:\"\";s:0:\"\";}s:13:\"6.x-1.0-beta1\";a:21:{s:4:\"name\";s:25:\"panels_tabs 6.x-1.0-beta1\";s:7:\"version\";s:13:\"6.x-1.0-beta1\";s:3:\"tag\";s:19:\"DRUPAL-6--1-0-BETA1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/806430\";s:13:\"download_link\";s:69:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta1.tar.gz\";s:4:\"date\";s:10:\"1274541907\";s:6:\"mdhash\";s:32:\"f5ec0ca61f181bfb537a96737266db01\";s:8:\"filesize\";s:4:\"8714\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:135:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta1.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.0-beta1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f5ec0ca61f181bfb537a96737266db0166d66778ed06816772fc4e8f8b57a01d\";s:4:\"size\";s:8:\"87149817\";s:8:\"filedate\";s:20:\"12745419071293233720\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-1.x-dev\";a:19:{s:4:\"name\";s:23:\"panels_tabs 6.x-1.x-dev\";s:7:\"version\";s:11:\"6.x-1.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/461916\";s:13:\"download_link\";s:67:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.x-dev.tar.gz\";s:4:\"date\";s:10:\"1284164179\";s:6:\"mdhash\";s:32:\"51aeafacf047f58d672f4c5fed1406ae\";s:8:\"filesize\";s:5:\"10573\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:131:\"http://ftp.drupal.org/files/projects/panels_tabs-6.x-1.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/panels_tabs-6.x-1.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"51aeafacf047f58d672f4c5fed1406aecb1a196b95f2236967a3f8de38aa3fc9\";s:4:\"size\";s:10:\"1057312762\";s:8:\"filedate\";s:20:\"12841641791293251025\";s:0:\"\";s:0:\"\";}}s:14:\"latest_version\";s:11:\"6.x-1.0-rc6\";s:11:\"recommended\";s:11:\"6.x-1.0-rc6\";s:6:\"status\";i:5;}s:4:\"tabs\";a:23:{s:4:\"name\";s:4:\"tabs\";s:4:\"info\";a:5:{s:4:\"name\";s:4:\"Tabs\";s:7:\"version\";s:7:\"6.x-1.3\";s:7:\"project\";s:4:\"tabs\";s:9:\"datestamp\";s:10:\"1264529109\";s:16:\"_info_file_ctime\";i:1296890108;}s:9:\"datestamp\";s:10:\"1264529109\";s:8:\"includes\";a:1:{s:4:\"tabs\";s:4:\"Tabs\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:7:\"6.x-1.3\";s:14:\"existing_major\";s:1:\"1\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:21:\"Tabs (jQuery UI tabs)\";s:10:\"short_name\";s:4:\"tabs\";s:10:\"dc:creator\";s:5:\"nedjo\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"1\";s:16:\"supported_majors\";s:1:\"1\";s:13:\"default_major\";s:1:\"1\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:30:\"http://drupal.org/project/tabs\";s:8:\"releases\";a:5:{s:7:\"6.x-1.3\";a:19:{s:4:\"name\";s:12:\"tabs 6.x-1.3\";s:7:\"version\";s:7:\"6.x-1.3\";s:3:\"tag\";s:13:\"DRUPAL-6--1-3\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/696018\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.3.tar.gz\";s:4:\"date\";s:10:\"1264529110\";s:6:\"mdhash\";s:32:\"b7fa83e73b7b6639ab63a239a4f2925b\";s:8:\"filesize\";s:5:\"19964\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.3.tar.gzhttp://ftp.drupal.org/files/projects/tabs-6.x-1.3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"b7fa83e73b7b6639ab63a239a4f2925b461031d7b3707bdf24cee000b278ad4b\";s:4:\"size\";s:10:\"1996422999\";s:8:\"filedate\";s:20:\"12645291101293234800\";s:0:\"\";s:0:\"\";}s:7:\"6.x-1.2\";a:20:{s:4:\"name\";s:12:\"tabs 6.x-1.2\";s:7:\"version\";s:7:\"6.x-1.2\";s:3:\"tag\";s:13:\"DRUPAL-6--1-2\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/560124\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.2.tar.gz\";s:4:\"date\";s:10:\"1251300404\";s:6:\"mdhash\";s:32:\"b32edf2cd61a613ac3bc84e8c6f4761b\";s:8:\"filesize\";s:5:\"19545\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.2.tar.gzhttp://ftp.drupal.org/files/projects/tabs-6.x-1.2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"b32edf2cd61a613ac3bc84e8c6f4761b707b9c2770366bc20b954908f895c037\";s:4:\"size\";s:10:\"1954522620\";s:8:\"filedate\";s:20:\"12513004041293234801\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.1\";a:19:{s:4:\"name\";s:12:\"tabs 6.x-1.1\";s:7:\"version\";s:7:\"6.x-1.1\";s:3:\"tag\";s:13:\"DRUPAL-6--1-1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/553714\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.1.tar.gz\";s:4:\"date\";s:10:\"1250697164\";s:6:\"mdhash\";s:32:\"8f3102fff568af9c92bbbff7a0d7b0ce\";s:8:\"filesize\";s:5:\"19384\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.1.tar.gzhttp://ftp.drupal.org/files/projects/tabs-6.x-1.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"8f3102fff568af9c92bbbff7a0d7b0ce05767815992da6fd865d0a72f687f065\";s:4:\"size\";s:10:\"1938422362\";s:8:\"filedate\";s:20:\"12506971641293234801\";s:0:\"\";s:0:\"\";}s:7:\"6.x-1.0\";a:19:{s:4:\"name\";s:12:\"tabs 6.x-1.0\";s:7:\"version\";s:7:\"6.x-1.0\";s:3:\"tag\";s:13:\"DRUPAL-6--1-0\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/304702\";s:13:\"download_link\";s:56:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.0.tar.gz\";s:4:\"date\";s:10:\"1220673919\";s:6:\"mdhash\";s:32:\"5f19cca8a0742d7036449e3f3588cc3c\";s:8:\"filesize\";s:5:\"15675\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:109:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.0.tar.gzhttp://ftp.drupal.org/files/projects/tabs-6.x-1.0.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"5f19cca8a0742d7036449e3f3588cc3cf4e989d07c7242cff414bd51fdd1617f\";s:4:\"size\";s:10:\"1567517534\";s:8:\"filedate\";s:20:\"12206739191293234800\";s:0:\"\";s:0:\"\";}s:11:\"6.x-1.x-dev\";a:19:{s:4:\"name\";s:16:\"tabs 6.x-1.x-dev\";s:7:\"version\";s:11:\"6.x-1.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/239151\";s:13:\"download_link\";s:60:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.x-dev.tar.gz\";s:4:\"date\";s:10:\"1278835869\";s:6:\"mdhash\";s:32:\"dd3e32b6372271d45ecb5e10b028a6e6\";s:8:\"filesize\";s:5:\"23493\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:117:\"http://ftp.drupal.org/files/projects/tabs-6.x-1.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/tabs-6.x-1.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"dd3e32b6372271d45ecb5e10b028a6e64e9fde14214261623e0ad2e78f2db8f7\";s:4:\"size\";s:10:\"2349330508\";s:8:\"filedate\";s:20:\"12788358691293251386\";s:0:\"\";s:0:\"\";}}s:14:\"latest_version\";s:7:\"6.x-1.3\";s:11:\"recommended\";s:7:\"6.x-1.3\";s:6:\"status\";i:5;}s:5:\"views\";a:24:{s:4:\"name\";s:5:\"views\";s:4:\"info\";a:6:{s:4:\"name\";s:5:\"Views\";s:7:\"package\";s:5:\"Views\";s:7:\"version\";s:8:\"6.x-2.12\";s:7:\"project\";s:5:\"views\";s:9:\"datestamp\";s:10:\"1292446272\";s:16:\"_info_file_ctime\";i:1296890114;}s:9:\"datestamp\";s:10:\"1292446272\";s:8:\"includes\";a:3:{s:5:\"views\";s:5:\"Views\";s:12:\"views_export\";s:14:\"Views exporter\";s:8:\"views_ui\";s:8:\"Views UI\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:8:\"6.x-2.12\";s:14:\"existing_major\";s:1:\"2\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:5:\"Views\";s:10:\"short_name\";s:5:\"views\";s:10:\"dc:creator\";s:13:\"merlinofchaos\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"2\";s:16:\"supported_majors\";s:3:\"2,3\";s:13:\"default_major\";s:1:\"2\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:31:\"http://drupal.org/project/views\";s:8:\"releases\";a:32:{s:14:\"6.x-3.0-alpha3\";a:21:{s:4:\"name\";s:20:\"views 6.x-3.0-alpha3\";s:7:\"version\";s:14:\"6.x-3.0-alpha3\";s:3:\"tag\";s:20:\"DRUPAL-6--3-0-ALPHA3\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/765092\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/views-6.x-3.0-alpha3.tar.gz\";s:4:\"date\";s:10:\"1270684212\";s:6:\"mdhash\";s:32:\"fe7b96742eb7d8f62f011f9106896256\";s:8:\"filesize\";s:7:\"1639781\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/views-6.x-3.0-alpha3.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-3.0-alpha3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"fe7b96742eb7d8f62f011f9106896256437509c636388918615f0ae7d9a6bc06\";s:4:\"size\";s:14:\"16397811826176\";s:8:\"filedate\";s:20:\"12706842121293229055\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:3:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";i:2;s:15:\"Security update\";}}}s:14:\"6.x-3.0-alpha2\";a:21:{s:4:\"name\";s:20:\"views 6.x-3.0-alpha2\";s:7:\"version\";s:14:\"6.x-3.0-alpha2\";s:3:\"tag\";s:20:\"DRUPAL-6--3-0-ALPHA2\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/695302\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/views-6.x-3.0-alpha2.tar.gz\";s:4:\"date\";s:10:\"1264463413\";s:6:\"mdhash\";s:32:\"6549c80d447a4fa7f8071dfe69fed6fd\";s:8:\"filesize\";s:7:\"1584488\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/views-6.x-3.0-alpha2.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-3.0-alpha2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"6549c80d447a4fa7f8071dfe69fed6fd017c4fa11bde8d45b20064fc0ade01fc\";s:4:\"size\";s:14:\"15844881760044\";s:8:\"filedate\";s:20:\"12644634131293229051\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:14:\"6.x-3.0-alpha1\";a:21:{s:4:\"name\";s:20:\"views 6.x-3.0-alpha1\";s:7:\"version\";s:14:\"6.x-3.0-alpha1\";s:3:\"tag\";s:20:\"DRUPAL-6--3-0-ALPHA1\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/629202\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/views-6.x-3.0-alpha1.tar.gz\";s:4:\"date\";s:10:\"1257895600\";s:6:\"mdhash\";s:32:\"0cb60791933141335a7f5032de687004\";s:8:\"filesize\";s:7:\"1552538\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/views-6.x-3.0-alpha1.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-3.0-alpha1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"0cb60791933141335a7f5032de68700485b6a98e4945100c3187c877402abe6a\";s:4:\"size\";s:14:\"15525381715724\";s:8:\"filedate\";s:20:\"12578956001293229048\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:11:\"6.x-3.x-dev\";a:20:{s:4:\"name\";s:17:\"views 6.x-3.x-dev\";s:7:\"version\";s:11:\"6.x-3.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--3\";s:13:\"version_major\";s:1:\"3\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/467670\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/views-6.x-3.x-dev.tar.gz\";s:4:\"date\";s:10:\"1296866896\";s:6:\"mdhash\";s:32:\"b173ca03a1a668ffaa171d7f19763f67\";s:8:\"filesize\";s:7:\"1639238\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/views-6.x-3.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-3.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"b173ca03a1a668ffaa171d7f19763f67581a9c424ded54691c41be6f4f30ca03\";s:4:\"size\";s:14:\"16392381854349\";s:8:\"filedate\";s:20:\"12968668961296866897\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:8:\"6.x-2.12\";a:20:{s:4:\"name\";s:14:\"views 6.x-2.12\";s:7:\"version\";s:8:\"6.x-2.12\";s:3:\"tag\";s:14:\"DRUPAL-6--2-12\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:2:\"12\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/999386\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/views-6.x-2.12.tar.gz\";s:4:\"date\";s:10:\"1292446274\";s:6:\"mdhash\";s:32:\"2b666d68e8566f14b85cf546d643e3e5\";s:8:\"filesize\";s:7:\"1662696\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/views-6.x-2.12.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.12.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"2b666d68e8566f14b85cf546d643e3e52816cbd1d3e70a77a48af89b58ccdf56\";s:4:\"size\";s:14:\"16626961831338\";s:8:\"filedate\";s:20:\"12924462741293229060\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:15:\"Security update\";}}}s:8:\"6.x-2.11\";a:20:{s:4:\"name\";s:14:\"views 6.x-2.11\";s:7:\"version\";s:8:\"6.x-2.11\";s:3:\"tag\";s:14:\"DRUPAL-6--2-11\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:2:\"11\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/829846\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/views-6.x-2.11.tar.gz\";s:4:\"date\";s:10:\"1276743616\";s:6:\"mdhash\";s:32:\"ea5ef15e0d03c03627f7c5ea2350d78d\";s:8:\"filesize\";s:7:\"1662750\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/views-6.x-2.11.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.11.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"ea5ef15e0d03c03627f7c5ea2350d78d3f66c6707e1d1513f6447e9469875d70\";s:4:\"size\";s:14:\"16627501831331\";s:8:\"filedate\";s:20:\"12767436161293229058\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:9:\"Bug fixes\";i:1;s:15:\"Security update\";}}}s:8:\"6.x-2.10\";a:20:{s:4:\"name\";s:14:\"views 6.x-2.10\";s:7:\"version\";s:8:\"6.x-2.10\";s:3:\"tag\";s:14:\"DRUPAL-6--2-10\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:2:\"10\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/766164\";s:13:\"download_link\";s:58:\"http://ftp.drupal.org/files/projects/views-6.x-2.10.tar.gz\";s:4:\"date\";s:10:\"1270766109\";s:6:\"mdhash\";s:32:\"a5868e2316ed2b920d621602b0ee78b3\";s:8:\"filesize\";s:7:\"1655007\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:113:\"http://ftp.drupal.org/files/projects/views-6.x-2.10.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.10.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"a5868e2316ed2b920d621602b0ee78b397f7c56f826f85e72cc5bfda10a4c2b0\";s:4:\"size\";s:14:\"16550071823593\";s:8:\"filedate\";s:20:\"12707661091293229056\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.9\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.9\";s:7:\"version\";s:7:\"6.x-2.9\";s:3:\"tag\";s:13:\"DRUPAL-6--2-9\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"9\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/765088\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.9.tar.gz\";s:4:\"date\";s:10:\"1270683914\";s:6:\"mdhash\";s:32:\"81534c4df203820488063ddba3892886\";s:8:\"filesize\";s:7:\"1654130\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.9.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.9.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"81534c4df203820488063ddba3892886304d5acceb8381f10b8e8219845b2f1b\";s:4:\"size\";s:14:\"16541301823014\";s:8:\"filedate\";s:20:\"12706839141293229052\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:9:\"Bug fixes\";i:1;s:15:\"Security update\";}}}s:7:\"6.x-2.8\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.8\";s:7:\"version\";s:7:\"6.x-2.8\";s:3:\"tag\";s:13:\"DRUPAL-6--2-8\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"8\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/649642\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.8.tar.gz\";s:4:\"date\";s:10:\"1259799378\";s:6:\"mdhash\";s:32:\"70c2e02d6f7288e3979108ab96966ef6\";s:8:\"filesize\";s:7:\"1553915\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.8.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.8.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"70c2e02d6f7288e3979108ab96966ef677e7d4e1a1a76f39e8130cd18abcabd0\";s:4:\"size\";s:14:\"15539151718572\";s:8:\"filedate\";s:20:\"12597993781293229049\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.7\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.7\";s:7:\"version\";s:7:\"6.x-2.7\";s:3:\"tag\";s:13:\"DRUPAL-6--2-7\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"7\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/621428\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.7.tar.gz\";s:4:\"date\";s:10:\"1257197511\";s:6:\"mdhash\";s:32:\"993a4ce82f5eb6f3f2166de7aa5edbce\";s:8:\"filesize\";s:7:\"1551476\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.7.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.7.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"993a4ce82f5eb6f3f2166de7aa5edbce391b6108f3e1d20b54500a09a5ab0c5f\";s:4:\"size\";s:14:\"15514761716247\";s:8:\"filedate\";s:20:\"12571975111293229047\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.6\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.6\";s:7:\"version\";s:7:\"6.x-2.6\";s:3:\"tag\";s:13:\"DRUPAL-6--2-6\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"6\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/488082\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.6.tar.gz\";s:4:\"date\";s:10:\"1244671916\";s:6:\"mdhash\";s:32:\"a39827a5430373ab8508f2773b0bc6ea\";s:8:\"filesize\";s:7:\"1534198\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.6.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.6.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"a39827a5430373ab8508f2773b0bc6eaa114fe7417ddea08b0c81eac860afe20\";s:4:\"size\";s:14:\"15341981696007\";s:8:\"filedate\";s:20:\"12446719161293229044\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:3:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";i:2;s:15:\"Security update\";}}}s:7:\"6.x-2.5\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.5\";s:7:\"version\";s:7:\"6.x-2.5\";s:3:\"tag\";s:13:\"DRUPAL-6--2-5\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"5\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/431016\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.5.tar.gz\";s:4:\"date\";s:10:\"1239478365\";s:6:\"mdhash\";s:32:\"2098b66ccb996c38463bc1f276e2c5e4\";s:8:\"filesize\";s:7:\"1421005\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.5.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.5.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"2098b66ccb996c38463bc1f276e2c5e4894bc955a58d350423e254988589d1bb\";s:4:\"size\";s:14:\"14210051569640\";s:8:\"filedate\";s:20:\"12394783651293229042\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.4\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.4\";s:7:\"version\";s:7:\"6.x-2.4\";s:3:\"tag\";s:13:\"DRUPAL-6--2-4\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/426916\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.4.tar.gz\";s:4:\"date\";s:10:\"1239147355\";s:6:\"mdhash\";s:32:\"7da75bea2204e45cc1c31379ed8c10ac\";s:8:\"filesize\";s:7:\"1419570\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.4.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"7da75bea2204e45cc1c31379ed8c10acfb33f3ccc3c8d50f578a41da048904f5\";s:4:\"size\";s:14:\"14195701567611\";s:8:\"filedate\";s:20:\"12391473551293229040\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.3\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.3\";s:7:\"version\";s:7:\"6.x-2.3\";s:3:\"tag\";s:13:\"DRUPAL-6--2-3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/370526\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.3.tar.gz\";s:4:\"date\";s:10:\"1233981351\";s:6:\"mdhash\";s:32:\"582bde5b7a68357c026a2bee689fe3cb\";s:8:\"filesize\";s:7:\"1365883\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.3.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"582bde5b7a68357c026a2bee689fe3cb9a6164de134d739f8ad8ade8b4dcc5b7\";s:4:\"size\";s:14:\"13658831505942\";s:8:\"filedate\";s:20:\"12339813511293229039\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.2\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.2\";s:7:\"version\";s:7:\"6.x-2.2\";s:3:\"tag\";s:13:\"DRUPAL-6--2-2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/347831\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.2.tar.gz\";s:4:\"date\";s:10:\"1229455243\";s:6:\"mdhash\";s:32:\"71a5f10609c8cce32bae5a09a2913ba5\";s:8:\"filesize\";s:7:\"1315921\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.2.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"71a5f10609c8cce32bae5a09a2913ba5b7040507e0b4b12652dc0093718a9974\";s:4:\"size\";s:14:\"13159211449378\";s:8:\"filedate\";s:20:\"12294552431293229038\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:9:\"Bug fixes\";i:1;s:15:\"Security update\";}}}s:7:\"6.x-2.1\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.1\";s:7:\"version\";s:7:\"6.x-2.1\";s:3:\"tag\";s:13:\"DRUPAL-6--2-1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/323897\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.1.tar.gz\";s:4:\"date\";s:10:\"1224538829\";s:6:\"mdhash\";s:32:\"46b80d1acfdd785720de91330c770980\";s:8:\"filesize\";s:7:\"1304664\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.1.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"46b80d1acfdd785720de91330c7709807699c07236fa9750e8174ffb0ccc7045\";s:4:\"size\";s:14:\"13046641436903\";s:8:\"filedate\";s:20:\"12245388291293229036\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.0\";a:20:{s:4:\"name\";s:13:\"views 6.x-2.0\";s:7:\"version\";s:7:\"6.x-2.0\";s:3:\"tag\";s:13:\"DRUPAL-6--2-0\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/322829\";s:13:\"download_link\";s:57:\"http://ftp.drupal.org/files/projects/views-6.x-2.0.tar.gz\";s:4:\"date\";s:10:\"1224280828\";s:6:\"mdhash\";s:32:\"879ac52df90bf18d1c9d3d454febf609\";s:8:\"filesize\";s:7:\"1304512\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:111:\"http://ftp.drupal.org/files/projects/views-6.x-2.0.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"879ac52df90bf18d1c9d3d454febf6094070ba53f7b9f6be9caf9422aa2782d8\";s:4:\"size\";s:14:\"13045121436092\";s:8:\"filedate\";s:20:\"12242808281293229035\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-2.0-rc5\";a:21:{s:4:\"name\";s:17:\"views 6.x-2.0-rc5\";s:7:\"version\";s:11:\"6.x-2.0-rc5\";s:3:\"tag\";s:17:\"DRUPAL-6--2-0-RC5\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc5\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/318786\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc5.tar.gz\";s:4:\"date\";s:10:\"1223507724\";s:6:\"mdhash\";s:32:\"f425efe6979c32e7de3cfdc5c6f01a28\";s:8:\"filesize\";s:7:\"1303138\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc5.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-rc5.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f425efe6979c32e7de3cfdc5c6f01a28b42bcaa44d7939db1426cc86c5b27dee\";s:4:\"size\";s:14:\"13031381434528\";s:8:\"filedate\";s:20:\"12235077241293229032\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-2.0-rc4\";a:21:{s:4:\"name\";s:17:\"views 6.x-2.0-rc4\";s:7:\"version\";s:11:\"6.x-2.0-rc4\";s:3:\"tag\";s:17:\"DRUPAL-6--2-0-RC4\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/315506\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc4.tar.gz\";s:4:\"date\";s:10:\"1222819523\";s:6:\"mdhash\";s:32:\"11e1fae3b6ec5b05abdf7bd3f4148628\";s:8:\"filesize\";s:7:\"1301241\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc4.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-rc4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"11e1fae3b6ec5b05abdf7bd3f41486281ad45cabf2bd0908080882766dd93567\";s:4:\"size\";s:14:\"13012411433044\";s:8:\"filedate\";s:20:\"12228195231293229030\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-2.0-rc3\";a:21:{s:4:\"name\";s:17:\"views 6.x-2.0-rc3\";s:7:\"version\";s:11:\"6.x-2.0-rc3\";s:3:\"tag\";s:17:\"DRUPAL-6--2-0-RC3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/309397\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc3.tar.gz\";s:4:\"date\";s:10:\"1221602125\";s:6:\"mdhash\";s:32:\"f80c1846f8b53961b940c75cb2e19cdc\";s:8:\"filesize\";s:7:\"1292652\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc3.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-rc3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f80c1846f8b53961b940c75cb2e19cdcabd978653ca111483fa57d74973229d4\";s:4:\"size\";s:14:\"12926521418663\";s:8:\"filedate\";s:20:\"12216021251293229029\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-2.0-rc2\";a:21:{s:4:\"name\";s:17:\"views 6.x-2.0-rc2\";s:7:\"version\";s:11:\"6.x-2.0-rc2\";s:3:\"tag\";s:17:\"DRUPAL-6--2-0-RC2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/307230\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc2.tar.gz\";s:4:\"date\";s:10:\"1221173427\";s:6:\"mdhash\";s:32:\"e6abdee467e234d63fcb815c3156ee4c\";s:8:\"filesize\";s:7:\"1324961\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc2.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-rc2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"e6abdee467e234d63fcb815c3156ee4c502f8f86ac82332ce865b146e8df2aec\";s:4:\"size\";s:14:\"13249611451807\";s:8:\"filedate\";s:20:\"12211734271293229028\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:11:\"6.x-2.0-rc1\";a:21:{s:4:\"name\";s:17:\"views 6.x-2.0-rc1\";s:7:\"version\";s:11:\"6.x-2.0-rc1\";s:3:\"tag\";s:17:\"DRUPAL-6--2-0-RC1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:3:\"rc1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/277862\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc1.tar.gz\";s:4:\"date\";s:10:\"1215030345\";s:6:\"mdhash\";s:32:\"7968787a990c56061aa99ec08231f543\";s:8:\"filesize\";s:7:\"2796661\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-rc1.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-rc1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"7968787a990c56061aa99ec08231f5430390e30be6f930fa59c1b9d8f5a20cc5\";s:4:\"size\";s:14:\"27966612848168\";s:8:\"filedate\";s:20:\"12150303451293229027\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.0-beta4\";a:21:{s:4:\"name\";s:19:\"views 6.x-2.0-beta4\";s:7:\"version\";s:13:\"6.x-2.0-beta4\";s:3:\"tag\";s:19:\"DRUPAL-6--2-0-BETA4\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/270323\";s:13:\"download_link\";s:63:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-beta4.tar.gz\";s:4:\"date\";s:10:\"1213384535\";s:6:\"mdhash\";s:32:\"7c69feceffdef7e12ca42a479335f2bc\";s:8:\"filesize\";s:7:\"2762695\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:123:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-beta4.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-beta4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"7c69feceffdef7e12ca42a479335f2bcdfbc981f2fa7f12b7e0187650d258f3f\";s:4:\"size\";s:14:\"27626952812833\";s:8:\"filedate\";s:20:\"12133845351293229024\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.0-beta3\";a:21:{s:4:\"name\";s:19:\"views 6.x-2.0-beta3\";s:7:\"version\";s:13:\"6.x-2.0-beta3\";s:3:\"tag\";s:19:\"DRUPAL-6--2-0-BETA3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/260452\";s:13:\"download_link\";s:63:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-beta3.tar.gz\";s:4:\"date\";s:10:\"1211247918\";s:6:\"mdhash\";s:32:\"cb558adc81c9e823c10bd19f7f32680d\";s:8:\"filesize\";s:6:\"246695\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:123:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-beta3.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-beta3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"cb558adc81c9e823c10bd19f7f32680d6ecfa50af8a14971775d227ca9c861c5\";s:4:\"size\";s:12:\"246695289400\";s:8:\"filedate\";s:20:\"12112479181293229022\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.0-beta2\";a:21:{s:4:\"name\";s:19:\"views 6.x-2.0-beta2\";s:7:\"version\";s:13:\"6.x-2.0-beta2\";s:3:\"tag\";s:19:\"DRUPAL-6--2-0-BETA2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/251422\";s:13:\"download_link\";s:63:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-beta2.tar.gz\";s:4:\"date\";s:10:\"1209167713\";s:6:\"mdhash\";s:32:\"f11cc711db983d6b8be55df473f3e440\";s:8:\"filesize\";s:6:\"226958\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:123:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-beta2.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-beta2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f11cc711db983d6b8be55df473f3e4405b4a6b7df0ddea7040f69db4d6311815\";s:4:\"size\";s:12:\"226958265801\";s:8:\"filedate\";s:20:\"12091677131293229022\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:13:\"6.x-2.0-beta1\";a:21:{s:4:\"name\";s:19:\"views 6.x-2.0-beta1\";s:7:\"version\";s:13:\"6.x-2.0-beta1\";s:3:\"tag\";s:19:\"DRUPAL-6--2-0-BETA1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:5:\"beta1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/250924\";s:13:\"download_link\";s:63:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-beta1.tar.gz\";s:4:\"date\";s:10:\"1209076839\";s:6:\"mdhash\";s:32:\"abf2a3fc0ec77ed4ca641bfbcd0a577a\";s:8:\"filesize\";s:6:\"216246\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:123:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-beta1.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-beta1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"abf2a3fc0ec77ed4ca641bfbcd0a577a4529bb8dad1745f20257ea8ff2759398\";s:4:\"size\";s:12:\"216246254220\";s:8:\"filedate\";s:20:\"12090768391293229022\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-2.0-alpha5\";a:21:{s:4:\"name\";s:20:\"views 6.x-2.0-alpha5\";s:7:\"version\";s:14:\"6.x-2.0-alpha5\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA5\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha5\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/245993\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha5.tar.gz\";s:4:\"date\";s:10:\"1208050514\";s:6:\"mdhash\";s:32:\"4a0ab2a45188bb205a69d7319bfa0103\";s:8:\"filesize\";s:6:\"293424\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha5.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-alpha5.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"4a0ab2a45188bb205a69d7319bfa0103b55126a9c06125041e9c3d9c6954b6c8\";s:4:\"size\";s:12:\"293424328971\";s:8:\"filedate\";s:20:\"12080505141293229021\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-2.0-alpha4\";a:21:{s:4:\"name\";s:20:\"views 6.x-2.0-alpha4\";s:7:\"version\";s:14:\"6.x-2.0-alpha4\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA4\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha4\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/239997\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha4.tar.gz\";s:4:\"date\";s:10:\"1206753612\";s:6:\"mdhash\";s:32:\"3b60a384ff4bf4559e15530e4b68728d\";s:8:\"filesize\";s:6:\"259834\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha4.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-alpha4.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"3b60a384ff4bf4559e15530e4b68728d07dcaee0bdf90ef3f7f8bebb3a51afe2\";s:4:\"size\";s:12:\"259834285148\";s:8:\"filedate\";s:20:\"12067536121293229021\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-2.0-alpha3\";a:21:{s:4:\"name\";s:20:\"views 6.x-2.0-alpha3\";s:7:\"version\";s:14:\"6.x-2.0-alpha3\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/234752\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha3.tar.gz\";s:4:\"date\";s:10:\"1205632511\";s:6:\"mdhash\";s:32:\"378cf25063ed356d973612ffb16c06ba\";s:8:\"filesize\";s:6:\"233853\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha3.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-alpha3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"378cf25063ed356d973612ffb16c06ba0cf0b34ceb2519dc29307a41427b2ced\";s:4:\"size\";s:12:\"233853258992\";s:8:\"filedate\";s:20:\"12056325111293229020\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-2.0-alpha2\";a:21:{s:4:\"name\";s:20:\"views 6.x-2.0-alpha2\";s:7:\"version\";s:14:\"6.x-2.0-alpha2\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/223163\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha2.tar.gz\";s:4:\"date\";s:10:\"1203316508\";s:6:\"mdhash\";s:32:\"168b56a4ae8de81460ff5b9cc48a2233\";s:8:\"filesize\";s:6:\"196366\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha2.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-alpha2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"168b56a4ae8de81460ff5b9cc48a223369e4effae513c3d3418dd497f41c4f25\";s:4:\"size\";s:12:\"196366216486\";s:8:\"filedate\";s:20:\"12033165081293229020\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-2.0-alpha1\";a:21:{s:4:\"name\";s:20:\"views 6.x-2.0-alpha1\";s:7:\"version\";s:14:\"6.x-2.0-alpha1\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/222747\";s:13:\"download_link\";s:64:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha1.tar.gz\";s:4:\"date\";s:10:\"1203222009\";s:6:\"mdhash\";s:32:\"f836b5c79c2ad78cac252135febffdab\";s:8:\"filesize\";s:6:\"195064\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:125:\"http://ftp.drupal.org/files/projects/views-6.x-2.0-alpha1.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.0-alpha1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"f836b5c79c2ad78cac252135febffdabf2a9d78231855f533a2aa9b9fbe620a8\";s:4:\"size\";s:12:\"195064215123\";s:8:\"filedate\";s:20:\"12032220091293229020\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:11:\"6.x-2.x-dev\";a:19:{s:4:\"name\";s:17:\"Views 6.x-2.x-dev\";s:7:\"version\";s:11:\"6.x-2.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:28:\"http://drupal.org/node/95897\";s:13:\"download_link\";s:61:\"http://ftp.drupal.org/files/projects/views-6.x-2.x-dev.tar.gz\";s:4:\"date\";s:10:\"1296866893\";s:6:\"mdhash\";s:32:\"9f892affc9cfabcd54b30d0cac203b21\";s:8:\"filesize\";s:7:\"1625890\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:119:\"http://ftp.drupal.org/files/projects/views-6.x-2.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/views-6.x-2.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"9f892affc9cfabcd54b30d0cac203b21cfaa83a290873cd3211d80c87abd751e\";s:4:\"size\";s:14:\"16258901804681\";s:8:\"filedate\";s:20:\"12968668931296866894\";s:0:\"\";s:0:\"\";}}s:4:\"also\";a:1:{i:3;s:14:\"6.x-3.0-alpha3\";}s:14:\"latest_version\";s:8:\"6.x-2.12\";s:11:\"recommended\";s:8:\"6.x-2.12\";s:6:\"status\";i:5;}s:7:\"wysiwyg\";a:23:{s:4:\"name\";s:7:\"wysiwyg\";s:4:\"info\";a:6:{s:4:\"name\";s:7:\"Wysiwyg\";s:7:\"package\";s:14:\"User interface\";s:7:\"version\";s:7:\"6.x-2.2\";s:7:\"project\";s:7:\"wysiwyg\";s:9:\"datestamp\";s:10:\"1292817061\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1292817061\";s:8:\"includes\";a:1:{s:7:\"wysiwyg\";s:7:\"Wysiwyg\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}s:16:\"existing_version\";s:7:\"6.x-2.2\";s:14:\"existing_major\";s:1:\"2\";s:12:\"install_type\";s:8:\"official\";s:5:\"title\";s:7:\"Wysiwyg\";s:10:\"short_name\";s:7:\"wysiwyg\";s:10:\"dc:creator\";s:3:\"sun\";s:11:\"api_version\";s:3:\"6.x\";s:17:\"recommended_major\";s:1:\"2\";s:16:\"supported_majors\";s:1:\"2\";s:13:\"default_major\";s:1:\"2\";s:14:\"project_status\";s:9:\"published\";s:4:\"link\";s:33:\"http://drupal.org/project/wysiwyg\";s:8:\"releases\";a:13:{s:7:\"6.x-2.3\";a:20:{s:4:\"name\";s:15:\"wysiwyg 6.x-2.3\";s:7:\"version\";s:7:\"6.x-2.3\";s:3:\"tag\";s:13:\"DRUPAL-6--2-3\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"3\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:30:\"http://drupal.org/node/1045688\";s:13:\"download_link\";s:59:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.3.tar.gz\";s:4:\"date\";s:10:\"1296430415\";s:6:\"mdhash\";s:32:\"ac0ec7e82ba38de68c4ea8428dee648e\";s:8:\"filesize\";s:6:\"114316\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:115:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.3.tar.gzhttp://ftp.drupal.org/files/projects/wysiwyg-6.x-2.3.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"ac0ec7e82ba38de68c4ea8428dee648eb308ed4b8025f34ba961dd595d793512\";s:4:\"size\";s:12:\"114316162939\";s:8:\"filedate\";s:20:\"12964304151296430415\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.2\";a:20:{s:4:\"name\";s:15:\"wysiwyg 6.x-2.2\";s:7:\"version\";s:7:\"6.x-2.2\";s:3:\"tag\";s:13:\"DRUPAL-6--2-2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"2\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:30:\"http://drupal.org/node/1002892\";s:13:\"download_link\";s:59:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.2.tar.gz\";s:4:\"date\";s:10:\"1292817062\";s:6:\"mdhash\";s:32:\"b8ac6fcda4356d136b0251b721da597d\";s:8:\"filesize\";s:6:\"116238\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:115:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.2.tar.gzhttp://ftp.drupal.org/files/projects/wysiwyg-6.x-2.2.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"b8ac6fcda4356d136b0251b721da597d11312176b65a80ca403718081ecacd2a\";s:4:\"size\";s:12:\"116238166937\";s:8:\"filedate\";s:20:\"12928170621293235980\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.1\";a:20:{s:4:\"name\";s:15:\"wysiwyg 6.x-2.1\";s:7:\"version\";s:7:\"6.x-2.1\";s:3:\"tag\";s:13:\"DRUPAL-6--2-1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/736112\";s:13:\"download_link\";s:59:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.1.tar.gz\";s:4:\"date\";s:10:\"1268063714\";s:6:\"mdhash\";s:32:\"8a3ee47e20e9008c40ae96a6e4747a4f\";s:8:\"filesize\";s:6:\"108490\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:115:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.1.tar.gzhttp://ftp.drupal.org/files/projects/wysiwyg-6.x-2.1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"8a3ee47e20e9008c40ae96a6e4747a4f205dd71476eef40f1118d7ba9b3b9454\";s:4:\"size\";s:12:\"108490152986\";s:8:\"filedate\";s:20:\"12680637141293235980\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-2.0\";a:20:{s:4:\"name\";s:15:\"wysiwyg 6.x-2.0\";s:7:\"version\";s:7:\"6.x-2.0\";s:3:\"tag\";s:13:\"DRUPAL-6--2-0\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/487044\";s:13:\"download_link\";s:59:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.0.tar.gz\";s:4:\"date\";s:10:\"1244598972\";s:6:\"mdhash\";s:32:\"0dcc5b435b6698e61a336d32f280ed95\";s:8:\"filesize\";s:5:\"89627\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:115:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.0.tar.gzhttp://ftp.drupal.org/files/projects/wysiwyg-6.x-2.0.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"0dcc5b435b6698e61a336d32f280ed95902f277c2240082707dff0996a988bfb\";s:4:\"size\";s:11:\"89627124156\";s:8:\"filedate\";s:20:\"12445989721293235980\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:14:\"6.x-2.0-alpha1\";a:21:{s:4:\"name\";s:22:\"wysiwyg 6.x-2.0-alpha1\";s:7:\"version\";s:14:\"6.x-2.0-alpha1\";s:3:\"tag\";s:20:\"DRUPAL-6--2-0-ALPHA1\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_patch\";s:1:\"0\";s:13:\"version_extra\";s:6:\"alpha1\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/464872\";s:13:\"download_link\";s:66:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.0-alpha1.tar.gz\";s:4:\"date\";s:10:\"1242523576\";s:6:\"mdhash\";s:32:\"a745141da5436606e8bdf848cfd6da20\";s:8:\"filesize\";s:5:\"80232\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:129:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.0-alpha1.tar.gzhttp://ftp.drupal.org/files/projects/wysiwyg-6.x-2.0-alpha1.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"a745141da5436606e8bdf848cfd6da2042fbdae3f4ea5c2a50fdcacd106680e5\";s:4:\"size\";s:11:\"80232110128\";s:8:\"filedate\";s:20:\"12425235761293235981\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:12:\"New features\";}}}s:11:\"6.x-2.x-dev\";a:19:{s:4:\"name\";s:19:\"wysiwyg 6.x-2.x-dev\";s:7:\"version\";s:11:\"6.x-2.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--2\";s:13:\"version_major\";s:1:\"2\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:9:\"published\";s:12:\"release_link\";s:29:\"http://drupal.org/node/365590\";s:13:\"download_link\";s:63:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.x-dev.tar.gz\";s:4:\"date\";s:10:\"1296737459\";s:6:\"mdhash\";s:32:\"cbcbae1dca8674986d7743971461ac66\";s:8:\"filesize\";s:6:\"114456\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:10:\"\n    \n    \";s:3:\"url\";s:123:\"http://ftp.drupal.org/files/projects/wysiwyg-6.x-2.x-dev.tar.gzhttp://ftp.drupal.org/files/projects/wysiwyg-6.x-2.x-dev.zip\";s:12:\"archive_type\";s:9:\"tar.gzzip\";s:3:\"md5\";s:64:\"cbcbae1dca8674986d7743971461ac667b40b527bbb73e6a53babe43dbe6fa42\";s:4:\"size\";s:12:\"114456163015\";s:8:\"filedate\";s:20:\"12967374591296737459\";s:0:\"\";s:0:\"\";}s:7:\"6.x-1.2\";a:17:{s:4:\"name\";s:15:\"wysiwyg 6.x-1.2\";s:7:\"version\";s:7:\"6.x-1.2\";s:3:\"tag\";s:13:\"DRUPAL-6--1-2\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"2\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1242522960\";s:6:\"mdhash\";s:32:\"4d4e038fb609ad57b7430a563f03fd09\";s:8:\"filesize\";s:5:\"65875\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"4d4e038fb609ad57b7430a563f03fd09\";s:4:\"size\";s:5:\"65875\";s:8:\"filedate\";s:10:\"1242522960\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.1\";a:17:{s:4:\"name\";s:15:\"wysiwyg 6.x-1.1\";s:7:\"version\";s:7:\"6.x-1.1\";s:3:\"tag\";s:13:\"DRUPAL-6--1-1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"1\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1236562853\";s:6:\"mdhash\";s:32:\"e0d84b73c7f903d9f50e96ff39e15c4a\";s:8:\"filesize\";s:5:\"65534\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"e0d84b73c7f903d9f50e96ff39e15c4a\";s:4:\"size\";s:5:\"65534\";s:8:\"filedate\";s:10:\"1236562853\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}s:7:\"6.x-1.0\";a:17:{s:4:\"name\";s:15:\"wysiwyg 6.x-1.0\";s:7:\"version\";s:7:\"6.x-1.0\";s:3:\"tag\";s:13:\"DRUPAL-6--1-0\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_patch\";s:1:\"0\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1234552285\";s:6:\"mdhash\";s:32:\"47f4db6f8b9f711835203a1a04c4c287\";s:8:\"filesize\";s:5:\"59227\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"47f4db6f8b9f711835203a1a04c4c287\";s:4:\"size\";s:5:\"59227\";s:8:\"filedate\";s:10:\"1234552285\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:11:\"6.x-1.x-dev\";a:16:{s:4:\"name\";s:19:\"wysiwyg 6.x-1.x-dev\";s:7:\"version\";s:11:\"6.x-1.x-dev\";s:3:\"tag\";s:11:\"DRUPAL-6--1\";s:13:\"version_major\";s:1:\"1\";s:13:\"version_extra\";s:3:\"dev\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1244161854\";s:6:\"mdhash\";s:32:\"88d40ccdebd0bb3dd21f6890adf60bfd\";s:8:\"filesize\";s:5:\"71871\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"88d40ccdebd0bb3dd21f6890adf60bfd\";s:4:\"size\";s:5:\"71871\";s:8:\"filedate\";s:10:\"1244161854\";s:0:\"\";s:0:\"\";}s:7:\"6.x-0.5\";a:17:{s:4:\"name\";s:15:\"wysiwyg 6.x-0.5\";s:7:\"version\";s:7:\"6.x-0.5\";s:3:\"tag\";s:13:\"DRUPAL-6--0-5\";s:13:\"version_major\";s:1:\"0\";s:13:\"version_patch\";s:1:\"5\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1228142425\";s:6:\"mdhash\";s:32:\"dfc9b006642cda543fd17c841462cee2\";s:8:\"filesize\";s:5:\"54206\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"dfc9b006642cda543fd17c841462cee2\";s:4:\"size\";s:5:\"54206\";s:8:\"filedate\";s:10:\"1228142425\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-0.4\";a:17:{s:4:\"name\";s:15:\"wysiwyg 6.x-0.4\";s:7:\"version\";s:7:\"6.x-0.4\";s:3:\"tag\";s:13:\"DRUPAL-6--0-4\";s:13:\"version_major\";s:1:\"0\";s:13:\"version_patch\";s:1:\"4\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1224021920\";s:6:\"mdhash\";s:32:\"db01863f705e57477d6508bd083c75f2\";s:8:\"filesize\";s:5:\"50865\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"db01863f705e57477d6508bd083c75f2\";s:4:\"size\";s:5:\"50865\";s:8:\"filedate\";s:10:\"1224021920\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:2:{i:0;s:12:\"New features\";i:1;s:9:\"Bug fixes\";}}}s:7:\"6.x-0.3\";a:17:{s:4:\"name\";s:15:\"wysiwyg 6.x-0.3\";s:7:\"version\";s:7:\"6.x-0.3\";s:3:\"tag\";s:13:\"DRUPAL-6--0-3\";s:13:\"version_major\";s:1:\"0\";s:13:\"version_patch\";s:1:\"3\";s:6:\"status\";s:11:\"unpublished\";s:4:\"date\";s:10:\"1221251441\";s:6:\"mdhash\";s:32:\"3fd04f042435a957e4abed89ab71e4ea\";s:8:\"filesize\";s:5:\"45967\";s:5:\"files\";s:4:\"\n   \";s:4:\"file\";s:5:\"\n    \";s:12:\"archive_type\";s:6:\"tar.gz\";s:3:\"md5\";s:32:\"3fd04f042435a957e4abed89ab71e4ea\";s:4:\"size\";s:5:\"45967\";s:8:\"filedate\";s:10:\"1221251441\";s:0:\"\";s:0:\"\";s:5:\"terms\";a:1:{s:12:\"Release type\";a:1:{i:0;s:9:\"Bug fixes\";}}}}s:14:\"latest_version\";s:7:\"6.x-2.3\";s:11:\"recommended\";s:7:\"6.x-2.3\";s:6:\"status\";i:4;}}',1296910555,1296906955,NULL,1),('update_project_projects','a:20:{s:10:\"admin_menu\";a:7:{s:4:\"name\";s:10:\"admin_menu\";s:4:\"info\";a:6:{s:4:\"name\";s:19:\"Administration menu\";s:7:\"package\";s:14:\"Administration\";s:7:\"version\";s:7:\"6.x-1.6\";s:7:\"project\";s:10:\"admin_menu\";s:9:\"datestamp\";s:10:\"1283512306\";s:16:\"_info_file_ctime\";i:1296890116;}s:9:\"datestamp\";s:10:\"1283512306\";s:8:\"includes\";a:1:{s:10:\"admin_menu\";s:19:\"Administration menu\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:13:\"advanced_help\";a:7:{s:4:\"name\";s:13:\"advanced_help\";s:4:\"info\";a:5:{s:4:\"name\";s:13:\"Advanced help\";s:7:\"version\";s:7:\"6.x-1.2\";s:7:\"project\";s:13:\"advanced_help\";s:9:\"datestamp\";s:10:\"1238954409\";s:16:\"_info_file_ctime\";i:1296890111;}s:9:\"datestamp\";s:10:\"1238954409\";s:8:\"includes\";a:1:{s:13:\"advanced_help\";s:13:\"Advanced help\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:6:\"drupal\";a:7:{s:4:\"name\";s:6:\"drupal\";s:4:\"info\";a:6:{s:4:\"name\";s:5:\"Block\";s:7:\"package\";s:15:\"Core - required\";s:7:\"version\";s:4:\"6.20\";s:7:\"project\";s:6:\"drupal\";s:9:\"datestamp\";s:10:\"1292447788\";s:16:\"_info_file_ctime\";i:1296890116;}s:9:\"datestamp\";s:10:\"1292447788\";s:8:\"includes\";a:10:{s:5:\"block\";s:5:\"Block\";s:7:\"contact\";s:7:\"Contact\";s:6:\"filter\";s:6:\"Filter\";s:4:\"menu\";s:4:\"Menu\";s:4:\"node\";s:4:\"Node\";s:4:\"path\";s:4:\"Path\";s:6:\"system\";s:6:\"System\";s:6:\"update\";s:13:\"Update status\";s:4:\"user\";s:4:\"User\";s:3:\"fwt\";s:18:\"Fifth Wave Trading\";}s:12:\"project_type\";s:4:\"core\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:7:\"captcha\";a:7:{s:4:\"name\";s:7:\"captcha\";s:4:\"info\";a:6:{s:4:\"name\";s:7:\"CAPTCHA\";s:7:\"package\";s:12:\"Spam control\";s:7:\"version\";s:7:\"6.x-2.3\";s:7:\"project\";s:7:\"captcha\";s:9:\"datestamp\";s:10:\"1289346944\";s:16:\"_info_file_ctime\";i:1296890116;}s:9:\"datestamp\";s:10:\"1289346944\";s:8:\"includes\";a:2:{s:7:\"captcha\";s:7:\"CAPTCHA\";s:13:\"image_captcha\";s:13:\"Image CAPTCHA\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:19:\"cck_fieldgroup_tabs\";a:7:{s:4:\"name\";s:19:\"cck_fieldgroup_tabs\";s:4:\"info\";a:6:{s:4:\"name\";s:19:\"CCK Fieldgroup Tabs\";s:7:\"package\";s:3:\"CCK\";s:7:\"version\";s:7:\"6.x-1.2\";s:7:\"project\";s:19:\"cck_fieldgroup_tabs\";s:9:\"datestamp\";s:10:\"1264602006\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1264602006\";s:8:\"includes\";a:1:{s:19:\"cck_fieldgroup_tabs\";s:19:\"CCK Fieldgroup Tabs\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:11:\"contemplate\";a:7:{s:4:\"name\";s:11:\"contemplate\";s:4:\"info\";a:6:{s:4:\"name\";s:17:\"Content Templates\";s:7:\"package\";s:3:\"CCK\";s:7:\"version\";s:7:\"6.x-1.2\";s:7:\"project\";s:11:\"contemplate\";s:9:\"datestamp\";s:10:\"1279686006\";s:16:\"_info_file_ctime\";i:1296890108;}s:9:\"datestamp\";s:10:\"1279686006\";s:8:\"includes\";a:1:{s:11:\"contemplate\";s:17:\"Content Templates\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:3:\"cck\";a:7:{s:4:\"name\";s:3:\"cck\";s:4:\"info\";a:6:{s:4:\"name\";s:7:\"Content\";s:7:\"package\";s:3:\"CCK\";s:7:\"version\";s:7:\"6.x-2.9\";s:7:\"project\";s:3:\"cck\";s:9:\"datestamp\";s:10:\"1294407979\";s:16:\"_info_file_ctime\";i:1296890116;}s:9:\"datestamp\";s:10:\"1294407979\";s:8:\"includes\";a:9:{s:7:\"content\";s:7:\"Content\";s:12:\"content_copy\";s:12:\"Content Copy\";s:19:\"content_permissions\";s:19:\"Content Permissions\";s:10:\"fieldgroup\";s:10:\"Fieldgroup\";s:13:\"nodereference\";s:14:\"Node Reference\";s:6:\"number\";s:6:\"Number\";s:13:\"optionwidgets\";s:14:\"Option Widgets\";s:4:\"text\";s:4:\"Text\";s:13:\"userreference\";s:14:\"User Reference\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:6:\"ctools\";a:7:{s:4:\"name\";s:6:\"ctools\";s:4:\"info\";a:6:{s:4:\"name\";s:11:\"Chaos tools\";s:7:\"package\";s:16:\"Chaos tool suite\";s:7:\"version\";s:7:\"6.x-1.8\";s:7:\"project\";s:6:\"ctools\";s:9:\"datestamp\";s:10:\"1288393844\";s:16:\"_info_file_ctime\";i:1296890115;}s:9:\"datestamp\";s:10:\"1288393844\";s:8:\"includes\";a:8:{s:6:\"ctools\";s:11:\"Chaos tools\";s:21:\"ctools_access_ruleset\";s:15:\"Custom rulesets\";s:18:\"ctools_ajax_sample\";s:33:\"Chaos Tools (CTools) AJAX Example\";s:21:\"ctools_custom_content\";s:20:\"Custom content panes\";s:21:\"ctools_plugin_example\";s:35:\"Chaos Tools (CTools) Plugin Example\";s:12:\"page_manager\";s:12:\"Page manager\";s:8:\"stylizer\";s:8:\"Stylizer\";s:13:\"views_content\";s:19:\"Views content panes\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:5:\"devel\";a:7:{s:4:\"name\";s:5:\"devel\";s:4:\"info\";a:6:{s:4:\"name\";s:5:\"Devel\";s:7:\"package\";s:11:\"Development\";s:7:\"version\";s:8:\"6.x-1.23\";s:7:\"project\";s:5:\"devel\";s:9:\"datestamp\";s:10:\"1291650062\";s:16:\"_info_file_ctime\";i:1296890110;}s:9:\"datestamp\";s:10:\"1291650062\";s:8:\"includes\";a:3:{s:5:\"devel\";s:5:\"Devel\";s:14:\"devel_generate\";s:14:\"Devel generate\";s:17:\"devel_node_access\";s:17:\"Devel node access\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:9:\"filefield\";a:7:{s:4:\"name\";s:9:\"filefield\";s:4:\"info\";a:6:{s:4:\"name\";s:9:\"FileField\";s:7:\"package\";s:3:\"CCK\";s:7:\"version\";s:7:\"6.x-3.9\";s:7:\"project\";s:9:\"filefield\";s:9:\"datestamp\";s:10:\"1292197563\";s:16:\"_info_file_ctime\";i:1296890114;}s:9:\"datestamp\";s:10:\"1292197563\";s:8:\"includes\";a:1:{s:9:\"filefield\";s:9:\"FileField\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:9:\"jquery_ui\";a:7:{s:4:\"name\";s:9:\"jquery_ui\";s:4:\"info\";a:6:{s:4:\"name\";s:9:\"jQuery UI\";s:7:\"package\";s:14:\"User interface\";s:7:\"version\";s:7:\"6.x-1.4\";s:7:\"project\";s:9:\"jquery_ui\";s:9:\"datestamp\";s:10:\"1284001909\";s:16:\"_info_file_ctime\";i:1296890111;}s:9:\"datestamp\";s:10:\"1284001909\";s:8:\"includes\";a:1:{s:9:\"jquery_ui\";s:9:\"jQuery UI\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:13:\"jquery_update\";a:7:{s:4:\"name\";s:13:\"jquery_update\";s:4:\"info\";a:6:{s:4:\"name\";s:13:\"jQuery Update\";s:7:\"package\";s:14:\"User Interface\";s:7:\"version\";s:7:\"6.x-1.1\";s:7:\"project\";s:13:\"jquery_update\";s:9:\"datestamp\";s:10:\"1214262616\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1214262616\";s:8:\"includes\";a:1:{s:13:\"jquery_update\";s:13:\"jQuery Update\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:4:\"link\";a:7:{s:4:\"name\";s:4:\"link\";s:4:\"info\";a:6:{s:4:\"name\";s:4:\"Link\";s:7:\"package\";s:3:\"CCK\";s:7:\"version\";s:7:\"6.x-2.9\";s:7:\"project\";s:4:\"link\";s:9:\"datestamp\";s:10:\"1276539609\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1276539609\";s:8:\"includes\";a:1:{s:4:\"link\";s:4:\"Link\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:12:\"mobileplugin\";a:7:{s:4:\"name\";s:12:\"mobileplugin\";s:4:\"info\";a:6:{s:4:\"name\";s:13:\"Mobile Plugin\";s:7:\"package\";s:6:\"Mobile\";s:7:\"version\";s:7:\"6.x-2.0\";s:7:\"project\";s:12:\"mobileplugin\";s:9:\"datestamp\";s:10:\"1264526408\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1264526408\";s:8:\"includes\";a:1:{s:12:\"mobileplugin\";s:13:\"Mobile Plugin\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:10:\"multiblock\";a:7:{s:4:\"name\";s:10:\"multiblock\";s:4:\"info\";a:5:{s:4:\"name\";s:10:\"MultiBlock\";s:7:\"version\";s:7:\"6.x-1.3\";s:7:\"project\";s:10:\"multiblock\";s:9:\"datestamp\";s:10:\"1233076829\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1233076829\";s:8:\"includes\";a:1:{s:10:\"multiblock\";s:10:\"MultiBlock\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:6:\"panels\";a:7:{s:4:\"name\";s:6:\"panels\";s:4:\"info\";a:6:{s:4:\"name\";s:6:\"Panels\";s:7:\"package\";s:6:\"Panels\";s:7:\"version\";s:7:\"6.x-3.9\";s:7:\"project\";s:6:\"panels\";s:9:\"datestamp\";s:10:\"1294876603\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1294876603\";s:8:\"includes\";a:4:{s:6:\"panels\";s:6:\"Panels\";s:10:\"panels_ipe\";s:22:\"Panels In-Place Editor\";s:11:\"panels_mini\";s:11:\"Mini panels\";s:11:\"panels_node\";s:11:\"Panel nodes\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:11:\"panels_tabs\";a:7:{s:4:\"name\";s:11:\"panels_tabs\";s:4:\"info\";a:6:{s:4:\"name\";s:16:\"Tabs panel style\";s:7:\"package\";s:20:\"Panels style plugins\";s:7:\"version\";s:11:\"6.x-1.0-rc6\";s:7:\"project\";s:11:\"panels_tabs\";s:9:\"datestamp\";s:10:\"1286015464\";s:16:\"_info_file_ctime\";i:1296890116;}s:9:\"datestamp\";s:10:\"1286015464\";s:8:\"includes\";a:1:{s:11:\"panels_tabs\";s:16:\"Tabs panel style\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:4:\"tabs\";a:7:{s:4:\"name\";s:4:\"tabs\";s:4:\"info\";a:5:{s:4:\"name\";s:4:\"Tabs\";s:7:\"version\";s:7:\"6.x-1.3\";s:7:\"project\";s:4:\"tabs\";s:9:\"datestamp\";s:10:\"1264529109\";s:16:\"_info_file_ctime\";i:1296890108;}s:9:\"datestamp\";s:10:\"1264529109\";s:8:\"includes\";a:1:{s:4:\"tabs\";s:4:\"Tabs\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:5:\"views\";a:7:{s:4:\"name\";s:5:\"views\";s:4:\"info\";a:6:{s:4:\"name\";s:5:\"Views\";s:7:\"package\";s:5:\"Views\";s:7:\"version\";s:8:\"6.x-2.12\";s:7:\"project\";s:5:\"views\";s:9:\"datestamp\";s:10:\"1292446272\";s:16:\"_info_file_ctime\";i:1296890114;}s:9:\"datestamp\";s:10:\"1292446272\";s:8:\"includes\";a:3:{s:5:\"views\";s:5:\"Views\";s:12:\"views_export\";s:14:\"Views exporter\";s:8:\"views_ui\";s:8:\"Views UI\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}s:7:\"wysiwyg\";a:7:{s:4:\"name\";s:7:\"wysiwyg\";s:4:\"info\";a:6:{s:4:\"name\";s:7:\"Wysiwyg\";s:7:\"package\";s:14:\"User interface\";s:7:\"version\";s:7:\"6.x-2.2\";s:7:\"project\";s:7:\"wysiwyg\";s:9:\"datestamp\";s:10:\"1292817061\";s:16:\"_info_file_ctime\";i:1296890109;}s:9:\"datestamp\";s:10:\"1292817061\";s:8:\"includes\";a:1:{s:7:\"wysiwyg\";s:7:\"Wysiwyg\";}s:12:\"project_type\";s:6:\"module\";s:10:\"sub_themes\";a:0:{}s:11:\"base_themes\";a:0:{}}}',1297032758,1297029158,NULL,1);

--
-- Table structure for table `cache_views`
--

CREATE TABLE `cache_views` (
  `cid` varchar(255) NOT NULL DEFAULT '',
  `data` longblob,
  `expire` int(11) NOT NULL DEFAULT '0',
  `created` int(11) NOT NULL DEFAULT '0',
  `headers` text,
  `serialized` smallint(6) NOT NULL DEFAULT '0',
  PRIMARY KEY (`cid`),
  KEY `expire` (`expire`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `cache_views`
--

INSERT INTO `cache_views` VALUES ('views_default_views_index:en','a:3:{i:0;s:9:\"frontpage\";i:1;s:8:\"glossary\";i:2;s:7:\"archive\";}',0,1295785759,'',1),('views_default:frontpage:en','O:4:\"view\":23:{s:8:\"db_table\";s:10:\"views_view\";s:10:\"base_table\";s:4:\"node\";s:5:\"built\";b:0;s:8:\"executed\";b:0;s:4:\"args\";a:0:{}s:10:\"build_info\";a:0:{}s:8:\"use_ajax\";b:0;s:6:\"result\";a:0:{}s:5:\"pager\";a:5:{s:9:\"use_pager\";b:0;s:14:\"items_per_page\";i:10;s:7:\"element\";i:0;s:6:\"offset\";i:0;s:12:\"current_page\";i:0;}s:17:\"attachment_before\";s:0:\"\";s:16:\"attachment_after\";s:0:\"\";s:12:\"exposed_data\";a:0:{}s:13:\"exposed_input\";a:0:{}s:8:\"old_view\";a:0:{}s:3:\"vid\";s:0:\"\";s:4:\"name\";s:9:\"frontpage\";s:11:\"description\";s:119:\"Emulates the default Drupal front page; you may set the default home page path to this view to make it your front page.\";s:3:\"tag\";s:7:\"default\";s:8:\"view_php\";s:0:\"\";s:12:\"is_cacheable\";s:1:\"0\";s:7:\"display\";a:3:{s:7:\"default\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:7:\"default\";s:13:\"display_title\";s:8:\"Defaults\";s:14:\"display_plugin\";s:7:\"default\";s:8:\"position\";i:0;s:15:\"display_options\";a:15:{s:5:\"sorts\";a:2:{s:6:\"sticky\";a:4:{s:2:\"id\";s:6:\"sticky\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:6:\"sticky\";s:5:\"order\";s:4:\"DESC\";}s:7:\"created\";a:6:{s:2:\"id\";s:7:\"created\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:7:\"created\";s:5:\"order\";s:4:\"DESC\";s:12:\"relationship\";s:4:\"none\";s:11:\"granularity\";s:6:\"second\";}}s:8:\"defaults\";a:11:{s:5:\"sorts\";b:0;s:7:\"filters\";b:0;s:6:\"access\";b:0;s:14:\"items_per_page\";b:0;s:6:\"offset\";b:0;s:9:\"use_pager\";b:0;s:13:\"pager_element\";b:0;s:12:\"style_plugin\";b:0;s:13:\"style_options\";b:0;s:10:\"row_plugin\";b:0;s:11:\"row_options\";b:0;}s:7:\"filters\";a:2:{s:7:\"promote\";a:8:{s:2:\"id\";s:7:\"promote\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:7:\"promote\";s:8:\"operator\";s:1:\"=\";s:5:\"value\";s:1:\"1\";s:5:\"group\";i:0;s:7:\"exposed\";b:0;s:6:\"expose\";a:2:{s:8:\"operator\";b:0;s:5:\"label\";s:0:\"\";}}s:6:\"status\";a:8:{s:2:\"id\";s:6:\"status\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:6:\"status\";s:8:\"operator\";s:1:\"=\";s:5:\"value\";s:1:\"1\";s:5:\"group\";i:0;s:7:\"exposed\";b:0;s:6:\"expose\";a:2:{s:8:\"operator\";b:0;s:5:\"label\";s:0:\"\";}}}s:6:\"access\";a:3:{s:4:\"type\";s:4:\"none\";s:4:\"role\";a:0:{}s:4:\"perm\";s:0:\"\";}s:13:\"header_format\";s:1:\"1\";s:13:\"footer_format\";s:1:\"1\";s:12:\"empty_format\";s:1:\"1\";s:14:\"items_per_page\";i:10;s:6:\"offset\";i:0;s:9:\"use_pager\";s:1:\"1\";s:13:\"pager_element\";i:0;s:12:\"style_plugin\";s:7:\"default\";s:13:\"style_options\";a:0:{}s:10:\"row_plugin\";s:4:\"node\";s:11:\"row_options\";a:2:{s:6:\"teaser\";i:1;s:5:\"links\";i:1;}}}s:4:\"page\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:4:\"page\";s:13:\"display_title\";s:4:\"Page\";s:14:\"display_plugin\";s:4:\"page\";s:8:\"position\";i:0;s:15:\"display_options\";a:3:{s:4:\"path\";s:9:\"frontpage\";s:4:\"menu\";a:3:{s:4:\"type\";s:4:\"none\";s:5:\"title\";s:0:\"\";s:6:\"weight\";i:0;}s:11:\"tab_options\";a:3:{s:4:\"type\";s:4:\"none\";s:5:\"title\";s:0:\"\";s:6:\"weight\";i:0;}}}s:4:\"feed\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:4:\"feed\";s:13:\"display_title\";s:4:\"Feed\";s:14:\"display_plugin\";s:4:\"feed\";s:8:\"position\";i:0;s:15:\"display_options\";a:10:{s:14:\"sitename_title\";s:1:\"1\";s:5:\"title\";s:15:\"Front page feed\";s:8:\"defaults\";a:2:{s:5:\"title\";b:0;s:14:\"sitename_title\";b:0;}s:13:\"style_options\";a:2:{s:19:\"mission_description\";i:1;s:11:\"description\";s:0:\"\";}s:10:\"row_plugin\";s:8:\"node_rss\";s:11:\"row_options\";a:1:{s:11:\"item_length\";s:7:\"default\";}s:4:\"path\";s:7:\"rss.xml\";s:4:\"menu\";a:3:{s:4:\"type\";s:4:\"none\";s:5:\"title\";s:0:\"\";s:6:\"weight\";i:0;}s:11:\"tab_options\";a:3:{s:4:\"type\";s:4:\"none\";s:5:\"title\";s:0:\"\";s:6:\"weight\";i:0;}s:8:\"displays\";a:2:{s:7:\"default\";s:7:\"default\";s:4:\"page\";s:4:\"page\";}}}}s:11:\"api_version\";i:2;s:8:\"disabled\";b:1;}',0,1295785759,'',1),('views_default:glossary:en','O:4:\"view\":23:{s:8:\"db_table\";s:10:\"views_view\";s:10:\"base_table\";s:4:\"node\";s:5:\"built\";b:0;s:8:\"executed\";b:0;s:4:\"args\";a:0:{}s:10:\"build_info\";a:0:{}s:8:\"use_ajax\";b:0;s:6:\"result\";a:0:{}s:5:\"pager\";a:5:{s:9:\"use_pager\";b:0;s:14:\"items_per_page\";i:10;s:7:\"element\";i:0;s:6:\"offset\";i:0;s:12:\"current_page\";i:0;}s:17:\"attachment_before\";s:0:\"\";s:16:\"attachment_after\";s:0:\"\";s:12:\"exposed_data\";a:0:{}s:13:\"exposed_input\";a:0:{}s:8:\"old_view\";a:0:{}s:3:\"vid\";s:0:\"\";s:4:\"name\";s:8:\"glossary\";s:11:\"description\";s:33:\"A list of all content, by letter.\";s:3:\"tag\";s:7:\"default\";s:8:\"view_php\";s:0:\"\";s:12:\"is_cacheable\";s:1:\"0\";s:7:\"display\";a:3:{s:7:\"default\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:7:\"default\";s:13:\"display_title\";s:8:\"Defaults\";s:14:\"display_plugin\";s:7:\"default\";s:8:\"position\";i:0;s:15:\"display_options\";a:13:{s:6:\"fields\";a:3:{s:5:\"title\";a:7:{s:5:\"label\";s:5:\"Title\";s:12:\"link_to_node\";i:1;s:7:\"exclude\";i:0;s:2:\"id\";s:5:\"title\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:5:\"title\";s:12:\"relationship\";s:4:\"none\";}s:4:\"name\";a:7:{s:5:\"label\";s:6:\"Author\";s:12:\"link_to_user\";i:1;s:7:\"exclude\";i:0;s:2:\"id\";s:4:\"name\";s:5:\"table\";s:5:\"users\";s:5:\"field\";s:4:\"name\";s:12:\"relationship\";s:4:\"none\";}s:7:\"changed\";a:8:{s:5:\"label\";s:11:\"Last update\";s:11:\"date_format\";s:5:\"large\";s:18:\"custom_date_format\";s:0:\"\";s:7:\"exclude\";i:0;s:2:\"id\";s:7:\"changed\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:7:\"changed\";s:12:\"relationship\";s:4:\"none\";}}s:8:\"defaults\";a:12:{s:6:\"fields\";b:0;s:9:\"arguments\";b:0;s:6:\"access\";b:0;s:8:\"use_ajax\";b:0;s:14:\"items_per_page\";b:0;s:6:\"offset\";b:0;s:9:\"use_pager\";b:0;s:13:\"pager_element\";b:0;s:12:\"style_plugin\";b:0;s:13:\"style_options\";b:0;s:10:\"row_plugin\";b:0;s:11:\"row_options\";b:0;}s:9:\"arguments\";a:1:{s:5:\"title\";a:25:{s:14:\"default_action\";s:7:\"default\";s:12:\"style_plugin\";s:15:\"default_summary\";s:13:\"style_options\";a:0:{}s:8:\"wildcard\";s:3:\"all\";s:21:\"wildcard_substitution\";s:3:\"All\";s:5:\"title\";s:0:\"\";s:21:\"default_argument_type\";s:5:\"fixed\";s:16:\"default_argument\";s:0:\"\";s:13:\"validate_type\";s:4:\"none\";s:13:\"validate_fail\";s:9:\"not found\";s:8:\"glossary\";i:1;s:5:\"limit\";s:1:\"1\";s:4:\"case\";s:5:\"upper\";s:9:\"path_case\";s:5:\"lower\";s:14:\"transform_dash\";i:0;s:2:\"id\";s:5:\"title\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:5:\"title\";s:12:\"relationship\";s:4:\"none\";s:21:\"default_argument_user\";i:0;s:22:\"default_argument_fixed\";s:1:\"a\";s:20:\"default_argument_php\";s:0:\"\";s:28:\"validate_argument_vocabulary\";a:0:{}s:22:\"validate_argument_type\";s:3:\"tid\";s:21:\"validate_argument_php\";s:0:\"\";}}s:6:\"access\";a:3:{s:4:\"type\";s:4:\"none\";s:4:\"role\";a:0:{}s:4:\"perm\";s:0:\"\";}s:8:\"use_ajax\";s:1:\"1\";s:14:\"items_per_page\";i:36;s:6:\"offset\";i:0;s:9:\"use_pager\";s:1:\"1\";s:13:\"pager_element\";i:0;s:12:\"style_plugin\";s:5:\"table\";s:13:\"style_options\";a:7:{s:8:\"grouping\";s:0:\"\";s:8:\"override\";i:1;s:6:\"sticky\";i:0;s:5:\"order\";s:3:\"asc\";s:7:\"columns\";a:3:{s:5:\"title\";s:5:\"title\";s:4:\"name\";s:4:\"name\";s:7:\"changed\";s:7:\"changed\";}s:4:\"info\";a:3:{s:5:\"title\";a:2:{s:8:\"sortable\";i:1;s:9:\"separator\";s:0:\"\";}s:4:\"name\";a:2:{s:8:\"sortable\";i:1;s:9:\"separator\";s:0:\"\";}s:7:\"changed\";a:2:{s:8:\"sortable\";i:1;s:9:\"separator\";s:0:\"\";}}s:7:\"default\";s:5:\"title\";}s:10:\"row_plugin\";s:6:\"fields\";s:11:\"row_options\";a:0:{}}}s:4:\"page\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:4:\"page\";s:13:\"display_title\";s:4:\"Page\";s:14:\"display_plugin\";s:4:\"page\";s:8:\"position\";i:0;s:15:\"display_options\";a:3:{s:4:\"path\";s:8:\"glossary\";s:4:\"menu\";a:3:{s:4:\"type\";s:6:\"normal\";s:5:\"title\";s:8:\"Glossary\";s:6:\"weight\";s:1:\"0\";}s:11:\"tab_options\";a:3:{s:4:\"type\";s:4:\"none\";s:5:\"title\";s:0:\"\";s:6:\"weight\";i:0;}}}s:10:\"attachment\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:10:\"attachment\";s:13:\"display_title\";s:10:\"Attachment\";s:14:\"display_plugin\";s:10:\"attachment\";s:8:\"position\";i:0;s:15:\"display_options\";a:4:{s:9:\"arguments\";a:1:{s:5:\"title\";a:23:{s:14:\"default_action\";s:11:\"summary asc\";s:12:\"style_plugin\";s:19:\"unformatted_summary\";s:13:\"style_options\";a:5:{s:5:\"count\";i:1;s:8:\"override\";i:0;s:14:\"items_per_page\";s:2:\"25\";s:6:\"inline\";i:1;s:9:\"separator\";s:3:\" | \";}s:8:\"wildcard\";s:3:\"all\";s:21:\"wildcard_substitution\";s:3:\"All\";s:5:\"title\";s:0:\"\";s:21:\"default_argument_type\";s:5:\"fixed\";s:16:\"default_argument\";s:0:\"\";s:13:\"validate_type\";s:4:\"none\";s:13:\"validate_fail\";s:9:\"not found\";s:8:\"glossary\";i:1;s:5:\"limit\";s:1:\"1\";s:4:\"case\";s:5:\"upper\";s:9:\"path_case\";s:5:\"lower\";s:14:\"transform_dash\";i:0;s:2:\"id\";s:5:\"title\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:5:\"title\";s:12:\"relationship\";s:4:\"none\";s:21:\"default_argument_user\";i:0;s:22:\"default_argument_fixed\";s:1:\"a\";s:28:\"validate_argument_vocabulary\";a:0:{}s:21:\"validate_argument_php\";s:0:\"\";}}s:8:\"defaults\";a:1:{s:9:\"arguments\";b:0;}s:17:\"inherit_arguments\";i:0;s:8:\"displays\";a:2:{s:7:\"default\";s:7:\"default\";s:4:\"page\";s:4:\"page\";}}}}s:11:\"api_version\";i:2;s:8:\"disabled\";b:1;}',0,1295785759,'',1),('views_default:archive:en','O:4:\"view\":23:{s:8:\"db_table\";s:10:\"views_view\";s:10:\"base_table\";s:4:\"node\";s:5:\"built\";b:0;s:8:\"executed\";b:0;s:4:\"args\";a:0:{}s:10:\"build_info\";a:0:{}s:8:\"use_ajax\";b:0;s:6:\"result\";a:0:{}s:5:\"pager\";a:5:{s:9:\"use_pager\";b:0;s:14:\"items_per_page\";i:10;s:7:\"element\";i:0;s:6:\"offset\";i:0;s:12:\"current_page\";i:0;}s:17:\"attachment_before\";s:0:\"\";s:16:\"attachment_after\";s:0:\"\";s:12:\"exposed_data\";a:0:{}s:13:\"exposed_input\";a:0:{}s:8:\"old_view\";a:0:{}s:3:\"vid\";s:0:\"\";s:4:\"name\";s:7:\"archive\";s:11:\"description\";s:61:\"Display a list of months that link to content for that month.\";s:3:\"tag\";s:7:\"default\";s:8:\"view_php\";s:0:\"\";s:12:\"is_cacheable\";s:1:\"0\";s:7:\"display\";a:3:{s:7:\"default\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:7:\"default\";s:13:\"display_title\";s:8:\"Defaults\";s:14:\"display_plugin\";s:7:\"default\";s:8:\"position\";i:0;s:15:\"display_options\";a:14:{s:5:\"title\";s:15:\"Monthly archive\";s:8:\"defaults\";a:13:{s:5:\"title\";b:0;s:5:\"sorts\";b:0;s:9:\"arguments\";b:0;s:7:\"filters\";b:0;s:6:\"access\";b:0;s:14:\"items_per_page\";b:0;s:6:\"offset\";b:0;s:9:\"use_pager\";b:0;s:13:\"pager_element\";b:0;s:12:\"style_plugin\";b:0;s:13:\"style_options\";b:0;s:10:\"row_plugin\";b:0;s:11:\"row_options\";b:0;}s:5:\"sorts\";a:1:{s:7:\"created\";a:6:{s:2:\"id\";s:7:\"created\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:7:\"created\";s:5:\"order\";s:4:\"DESC\";s:11:\"granularity\";s:6:\"second\";s:12:\"relationship\";s:4:\"none\";}}s:9:\"arguments\";a:1:{s:18:\"created_year_month\";a:13:{s:2:\"id\";s:18:\"created_year_month\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:18:\"created_year_month\";s:14:\"default_action\";s:12:\"summary desc\";s:12:\"style_plugin\";s:15:\"default_summary\";s:13:\"style_options\";a:3:{s:5:\"count\";i:1;s:8:\"override\";i:1;s:14:\"items_per_page\";s:2:\"30\";}s:8:\"wildcard\";s:3:\"all\";s:21:\"wildcard_substitution\";s:3:\"All\";s:5:\"title\";s:2:\"%1\";s:12:\"relationship\";s:4:\"none\";s:13:\"validate_type\";s:4:\"none\";s:13:\"validate_fail\";s:9:\"not found\";s:21:\"default_argument_type\";s:5:\"fixed\";}}s:7:\"filters\";a:1:{s:6:\"status\";a:9:{s:2:\"id\";s:6:\"status\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:6:\"status\";s:8:\"operator\";s:1:\"=\";s:5:\"value\";i:1;s:5:\"group\";i:0;s:7:\"exposed\";b:0;s:6:\"expose\";a:2:{s:8:\"operator\";b:0;s:5:\"label\";s:0:\"\";}s:12:\"relationship\";s:4:\"none\";}}s:6:\"access\";a:3:{s:4:\"type\";s:4:\"none\";s:4:\"role\";a:0:{}s:4:\"perm\";s:0:\"\";}s:14:\"items_per_page\";i:10;s:6:\"offset\";i:0;s:9:\"use_pager\";s:1:\"1\";s:13:\"pager_element\";i:0;s:12:\"style_plugin\";s:7:\"default\";s:13:\"style_options\";a:0:{}s:10:\"row_plugin\";s:4:\"node\";s:11:\"row_options\";a:2:{s:6:\"teaser\";b:1;s:5:\"links\";b:1;}}}s:4:\"page\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:4:\"page\";s:13:\"display_title\";s:4:\"Page\";s:14:\"display_plugin\";s:4:\"page\";s:8:\"position\";i:0;s:15:\"display_options\";a:3:{s:4:\"path\";s:7:\"archive\";s:4:\"menu\";a:3:{s:4:\"type\";s:4:\"none\";s:5:\"title\";s:0:\"\";s:6:\"weight\";i:0;}s:11:\"tab_options\";a:3:{s:4:\"type\";s:4:\"none\";s:5:\"title\";s:0:\"\";s:6:\"weight\";i:0;}}}s:5:\"block\";O:13:\"views_display\":7:{s:8:\"db_table\";s:13:\"views_display\";s:3:\"vid\";i:0;s:2:\"id\";s:5:\"block\";s:13:\"display_title\";s:5:\"Block\";s:14:\"display_plugin\";s:5:\"block\";s:8:\"position\";i:0;s:15:\"display_options\";a:3:{s:9:\"arguments\";a:1:{s:18:\"created_year_month\";a:13:{s:2:\"id\";s:18:\"created_year_month\";s:5:\"table\";s:4:\"node\";s:5:\"field\";s:18:\"created_year_month\";s:14:\"default_action\";s:11:\"summary asc\";s:12:\"style_plugin\";s:15:\"default_summary\";s:13:\"style_options\";a:3:{s:5:\"count\";i:1;s:8:\"override\";i:0;s:14:\"items_per_page\";s:2:\"30\";}s:8:\"wildcard\";s:3:\"all\";s:21:\"wildcard_substitution\";s:3:\"All\";s:5:\"title\";s:2:\"%1\";s:12:\"relationship\";s:4:\"none\";s:13:\"validate_type\";s:4:\"none\";s:13:\"validate_fail\";s:9:\"not found\";s:21:\"default_argument_type\";s:5:\"fixed\";}}s:8:\"defaults\";a:1:{s:9:\"arguments\";b:0;}s:17:\"block_description\";s:12:\"Archive list\";}}}s:11:\"api_version\";i:2;s:8:\"disabled\";b:1;}',0,1295785759,'',1);

--
-- Table structure for table `cache_views_data`
--

CREATE TABLE `cache_views_data` (
  `cid` varchar(255) NOT NULL DEFAULT '',
  `data` longblob,
  `expire` int(11) NOT NULL DEFAULT '0',
  `created` int(11) NOT NULL DEFAULT '0',
  `headers` text,
  `serialized` smallint(6) NOT NULL DEFAULT '1',
  PRIMARY KEY (`cid`),
  KEY `expire` (`expire`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `cache_views_data`
--


--
-- Table structure for table `captcha_points`
--

CREATE TABLE `captcha_points` (
  `form_id` varchar(128) NOT NULL,
  `module` varchar(64) DEFAULT NULL,
  `type` varchar(64) DEFAULT NULL,
  PRIMARY KEY (`form_id`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `captcha_points`
--

INSERT INTO `captcha_points` VALUES ('comment_form',NULL,NULL),('contact_mail_user',NULL,NULL),('user_register',NULL,NULL),('user_pass',NULL,NULL),('user_login',NULL,NULL),('user_login_block',NULL,NULL),('forum_node_form',NULL,NULL),('contact_mail_page','captcha','Math');

--
-- Table structure for table `captcha_sessions`
--

CREATE TABLE `captcha_sessions` (
  `csid` int(11) NOT NULL AUTO_INCREMENT,
  `uid` int(11) NOT NULL DEFAULT '0',
  `sid` varchar(64) NOT NULL DEFAULT '',
  `ip_address` varchar(128) DEFAULT NULL,
  `timestamp` int(11) NOT NULL DEFAULT '0',
  `form_id` varchar(128) NOT NULL,
  `solution` varchar(128) NOT NULL DEFAULT '',
  `status` int(11) NOT NULL DEFAULT '0',
  `attempts` int(11) NOT NULL DEFAULT '0',
  `token` varchar(64) DEFAULT NULL,
  PRIMARY KEY (`csid`),
  KEY `csid_ip` (`csid`,`ip_address`)
) ENGINE=MyISAM AUTO_INCREMENT=16 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `captcha_sessions`
--

INSERT INTO `captcha_sessions` VALUES (12,0,'r8d0cvu2j3v9ll8vufc2thgmh4','10.1.1.2',1296835672,'contact_mail_page','4',0,0,'dc278bc877d89cd5eb44dd7cc4ba53c0'),(13,0,'8186974718454adb58c6155e86fb99a6','211.26.157.75',1296890657,'contact_mail_page','7',0,0,'5ba1ad974829125c459d8d3f9b77e457'),(14,0,'8186974718454adb58c6155e86fb99a6','211.26.157.75',1296891336,'contact_mail_page','7',0,0,'806e301592ca89a68a039344e7e2d31f'),(15,0,'72035425dc1eeadf256e44569120a50f','211.26.157.75',1296906538,'contact_mail_page','11',0,0,'cf65944db9baaaf44a43562583906d63');

--
-- Table structure for table `comments`
--

CREATE TABLE `comments` (
  `cid` int(11) NOT NULL AUTO_INCREMENT,
  `pid` int(11) NOT NULL DEFAULT '0',
  `nid` int(11) NOT NULL DEFAULT '0',
  `uid` int(11) NOT NULL DEFAULT '0',
  `subject` varchar(64) NOT NULL DEFAULT '',
  `comment` longtext NOT NULL,
  `hostname` varchar(128) NOT NULL DEFAULT '',
  `timestamp` int(11) NOT NULL DEFAULT '0',
  `status` tinyint(3) unsigned NOT NULL DEFAULT '0',
  `format` smallint(6) NOT NULL DEFAULT '0',
  `thread` varchar(255) NOT NULL,
  `name` varchar(60) DEFAULT NULL,
  `mail` varchar(64) DEFAULT NULL,
  `homepage` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`cid`),
  KEY `pid` (`pid`),
  KEY `nid` (`nid`),
  KEY `status` (`status`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `comments`
--


--
-- Table structure for table `contact`
--

CREATE TABLE `contact` (
  `cid` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `category` varchar(255) NOT NULL DEFAULT '',
  `recipients` longtext NOT NULL,
  `reply` longtext NOT NULL,
  `weight` tinyint(4) NOT NULL DEFAULT '0',
  `selected` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`cid`),
  UNIQUE KEY `category` (`category`),
  KEY `list` (`weight`,`category`)
) ENGINE=MyISAM AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `contact`
--

INSERT INTO `contact` VALUES (1,'Default','christian.kanakis@gmail.com','',0,1);

--
-- Table structure for table `contemplate`
--

CREATE TABLE `contemplate` (
  `type` varchar(32) NOT NULL DEFAULT '',
  `teaser` text NOT NULL,
  `body` text NOT NULL,
  `rss` text NOT NULL,
  `enclosure` varchar(128) NOT NULL,
  `flags` int(10) unsigned NOT NULL DEFAULT '7',
  KEY `type` (`type`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `contemplate`
--


--
-- Table structure for table `contemplate_files`
--

CREATE TABLE `contemplate_files` (
  `site` varchar(255) NOT NULL,
  `data` longblob NOT NULL,
  UNIQUE KEY `site` (`site`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `contemplate_files`
--


--
-- Table structure for table `content_group`
--

CREATE TABLE `content_group` (
  `group_type` varchar(32) NOT NULL DEFAULT 'standard',
  `type_name` varchar(32) NOT NULL DEFAULT '',
  `group_name` varchar(32) NOT NULL DEFAULT '',
  `label` varchar(255) NOT NULL DEFAULT '',
  `settings` mediumtext NOT NULL,
  `weight` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`type_name`,`group_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `content_group`
--


--
-- Table structure for table `content_group_fields`
--

CREATE TABLE `content_group_fields` (
  `type_name` varchar(32) NOT NULL DEFAULT '',
  `group_name` varchar(32) NOT NULL DEFAULT '',
  `field_name` varchar(32) NOT NULL DEFAULT '',
  PRIMARY KEY (`type_name`,`group_name`,`field_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `content_group_fields`
--


--
-- Table structure for table `content_node_field`
--

CREATE TABLE `content_node_field` (
  `field_name` varchar(32) NOT NULL DEFAULT '',
  `type` varchar(127) NOT NULL DEFAULT '',
  `global_settings` mediumtext NOT NULL,
  `required` tinyint(4) NOT NULL DEFAULT '0',
  `multiple` tinyint(4) NOT NULL DEFAULT '0',
  `db_storage` tinyint(4) NOT NULL DEFAULT '1',
  `module` varchar(127) NOT NULL DEFAULT '',
  `db_columns` mediumtext NOT NULL,
  `active` tinyint(4) NOT NULL DEFAULT '0',
  `locked` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`field_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `content_node_field`
--


--
-- Table structure for table `content_node_field_instance`
--

CREATE TABLE `content_node_field_instance` (
  `field_name` varchar(32) NOT NULL DEFAULT '',
  `type_name` varchar(32) NOT NULL DEFAULT '',
  `weight` int(11) NOT NULL DEFAULT '0',
  `label` varchar(255) NOT NULL DEFAULT '',
  `widget_type` varchar(32) NOT NULL DEFAULT '',
  `widget_settings` mediumtext NOT NULL,
  `display_settings` mediumtext NOT NULL,
  `description` mediumtext NOT NULL,
  `widget_module` varchar(127) NOT NULL DEFAULT '',
  `widget_active` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`field_name`,`type_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `content_node_field_instance`
--


--
-- Table structure for table `ctools_access_ruleset`
--

CREATE TABLE `ctools_access_ruleset` (
  `rsid` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) DEFAULT NULL,
  `admin_title` varchar(255) DEFAULT NULL,
  `admin_description` longtext,
  `requiredcontexts` longtext,
  `contexts` longtext,
  `relationships` longtext,
  `access` longtext,
  PRIMARY KEY (`rsid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `ctools_access_ruleset`
--


--
-- Table structure for table `ctools_css_cache`
--

CREATE TABLE `ctools_css_cache` (
  `cid` varchar(128) NOT NULL,
  `filename` varchar(255) DEFAULT NULL,
  `css` longtext,
  `filter` tinyint(4) DEFAULT NULL,
  PRIMARY KEY (`cid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `ctools_css_cache`
--


--
-- Table structure for table `ctools_custom_content`
--

CREATE TABLE `ctools_custom_content` (
  `cid` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) DEFAULT NULL,
  `admin_title` varchar(255) DEFAULT NULL,
  `admin_description` longtext,
  `category` varchar(255) DEFAULT NULL,
  `settings` longtext,
  PRIMARY KEY (`cid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `ctools_custom_content`
--


--
-- Table structure for table `ctools_object_cache`
--

CREATE TABLE `ctools_object_cache` (
  `sid` varchar(64) NOT NULL,
  `name` varchar(128) NOT NULL,
  `obj` varchar(32) NOT NULL,
  `updated` int(10) unsigned NOT NULL DEFAULT '0',
  `data` longtext,
  PRIMARY KEY (`sid`,`obj`,`name`),
  KEY `updated` (`updated`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `ctools_object_cache`
--


--
-- Table structure for table `devel_queries`
--

CREATE TABLE `devel_queries` (
  `qid` int(11) NOT NULL AUTO_INCREMENT,
  `function` varchar(255) NOT NULL DEFAULT '',
  `query` text NOT NULL,
  `hash` varchar(255) NOT NULL DEFAULT '',
  PRIMARY KEY (`hash`),
  KEY `qid` (`qid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `devel_queries`
--


--
-- Table structure for table `devel_times`
--

CREATE TABLE `devel_times` (
  `tid` int(11) NOT NULL AUTO_INCREMENT,
  `qid` int(11) NOT NULL DEFAULT '0',
  `time` float DEFAULT NULL,
  PRIMARY KEY (`tid`),
  KEY `qid` (`qid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `devel_times`
--


--
-- Table structure for table `fckeditor_role`
--

CREATE TABLE `fckeditor_role` (
  `name` varchar(128) NOT NULL DEFAULT '',
  `rid` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`name`,`rid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `fckeditor_role`
--

INSERT INTO `fckeditor_role` VALUES ('Advanced',2),('Default',1);

--
-- Table structure for table `fckeditor_settings`
--

CREATE TABLE `fckeditor_settings` (
  `name` varchar(128) NOT NULL DEFAULT '',
  `settings` text,
  PRIMARY KEY (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `fckeditor_settings`
--

INSERT INTO `fckeditor_settings` VALUES ('Default','a:28:{s:15:\"allow_user_conf\";s:1:\"f\";s:8:\"min_rows\";i:1;s:9:\"excl_mode\";i:0;s:11:\"filebrowser\";s:4:\"none\";s:11:\"quickupload\";s:1:\"f\";s:2:\"ss\";s:1:\"2\";s:7:\"filters\";a:1:{s:8:\"filter/0\";i:1;}s:7:\"default\";s:1:\"t\";s:11:\"show_toggle\";s:1:\"t\";s:5:\"popup\";s:1:\"f\";s:4:\"skin\";s:7:\"default\";s:7:\"toolbar\";s:11:\"DrupalBasic\";s:6:\"expand\";s:1:\"t\";s:5:\"width\";s:4:\"100%\";s:4:\"lang\";s:2:\"en\";s:9:\"auto_lang\";s:1:\"t\";s:10:\"enter_mode\";s:1:\"p\";s:16:\"shift_enter_mode\";s:2:\"br\";s:11:\"font_format\";s:35:\"p;div;pre;address;h1;h2;h3;h4;h5;h6\";s:13:\"format_source\";s:1:\"t\";s:13:\"format_output\";s:1:\"t\";s:8:\"css_mode\";s:5:\"theme\";s:8:\"css_path\";s:0:\"\";s:11:\"user_choose\";s:1:\"f\";s:18:\"show_fieldnamehint\";s:1:\"t\";s:16:\"autofixplaintext\";s:1:\"f\";s:10:\"excl_regex\";s:0:\"\";s:17:\"simple_incl_regex\";s:0:\"\";}'),('Advanced','a:28:{s:15:\"allow_user_conf\";s:1:\"f\";s:8:\"min_rows\";i:1;s:9:\"excl_mode\";i:0;s:11:\"filebrowser\";s:4:\"none\";s:11:\"quickupload\";s:1:\"f\";s:2:\"ss\";s:1:\"2\";s:7:\"filters\";a:1:{s:8:\"filter/0\";i:1;}s:7:\"default\";s:1:\"t\";s:11:\"show_toggle\";s:1:\"t\";s:5:\"popup\";s:1:\"f\";s:4:\"skin\";s:7:\"default\";s:7:\"toolbar\";s:14:\"DrupalFiltered\";s:6:\"expand\";s:1:\"t\";s:5:\"width\";s:4:\"100%\";s:4:\"lang\";s:2:\"en\";s:9:\"auto_lang\";s:1:\"t\";s:10:\"enter_mode\";s:1:\"p\";s:16:\"shift_enter_mode\";s:2:\"br\";s:11:\"font_format\";s:35:\"p;div;pre;address;h1;h2;h3;h4;h5;h6\";s:13:\"format_source\";s:1:\"t\";s:13:\"format_output\";s:1:\"t\";s:8:\"css_mode\";s:5:\"theme\";s:8:\"css_path\";s:0:\"\";s:11:\"user_choose\";s:1:\"f\";s:18:\"show_fieldnamehint\";s:1:\"t\";s:16:\"autofixplaintext\";s:1:\"f\";s:10:\"excl_regex\";s:0:\"\";s:17:\"simple_incl_regex\";s:0:\"\";}'),('FCKeditor Global Profile','a:6:{s:9:\"excl_mode\";i:0;s:4:\"excl\";s:597:\"admin/user/settings.edit-user-mail-*\n*.edit-pages\n*.edit-pathauto-ignore-words\n*.edit-recipients\n*.edit-reply\n*.edit-description\n*.edit-synonyms\n*.edit-img-assist-textareas\n*.edit-img-assist-paths\n*.edit-nodewords-description\n*.edit-nodewords-description-value\nadmin/content/nodewords/global*\n*.edit-relatedlinks-fieldset-relatedlinks\n*.edit-allowed-values-php\n*.edit-allowed-values\n*.edit-update-notify-emails\n*.edit-googleanalytics-*\n*.edit-piwik-*\n*.edit-feedburner-useragents\n*@*.edit-webform-*\nwebform@*.edit-extra-items\nadmin/*/logintoboggan\nadmin/settings/actions/configure/*\n*.edit-target\n\";s:16:\"simple_incl_mode\";i:1;s:11:\"simple_incl\";s:163:\"*.edit-signature\nadmin/settings/site-information.*\nadmin/settings/site-maintenance.*\n*.edit-page-help\n*.edit-user-registration-help\n*.edit-user-picture-guidelines\n\";s:10:\"excl_regex\";s:913:\"#(?:^.*@admin/user/settings\\.edit\\-user\\-mail\\-.*$)|(?:^.*@.*\\.edit\\-pages$)|(?:^.*@.*\\.edit\\-pathauto\\-ignore\\-words$)|(?:^.*@.*\\.edit\\-recipients$)|(?:^.*@.*\\.edit\\-reply$)|(?:^.*@.*\\.edit\\-description$)|(?:^.*@.*\\.edit\\-synonyms$)|(?:^.*@.*\\.edit\\-img\\-assist\\-textareas$)|(?:^.*@.*\\.edit\\-img\\-assist\\-paths$)|(?:^.*@.*\\.edit\\-nodewords\\-description$)|(?:^.*@.*\\.edit\\-nodewords\\-description\\-value$)|(?:^.*@admin/content/nodewords/global.*\\..*$)|(?:^.*@.*\\.edit\\-relatedlinks\\-fieldset\\-relatedlinks$)|(?:^.*@.*\\.edit\\-allowed\\-values\\-php$)|(?:^.*@.*\\.edit\\-allowed\\-values$)|(?:^.*@.*\\.edit\\-update\\-notify\\-emails$)|(?:^.*@.*\\.edit\\-googleanalytics\\-.*$)|(?:^.*@.*\\.edit\\-piwik\\-.*$)|(?:^.*@.*\\.edit\\-feedburner\\-useragents$)|(?:^.*@.*\\.edit\\-webform\\-.*$)|(?:^webform@.*\\.edit\\-extra\\-items$)|(?:^.*@admin/.*/logintoboggan\\..*$)|(?:^.*@admin/settings/actions/configure/.*\\..*$)|(?:^.*@.*\\.edit\\-target$)#\";s:17:\"simple_incl_regex\";s:241:\"#(?:^.*@.*\\.edit\\-signature$)|(?:^.*@admin/settings/site\\-information\\..*$)|(?:^.*@admin/settings/site\\-maintenance\\..*$)|(?:^.*@.*\\.edit\\-page\\-help$)|(?:^.*@.*\\.edit\\-user\\-registration\\-help$)|(?:^.*@.*\\.edit\\-user\\-picture\\-guidelines$)#\";}');

--
-- Table structure for table `filefield_meta`
--

CREATE TABLE `filefield_meta` (
  `fid` int(10) unsigned NOT NULL,
  `width` int(10) unsigned DEFAULT NULL,
  `height` int(10) unsigned DEFAULT NULL,
  `duration` float DEFAULT NULL,
  `audio_format` varchar(10) NOT NULL DEFAULT '',
  `audio_sample_rate` mediumint(9) NOT NULL DEFAULT '0',
  `audio_channel_mode` varchar(10) NOT NULL DEFAULT '',
  `audio_bitrate` float NOT NULL DEFAULT '0',
  `audio_bitrate_mode` varchar(4) NOT NULL DEFAULT '',
  `tags` text,
  PRIMARY KEY (`fid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `filefield_meta`
--


--
-- Table structure for table `files`
--

CREATE TABLE `files` (
  `fid` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `uid` int(10) unsigned NOT NULL DEFAULT '0',
  `filename` varchar(255) NOT NULL DEFAULT '',
  `filepath` varchar(255) NOT NULL DEFAULT '',
  `filemime` varchar(255) NOT NULL DEFAULT '',
  `filesize` int(10) unsigned NOT NULL DEFAULT '0',
  `status` int(11) NOT NULL DEFAULT '0',
  `timestamp` int(10) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`fid`),
  KEY `uid` (`uid`),
  KEY `status` (`status`),
  KEY `timestamp` (`timestamp`)
) ENGINE=MyISAM AUTO_INCREMENT=157 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `files`
--

INSERT INTO `files` VALUES (51,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293678763),(50,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293678750),(49,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293678227),(6,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293000452),(7,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293000598),(8,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293000642),(9,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293000670),(10,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293000851),(11,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293000862),(12,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293001012),(13,1,'Image_2.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_2.png','image/png',37071,1,1293001060),(14,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293007580),(15,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293007607),(16,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293007658),(17,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293007690),(18,1,'Image_1.png','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/Image_1.png','image/png',24096,1,1293007768),(19,1,'charts.fwc','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/charts.fwc','application/octet-stream',158363,1,1293008423),(129,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786067),(128,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786001),(127,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295785963),(109,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295785590),(45,1,'charts.fwc','sites/default/files/nsecffe1660vego19p95tpck10/charts.fwc','application/octet-stream',170691,1,1293083637),(46,1,'charts.fwc','sites/default/files/nsecffe1660vego19p95tpck10/charts.fwc','application/octet-stream',170691,1,1293083645),(47,1,'charts.fwc','sites/default/files/6bhsoh9jdamla24u88pd83a4a6/charts.fwc','application/octet-stream',158363,1,1293090322),(52,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293679021),(53,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293679087),(54,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293679132),(105,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295784359),(64,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293679514),(65,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293679669),(66,1,'charts.fwc','sites/default/files/charts.fwc','application/octet-stream',158363,1,1293679827),(99,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295784238),(74,1,'charts.fwc','sites/default/files/66s660iqk6l0vkn86dns2o8bq3/charts.fwc','application/octet-stream',158363,1,1293681307),(75,1,'charts.fwc','sites/default/files/66s660iqk6l0vkn86dns2o8bq3/charts.fwc','application/octet-stream',158363,1,1293681318),(76,1,'charts.fwc','sites/default/files/66s660iqk6l0vkn86dns2o8bq3/charts.fwc','application/octet-stream',158363,1,1293681804),(77,1,'charts.fwc','sites/default/files/66s660iqk6l0vkn86dns2o8bq3/charts.fwc','application/octet-stream',158363,1,1293691476),(78,1,'charts.fwc','sites/default/files/66s660iqk6l0vkn86dns2o8bq3/charts.fwc','application/octet-stream',158363,1,1293691543),(79,1,'charts.fwc','sites/default/files/66s660iqk6l0vkn86dns2o8bq3/charts.fwc','application/octet-stream',158363,1,1293691661),(80,1,'charts.fwc','sites/default/files/66s660iqk6l0vkn86dns2o8bq3/charts.fwc','application/octet-stream',158363,1,1293709887),(93,1,'charts.fwc','sites/default/files/6icgknvvpo0jqd5fnu1fjmjpl4/charts.fwc','application/octet-stream',158363,1,1295163973),(92,1,'charts.fwc','sites/default/files/6icgknvvpo0jqd5fnu1fjmjpl4/charts.fwc','application/octet-stream',158363,1,1295163916),(94,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295783826),(90,1,'graphs.fwg','sites/default/files/6icgknvvpo0jqd5fnu1fjmjpl4/graphs.fwg','application/octet-stream',103150,1,1295163711),(89,1,'graphs.fwg','sites/default/files/6icgknvvpo0jqd5fnu1fjmjpl4/graphs.fwg','application/octet-stream',103150,1,1295163689),(88,1,'graphs.fwg','sites/default/files/6icgknvvpo0jqd5fnu1fjmjpl4/graphs.fwg','application/octet-stream',103150,1,1295163670),(133,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786169),(134,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786179),(135,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786194),(136,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786224),(137,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786321),(140,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786364),(145,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786850),(147,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295786903),(156,1,'charts.fwc','sites/default/files/8b6f6724be3618f992c008c12def2232/charts.fwc','application/octet-stream',158363,1,1296990303),(153,1,'charts.fwc','sites/default/files/iek98ll5vvmbrh2qqbgh0io015/charts.fwc','application/octet-stream',158363,1,1295787293),(155,1,'charts.fwc','sites/default/files/8b6f6724be3618f992c008c12def2232/charts.fwc','application/octet-stream',158363,1,1296990170);

--
-- Table structure for table `filter_formats`
--

CREATE TABLE `filter_formats` (
  `format` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) NOT NULL DEFAULT '',
  `roles` varchar(255) NOT NULL DEFAULT '',
  `cache` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`format`),
  UNIQUE KEY `name` (`name`)
) ENGINE=MyISAM AUTO_INCREMENT=3 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `filter_formats`
--

INSERT INTO `filter_formats` VALUES (1,'Filtered HTML',',1,2,',1),(2,'Full HTML','',1);

--
-- Table structure for table `filters`
--

CREATE TABLE `filters` (
  `fid` int(11) NOT NULL AUTO_INCREMENT,
  `format` int(11) NOT NULL DEFAULT '0',
  `module` varchar(64) NOT NULL DEFAULT '',
  `delta` tinyint(4) NOT NULL DEFAULT '0',
  `weight` tinyint(4) NOT NULL DEFAULT '0',
  PRIMARY KEY (`fid`),
  UNIQUE KEY `fmd` (`format`,`module`,`delta`),
  KEY `list` (`format`,`weight`,`module`,`delta`)
) ENGINE=MyISAM AUTO_INCREMENT=8 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `filters`
--

INSERT INTO `filters` VALUES (1,1,'filter',2,0),(2,1,'filter',0,1),(3,1,'filter',1,2),(4,1,'filter',3,10),(5,2,'filter',2,0),(6,2,'filter',1,1),(7,2,'filter',3,10);

--
-- Table structure for table `flood`
--

CREATE TABLE `flood` (
  `fid` int(11) NOT NULL AUTO_INCREMENT,
  `event` varchar(64) NOT NULL DEFAULT '',
  `hostname` varchar(128) NOT NULL DEFAULT '',
  `timestamp` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`fid`),
  KEY `allow` (`event`,`hostname`,`timestamp`)
) ENGINE=MyISAM AUTO_INCREMENT=28 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `flood`
--


--
-- Table structure for table `history`
--

CREATE TABLE `history` (
  `uid` int(11) NOT NULL DEFAULT '0',
  `nid` int(11) NOT NULL DEFAULT '0',
  `timestamp` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`uid`,`nid`),
  KEY `nid` (`nid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `history`
--

INSERT INTO `history` VALUES (1,0,1295783003);

--
-- Table structure for table `menu_custom`
--

CREATE TABLE `menu_custom` (
  `menu_name` varchar(32) NOT NULL DEFAULT '',
  `title` varchar(255) NOT NULL DEFAULT '',
  `description` text,
  PRIMARY KEY (`menu_name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `menu_custom`
--

INSERT INTO `menu_custom` VALUES ('navigation','Navigation','The navigation menu is provided by Drupal and is the main interactive menu for any site. It is usually the only menu that contains personalized links for authenticated users, and is often not even visible to anonymous users.'),('primary-links','Primary links','Primary links are often used at the theme layer to show the major sections of a site. A typical representation for primary links would be tabs along the top.'),('secondary-links','Secondary links','Secondary links are often used for pages like legal notices, contact details, and other secondary navigation items that play a lesser role than primary links'),('menu-subscriber-links','Subscriber links',''),('menu-subscribers','Subscribers',''),('devel','Development','Development links.');

--
-- Table structure for table `menu_links`
--

CREATE TABLE `menu_links` (
  `menu_name` varchar(32) NOT NULL DEFAULT '',
  `mlid` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `plid` int(10) unsigned NOT NULL DEFAULT '0',
  `link_path` varchar(255) NOT NULL DEFAULT '',
  `router_path` varchar(255) NOT NULL DEFAULT '',
  `link_title` varchar(255) NOT NULL DEFAULT '',
  `options` text,
  `module` varchar(255) NOT NULL DEFAULT 'system',
  `hidden` smallint(6) NOT NULL DEFAULT '0',
  `external` smallint(6) NOT NULL DEFAULT '0',
  `has_children` smallint(6) NOT NULL DEFAULT '0',
  `expanded` smallint(6) NOT NULL DEFAULT '0',
  `weight` int(11) NOT NULL DEFAULT '0',
  `depth` smallint(6) NOT NULL DEFAULT '0',
  `customized` smallint(6) NOT NULL DEFAULT '0',
  `p1` int(10) unsigned NOT NULL DEFAULT '0',
  `p2` int(10) unsigned NOT NULL DEFAULT '0',
  `p3` int(10) unsigned NOT NULL DEFAULT '0',
  `p4` int(10) unsigned NOT NULL DEFAULT '0',
  `p5` int(10) unsigned NOT NULL DEFAULT '0',
  `p6` int(10) unsigned NOT NULL DEFAULT '0',
  `p7` int(10) unsigned NOT NULL DEFAULT '0',
  `p8` int(10) unsigned NOT NULL DEFAULT '0',
  `p9` int(10) unsigned NOT NULL DEFAULT '0',
  `updated` smallint(6) NOT NULL DEFAULT '0',
  PRIMARY KEY (`mlid`),
  KEY `path_menu` (`link_path`(128),`menu_name`),
  KEY `menu_plid_expand_child` (`menu_name`,`plid`,`expanded`,`has_children`),
  KEY `menu_parents` (`menu_name`,`p1`,`p2`,`p3`,`p4`,`p5`,`p6`,`p7`,`p8`,`p9`),
  KEY `router_path` (`router_path`(128))
) ENGINE=MyISAM AUTO_INCREMENT=1092 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `menu_links`
--



--
-- Table structure for table `menu_router`
--

CREATE TABLE `menu_router` (
  `path` varchar(255) NOT NULL DEFAULT '',
  `load_functions` text NOT NULL,
  `to_arg_functions` text NOT NULL,
  `access_callback` varchar(255) NOT NULL DEFAULT '',
  `access_arguments` text,
  `page_callback` varchar(255) NOT NULL DEFAULT '',
  `page_arguments` text,
  `fit` int(11) NOT NULL DEFAULT '0',
  `number_parts` smallint(6) NOT NULL DEFAULT '0',
  `tab_parent` varchar(255) NOT NULL DEFAULT '',
  `tab_root` varchar(255) NOT NULL DEFAULT '',
  `title` varchar(255) NOT NULL DEFAULT '',
  `title_callback` varchar(255) NOT NULL DEFAULT '',
  `title_arguments` varchar(255) NOT NULL DEFAULT '',
  `type` int(11) NOT NULL DEFAULT '0',
  `block_callback` varchar(255) NOT NULL DEFAULT '',
  `description` text NOT NULL,
  `position` varchar(255) NOT NULL DEFAULT '',
  `weight` int(11) NOT NULL DEFAULT '0',
  `file` mediumtext,
  PRIMARY KEY (`path`),
  KEY `fit` (`fit`),
  KEY `tab_parent` (`tab_parent`),
  KEY `tab_root_weight_title` (`tab_root`(64),`weight`,`title`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `menu_router`
--



--
-- Table structure for table `mobileplugin_groups`
--

CREATE TABLE `mobileplugin_groups` (
  `name` varchar(60) NOT NULL,
  `theme` varchar(60) NOT NULL,
  `data` text NOT NULL,
  PRIMARY KEY (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `mobileplugin_groups`
--

INSERT INTO `mobileplugin_groups` VALUES ('mobile','mobile_garland','');

--
-- Table structure for table `mobileplugin_rules`
--

CREATE TABLE `mobileplugin_rules` (
  `rid` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `capability` varchar(60) NOT NULL,
  `operator` varchar(2) NOT NULL,
  `value` varchar(60) NOT NULL,
  `group_name` varchar(60) NOT NULL,
  `weight` int(11) NOT NULL,
  PRIMARY KEY (`rid`)
) ENGINE=MyISAM AUTO_INCREMENT=5 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `mobileplugin_rules`
--

INSERT INTO `mobileplugin_rules` VALUES (1,'USERAGENT','=~','Windows NT\nPPC Mac OS X\nIntel Mac OS X','no',1),(2,'USERAGENT','=~','Series60/5.0\nMaemo\niPhone\niPod\nwebOS','mobile,1',2),(3,'USERAGENT','=~','Series60\nwebKit\nAndroid','mobile,0',3),(4,'is_wireless_device','==','true','mobile',10);

--
-- Table structure for table `multiblock`
--

CREATE TABLE `multiblock` (
  `delta` int(11) NOT NULL AUTO_INCREMENT,
  `title` varchar(64) NOT NULL DEFAULT '',
  `module` varchar(64) NOT NULL DEFAULT '',
  `orig_delta` varchar(32) NOT NULL DEFAULT '0',
  `multi_settings` tinyint(3) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`delta`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `multiblock`
--


--
-- Table structure for table `node`
--

CREATE TABLE `node` (
  `nid` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `vid` int(10) unsigned NOT NULL DEFAULT '0',
  `type` varchar(32) NOT NULL DEFAULT '',
  `language` varchar(12) NOT NULL DEFAULT '',
  `title` varchar(255) NOT NULL DEFAULT '',
  `uid` int(11) NOT NULL DEFAULT '0',
  `status` int(11) NOT NULL DEFAULT '1',
  `created` int(11) NOT NULL DEFAULT '0',
  `changed` int(11) NOT NULL DEFAULT '0',
  `comment` int(11) NOT NULL DEFAULT '0',
  `promote` int(11) NOT NULL DEFAULT '0',
  `moderate` int(11) NOT NULL DEFAULT '0',
  `sticky` int(11) NOT NULL DEFAULT '0',
  `tnid` int(10) unsigned NOT NULL DEFAULT '0',
  `translate` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`nid`),
  UNIQUE KEY `vid` (`vid`),
  KEY `node_changed` (`changed`),
  KEY `node_created` (`created`),
  KEY `node_moderate` (`moderate`),
  KEY `node_promote_status` (`promote`,`status`),
  KEY `node_status_type` (`status`,`type`,`nid`),
  KEY `node_title_type` (`title`,`type`(4)),
  KEY `node_type` (`type`(4)),
  KEY `uid` (`uid`),
  KEY `tnid` (`tnid`),
  KEY `translate` (`translate`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `node`
--


--
-- Table structure for table `node_access`
--

CREATE TABLE `node_access` (
  `nid` int(10) unsigned NOT NULL DEFAULT '0',
  `gid` int(10) unsigned NOT NULL DEFAULT '0',
  `realm` varchar(255) NOT NULL DEFAULT '',
  `grant_view` tinyint(3) unsigned NOT NULL DEFAULT '0',
  `grant_update` tinyint(3) unsigned NOT NULL DEFAULT '0',
  `grant_delete` tinyint(3) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`nid`,`gid`,`realm`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `node_access`
--

INSERT INTO `node_access` VALUES (0,0,'all',1,0,0);

--
-- Table structure for table `node_comment_statistics`
--

CREATE TABLE `node_comment_statistics` (
  `nid` int(10) unsigned NOT NULL DEFAULT '0',
  `last_comment_timestamp` int(11) NOT NULL DEFAULT '0',
  `last_comment_name` varchar(60) DEFAULT NULL,
  `last_comment_uid` int(11) NOT NULL DEFAULT '0',
  `comment_count` int(10) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`nid`),
  KEY `node_comment_timestamp` (`last_comment_timestamp`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `node_comment_statistics`
--


--
-- Table structure for table `node_counter`
--

CREATE TABLE `node_counter` (
  `nid` int(11) NOT NULL DEFAULT '0',
  `totalcount` bigint(20) unsigned NOT NULL DEFAULT '0',
  `daycount` mediumint(8) unsigned NOT NULL DEFAULT '0',
  `timestamp` int(10) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`nid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `node_counter`
--


--
-- Table structure for table `node_revisions`
--

CREATE TABLE `node_revisions` (
  `nid` int(10) unsigned NOT NULL DEFAULT '0',
  `vid` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `uid` int(11) NOT NULL DEFAULT '0',
  `title` varchar(255) NOT NULL DEFAULT '',
  `body` longtext NOT NULL,
  `teaser` longtext NOT NULL,
  `log` longtext NOT NULL,
  `timestamp` int(11) NOT NULL DEFAULT '0',
  `format` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`vid`),
  KEY `nid` (`nid`),
  KEY `uid` (`uid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `node_revisions`
--


--
-- Table structure for table `node_type`
--

CREATE TABLE `node_type` (
  `type` varchar(32) NOT NULL,
  `name` varchar(255) NOT NULL DEFAULT '',
  `module` varchar(255) NOT NULL,
  `description` mediumtext NOT NULL,
  `help` mediumtext NOT NULL,
  `has_title` tinyint(3) unsigned NOT NULL,
  `title_label` varchar(255) NOT NULL DEFAULT '',
  `has_body` tinyint(3) unsigned NOT NULL,
  `body_label` varchar(255) NOT NULL DEFAULT '',
  `min_word_count` smallint(5) unsigned NOT NULL,
  `custom` tinyint(4) NOT NULL DEFAULT '0',
  `modified` tinyint(4) NOT NULL DEFAULT '0',
  `locked` tinyint(4) NOT NULL DEFAULT '0',
  `orig_type` varchar(255) NOT NULL DEFAULT '',
  PRIMARY KEY (`type`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `node_type`
--

INSERT INTO `node_type` VALUES ('page','Page','node','A <em>page</em>, similar in form to a <em>story</em>, is a simple method for creating and displaying information that rarely changes, such as an \"About us\" section of a website. By default, a <em>page</em> entry does not allow visitor comments and is not featured on the site\'s initial home page.','',1,'Title',1,'Body',0,1,1,0,'page'),('story','Story','node','A <em>story</em>, similar in form to a <em>page</em>, is ideal for creating and displaying content that informs or engages website visitors. Press releases, site announcements, and informal blog-like entries may all be created with a <em>story</em> entry. By default, a <em>story</em> entry is automatically featured on the site\'s initial home page, and provides the ability to post comments.','',1,'Title',1,'Body',0,1,1,0,'story'),('panel','Panel','panels_node','A panel layout broken up into rows and columns.','',1,'Title',1,'Teaser',0,0,0,1,'panel');

--
-- Table structure for table `page_manager_handlers`
--

CREATE TABLE `page_manager_handlers` (
  `did` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) DEFAULT NULL,
  `task` varchar(64) DEFAULT NULL,
  `subtask` varchar(64) NOT NULL DEFAULT '',
  `handler` varchar(64) DEFAULT NULL,
  `weight` int(11) DEFAULT NULL,
  `conf` longtext NOT NULL,
  PRIMARY KEY (`did`),
  UNIQUE KEY `name` (`name`),
  KEY `fulltask` (`task`,`subtask`,`weight`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `page_manager_handlers`
--


--
-- Table structure for table `page_manager_pages`
--

CREATE TABLE `page_manager_pages` (
  `pid` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) DEFAULT NULL,
  `task` varchar(64) DEFAULT 'page',
  `admin_title` varchar(255) DEFAULT NULL,
  `admin_description` longtext,
  `path` varchar(255) DEFAULT NULL,
  `access` longtext NOT NULL,
  `menu` longtext NOT NULL,
  `arguments` longtext NOT NULL,
  `conf` longtext NOT NULL,
  PRIMARY KEY (`pid`),
  UNIQUE KEY `name` (`name`),
  KEY `task` (`task`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `page_manager_pages`
--


--
-- Table structure for table `page_manager_weights`
--

CREATE TABLE `page_manager_weights` (
  `name` varchar(255) NOT NULL DEFAULT '',
  `weight` int(11) DEFAULT NULL,
  PRIMARY KEY (`name`),
  KEY `weights` (`name`,`weight`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `page_manager_weights`
--


--
-- Table structure for table `panels_display`
--

CREATE TABLE `panels_display` (
  `did` int(11) NOT NULL AUTO_INCREMENT,
  `layout` varchar(32) DEFAULT '',
  `layout_settings` longtext,
  `panel_settings` longtext,
  `cache` text,
  `title` varchar(255) DEFAULT '',
  `hide_title` tinyint(4) DEFAULT '0',
  `title_pane` int(11) DEFAULT '0',
  PRIMARY KEY (`did`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `panels_display`
--


--
-- Table structure for table `panels_layout`
--

CREATE TABLE `panels_layout` (
  `lid` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) DEFAULT NULL,
  `admin_title` varchar(255) DEFAULT NULL,
  `admin_description` longtext,
  `category` varchar(255) DEFAULT NULL,
  `plugin` varchar(255) DEFAULT NULL,
  `settings` longtext,
  PRIMARY KEY (`lid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `panels_layout`
--


--
-- Table structure for table `panels_mini`
--

CREATE TABLE `panels_mini` (
  `pid` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) DEFAULT NULL,
  `category` varchar(64) DEFAULT NULL,
  `did` int(11) DEFAULT NULL,
  `admin_title` varchar(128) DEFAULT NULL,
  `admin_description` longtext,
  `requiredcontexts` longtext,
  `contexts` longtext,
  `relationships` longtext,
  PRIMARY KEY (`pid`),
  UNIQUE KEY `name` (`name`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `panels_mini`
--


--
-- Table structure for table `panels_node`
--

CREATE TABLE `panels_node` (
  `nid` int(11) NOT NULL DEFAULT '0',
  `css_id` varchar(255) DEFAULT NULL,
  `did` int(11) NOT NULL,
  `pipeline` varchar(255) DEFAULT NULL,
  PRIMARY KEY (`did`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `panels_node`
--


--
-- Table structure for table `panels_pane`
--

CREATE TABLE `panels_pane` (
  `pid` int(11) NOT NULL AUTO_INCREMENT,
  `did` int(11) NOT NULL DEFAULT '0',
  `panel` varchar(32) DEFAULT '',
  `type` varchar(32) DEFAULT '',
  `subtype` varchar(64) DEFAULT '',
  `shown` tinyint(4) DEFAULT '1',
  `access` longtext,
  `configuration` longtext,
  `cache` longtext,
  `style` longtext,
  `css` longtext,
  `extras` longtext,
  `position` smallint(6) DEFAULT '0',
  PRIMARY KEY (`pid`),
  KEY `did_idx` (`did`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `panels_pane`
--


--
-- Table structure for table `panels_renderer_pipeline`
--

CREATE TABLE `panels_renderer_pipeline` (
  `rpid` int(11) NOT NULL AUTO_INCREMENT,
  `name` varchar(255) DEFAULT NULL,
  `admin_title` varchar(255) DEFAULT NULL,
  `admin_description` longtext,
  `weight` smallint(6) DEFAULT '0',
  `settings` longtext,
  PRIMARY KEY (`rpid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `panels_renderer_pipeline`
--


--
-- Table structure for table `performance_detail`
--

CREATE TABLE `performance_detail` (
  `pid` int(11) NOT NULL AUTO_INCREMENT,
  `timestamp` int(11) NOT NULL DEFAULT '0',
  `bytes` int(11) NOT NULL DEFAULT '0',
  `ms` int(11) NOT NULL DEFAULT '0',
  `query_count` int(11) NOT NULL DEFAULT '0',
  `query_timer` int(11) NOT NULL DEFAULT '0',
  `anon` int(11) DEFAULT '1',
  `path` varchar(255) DEFAULT NULL,
  `data` longblob,
  PRIMARY KEY (`pid`),
  KEY `timestamp` (`timestamp`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `performance_detail`
--


--
-- Table structure for table `performance_summary`
--

CREATE TABLE `performance_summary` (
  `path` varchar(255) NOT NULL DEFAULT '',
  `last_access` int(11) NOT NULL DEFAULT '0',
  `bytes_max` int(11) NOT NULL DEFAULT '0',
  `bytes_avg` int(11) NOT NULL DEFAULT '0',
  `ms_max` int(11) NOT NULL DEFAULT '0',
  `ms_avg` int(11) NOT NULL DEFAULT '0',
  `query_count_max` int(11) NOT NULL DEFAULT '0',
  `query_count_avg` int(11) NOT NULL DEFAULT '0',
  `query_timer_max` int(11) NOT NULL DEFAULT '0',
  `query_timer_avg` int(11) NOT NULL DEFAULT '0',
  `num_accesses` int(11) NOT NULL DEFAULT '0',
  PRIMARY KEY (`path`),
  KEY `last_access` (`last_access`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `performance_summary`
--


--
-- Table structure for table `permission`
--

CREATE TABLE `permission` (
  `pid` int(11) NOT NULL AUTO_INCREMENT,
  `rid` int(10) unsigned NOT NULL DEFAULT '0',
  `perm` longtext,
  `tid` int(10) unsigned NOT NULL DEFAULT '0',
  PRIMARY KEY (`pid`),
  KEY `rid` (`rid`)
) ENGINE=MyISAM AUTO_INCREMENT=6 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `permission`
--

INSERT INTO `permission` VALUES (4,2,'skip CAPTCHA, access site-wide contact form, access content',0),(3,1,'access site-wide contact form, access content',0),(5,3,'skip CAPTCHA, access site-wide contact form, access content',0);

--
-- Table structure for table `persistent_login`
--

CREATE TABLE `persistent_login` (
  `uid` int(10) unsigned NOT NULL,
  `series` varchar(32) NOT NULL,
  `token` varchar(32) NOT NULL,
  `expires` int(10) unsigned NOT NULL,
  PRIMARY KEY (`uid`,`series`),
  KEY `expires` (`expires`),
  KEY `uid_expires` (`uid`,`expires`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `persistent_login`
--


--
-- Table structure for table `persistent_login_history`
--

CREATE TABLE `persistent_login_history` (
  `uid` int(10) unsigned NOT NULL,
  `series` varchar(32) NOT NULL,
  `token` varchar(32) NOT NULL,
  `expires` int(10) unsigned NOT NULL,
  `at` int(10) unsigned NOT NULL,
  `why` varchar(255) NOT NULL,
  PRIMARY KEY (`uid`,`series`,`token`),
  KEY `expires` (`at`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `persistent_login_history`
--


--
-- Table structure for table `role`
--

CREATE TABLE `role` (
  `rid` int(10) unsigned NOT NULL AUTO_INCREMENT,
  `name` varchar(64) NOT NULL DEFAULT '',
  PRIMARY KEY (`rid`),
  UNIQUE KEY `name` (`name`)
) ENGINE=MyISAM AUTO_INCREMENT=4 DEFAULT CHARSET=utf8;

--
-- Dumping data for table `role`
--

INSERT INTO `role` VALUES (1,'anonymous user'),(2,'authenticated user'),(3,'serviceman');

--
-- Table structure for table `search_dataset`
--

CREATE TABLE `search_dataset` (
  `sid` int(10) unsigned NOT NULL DEFAULT '0',
  `type` varchar(16) DEFAULT NULL,
  `data` longtext NOT NULL,
  `reindex` int(10) unsigned NOT NULL DEFAULT '0',
  UNIQUE KEY `sid_type` (`sid`,`type`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

--
-- Dumping data for table `search_dataset`
--

INSERT INTO `search_dataset` VALUES (1,'help',' using advanced help the advanced help system is a pluggable system that provides advanced help facilities for drupal and its modules although the advanced help does not provide general help by itself it provides a powerful and easy framework that modules may use to provide their own help modules utilizing advanced help should create a help subdirectory inside their module s directory place the file modulenamehelpini in this subdirectory formatted similar to the following example buses title how buses are tied into the system file buses topicid title title of topic file filename of topic without the html extension weight how important the topic is on the index page parent the optional topic parent to use in the breadcrumb either topic or module topic all topics are addressed by the module providing the topic and by the topic id to embed links use the following format output theme advancedhelptopic module topic inside your help file link to other topics using the format  a href topic module topic   this format will ensure the popup status remains consistent when switching between links use  a href path examplejpg  to reference items within the help directory such as images you wish to embed within the help text use  a href baseurl admin settings siteconfiguration  to reference any normal path in the site if the search module is enabled the contents of help system will be indexed on cron if you enable new modules and wish to immediately index its help text visit the administration reports status report and click the run cron manually link example  don t click this  see  ini file format note  in previous versions advanced help did not require the s wrapped around the topic path and baseurl links this is currently still supported but may be removed in a future version by adding the s these tokens are now not limited to href and src paramaters  ',0),(2,'help',' translating advanced help to translate advanced help first create a translations help language directory in the module directory then copy the ini file and all html files from the help directory the ini file only needs to keep the titles and if there is a name or index name setting in the advanced help settings portion that should be retained any retained settings should be translated the rest of the data in the ini file may be discarded or ignored each file should then be translated in place when translating a html file you will find that the path keyword will lead to the original directory if you must translate items that are linked such as images use transpath instead which will lead to the translated directory this will allow you to pick and choose which linked items if any will be translated  ',0),(3,'help',' help ini file format the advanced help configuration file is in simple ini file format divided into sections for each help file plus an optional section for global settings that might be inherited for each help file the first line of an advanced help ini file should be id which will be a comment providing the cvs identifier for the file the indicates a comment character anything after the will be ignored global settings may be put into a section named  advanced help settings   this means that this name is reserved and it cannot be a help file in any module the following settings may be set in this section  line break if set to any value the line break filter will be applied to all help files defined by this module unless that help file specifically is set otherwise by default the line break filter is not applied however help files can be much easier to write with the line break filter on navigation if set to true the navigation will be displayed at the end of the help topic previous topic next topic and child topics css specify a css file that will be used for all help files unless overridden including the css extension this css file must reside in the help directory along with the html files and will not be affected by translation name may be set to override the module name as displayed in both the module index as well as the navigation and breadcrumb trail in general this does not need to be set but a few modules may want to use a more friendly name than appears in the info file index name this may be set to change the name of the module in the module index it overrides the name setting above as well as the module name in its info file hide this may be used to hide a module in the module index this is particularly useful for modules who insert their help files into the hierarchy of another module as might be done by modules that extend views or cck by setting hide true the module will not appear as its own entry each section after that will correspond to a single help file and each one may have the following settings  title the title of the topic presented to the user and used in links if you have special characters in your title be sure to enclose it in quotes file the filename without the html extension used for the topic this is optional if not specified the topic name wil be the file name weight the weight used for sorting topics on the administration page defaults to 0 of unspecified items with the same weight are sorted alphabetically parent the topic id to use in a hierarchy children will be listed beneath parents in the topic list and will have the parent in their breadcrumb trail you may parent this topic to another module s topic by using module topic as the identifier for example views display will make this a child of the display topic in the views module line break if set to true linebreaks will be converted into br and p tags automatically if unspecified will default to off set to 0 to disable the filter if this has been turned on in the global settings css specify a css file that will be used for this file this css file must reside in the help directory along with the html files this will override any css file added by the global system popup width the width in pixels of the popup window defaults to 500 if unspecified popup height the height in pixels of the popup window defaults to 500 if unspecified for example here is a version of the advancedhelphelpini file usingadvancedhelp title using advanced help weight 10 translation title translating advanced help inifile title help ini file format line break true  ',0),(4,'help',' why advanced help  the advanced help system was designed to replace the original drupal help system which has several flaws that make it hard to create new help hard to maintain existing help and particularly hard to access help the primary goal then is to increase the accessibility of help meaning the ability of both the user and the help text author to access the needed tools to use create maintain and translate the help this system is completely separate from drupal s hookhelp in drupal 6 it actually coexists with it in the future it is hoped that it will completely replace it allowing hookhelp to be deprecated and removed messages added to the top of a page are not really help often these messages are an introduction to a form or a short blurb telling a user what to do with a particular page the problem is these messages are always there they are easily ignored and they come before the actual page in general when users are learning they want to see the page first then ask questions the reverse order is much less conducive to actually teaching a user how to use something by allowing help to be available on request the system conforms more naturally to how most people work advanced help is organized by topic with the hookhelp method help text is organized by url path this is fine if you have help text describing how to use a particular page or what a particular page does but ultimately is limiting because manuals and documentation are usually grouped by topic and those topics are determined by the material itself advanced help allows the documentation author to organize topics as he or she sees fit the only restriction really is that each individual chunk of text needs to stand on its own as a discrete topic what s more modules can insert their topics into another module s hierarchy this would allow the drupal core to create a task based help navigation system which allows modules insert topics into that navigation fluidly this allows modules to continue to keep their systems separate yet integrate into the main system advanced help topics are processed html in their own files this separation makes it easy to find and modify currently everything is lumped together in hookhelp in php strings that are run through t and there is a fair amount of php code necessary in this system that actually gets in the way of writing good explanatory text in fact requiring a documentation author to understand php at all is a detriment the idea that documentation writers need to have php development as a skill seriously reduces the number of available contributors html on the other hand is a much more common skill is relatively easy to learn and the amount of html needed to write documentation is only a little bit more than the html used in forum posts another benefit to not using php is that the files themselves are safe they are unlikely to include malicious php code that could take over the server or do worse things this means that these files can be used relatively easily on the drupalorg hardware so that a module s help files can be made immediately available without needing to download the module it also means that descriptions of the module can be made on drupalorg that are version aware can be corrected easily in cvs with patches but can also be made available with the module so that drupalorg is not required this also means that we could if we wanted package the drupalorg handbooks or a subset of them directly into a drupal distribution or a drupal addon so that drupal administrators can have drupal help without needing to visit drupalorg this can be valuable in locked down corporate environments and on planes but more importantly the handbooks can be made version aware much more easily than the current method on drupalorg the downside to this method is that these books can t easily be made dynamic though the use of alter hooks could allow a module to make modifications to the help as needed doing this could make the help files less useful when you take them out of context advanced help files are translated as a file it is actually not easy to translate documents as strings particularly when the language being used is very much unlike english in fact when translating a document the organization of the sentences may change drastically it is also a burden on the cpu to do this as you are indexing on very long strings translators have a much better time translating a document as a unit because of the presence of the entire context advanced help has its own navigation system by making use of a navigation system specified in a ini file which is not php code and therefore safe to use on drupalorg sites the help can be structured like a book which is typical of online manuals this is familiar to users can be organized and reorganized and allows a module to include significantly richer text without burdening the php code with having its help loaded unnecessarily this book can be navigated hierarchically as well making it easy to keep related topics together advanced help is indexed by the search engine an important goal of this system was to add searchability to the help by being able to enter keywords into the search box and find relevant topics we come up with a system that resembles the kind of help that comes with many operating systems this is very valuable when searching through manuals trying to find out how to do a particular thing this search is specific to the help meaning that the help will not be mixed in with the global node search this can be considered both an advantage and a disadvantage for the most part this help system is meant to provide help to site administrators and content searches should not find it the disadvantage of course is when you want to use it for end user help you will not be able to inline help can be brought in via popups in addition to the manuallike hierarchical navigation advanced help can also provide contextsensitive additional help through a popup while popups are controversial the argument for using them is that when getting help while on a form  a popup will not throw away a user s data browsers are not very friendly to input forms if they are not submitted and navigating away from the form can be dangerous there are various other solutions to this problem but each one has a drawback the drawbacks to popups are well known but mostly it is the irritation of having new windows when getting help though a popup is usually invited help should not interfere with what the operation the user is trying to complete it differs greatly from the uninvited popup which are usually ads or popups meant to prevent users from navigating away from a site these popups can be added to a page with text links or icon links  ',0),(5,'help',' readme  id readmetxt v 12021 20100705 213721 soxofaan exp readme file for the captcha module for drupal captchamodule is the basic captcha module offering general captcha administration and a simple math challenge submodule imagecaptchamodule offers an image based challenge installation installation is like with all normal drupal modules extract the captcha folder from the tar ball to the modules directory from your website typically sites all modules dependencies the basic captcha module has no dependencies nothing special is required conflicts known issues captcha and page caching do not work together currently however the captcha module does support the drupal core page caching mechanism it just disables the caching of the pages where it has to put its challenges if you use other caching mechanisms it is possible that captcha s won t work and you get error messages like captcha validation error unknown captcha session id configuration the configuration page is at admin user captcha where you can configure the captcha module and enable challenges for the desired forms you can also tweak the image captcha to your liking  ',0),(6,'help',' fields and widgets the content construction kit cck is composed of numerous field and widget modules that can be used to add fields to any content type  ',0),(7,'help',' manage fields tab this page lets you manage the cck fields in your content type add fields and groups rearrange them access their configuration pages remove them from the content type  ',0),(8,'help',' add fields and groups the form elements at the bottom of the manage fields page let you add fields and groups to your content types the add existing field row is displayed only if there are fields available in other content types the add new group rows is displayed only if fieldgroup module is enabled your fields and groups will be created after you click the save button at the bottom of the page in subsequent pages you will be presented with the settings form for each field you added you will find more details on the required informations in the following pages  ',0),(9,'help',' add a new field at the bottom of the manage fields page for a content type you ll find this in order to add a new field to a content type you need to provide the following information label a humanreadable name for the field it will be used in input forms and on displayed content all characters are allowed including spaces accentuated or noneuropean characters field name a machinereadable name for the field it is used internally to identify the field and handle database storage when doing custom theming it is this identifier that you ll use to refer to that field important  the field name cannot be changed once the field has been created allowed characters az unaccentuated 09 and the underscore the length of the field name cannot exceed 32 characters including the field prefix that gets added automatically that is 26 free characters field type the type of data to be stored in that field important  the field type cannot be changed once the field has been created the available field types depend on the modules you have enabled on your site cck comes with 6 basic field types text integer float decimal node reference user reference additional modules can be downloaded to handle other field types such as dates files images look at the cck project page and the complete list of cckrelated modules  widget the form element that will be used to input data for this field on content forms text input select list etc each field type has its own list of available widgets when selecting a field type the list of widgets you can select is automatically updated  ',0),(10,'help',' add an existing field share a field across content types using a field across several content type can be handy if a piece of data is relevant for several content types a typical use case is a phone number field used in both restaurant and hotel content types even if hotels and restaurants are different enough to deserve their own specific set of fields and thus their own dedicated content types when a field has been added to more than one content type we also say it is shared and that it as several instances at the bottom of the manage fields page for a content type you ll find this in order to add a new instance of an existing field to a content type you need to provide the following information  label  a humanreadable name for the field it will be used in input forms and on displayed content all characters are allowed including spaces accentuated or noneuropean characters field  the field to be shared a field cannot appear more than once in each content type thus only fields that are not already present in the current content type will be proposed as shareable if none the add existing field option is not available on the manage fields page for this content type selecting a field automatically populates the label and widget values with the ones used by the previous field instance but you can change them if needed before submitting the form widget  the form element that will be used to input data for this field on content forms text input select list etc each field type has its own list of available widgets when selecting a field to share the list of widgets you can select is automatically updated  ',0),(11,'help',' add a new group field groups are used to visually gather several fields that are associated by some sort of logic for instance several text fields that hold the different parts of an address on input forms and displayed content the corresponding fields are enclosed inside an html fieldset at the bottom of the manage fields page for a content type you ll find this in order to add a new group to a content type you need to provide the following information  label  a humanreadable name for the group it will be used in input forms and on displayed content all characters are allowed including spaces accentuated or noneuropean characters group name a machinereadable name for the group it is used internally to identify the group when doing custom theming it is this identifier that you ll use to refer to that group important  the group name cannot be changed once the group has been created allowed characters az unaccentuated 09 and the underscore the length of the group name cannot exceed 32 characters including the group prefix that gets added automatically that is 26 free characters once a group has been created you can define what fields it will enclose by rearranging fields and groups   ',0),(12,'help',' rearrange fields and groups to change the order of fields grab a draganddrop handle and drag the field to a new location in the list grab a handle by clicking and holding the mouse while hovering over a handle icon remember that your changes will not be saved until you click the save button at the bottom of the page the order you define will be used both on input forms when creating or editing a post and on content display teasers content page rss items you can also change the order of noncck fields like title or file attachments  depending on the field this will affect input forms and or content display some of those fields are not displayed in both contexts if your content type has groups requires the fieldgroup module you can move a field inside a group by dragging it below the row of the group and then slightly to the right before dropping it note that groups can also be reordered but can currently not be nested inside other groups when adding a field or a group you can drag them directly to the intended spot in the list of fields and groups that are already present in your content type before clicking save   ',0),(13,'help',' remove fields and groups removing a field when you remove a field from a content type the data it holds are permanently erased you will be asked to confirm this action you will have to manually update your views pathauto settings etc if needed note if the field is shared across several content types removing it from one content type does not affect the data for the other content types removing a group removing a group from a content type does not remove the fields it contains and therefore erases no field data  ',0),(14,'help',' theming cck data in nodes note  these instructions assume you are familiar with the basic concepts of drupal 6 theming for more informations see the theme guide for drupal 6  and more specifically the overriding themable output section there are 3 levels where you can customize how the data in cck fields is displayed in nodes  ',0),(15,'help',' node templates template files all themes usually come with a default nodetplphp template drupal core lets you use the following variant suggestion node contenttypename tplphp ex nodestorytplphp if present will be used to theme a story node important  whenever you add new template files in your theme you need to rebuild the theme registry or the theme engine won t see them you can do that by visiting the administer modules page or using devel module  s clear cache link template variables cck makes the following variables available in your theme s node templates fieldname rendered contains the rendered html for the field including the label and all the field s values with the settings defined on the display fields tab groupname rendered contains the rendered html for the fieldgroup if any including the label and all the group s fields with the settings defined on the display fields tab this variable therefore includes the html contained in all the fieldname rendered variables for the group s fields fieldname contains the raw values of the fields in the usual arrayformat used internally by cck what you find in there depends on the field type each value also contains a view element that holds the readytodisplay value as rendered by the formatter for instance array 0 array nid 5 view a href node 5 title of node 5 a  raw data are not sanitized for output it is therefore not advised to use them directly  use the view value or run the values through contentformat  excluding fields from the content variable by default the content variable used in node templates contains the rendered html for the whole node cck fields and fieldgroups but also body file attachments fivestar widgets if for some fields you want to use the more finegrained variables described above you might want to use the exclude checkboxes on the display fields screen so that the output of those fields is excluded from the content variable you can then customize the display and layout of some cck fields or groups using the fieldname rendered groupname rendered variables and trust content to display the rest without getting duplicate information advanced trick the exclude checkboxes affect all active themes on sites with multiple themes however the list of fields to exclude from content might need to be different across the themes depending on how their respective node templates are structured a theme can bypass those settings by overriding the themecontentexclude function to specify the list of fields to exclude for this theme see the phpdoc of the function for more information  special case nodes in nodereference fields in addition to the above the following suggestions will be looked for in priority for nodes that are displayed as values of a nodereference field using the teaser or full node formatters nodenodereference referringfieldname typename tplphp ex nodenodereferencefieldnoderefstorytplphp if present will be used to theme a story node when refererenced in the fieldnoderef field nodenodereference typename tplphp ex nodenodereferencestorytplphp if present will be used to theme a story node when refererenced in any nodereference field nodenodereference referringfieldname tplphp ex nodenodereferencefieldnodereftplphp if present will be used to a node refererenced in the fieldnoderef field nodenodereferencetplphp if present will be used to theme nodes referenced in nodereference fields the following additional variables are available in templates for referenced nodes referringfield the nodereference field that references the current node referringnode the node referencing the current node  ',0),(16,'help',' field templates fieldlevel theming determines how the values of a given field are displayed the resulting output ends up in the content and fieldname rendered variables in the node templates template files in order to customize field themeing copy the contentfieldtplphp template file into your theme s root folder please keep the contents of the cck theme folder untouched for the same reason need to copy the file instead of just moving it edit that copy to your liking see the comments in cck theme content contentfieldtplphp for a list of all variables available in this template template suggestions in addition the theme layer will also look for fieldspecific variants suggestions in the following order of precedence contentfield fieldname contenttypename tplphp ex contentfieldfieldmyfieldstorytplphp if present will be used to theme the fieldmyfield field when displaying a story node contentfield contenttypename tplphp ex contentfieldstorytplphp if present will be used to theme all fields of story nodes contentfield fieldname tplphp ex contentfieldfieldmyfieldtplphp if present will be used to theme all fieldmyfield field in all the content types it appears in contentfieldtplphp if none of the above is present the base template will be used important  suggestions work only if the theme also has the base template file if your theme has contentfield tplphp files it must also have a contentfieldtplphp file whenever you add new template files in your theme you need to rebuild the theme registry or the theme engine won t see them you can do that by visiting the administer modules page or using devel module  s clear cache link see the working with template suggestions section of the theme guide for drupal 6 for more informations about templates and template suggestions  ',0),(17,'help',' formatter theme functions formatters are used to turn the raw data for a single field value into html the display fields tab lets you chose which formatter you want to use for each of your fields in cck 20 for drupal 6 all formatters now go through the theme layer therefore overriding a formatter s theme is another way you can alter how your values are displayed whereas changing contentfieldtplphp lets you change the html that wraps the values most formatters come as theme functions but some might use templates instead either way you can override them using the usual drupal 6 theme override practices for more informations see the theme guide for drupal 6  and more specifically the overriding themable output section  ',0),(18,'help',' nodereference field the nodereference field stores the nid of a related node the title of the related node is usually displayed as the value of this field the nodereference field can use an autocomplete widget or when used with optionwidgets  the available values can be presented to the end user in a dropdown select list checkboxes or radios a nodereference field can be used in views to create a relationship to another node to allow you to use any field argument or filter from the related node in your view  ',0),(19,'help',' number field the number field stores numeric data in the database it can either be an integer value a decimal value or a float value the number field provides a place for the administrator to create a list of allowed values for the field when used with optionwidgets  the allowed values are presented to the end user in a dropdown select list checkboxes or radios  ',0),(20,'help',' optionwidgets optionwidgets creates dropdown select lists checkboxes and radio widgets that can be used with fields that have specific allowed values the number and text fields have settings for creating lists of allowed values that can be used in optionwidgets the nodereference and userreference fields use optionwidgets to present the possible values in select lists or checkboxes  ',0),(21,'help',' text field the text field stores textual data in the database it can either be a simple textfield to hold up to 255 characters or a textarea of an unlimited size that can be combined with input filters to store lengthy descriptions and html code the text field provides a place for the administrator to create a list of allowed values for the field when used with optionwidgets  the allowed values are presented to the end user in a dropdown select list checkboxes or radios  ',0),(22,'help',' userreference field the userreference field stores the uid of a related user the name of the related user is usually displayed as the value of this field the userreference field can use an autocomplete widget or when used with optionwidgets  the available values can be presented to the end user in a dropdown select list checkboxes or radios a userreference field can be used in views to create a relationship to a user to allow you to use any field argument or filter from the related user in your view  ',0),(23,'help',' about chaos tool suite the chaos tool suite is a series of tools for developers to make code that i ve found to be very useful to views and panels more readily available certain methods of doing things particularly with ajax exportable objects and a plugin system are proving to be ideas that are useful outside of just views and panels this module does not offer much directly ot the end user but instead creates a library for other modules to use if you are an end user and some module asked you to install the ctools suite then this is far as you really need to go if you re a developer and are interested in these tools read on  tools provided by ctools plugins the plugins tool allows a module to allow other modules and themes to provide plugins which provide some kind of functionality or some kind of task for example in panels there are several types of plugins content types which are like blocks layouts which are page layouts and styles which can be used to style a panel each plugin is represented by a inc file and the functionaly they offer can differ wildly context context is the idea that the objects that are used in page generation have more value than simply creating a single piece of output instead contexts can be used to create multiple pieces of content that can all be put onto the page additionally contexts can be used to derive other contexts via relationships such as determining the node author and displaying data about the new context ajax tools ajax also known as ahah is a method of allowing the browser and the server to communicate without requiring a page refresh it can be used to create complicated interactive forms but it is somewhat difficult to integrate into drupal s form api these tools make it easier to accomplish this goal in addition ctools provides a few other javascript helpers such as a modal dialog a collapsible div a simple dropdown and dependent checkboxes css scrubbing and caching drupal comes with a fantastic array of tools to ensure html is safe to output but does not contain any similar tools for css ctools provides a small tool to sanitize css so that userinput css code can still be safely used it also provides a method for caching css for better performance exportable objects views and panels both use objects that can either be in code or in the database and the object can be exported into a piece of php code so that it can be moved from site to site or out of the database entirely this library abstracts that so that other modules can use this same concept for their data form tools drupal 6 s fapi really improved over drupal 5 and made a lot of things possible still it missed a few items that were needed to make form wizards and truly dynamic ajax forms possible ctools includes a replacement for drupalgetform that has a few more options and allows the caller to examine the formstate once the form has completed form wizards finally an easy way to have form wizards which is any form which is actually a string of forms that build up to a final conclusion the form wizard supports a single entry point the ability to choose whether or not the user can go forward back up on the form and easy callbacks to handle the difficult job of dealing with data in between forms temporary object cache for normal forms all of the data needed for an object is stored in the form so that the browser handles a lot of the work for multistep and ajax forms however this is impractical and letting the browser store data can be insecure the object cache provides a nonvolatile location to store temporary data while the form is being worked on this is much safer than the standard drupal caching mechanism which is volatile meaning it can be cleared at any time and any system using it must be capable of recreating the data that was there this system also allows for object locking since any object which has an item in the cache from another person can be assumed to be locked for editing  ',0),(24,'help',' context tool ',0),(25,'help',' context based access control plugins access plugins allow context based access control to pages title title of the plugin description description of the plugin callback callback to see if there is access is available params conf contexts account required context zero or more required contexts for this access plugin default an array of defaults or a callback giving defaults settings form settings form params form formstate conf settings form validate settings form submit warning your settings array will be stored in the menu system to reduce loads so be trim ',0),(26,'help',' context plugins context plugin data title visible title description description of context context callback to create a context params empty data null conf false settings form callback to show a context setting form params conf external false settings form validate params form formvalues formstate settings form submit params ctoolscontextnodesettingsformsubmit keyword the default keyword to use context name the unique identifier for this context for use by required context checks no ui if true this context cannot be selected  ',0),(27,'help',' argument plugins arguments create a context from external input which is assumed to be a string as though it came from a url element title title description description keyword default keyword for the context context callback to create the context params arg null conf null empty false default either an array of default settings or a string which is a callback or null to not use settings form params form formstate conf gets the whole form should put anything it wants to keep automatically in form settings settings form validate params form formstate settings form submit params form formstate criteria form params form formstate conf argument id gets the whole argument it should only put form widgets in form id conf may not be properly initialized so always guard against this due to arguments being changed and handlers not being updated to match submit validate criteria select returns true if the selected criteria matches the context params context conf  ',0),(28,'help',' relationship plugins  title the title to display description description to display keyword default keyword for the context created by this relationship required context one or more ctoolscontextrequired optional objects describing the context input new panelsrequiredcontext t node node context the callback to create the context params context null conf settings form settings form params conf settings form validate validate  ',0),(29,'help',' content plugins the ctools pluggable content system provides various pieces of content as discrete bits of data that can be added to other applications such as panels or dashboard via the ui whatever the content is added to stores the configuration for that individual piece of content and provides this to the content each content type plugin will be contained in a inc file with subsidiary files if necessary in or near the same directory each content type consists of some information and one or more subtypes which all use the same renderer subtypes are considered to be instances of the type for example the views content type would have each view in the system as a subtype many content types will have exactly one subtype because the content and forms can be provided via ajax the plugin also provides a list of css and javascript information that should be available on whatever page the content or forms may be ajaxed onto for the purposes of selecting content from the ui each content subtype will have the following information a title a short description a category do we want to add hierarchy categories do we want category to be more than just a string an icon do we want multiple icons this becomes a hefty requirement each piece of content provides one or more configuration forms if necessary and the system that includes the content will handle the data storage these forms can be provided in sequence as wizards or as extra forms that can be accessed through advanced administration the plugin for a content type should contain title for use on the content permissions screen content types either an array of content type definitions or a callback that will return content type definitions this callback will get the plugin definition as an argument content type optional provide a single content type definition this is only necessary if content types might be intensive render callback the callback to render the content parameters subtype the name of the subtype being rendered not the loaded subtype data conf the stored configuration for the content args any arguments passed context an array of contexts requested by the required contexts and assigned by the configuration step incomingcontent any incoming content if this is a wrapper admin title a callback to provide the administrative title if it is not a function then it will be counted as a string to use as the admin title admin info a callback to provide administrative information about the content to be displayed when manipulating the content it should contain a summary of configuration edit form either a single form id or an array of forms keyed by form id with the value to be used as the title of the form title me be used as a placeholder for the administrative title if necessary example array ctoolsexamplecontentformsecond t configure first form ctoolsexamplecontentformfirst t configure second form the first form will always have required configuration added to it these forms are normal fapi forms but you do not need to provide buttons these will be added by the form wizard add form optional if different from the edit forms provide them here in the same manner also may be set to false to not have an add form css a file or array of css files that are necessary for the content js a file or array of javascript files that are necessary for the content to be displayed admin css a file or array of css files that are necessary for the forms admin js a file or array of javascript files that are necessary for the forms extra forms an array of form information to handle extra administrative forms no title override set to true if the title cannot be overridden single set to true if this content provides exactly one subtype render last set to true if for some reason this content needs to render after other content this is primarily used for forms to ensure that render order is correct todo many of the above callbacks can be assumed based upon patterns modulename name function ie render admintitle admininfo etc todo some kind of simple access control to easily filter out content the subtype definition should contain title the title of the subtype icon the icon to display for the subtype path the path for the icon if it is not in the same directory as the plugin description the short description of the subtype to be used when selecting it in the ui category either a text string for the category or an array of the text string followed by the category weight required context optional either a ctoolscontextrequired or ctoolscontextoptional or array of contexts for this content if omitted no contexts are used rendered content rendered content is a little more than just html title the safe to render title of the content content the safe to render html content links an array of links associated with the content suitable for theme links more an optional more link destination only adminlinks administrative links associated with the content suitable for theme links feeds an array of feed icons or links associated with the content each member of the array is rendered html type the content type subtype the content subtype these two may be used together as moduledelta for block style rendering todo example todo after implementations are updated to new version  ',0),(30,'help',' plugins and apis tool the plugins tool allows a module to allow other modules and themes to provide plugins which provide some kind of functionality or some kind of task for example in panels there are several types of plugins content types which are like blocks layouts which are page layouts and styles which can be used to style a panel each plugin is represented by a inc file and the functionality they offer can differ wildly a module which uses plugins can implement a hook describing the plugin which is not necessary as defaults will be filled in and then calls a ctools function which loads either all the known plugins used for listing choosing or loads a specific plugin used when its known which plugin is needed from the perspective of the plugin system a plugin is a packet of data usually some printable info and a list of callbacks it is up to the module implementing plugins to determine what that info means and what the callbacks do a module which implements plugins must first implement the hookctoolsplugindirectory function which simply tells the system which plugins are supported and what directory to look in each plugin will then be in a inc file in the directory supplied the inc file will contain a specially named hook which returns the data necessary to implement the plugin ',0),(31,'help',' implementing apis apis are a form of plugins that are tightly associated with a module instead of a module providing any number of plugins each module provides only one file for an api and this file can contain hooks that the module should invoke modules support this api by implementing hookctoolspluginapi module api if they support the api they return a packet of data function mymodulectoolspluginapi module api if module some module api some api return array version the minimum api version this system supports if this api version is incompatible then the inc file will not be loaded path where to find the file optional if not specified it will be the module s directory file an alternative version of the filename if not specified it will be module apiinc this implementation must be in the module file modules utilizing this can invole ctoolspluginapiinclude in order to ensure all modules that support the api will have their files loaded as necessary it s usually easiest to create a small helper function like this define mymoduleminimumversion 1 define mymoduleversion 1 function mymoduleincludeapi ctoolsinclude plugins return ctoolspluginapiinclude mymodule myapi mymoduleminimumversion mymoduleversion using a define will ensure your use of version numbers is consistent and easy to update when you make api changes you can then use the usual moduleinvoke type commands mymoduleincludeapi moduleinvoke myhook data if you need to pass references this construct is standard foreach mymoduleincludeapi as module info function module hookname just because they implement the api and include a file does not guarantee they implemented a hook function if functionexists function continue typically arraymerge is used below if data is returned result function data1 data2 data3 todo there needs to be a way to check api version without including anything as a module may simply provide normal plugins and versioning could still matter  ',0),(32,'help',' creating plugins there are two primary pieces to using plugins the first is getting the data and the second is using the data getting the data to create a plugin a module only has to execute ctoolsgetplugins with the right data ctoolsinclude plugins ctoolsgetplugins module type id in the above example module should be your module s name and type is the type of the plugin it is typically best practice to provide some kind of wrapper function to make this easier for example panels provides the following functions to implement the contenttypes plugin fetch metadata on a specific contenttype plugin param content type name of a panel content type return an array with information about the requested panel content type function panelsgetcontenttype contenttype ctoolsinclude context ctoolsinclude plugins return ctoolsgetplugins panels contenttypes contenttype fetch metadata for all contenttype plugins return an array of arrays with information about all available panel content types function panelsgetcontenttypes ctoolsinclude context ctoolsinclude plugins return ctoolsgetplugins panels contenttypes as a plugin creator your module can also implement a hook to give more information about this plugin and to enable a few features that are not normally enabled if you need any of these features simply implement hookctoolsplugintype where type is the same type sent to ctoolsgetplugins this isn t a true hook it will only be called for the module that was given this hook returns an array inform ctools that the layout plugin can be loaded from themes function panelsctoolspluginlayouts return array load themes true the following information can be specified cache defaults to  false if set to true the results of ctoolsgetplugins will be cached in the cache table by default thus preventing inc files from being loaded ctoolsgetplugins looking for a specific plugin will always load the appropriate inc file cache table defaults to   cache  if cache is true then this value specifies the cache table where the cached plugin information will be stored defaults defaults to  array  an array of defaults that should be added to each plugin this can be used to ensure that every plugin has the basic data necessary these defaults will not ovewrite data supplied by the plugin this could also be a function name in which case the callback will be used to provide defaults note however that the callbackbased approach is deprecated as it is redundant with the process callback and as such will be removed in later versions consequently you should only use the array form for maximum crossversion compatibility load themes defaults to  false if set to true then plugins of this type can be supplied by themes as well as modules if this is the case all themes that are currently enabled will provide a plugin note due to a slight ui bug in drupal it is possible for the default theme to be active but not enabled if this is the case that theme will not provide plugins so if you are using this feature be sure to document that issue also themes set via customtheme do not necessarily need to be enabled but the system has no way of knowing what those themes are so the enabled flag is the only true method of identifying which themes can provide layouts hook defaults to   dynamic value the name of the hook used to collect data for this plugin normally this is  module type  but this can be changed here if you change this you must be sure to document this for your plugin implementors as it will change the format of the specially named hook process defaults to    an optional function callback to use for processing a plugin this can be used to provide automated settings that must be calculated perplugin instance ie it is not enough to simply append an array via defaults the parameters on this callback are  callback plugin info  where plugin is a reference to the plugin as processed and info is the fully processed result of hookctoolspluginapiinfo extension defaults to   inc  can be used to change the extension on files containing plugins of this type by default the extension will be inc though it will default to info if info files is set to true do not include the dot in the extension if changing it that will be added automatically info file defaults to  false if set to true then the plugin will look for a info file instead of a inc internally this will look exactly the same though obviously a info file cannot contain functions this can be good for styles that may not need to contain code use hooks defaults to  true  use to enable support for plugin definition hooks instead of plugin definition files note using a central plugin definition hook is less optimal for the plugins system and as such this will default to false in later versions child plugins defaults to  false if set to true the plugin type can automatically have child plugins meaning each plugin can actually provide multiple plugins this is mostly used for plugins that store some of their information in the database such as views blocks or exportable custom versions of plugins to implement each plugin can have a get child and get children callback both of these should be implemented for performance reasons since it is best to avoid getting all children if necessary but if get child is not implemented it will fall back to get children if it has to child plugins should be named parent child with the being the separator so that it knows which parent plugin to ask for teh child the get children method should at least return the parent plugin as part of the list unless it wants the parent plugin itself to not be a choosable option which is not unheard of get children arguments are plugin parent and get child arguments are plugin parent child in addition there is a module and type settings these are for internal use of the plugin system and you should not change these using the data each plugin returns a packet of data which is added to with a few defaults each plugin is guaranteed to always have the following data name the name of the plugin this is also the key in the array of the full list of plugins and is placed here since that is not always available module the module that supplied the plugin file the actual file containing the plugin path the path to the file containing the plugin this is useful for using secondary files such as templates css files images etc that may come with a plugin any of the above items can be overridden by the plugin itself though the most likely one to be modified is the path the most likely data beyond simple printable data for a plugin to provide is a callback the plugin system provides a pair of functions to make it easy and consistent for these callbacks to be used the first is ctoolsplugingetfunction which requires the full plugin object get a function from a plugin if it exists if the plugin is not already loaded try ctoolspluginloadfunction instead param plugin the loaded plugin type param callbackname the identifier of the function for example settings form return the actual name of the function to call or null if the function does not exist function ctoolsplugingetfunction plugin callbackname the second does not require the full plugin object and will load it load a plugin and get a function name from it returning success only if the function exists param module the module that owns the plugin type param type the type of plugin param id the id of the specific plugin to load param callbackname the identifier of the function for example settings form return the actual name of the function to call or null if the function does not exist function ctoolspluginloadfunction module type id callbackname both of these functions will ensure any needed files are included in fact it allows each callback to specify alternative include files the plugin implementation could include code like this callbackname actualnameoffunctionhere or like this callbackname array file filename path filepath optional will use plugin path if absent function actualnameoffunctionhere an example for pluginexample type plugin array name myplugin module mymodule examplecallback array file mypluginextrafileinc function mymodulemypluginexamplecallback to utilize this callback on this plugin if function ctoolsplugingetfunction plugin examplecallback function arg1 arg2 etc  document your plugins  since the data provided by your plugin tends to be specific to your plugin type you really need to document what the data returned in the hook in the inc file will be or nobody will figure it out use advanced help and document it there if every system that utilizes plugins does this then plugin implementors will quickly learn to expect the documentation to be in the advanced help  ',0),(33,'help',' implementing plugins to implement plugins you need to implement a single hook in your module to tell the system where your plugins live and then you need to implement one or more inc files that contain the plugin data telling it where your plugins live to implement any plugins at all you must implement a single function for all plugins  hookctoolsplugindirectory  every time a module loads plugins this hook will be called to see which modules implement those plugins and in what directory those plugins will live function hookctoolsplugindirectory module plugin if module panels plugin contenttypes return plugins contenttypes the directory returned should be relative to your module another common usage is to simply return that you implement all plugins owned by a given module or modules function hookctoolsplugindirectory module plugin if module panels return plugins plugin typically it is recommended that all plugins be placed into the plugins directory for clarity and maintainability inside the directory any number of subdirectories can be used for plugins that require extra files such as templates css javascript or image files this is highly recommended mymodulemodule mymoduleinfo plugins contenttypes mycontenttypeinc layouts mylayoutinc mylaoutcss mylayouttplphp mylayoutimagepng how a theme can implement plugins themes can implement plugins if the plugin owner specified that it s possible in its hookctoolsapitype call if so it is generally exactly the same as modules except for one important difference themes don t get hookctoolsplugindirectory instead themes add a line to their info file plugins module type directory how to structure the inc file the top of the inc file should contain an array that defines the plugin this array is simply defined in the global namespace of the file and does not need a function note that previous versions of this plugin system required a specially named function while this function will still work its use is now discouraged as it is annoying to name properly this array should look something like this plugin array key value several values will be filled in for you automatically but you can override them if necessary they include name path file and module additionally the plugin can owner can provide other defaults as well after this array if your plugin needs functions they can be declared different plugin types have different needs here so exactly what else will be needed will change from type to type  ',0),(34,'help',' exportable objects tool exportable objects are objects that can live either in the database or in code or in both if they live in both then the object in code is considered to be overridden meaning that the version in code is ignored in favor of the version in the database the main benefit to this is that you can move objects that are intended to be structure or featurerelated into code thus removing them entirely from the database this is a very important part of the deployment path since in an ideal world the database is primarily user generated content whereas site structure and site features should be in code however many many features in drupal rely on objects being in the database and provide uis to create them using this system you can give your objects dual life they can be created in the ui exported into code and put in revision control views and panels both use this system heavily plus any object that properly implements this system can be utilized by the features module to be used as part of a bundle of objects that can be turned into feature modules typically exportable objects have two identifiers one identifier is a simple serial used for database identification it is a primary key in the database and can be used locally it also has a name which is an easy way to uniquely identify it this makes it much less likely that importing and exporting these objects across systems will have collisions they still can of course but with good name selection these problems can be worked around making your objects exportable to make your objects exportable you do have to do a medium amount of work create a chunk of code in your object s schema definition in the install file to introduce the object to ctools export system create a load function for your object that utilizes ctoolsexportloadobject create a save function for your object that utilizes drupalwriterecord or any method you desire create an import and export mechanism from the ui the export section of the schema file exportable objects are created by adding definition to the schema in an export section for example function mymoduleschema schema mymodulemyobj array description t table storing myobj definitions export array key name key name name primary key oid identifier myobj exports will be as myobj default hook defaultmymodulemyobj function hook name api array owner mymodule api defaultmymodulemyobjs base name for api include files minimumversion 1 currentversion 1 if the key is stored in a table that is joined in specify it key in table myjointable if your object s data is split up across multiple tables you can specify additional tables to join this is very useful when working with modules like exportablesmodule that has a special table for translating keys to local database ids the joined table must have its own schema definition if using joins you should implement a delete callback see below to ensure that deletes happen properly exportinc does not do this automatically join array exportables array the following parameters will be used in this way select from mymodulemyobj t0 inner join myjointable t1 on t0id t1id and extras table myjointable leftkey format rightkey id optionally you can define extra clauses to add to the inner join extras and extraclauses you must specify which fields will be loaded these fields must exist in the schema definition of the joined table load array machine and finally you can define other tables to perform inner joins otherjoins array table fields array name array type varchar length 255 description unique id for this object used to identify it programmatically oid array type serial unsigned true not null true description primary id field for the table not used for anything except internal lookups no export true do not export databaseonly keys primary key array oid unique keys array name array name return schema key this is the primary key of the exportable object and should be a string as names are more portable across systems it is possible to use numbers here but be aware that export collisions are very likely defaults to name key name human readable title of the export key defaults to name because the schema is cached do not translate this it must instead be translated when used primary key objects should contain a primary key which is a database identifier primarily used to determine if an object has been written or not this is required for the default crud save callback to work object the class the object should be created as defaults as stdclass can disable control whether or not the exportable objects can be disabled all this does is cause the disabled field on the object to always be set appropriately and a variable is kept to record the state changes made to this state must be handled by the owner of the object defaults to true status exportable objects can be enabled or disabled and this status is stored in a variable this defines what variable that is defaults to default table default hook what hook to invoke to find exportable objects that are currently defined these will all be gathered into a giant array defaults to default table identifier when exporting the object the identifier is the variable that the exported object will be placed in defaults to table bulk export declares whether or not the exportable will be available for bulk exporting list callback bulk export callback to provide a list of exportable objects to be chosen for bulk exporting defaults to module table list if the function exists if it is not a default listing function will be provided that will make a best effort to list the titles see ctoolsexportdefaultlist to hook code callback function used to generate an export for the bulk export process this is only necessary if the export is more complicated than simply listing the fields defaults to module table tohookcode create callback crud callback to use to create a new exportable item in memory if not provided the default function will be used the single argument is a boolean used to determine if defaults should be set on the object this object will not be written to the database by this callback load callback crud callback to use to load a single item if not provided the default load function will be used the callback will accept a single argument which should be an identifier of the export key load all callback crud callback to use to load all items usually for administrative purposes if not provided the default load function will be used the callback will accept a single argument to determine if the load cache should be reset or not save callback crud callback to use to save a single item if not provided the default save function will be used the callback will accept a single argument which should be the complete exportable object to save delete callback crud callback to use to delete a single item if not provided the default delete function will be used the callback will accept a single argument which can be either the object or just the export key to delete the callback must be able to accept either export callback crud callback to use for exporting if not provided the default export function will be used the callback will accept two arguments the first is the item to export the second is the indent to place on the export if any import callback crud callback to use for importing if not provided the default export function will be used this function will accept the code as a single argument and if the code evaluates return an object represented by that code in the case of failure this will return a string with human readable errors in addition each field can contain the following no export set to true to prevent that field from being exported export callback a function to override the export behavior it will receive myobject field value indent as arguments by default fields are exported through ctoolsvarexport  reserved keys on exportable objects exportable objects have several reserved keys that are used by the ctools export api each key can be found at myobj key on an object loaded through ctoolsexportloadobject implementing modules should not use these keys as they will be overwritten by the ctools export api apiversion the api version that this object implements disabled a boolean for whether the object is disabled exportmodule for objects that live in code the module which provides the default object exporttype a bitmask representation of an object current storage you can use this bitmask in combination with the exportincode and exportindatabase constants to test for an object s storage in your code incodeonly a boolean for whether the object lives only in code table the schema api table that this object belongs to type a string representing the storage type of this object can be one of the following  normal is an object that lives only in the database overridden is an object that lives in the database and is overriding the exported configuration of a corresponding object in code default is an object that lives only in code the load callback calling ctoolsexportcrudload table name will invoke your load callback and calling ctoolsexportcrudloadall table reset will invoke your load all callback the default handlers should be sufficient for most uses typically there will be two load functions a single load to load just one object and an all load to load all of the objects for use in administrating the objects or utilizing the objects when you need all of them using ctoolsexportloadobject you can easily do both as well as quite a bit in between this example duplicates the default functionality for loading one myobj load a single myobj function mymodulemyobjload name ctoolsinclude export result ctoolsexportloadobject mymodulemyobjs names array name if isset result name return result name  the save callback calling ctoolsexportcrudsave table object will invoke your save callback the default handlers should be sufficient for most uses for the default save mechanism to work you must define a primary key in the export section of your schema the following example duplicates the default functionality for the myobj save a single myobj function mymodulemyobjsave myobj update isset myobj oid isnumeric myobj oid array oid array return drupalwriterecord myobj myobj update  default hooks for your exports all exportables come with a default hook which can be used to put your exportable into code the easiest way to actually use this hook is to set up your exportable for bulk exporting enable the bulk export module and export an object  ',0),(35,'help',' exportable objects ui creator most user interfaces for exportables are very similar so ctools includes a tool to provide the framework for the most common ui this tool is a plugin of the exportui type in order to create a ui for your exportable object with this tool you first need to ensure that your module supports the plugin function hookctoolsplugindirectory module plugin if module ctools plugin exportui return plugins plugin then you need to create a plugin inc file describing your ui most of the ui runs with sane but simple defaults so for the very simplest ui you don t need to do very much this is a very simple example plugin for the example export type plugin array the name of the table as found in the schema in hookinstall this must be an exportable type with the export section defined schema example the access permission to use if not provided it will default to administer site configuration access administer example you can actually define large chunks of the menu system here nothing is required here if you leave out the values the prefix will default to admin build and the item will default to the plugin name menu array menu prefix admin build menu item example title of the top level menu note this should not be translated as the menu system will translate it menu title example description of the top level menu which is usually needed for menu items in an administration list will be translated by the menu system menu description administer site example objects these are required to provide proper strings for referring to the actual type of exportable proper means it will appear at the beginning of a sentence title singular t example title singular proper t example title plural t examples title plural proper t examples this will provide you with a form for editing the properties on your exportable with validate and submit handler the item being edited will be in formstate item the submit handler is only responsible for moving data from formstate values to formstate item all callbacks will accept form and formstate as arguments form array settings examplectoolsexportuiform validate examplectoolsexportuiformvalidate submit examplectoolsexportuiformsubmit for a more complete list of what you can set in your plugin please see ctoolsexportuidefaults in includes exportuiinc to see what the defaults are more advanced uis the bulk of this ui is built on an class called ctoolsexportui which is itself stored in ctools plugins exportui as the default plugin many uis will have more complex needs than the defaults provide using oo and overriding methods can allow an implementation to use the basics and still provide more where it is needed to utilize this first add a handler directive to your plugin inc file handler array class ctoolsexportuiexample parent ctoolsexportui then create your class in ctoolsexportuiexampleclassphp in your plugins directory class ctoolsexportuiexample extends ctoolsexportui you can override any method found in the class see the source file for details in particular there are several list methods that are good candidates for overriding if you need to provide richer data for listing sorting or filtering if you need multistep add edit forms you can override editpage addpage clonepage and importpage to put your wizard in place of the basic editing system for an example of how to use multistep wizards see the importpage method  ',0),(36,'help',' form tools ctools form tool is a replacement for drupalgetform that includes some additional functionality it takes formstate as an argument which is accepted as a reference meaning when the form is complete you can examine the formstate to see what the form did it can handle get as an input source or the input can be provided from some other source it can be told not to render or not to redirect which can be important during ajax operations it can provide a special wrapper form which is used by the wizard tool to provide a standard set of buttons to a form usage ctoolsinclude form output ctoolsbuildform formid formstate previously arguments to the form builder were passed into drupalgetform this is no longer true you have two options for passing arguments to the form with ctoolsbuildform set formstate args to an array which will then be passed to the builder as before or simply set formstate values and refer to them in the builder values you can set on formstate noredirect if set to true completely disables redirecting no matter what formstate redirect has been set to rerender defaults to true if set the form will be rerendered after submit if not redirected if set to false the form will not be rerendered after submit and output will be null method defaults to post may be set to get if get is in use form ids and tokens will not be used and all get forms will automatically be assumed to be submitted beware as this can have unexpected effects on default values as fapi doesn t quite know how to handle this state input defaults to post if using get you should set this to get wrapper callback if this is set to a function name the form will be wrapped in another form this changes how the builder callback work first form is set to a blank array then the wrapper callback is called with form and formstate as arguments then the form builder is called with form and formstate as arguments no other arguments are given args an array of arguments that will be passed to the form builder callback just as though they were passed as arguments to drupalgetform want form defaults to false if set instead of rendering the return value will be the form array it can then be rendered via drupalrender normally this is particularly useful for ajax operations that may need to process a form and then only render a part of it  ',0),(37,'help',' form wizard tool form wizards or multistep forms are a process by which the user goes through or can use an arbitrary number of different forms to create a single object or perform a single task traditionally the multistep form is difficult in drupal because there is no easy place to put data in between forms no longer the form wizard tool allows a single entry point to easily set up a wizard of multiple forms provide callbacks to handle data storage and updates between forms and when forms are completed this tool pairs well with the object cache tool for storage the form info array the wizard starts with an array of data that describes all of the forms available to the wizard and sets options for how the wizard will present and control the flow here is an example of the forminfo array as used in the delegator module forminfo array id delegatorpage path admin build pages edit pagename step show trail true show back true show return false next callback delegatorpageaddsubtasknext finish callback delegatorpageaddsubtaskfinish return callback delegatorpageaddsubtaskfinish cancel callback delegatorpageaddsubtaskcancel order array basic t basic settings argument t argument settings access t access control menu t menu settings multiple t task handlers forms array basic array form id delegatorpageformbasic access array form id delegatorpageformaccess menu array form id delegatorpageformmenu argument array form id delegatorpageformargument multiple array form id delegatorpageargumentformmultiple the above array starts with an id which is used to identify the wizard in various places and a path which is needed to redirect to the next step between forms it then creates some settings which control which pieces are displayed in this case it displays a form trail and a back button but not the return button then there are the wizard callbacks which allow the wizard to act appropriately when forms are submitted finally it contains a list of forms and their order so that it knows which forms to use and what order to use them by default note that the keys in the order and list of forms match that key is called the step and is used to identify each individual step of the wizard here is a full list of every item that can be in the form info array id an id for wizard this is used like a hook to automatically name callbacks  as well as a form step s form building function it is also used in trail theming path the path to use when redirecting between forms  step will be replaced with the key for the form return path when a form is complete this is the path to go to this is required if the return button is shown and not using ajax it is also used for the finish button if it is not present and needed the cancel path will also be checked cancel path when a form is canceled this is the path to go to this is required if the cancel is shown and not using ajax show trail if set to true the form trail will be shown like a breadcrumb at the top of each form defaults to false show back if set to true show a back button on each form defaults to false show return if set to true show a return button defaults to false show cancel if set to true show a cancel button defaults to false back text set the text of the back button defaults to t back next text set the text of the next button defaults to t continue return text set the text of the return button defaults to t update and return finish text set the text of the finish button defaults to t finish cancel text set the text of the cancel button defaults to t cancel ajax turn on ajax capabilities using ctools ajaxinc defaults to false modal put the wizard in the modal tool the modal must already be open and called from an ajax button for this to work which is easily accomplished using functions provided by the modal tool ajax render a callback to display the rendered form via ajax this is not required if using the modal tool but is required otherwise since ajax by itself does not know how to render the results params formstate output finish callback the function to call when a form is complete and the finish button has been clicked this function should finalize all data params formstate defaults to forminfo id finish if function exists cancel callback the function to call when a form is canceled by the user this function should clean up any data that is cached params formstate defaults to forminfo id cancel if function exists return callback the function to call when a form is complete and the return button has been clicked this is often the same as the finish callback params formstate defaults to forminfo id return if function exists next callback the function to call when the next button has been clicked this function should take the submitted data and cache it for later use by the finish callback params formstate defaults to forminfo id next if function exists order an optional array of forms keyed by the step which represents the default order the forms will be displayed in if not set the forms array will control the order note that submit callbacks can override the order so that branching logic can be used forms an array of form info arrays keyed by step describing every form available to the wizard if order array isn t set the wizard will use this to set the default order each array contains form id the id of the form as used in the drupal form system this is also the name of the function that represents the form builder defaults to forminfo id stepform include the name of a file to include which contains the code for this form this makes it easy to include the form wizard in another file or set of files this must be the full path of the file so be sure to use drupalgetpath when setting this this can also be an array of files if multiple files need to be included title the title of the form to be optionally set via drupalgettitle this is required when using the modal if formstate title is not set invoking the form wizard your module should create a page callback via hookmenu and this callback should contain an argument for the step the path that leads to this page callback should be the same as the path set in the forminfo array the page callback should set up the forminfo and figure out what the default step should be if no step is provided note that the wizard does not do this for you you must specify a step then invoke the form wizard formstate array ctoolsinclude wizard output ctoolswizardmultistepform forminfo step formstate if using ajax or the modal this part is actually done if not you have one more small step return output  forms and their callbacks each form within the wizard is a complete independent form using drupal s form api system it has a form builder callback as well as submit and validate callbacks and can be form altered the primary difference between these forms and a normal drupal form is that the submit handler should not save any data instead it should make any changes to a cached object usually placed on the formstate and only the finish or return handler should actually save any real data how you handle this is completely up to you the recommended best practice is to use the ctools object cache and a good way to do this is to write a couple of wrapper functions around the cache that look like these example functions get the cached changes to a given task handler function delegatorpagegetpagecache name ctoolsinclude objectcache cache ctoolsobjectcacheget delegatorpage name if cache cache delegatorpageload name cache locked ctoolsobjectcachetest delegatorpage name return cache store changes to a task handler in the object cache function delegatorpagesetpagecache name page ctoolsinclude objectcache cache ctoolsobjectcacheset delegatorpage name page remove an item from the object cache function delegatorpageclearpagecache name ctoolsinclude objectcache ctoolsobjectcacheclear delegatorpage name using these wrappers when performing a getcache operation it defaults to loading the real object it then checks to see if another user has this object cached using the ctoolsobjectcachetest function which automatically sets a lock which can be used to prevent writes later on with this set up the next finish and cancel callbacks are quite simple callback generated when the add page process is finished function delegatorpageaddsubtaskfinish formstate page formstate page create a real object from the cache delegatorpagesave page clear the cache delegatorpageclearpagecache formstate cache name callback generated when the next button is clicked all we do here is store the cache function delegatorpageaddsubtasknext formstate update the cache with changes delegatorpagesetpagecache formstate cache name formstate page callback generated when the cancel button is clicked all we do here is clear the cache function delegatorpageaddsubtaskcancel formstate update the cache with changes delegatorpageclearpagecache formstate cache name all that s needed to tie this together is to understand how the changes made it into the cache in the first place this happened in the various form submit handlers which made changes to formstate page based upon the values set in the form store the values from the basic settings form function delegatorpageformbasicsubmit form formstate if isset formstate page pid empty formstate page import formstate page name formstate values name formstate page admintitle formstate values admintitle formstate page path formstate values path no database operations were made during this submit and that s a very important distinction about this system proper handling of back button when using  show back true the cached data should be assigned to the  defaultvalue form property otherwise when the user goes back to the previous step the forms default values instead of his cached input is used form builder function for wizard function wizardidstep2form form formstate formstate my data mymodulegetcache formstate cache name form example array type radios title t title defaultvalue formstate my data example formstate my data example default options array default t default setting1 t setting1 submit handler to prepare needed values for storing in cache function wizardidstep2formsubmit form formstate formstate my data example formstate values example the data is stored in the my data object on submitting if the user goes back to this step the cached my data is used as the default form value the function mymodulegetcache  is like the cache functions explained above required fields cancel and back buttons if you have required fields in your forms the back and cancel buttons will not work as expected since validation of the form will fail you can add the following code to the top of your form validation to avoid this problem validation handler for step2 form function wizardidstep2formvalidate form formstate if the clicked button is anything but the normal flow if formstate clickedbutton next formstate next drupalgetmessages error formseterror null true return you form validation goes here  wizard for anonymous users if you are creating a wizard which is be used by anonymous users you might run into some issues with drupal s caching for anonymous users you can circumvent this by using hookinit and telling drupal to not cache your wizard pages implementation of hook init function mymoduleinit if the path leads to the wizard if drupalmatchpath get q path to your wizard set cache to false globals conf cache false  ',0),(38,'help',' ajax and javascript helper tools ',0),(39,'help',' javascript modal tool ctools provides a simple modal that can be used as a popup to place forms it differs from the normal modal frameworks in that it does not do its work via an iframe this is both an advantage and a disadvantage the iframe simply renders normal pages in a subbrowser and they can do their thing that makes it much easier to put arbitrary pages and forms in a modal however the iframe is not very good at actually communicating changes to the main page so you cannot open the modal have it do some work and then modify the page invoking the modal the basic form of the modal can be set up just by including the javascript and adding the proper class to a link or form that will open the modal to include the proper javascript simply include the library and call the addjs function ctoolsinclude modal ctoolsmodaladdjs you can have links and buttons bound to use the modal by adding the class ctoolsusemodal for convenience there is a helper function to try and do this though it s not great at doing all links so using this is optional render an image as a button link this will automatically apply an ajax class to the link and add the appropriate javascript to make this happen param image the path to an image to use that will be sent to theme image for rendering param dest the destination of the link param alt the alt text of the link param class any class to apply to the link todo this should be a options array function ctoolsmodalimagebutton image dest alt class return ctoolsajaxtextbutton theme image image dest alt class ctoolsusemodal render text as a link this will automatically apply an ajax class to the link and add the appropriate javascript to make this happen note html true so be sure any text is vetted chances are these kinds of buttons will not use user input so this is a very minor concern param image the path to an image to use that will be sent to theme image for rendering param dest the destination of the link param alt the alt text of the link param class any class to apply to the link todo this should be a options array function ctoolsmodaltextbutton text dest alt class return ctoolsajaxtextbutton text dest alt class ctoolsusemodal like with all ctools ajax functionality the href of the link will be the destination with any appearance of nojs converted to ajax for submit buttons however the url may be found a different slightly more complex way if you do not wish to simply submit the form to the modal you can create a url using hidden form fields the id of the item is taken and url is appended to it to derive a class name then all form elements that contain that class name are founded and their values put together to form a url for example let s say you have an add button and it has a select form item that tells your system what widget it is adding if the id of the add button is editadd you would place a hidden input with the base of your url in the form and give it a class of editaddurl you would then add editaddurl as a class to the select widget allowing you to convert this value to the form without posting if no url is found the action of the form will be used and the entire form posted to it customizing the modal if you do not wish to use the default modal the modal can be customized by creating an array of data to define a customized modal to do this you add an array of info to the javascript settings to define the customizations for the modal and add an additional class to your modal link or button to tell it which modal to use first you need to create a settings array you can do this most easily with a bit of php drupaladdjs array mymodalstyle array modalsize array type fixed width 250 height 250 setting the key to the array above in this case mymodalstyle is the identifier to your modal theme you can have multiple modal themes on a page so be sure to use an id that will not collide with some other module s use using your module or theme as a prefix is a good idea then when adding the ctoolsusemodal class to your link or button also add the following class ctoolsmodalid in the example case that would be ctoolsmodalmymodalstyle modalsize can be fixed or scale if fixed it will be a raw pixel value if scale it will be a percentage of the screen you can set  modalsize  an array of data to control the sizing of the modal it can contain  type  either fixed or scale  if fixed the modal will always be a fixed size if scale the modal will scale to a percentage of the browser window default scale  width  if fixed the width in pixels if scale the percentage of the screen expressed as a number less than zero for 80 percent use 8 for example  default 8 height  if fixed the height in pixels if scale the percentage of the screen expressed as a number less than zero for 80 percent use 8 for example  default 8 addwidth  any additional width to add to the modal in pixels only useful if the type is scale default 0 addheight  any additional height to add to the modal in pixels only useful if the type is scale default 0 contentright  the number of pixels to remove from the content inside the modal to make room for scroll bar and decorations default 25 contentbottom  the number of pixels to remove from the content inside the modal to make room for scroll bar and decorations default 45 modaltheme  the drupal javascript themable function which controls how the modal will be rendered this function must be in the drupalthemeprototype namespace if you set this value you must include a corresponding function in a javascript file and use drupaladdjs to add that file default ctoolsmodaldialog drupalthemeprototypectoolsmodaldialog function var html html div id ctoolsmodal html div class ctoolsmodalcontent panelsmodalcontent html div class modalheader html a class close href html drupalctoolsmodalcurrentsettingsclosetext drupalctoolsmodalcurrentsettingscloseimage html a html span id modaltitle class modaltitle span html div html div id modalcontent class modalcontent html div html div html div return html  throbbertheme  the drupal javascript themable function which controls how the modal throbber will be rendered this function must be in the drupalthemeprototype namespace if you set this value you must include a corresponding function in a javascript file and use drupaladdjs to add that file default ctoolsmodalthrobber drupalthemeprototypectoolsmodalthrobber function var html html div id modalthrobber html div class modalthrobberwrapper html drupalctoolsmodalcurrentsettingsthrobber html div html div return html  modaloptions  the options object that s sent to drupalctoolsmodalmodalcontent can contain any css settings that will be applied to the modal backdrop in particular settings such as opacity and background  default array opacity 55 background fff  animation  controls how the modal is animated when it is first drawn either show   fadein or slidedown  default show animationspeed  the speed of the animation expressed either as a word jquery understands slow medium or fast or a number of milliseconds for the animation to run defaults fast closetext  the text to display for the close button be sure to wrap this in t for translatability default t close window  closeimage  the image to use for the close button of the modal default theme image ctoolsimagepath iconclosewindowpng t close window t close window  loadingtext  the text to display for the modal title during loading along with the throbber be sure to wrap this in t for translatability default t close window  throbber  the html to display for the throbber image you can use this instead of ctoolsmodalthrobber theme if you just want to change the image but not the throbber html default theme image ctoolsimagepath throbbergif t loading t loading  rendering within the modal to render your data inside the modal you need to provide a page callback in your module that responds more or less like a normal page in order to handle degradability it s nice to allow your page to work both inside and outside of the modal so that users whose javascript is turned off can still use your page there are two ways to accomplish this first you can embed nojs as a portion of the url and then watch to see if that turns into ajax when the link is clicked second if you do not wish to modify the urls you can check post js or post ctoolsjs to see if that flag was set the url method is the most flexible because it is easy to send the two links along completely different paths if necessary and it is also much easier to manually test your module s output by manually visiting the nojs url it s actually quite difficult to do this if you have to set post js to test in your hookmenu you can use the a ctools ajax convenience loader to help items ctoolsajaxsample ctoolsjs login array title login page callback ctoolsajaxsamplelogin page arguments array 1 access callback true type menucallback the first argument to the page callback will be the result of ctoolsjsload which will return true if ajax was the string and false if anything else ie nojs is the string which means you can then declare your function like this function ctoolsajaxsamplelogin js if js react with the modal else react without the modal if your modal does not include a form rendering the output you wish to give the user is just a matter of calling the modal renderer with your data function ctoolsajaxhelloworld js title t greetings output p t hello world p if js ctoolsmodalrender title output else drupalsettitle title return output if you need to do more than just render your modal you can use a ctools commands array see the function ctoolsmodalrender for more information on what you need to do here if you are displaying a form and the vast majority of modals display forms then you need to do just slightly more fortunately there is the ctoolsmodalformwrapper function ctoolsinclude modal ctoolsinclude ajax formstate array title t title of my form ajax js output ctoolsmodalformwrapper myform formstate there are some possible states after calling the form wrapper 1 we are not using js and there is form output to be rendered 2 we are using js and the form was successfully submitted and we need to dismiss the modal most other states are handled automatically unless you set flags in formstate to avoid handling them so we only deal with those two states if empty output js commands array commands ctoolsmodalcommanddismiss t login success in typical usage you will do something else here such as update a div with html or redirect the page based upon the results of the modal form ctoolsajaxrender commands otherwise just return the output return output you can also use ctools form wizard inside the modal you do not need to do much special beyond setting formstate modal true in the wizard form it already knows how to handle the rest  ',0),(40,'help',' temporary object caching the ctools object cache is a specialized cache for storing data that is nonvolatile this differs from the standard drupal cache mechanism which is volatile meaning that the data can be cleared at any time and it is expected that any cached data can easily be reconstructed in contrast data stored in this cache is not expected to be reconstructable it is primarily used for storing user input which is retrieved in stages allowing for more complex user interface interactions the object cache consists of 3 normal functions for cache maintenance and 2 additional functions to facilitate locking to use any of these functions you must first use ctoolsinclude ctoolsinclude objectcache get an object from the nonvolatile ctools cache this function caches in memory as well so that multiple calls to this will not result in multiple database reads param obj a 32 character or less string to define what kind of object is being stored primarily this is used to prevent collisions param name the name of the object being stored param skipcache skip the memory cache meaning this must be read from the db again return the data that was cached function ctoolsobjectcacheget obj name skipcache false store an object in the nonvolatile ctools cache param obj a 32 character or less string to define what kind of object is being stored primarily this is used to prevent collisions param name the name of the object being stored param cache the object to be cached this will be serialized prior to writing function ctoolsobjectcacheset obj name cache remove an object from the nonvolatile ctools cache param obj a 32 character or less string to define what kind of object is being stored primarily this is used to prevent collisions param name the name of the object being removed function ctoolsobjectcacheclear obj name to facilitate locking which is the ability to prohibit updates by other users while one user has an object cached this system provides two functions determine if another user has a given object cached this is very useful for locking objects so that only one user can modify them param obj a 32 character or less string to define what kind of object is being stored primarily this is used to prevent collisions param name the name of the object being removed return an object containing the uid and updated date if found null if not function ctoolsobjectcachetest obj name the object returned by ctoolsobjectcachetest can be directly used to determine whether a user should be allowed to cache their own version of an object to allow the concept of breaking a lock that is clearing another users changes remove an object from the nonvolatile ctools cache for all session ids this is useful for clearing a lock param obj a 32 character or less string to define what kind of object is being stored primarily this is used to prevent collisions param name the name of the object being removed function ctoolsobjectcacheclearall obj name typical best practice is to use wrapper functions such as these get the cached changes to a given task handler function delegatorpagegetpagecache name ctoolsinclude objectcache cache ctoolsobjectcacheget delegatorpage name if cache cache delegatorpageload name cache locked ctoolsobjectcachetest delegatorpage name return cache store changes to a task handler in the object cache function delegatorpagesetpagecache name page ctoolsinclude objectcache cache ctoolsobjectcacheset delegatorpage name page remove an item from the object cache function delegatorpageclearpagecache name ctoolsinclude objectcache ctoolsobjectcacheclear delegatorpage name  ',0),(41,'help',' ctools plugin examples this demonstration module is intended for developers to look at and play with ctools plugins are not terribly difficult to do but it can be hard to sort through the various arguments and required functions the idea here is that you should have a starting point for most anything you want to do just work through the example and then start experimenting with changing it there are two parts to this demo first there is a sample panel provided that uses all the various plugins it s at ctoolsexample 12345  you can edit the panel and configure all the panes on it second the code is there for you to experiment with and change as you see fit sometimes starting with simple code and working with it can take you places that it s hard to go when you re looking at more complex examples  ',0),(42,'help',' module setup and hooks your module must provide a few things so that your plugins can be found first you need to implement hookctoolsplugindirectory here we re telling ctools that our plugins will be found in the module s directory in the plugins plugintype directory context plugins will be in ctoolspluginexample plugins contexts contenttype plugins will be in ctoolspluginexample plugins contenttypes php function ctoolspluginexamplectoolsplugindirectory module plugin if module ctools empty plugin return plugins plugin second if you module wants to provide default panels pages you can implement hookctoolspluginapi ctools will then pick up your panels pages in the file named modulename pagesdefaultinc php function ctoolspluginexamplectoolspluginapi module api if module panelsmini api panelsdefault return array version 1 if module pagemanager api pagesdefault return array version 1  ',0),(43,'help',' argument plugins starting at the beginning contexts are fundamental to ctools and they almost always start with an argument to a panels page so we ll start there too we first need to process an argument we re going to work with a simplecontext context type and argument and then with a content type that displays it so we ll start by with the simplecontext argument plugin in plugins arguments simplecontextarginc note that the name of the file simplecontextarginc is built from the machine name of our plugin simplecontextarg and note also that the primary function that we use to provide our argument ctoolspluginexamplesimplecontextargctoolsarguments is also built from the machine name this magic is most of the naming magic that you have to know you can browse plugins arguments simplecontextarginc and see the little that it does  ',0),(44,'help',' context plugins creating a context from an argument now that we have a plugin for a simplecontext argument we can create a plugin for a simplecontext context normally a context would take an argument which is a key like a node id nid and retrieve a more complex object from a database or whatever in our example we ll artificially transform the argument into an arbitrary context data object plugins contexts simplecontextinc implements our context note that there are actually two ways to create a context the normal one which we ve been referring to is to create a context from an argument however it is also possible to configure a context in a panel using the panels interface this is quite inflexible but might be useful for configuring single page however it means that we have a settings form for exactly that purpose our context would have to know how to create itself from a settings form as well as from an argument simplecontext can do that a context plugin can also provide keywords that expose parts of its context using keywords like masterkeyword dataitem the node plugin for ctools has node nid and node title for example the simplecontext plugin here provides the simplest of keywords  ',0),(45,'help',' content type plugins displaying content using a context now we get to the heart of the matter building a content type plugin a content type plugin uses the contexts available to it to display something plugins contenttypes simplecontextcontenttypeinc does this work for us note that our content type also has an edit form which can be used to configure its behavior this settings form is accessed through the panels interface and it s up to you what the settings mean to the code and the generation of content in the display rendering  ',0),(46,'help',' access plugins determining access and visibility we can use access plugins to determine access to a page or visibility of the panes in a page basically we just determine access based on configuration settings and the various contexts that are available to us the arbitrary example in plugins access arglengthinc determines access based on the length of the simplecontext argument you can configure whether access should be granted if the simplecontext argument is greater or less than some number  ',0),(47,'help',' relationships letting one context take us to another often a single data type can lead us to other data types for example a node has a user the author and the user has data associated with it a relationship plugin allows this kind of data to be accessed an example relationship plugin is provided in plugins relationships relcontextfromsimplecontextinc it looks at a simplecontext which we got from an argument and builds an artificial relcontext from that  ',0),(48,'help',' readme  id readmetxt v 16 20090327 035637 quicksketch exp filefield provides an file field type to cck it provides many advantages over the drupal core upload module including perfield upload control file extensions file size pernode upload size limits multiple fields per content type customizable paths for saving uploads plus token support for dynamic paths icons for uploaded file types filefield was written by darrel opry dopry maintained by nathan haug quicksketch and andrew morton drewish dependencies content filefield also provides additional features when used with the following imagefield see an image preview during editing token generate dynamic paths when saving images imagecache create thumbnails of images on output if your site is any larger than a personal blog you should definitely install the following modules to increase the security and stability of your uploads transliteration convert unsafe characters to file system safe names mimedetect check the content of files to ensure they match the extension install 1 copy the filefield folder to the modules folder in your installation 2 enable the module using administer site building modules admin build modules 3 create a new file field in through cck s interface visit administer content management content types admin content types then click manage fields on the type you want to add an file upload field select file as the field type and file as the widget type to create a new field 4 upload files on the node form for the type that you set up  ',0),(49,'help',' readme  id readmetxt v 14 20100125 212910 teemule exp mobile plugin provides a mobile optimized view to a drupal site features automatic device detection domain based mobile site distinction a block for user to select mobile or full desktop site a distinct theme for the mobile site documented theme provided separate block administration for the mobile site filtering out system or module css and js if not specifically allowed suggesting word breaks to long words scaling images smaller or setting smaller view size to external images replacing embedded youtube videos with thumbnails to myoutube separate configurable mobile groups based on device properties testing for selected roles or from the administration hooks and api to extend or support in other modules authors teemu lehtinen mikko hyytiainen nitro fx oy finland andrea trasatti included code from project http simplehtmldomsourceforgenet installation you will need a mobile optimized drupal theme to properly use this module install and enable a simple mobile theme mobilegarland http drupalorg project mobilegarland 1 download the latest stable mobile plugin release for your drupal branch 2 extract the contents to your sites all modules folder 3 enable the module and optimizations in administer site building modules 4 enable the module for your test roles in administer user management access control after testing enable the module for all roles in administer user management access control to enable users to override automatic device detection add a full mobile switch block to a desired region on your site in administer site building blocks see the guide at drupalorg for more information http drupalorg node 458912  ',0),(50,'help',' readme  id readmetxt v 14 20100125 212910 teemule exp mobile plugin provides a mobile optimized view to a drupal site features automatic device detection domain based mobile site distinction a block for user to select mobile or full desktop site a distinct theme for the mobile site documented theme provided separate block administration for the mobile site filtering out system or module css and js if not specifically allowed suggesting word breaks to long words scaling images smaller or setting smaller view size to external images replacing embedded youtube videos with thumbnails to myoutube separate configurable mobile groups based on device properties testing for selected roles or from the administration hooks and api to extend or support in other modules authors teemu lehtinen mikko hyytiainen nitro fx oy finland andrea trasatti included code from project http simplehtmldomsourceforgenet installation you will need a mobile optimized drupal theme to properly use this module install and enable a simple mobile theme mobilegarland http drupalorg project mobilegarland 1 download the latest stable mobile plugin release for your drupal branch 2 extract the contents to your sites all modules folder 3 enable the module and optimizations in administer site building modules 4 enable the module for your test roles in administer user management access control after testing enable the module for all roles in administer user management access control to enable users to override automatic device detection add a full mobile switch block to a desired region on your site in administer site building blocks see the guide at drupalorg for more information http drupalorg node 458912  ',0),(51,'help',' readme problem drupal s block module is limited by the fact that a block can only have one instance each block has a 11 relationship with its region weight visibility and other settings this means that it is impossible to have blocks in multiple regions or to have blocks that have different settings on different pages solution multiblock module will keep track of multiple instances of blocks and dispatch to their appropriate block hooks using this stratgey you would not enable any blocks that are implemented by other modules instead you will go to admin build block instances and create an instance of a block multiblock module will then implement this block in its own block hook which will forward any hookblock calls to the original module s hook using this method we can maintain multiple instances of blocks with different settings but the same implementation this should not affect blocklevel caching one catch here is that the configure and save op s for hookblock are usually implemented to save only one set of data this means that for blocks that are unaware of multiblock you will only be able to save custom data this doesnt include visibility weight region etc for one set of data how to use it 1 go to admin build block instances 2 select the type of block you want to create an instance of and type a unique title for that instance 3 click add instance 4 go to admin build block 5 enable the block instance you have just created developing multiblockenabled blocks multiblock should successfully clone any regular block created with hookblock however if you clone a regular block that implements a save or configure op of hookblock the custom block settings of one block instance will overwrite the settings of another to get around this you can make a block multiblock enabled to do this you have to first add an op to your hookblock called mbenabled it should always return the string mbenabled once you do this the instances you create will get the block instance id passed in the edit variable for the view configure and save ops this will let you save and load different data to different instances based on this instance id it is passed in with the multiblockdelta key with the following format edit multiblockdelta array type value value blockid  ',0),(52,'help',' working with the panels api panels is a pluggable rendering engine apart from its datastructure almost nothing in panels is hardcoded every level of its rendering process is controlled by plugins of the ctools variety and therefore can be overriden some of these plugins behaviors are obvious from the ui whereas others are much more underthehood most site builders and module authors will find that plugins are the only way they need to interact with panels to do what they want however if you are building whole new uis applications that are to be driven by the panels engine you ll also need the more traditional api that manages panels editing and crud panels node and mini panels are examples of applications in this sense as is og panels  this page is divided into two sections the first dealing with panels rendering system the plugins the drive it and the second with the requirements for creating a panelsdriven application ui the former is a good starting place and should be of interest to anyone wanting to begin working with the panels api the panels rendering system panels rendering system takes a fullyloaded panelsdisplay object and turns it into html it doesn t care how that object was built or where it comes from it s just a rendering engine so long as the calling code provides a wellformed panelsdisplay object the engine will spit out html exactly how that process works is determined entirely by plugins panels utilizes eight different types of plugins within its rendering system four owned by panels and four by ctools let s run through that list layout plugins owned by panels layout plugins provide the html output skeleton for any panel they define a set of regions and optionally accompanying css js very analogous to how themes define block regions while layout plugins with complex logic are possible the flexible layout for example most layouts are nothing more than a region list a tplphp skeleton and some css style plugins owned by panels style plugins control the markup that wraps both individual panes and whole panel regions a basic style plugin need not provide more than some basic css and a theme function or tplphp file style bases owned by ctools panels implements the stylebases plugin type in order to interact with the stylizer system which technically lives in ctools though true ownership is a little blurred regardless panels uses this plugin to interact with stylaizer in order to allow the creation of style plugins in the ui this plugin is probably of interest only to module developers site builders can safely skip it context plugins owned by ctools context plugins are abstracted wrappers around bits of data a node user or taxonomy term are easy examples panels uses context plugins so that it can work with all these different bits of data without caring about the details of the datastructure itself context can be a confusing concept and you can learn more in the ctools help  note that argument and relationship plugins are technically also used by panels but because they re really means for creating more context they don t get separate entries in this list content type plugins owned by ctools can utilize context at the heart of the panels rendering process content type plugins define the rendering logic for every pane offering panels a renderable chunk from your module means defining one of these for those accustomed to the block system they can be thought of as a more verbose block definition contained neatly inside a single plugin content type plugins rely on context to provide them with source data when necessary this makes content plugins nice and portable access plugins owned by ctools can utilize context access plugins are essentially portable access checking logic responsible for answering yes or no given some contextual data panels uses these to define visibility rules on individual panes the other place these are commonly seen is in defining selection rules on page manager variants if your module introduces new permissioning concepts or access logic not a basic hookperm implementation you may want to consider also encapsulating that logic in one or more of these plugins for example organic groups might implement an access plugin to allow deny based on group membership or the date module might implement allow deny logic based on request time cache plugins owned by panels should utilize context panels cache plugins define caching strategies that can be applied to individual panes or to whole displays caching plugins must deal with two basic issues the cache backend to use for reading writing and ttlmanaging strategies ttl strategies can and should integrate heavily with the context as that is where the real differential benefit of panelsbased caching is vs standard core caching display renderers owned by panels utilizes everything else in the simplest terms display renderers take a fullyloaded panelsdisplay object and render it they are very complex powerful plugins one could use them to cause panels to bypass every single other plugin in this list fortunately there is virtually no circumstance under which one would need to implement these plugins in the process of building a single site only contrib developers working on highly complex use cases are likely to ever need them in short each display renderer plugin is a selfcontained panels rendering engine if you want to grok the panels rendering system study these panelsbased applications at its core panels is a rendering engine with no ui though it does provide common elements for reuse in admin uis so if you re working with panels via the web ui it means you re working with a panels application the three that ship with this version of panels are mini panels panel nodes and the integration with ctools page manager panels also implements a taskhandler plugin which is owned by page manager in ctools task handlers aren t strictly a part of panels rendering system itself though strictly speaking they wrap it so we won t cover them here  ',0),(53,'help',' layout plugins getting started  layout plugins are one of the simplest and most powerful sections of the panels api there are two different ways that a layout can be implemented via panels panels supports both module and theme implementations of panels the module implementation requires that hookctoolsplugindirectory define the directory in which your layout plugins exist this same hook defines the directory for all panels plugins alternately if you intend on implementing a layout in a theme this can be done primary through the theme s info file the ctools help does a great job of actually explaining this portion of the api ctools plugins  ctools explains even the layout hooks a little in its example but we ll recap quickly and expand on this information as ctools explains the actual plugin file must be named with care as it will directly affect your naming scheme for the hook within it this is really no different from any other hook within drupal except that we ll be using multiple replacements in this case the function we re looking to implement is an instance of function yourmodulepluginnameownermoduleplugintype in our case we already know that the function will be function yourmodulepluginnamepanelslayouts this is because the plugin type we re working with is a layout and the module that implements these layouts is the panels module for the rest of the naming scheme yourmodule will be replaced with either the name of your module that implements this layout or the name of the theme and pluginname will be replaced with whatever the name of the plugin file is for purposes of this example our module name us going to be layoutsample and our plugin will be firstlayout  directory structure  we re going to assume that you ve laid your directory structure out very similarly to how panels does it something like this is rather likely layoutsample layoutsampleinfo layoutsamplemodule plugins layouts firstlayout firstlayoutcss firstlayoutinc firstlayoutpng layoutsamplefirstlayouttplphp the name of our inc file is going to be the key to the entire layout plugin the inc file  we will start with the firstlayoutinc file as it s the most important file we re dealing with here firstlayoutinc will look similar to the following plugin array title t first layout icon firstlayoutpng theme layoutsamplefirstlayout css firstlayoutcss panels array main t main region right t right region the include file defines all the other files that our layout will utilize in order to be truly useful the array is fairly self explanitory but for the sake of specificity  title  the title of our layout utilized within the panels administration screens  icon  the graphical representation of our layout utilized within the panels administration screens  theme  the template file of our layout sharp eyed readers will note that the theme definition utilizes underscores instead of dashes and does not have tplphp after it this is refering to the layoutsamplefirstlayouttplphp file all the same it is simply how the naming convention works utilize dashes in the tpl file name and underscores when refering to it in your include file  css  the css file to be utilized for our layout utilized within the panels administration screens and when viewing the actual panel itself  panels  defines all the various regions within your panel this will be further utilized within our tplphp file there are many additional properties that can be added to the include file for purposes of this document we ll also make mention of the admin css property admin css is especially useful when utilizing a fixed width layout with fixed with panel regions this can break under most administrative circumstances and panels provides you with the ability to give an additional css layout for the administrative section it s a simple nicety and looks like this plugin array title t first layout icon firstlayoutpng theme layoutsamplefirstlayout css firstlayoutcss admin css firstlayoutadmincss panels array main t main region right t right region  the tplphp file  the tplphp file is very similar to any other template file within drupal the difference here is that we re being passed an array of regions through content and we also have a css id available to us for the entire panel in the form of cssid the template is very straight forward and will look similar to the following div class paneldisplay panelstackedtwothirdsonethird clearblock php if empty cssid print id cssid div class panelpanel panelcolfirst panelregionmain div class inside php print content main div div div class panelpanel panelcollast panelregionright div class inside php print content right div div div this is simply an example of what the html could look like you can alter an update this html to fit your own needs the other files  the css and png files are as simple as any other css or png file you ve ever utilized panels provides some images for its graphical representations of its layouts i would heavily encourage you to modify these to suit your needs the css files admin and non will be included at the appropriate times simply set them up to fit your purposes if you re utilizing fixed width panel regions it s probably smart to provide an admin css file as well with your panel layout  ',0),(54,'help',' style plugins ',0),(55,'help',' readme  id readmetxt v 112721 20090513 203034 dereine exp description configurable tabs panel style provides 3 kinds of tabs normal tabs horizontal filling disabled horizontally filling equal width tabs sets the width property forcing each tab to be equally wide if the text doesn t fit in the tab the overflow will be hidden horizontally filling smart width tabs calculates the length of the text in each tab and compares this to the total length of the text on all tabs it then sets the width property of each tab according to the percentage of text the tab contains pager links inside panels eg views with pagers will automatically be updated to ensure that the same tab is opened when the page is loaded dependencies panels 23 drupal 6 or 2 drupal 5 http drupalorg project panels a 5x2xdev tarball of july 6 or later or alternatively beta 5 with this patch applied http drupalorg node 278861 tabs drupal6 http drupalorg project tabs drupal 5 part of javascript tools http drupalorg project jstools installation 1 place this module directory in your modules folder this will usually be sites all modules 2 enable the module 3 go to the layout settings tab of the panels page mini panel on which you want to apply this style troubleshooting this module does not have any css of itself css is provided by the tabs module the tabs module itself only overrides the tabs style defined by the theme this means that you need a theme that already supports tabs or you won t see any tabs at all eg garland has tabs see http drupalorg node 258177 sponsors initial development paul ektov of http autobinru author wim leers mail work wimleerscom website http wimleerscom work the author can be contacted for paid customizations of this module as well as drupal consulting development and installation  ',0),(56,'help',' readme  persistent login module for drupal 6 id readmetxt v 1341 20090501 085809 markuspetrux exp current mantainer markuspetrux http drupalorg user 39593 original author bjaspan http drupalorg user 46413 contents of this file overview installation upgrading description overview the persistent login module provides the familiar remember me option in the user login form installation 1 install and activate persistent login like every other drupal module 2 for maximum security edit your settingsphp file so php session cookies have a lifetime of the browser session iniset sessioncookielifetime 0 3 visit admin settings persistentlogin to set how long persistent sessions should last and which pages users cannot access without a passwordbased login upgrading because persistent login interacts with the user login process some caution is required when upgrading it to a new version 1 log in as administrator 2 visit administer settings and open the site maintenance box select offline and press save configuration this is so users do not receive any error messages before the upgrade is complete 3 install the new persistent login module files 4 visit http yoursite updatephp to update the persistent login database schema if necessary you should do this every time you upgrade any module 5 return to administer settings site maintenance and put your site back online note if updatephp shows a version update for persistent login all currently remembered login sessions for all users may be lost everyone will have to log in again with their username and password description the persistent login module provides the familiar remember me option in the user login form the module s settings allow the administrator to control how long user logins are remembered control how many different persistent logins are remembered per user control which pages a remembered user can or cannot access without explicitly logging in with a username and password eg you cannot edit your account or change your password with just a persistent login each user s my account view tab gives them option of explicitly clearing all of his her remembered logins persistent login is independent of the php session settings and is more secure and userfriendly than simply setting a long php session lifetime for a detailed discussion of the design and security of persistent login see improved persistent login cookie best practice  ',0),(57,'help',' readme drupal tabsmodule readmetxt provides methods for clientside tabbed pages using the jquery ui tabs plugin see http docsjquerycom ui tabs developer usage tabs are generated through formsapistyle arrays using two element types defined in tabsmodule tabset a set of tabs and tabpage a tab page on a set of tabs tabs can be returned as part of normal forms or can be manually rendered through a call to the function tabsrender for documentation and examples see the docs directory in the dev version of the module  ',0),(58,'help',' readme  id readmetxt v 1641 20090621 035446 sun exp summary wysiwyg api allows to users of your site to use wysiwyg richtext and other clientside editors for editing contents this module depends on thirdparty editor libraries most often based on javascript for a full description visit the project page http drupalorg project wysiwyg bug reports feature suggestions and latest developments http drupalorg project issues wysiwyg requirements none installation install as usual see http drupalorg node 70151 for further information go to administer site configuration wysiwyg and follow the displayed installation instructions to download and install one of the supported editors configuration go to administer site configuration input formats and either configure the full html format assign it to trusted roles and disable html filter line break converter and optionally url filter or add a new input format assign it to trusted roles and ensure that above mentioned input filters are disabled setup editor profiles in administer site configuration wysiwyg contact current maintainers daniel f kudwien sun http drupalorg user 54136 henrik danielsson twod http drupalorg user 244227 this project has been sponsored by unleashed mind specialized in consulting and planning of drupal powered sites unleashed mind offers installation development theming customization and hosting to get you started visit http wwwunleashedmindcom for more information  ',0),(59,'help',' readme content template contemplate module for drupal by jeff robbins lullabot wwwlullabotcom what is the difference between contemplate and theming in drupal the presentational layer the theme is a walledoff and separate entity since it is possible for users to choose their own themes or to switch themes programmatically drupal does not make any assumptions about presentation in the way that it thinks about content this can become a problem when modules like cck are adding fields that you may want to show up in specific ways drupal s rss feeds and search indexing does not run through the theme layer this is as it should be because neither of these use presentational information however there are certainly times when you want to rearrange this content remove parts of it or display things in special ways you can affect most of the site display using your theme s node templates but if you would like to affect the content across multiple themes multiple sites or simply affect the rss feed and search indexing you ll want to use contemplate contemplate alters the way that drupal thinks of the content it alters the node teaser and or body fields before the theme is invoked so it will affect rss feed and search index in addition to the content variable that gets sent to your theme s node templates what does contemplate do this module allows modification of drupal s teaser body and rss feed using administrator defined templates these templates use php code in a manner very similar to the phptemplate theme engine and all of the node object variables are available for use in each template an example node object is displayed and it is as simple as clicking on its properties to add them to the current template this module was written to solve a need with the content construction kit cck where it had a tendency toward outputting content in a notverypretty way and as such it dovetails nicely with cck adding a template tab to cck contenttype editing pages and prepopulating the templates with cck s default layout this makes it easy to rearrange fields output different fields for teaser and body remove the field title headers output fields wrapped for use with tabsmodule part of jstools or anything you need diskbased templates it is also possible to create diskbased template files to do this copy the contents of a contemplate textarea and paste it into a file called node nodetype field tplphp where nodetype is the content type and field is either body teaser or rss it is also possible to create a template called node nodetype tplphp which will affect all cases and nodetplphp which will affect all node types place these files into a directory called contemplates inside of either your sites all directory or sites yoursite depending on your setup it is also possible to have multiple contemplate directories with sites all contemplates being the fallback for templates the contemplate does not find in the more specific site directory when adding or removing template files you will need to visit the content templates admin page to refresh the template list cache you do not need to do this again when making changes to the content of the templates ',0),(60,'help',' what is views  the views module allows administrators and site designers to create manage and display lists of content each list managed by the views module is known as a view and the output of a view is known as a display displays are provided in either block or page form and a single view may have multiple displays optional navigation aids including a system path and menu item can be set for each pagebased display of a view by default views may be created that list content a node view type content revisions a node revisions view type or users a user view type a view may be restricted to members of specific user roles and may be added edited or deleted at the views administration page the building block design of the views system provides power and flexibility allowing parameters to be specified only when needed while an advanced view may use all of available parameters to create complex and highly interactive applications a simple content listing may specify only a few options all views rely on a conceptual framework that includes  fields  or the individual pieces of data being displayed adding the fields node title   node type  and node post date to a node view for example includes the title content type and creation date in the displayed results relationships  or information about how data elements relate to one another if relationship data is available like that provided by a cck nodereference field items from a related node may be included in the view arguments  or additional parameters that dynamically refine the view results passed as part of the path adding an argument of node type to a node view with a path of content for example dynamically filters the displayed items by content type in this example shown with clean urls enabled accessing the view through the path  http wwwexamplecom content page  displays all posts of the type page the path  http wwwexamplecom content story  displays all posts of the type story and  http wwwexamplecom content  displays all posts regardless of type  sort criteria  which determine the order of items displayed in the view results adding the sort criteria node post date  in descending order to a node view  for example sorts the displayed posts in descending order by creation date filters  which limit items displayed in the results adding the filter node published  and setting it equal to published to a node view for example prevents unpublished items from being displayed displays  which control where the output will be seen every view has a default display which doesn t actually display the view anywhere but is used to hold the default settings for the view and is used when the view is called programmatically if another display is not specified much more useful to users are the page display which gives a view a path and allows it to be the primary content of a page or the block display which allows it to appear as secondary content on other pages  ',0),(61,'help',' getting started module developers the views api help pages can be found here  new users for those new to views it can be a complex system that appears totally overwhelming the good news is that the ui is designed to compartmentalize everything this means that for the most part you can ignore the parts you re not interested in start small and build your way up because of this the edit ui can seem overwhelming at first but there are really just a few things you have to know the rest you can find through exploration the views edit ui image below gives an overview of what you ll find on the edit ui the views edit ui notes 1 every view has a number of displays which represent where output will be placed if you re familiar with the original views 1 you could set a view to be a page with a url path or a block that could show up in a sidebar with views 2 you can add as many displays as you like in addition you have the default display which contains the basic settings but doesn t actually show up anywhere 2 when you click on the link for an item a form will open up for browsers with smaller resolutions you may have to scroll down a little to see this form if a form is open the item its attached to will be highlighted 3  overrides mean that a particular display is not using default settings when you create a new display many of its settings will start off using default values this will be indicated by italics and a lighter color if you change these values without first overriding them you will change the default value for all displays that use them 4 some items particularly styles have additional settings ordinarily when you update a style if it has additional settings you will automatically see that form next often you will need to go directly to those settings 5 you can safely leave a view page to go and do other things if you come back the view will still be there stored in a cache keep in mind however that while you do this that view is locked  meaning another user cannot edit this view without breaking the lock breaking the lock will discard your changes it helps to have something particular in mind that you want to accomplish when using views here are a couple of ideas and a brief sketch of how to accomplish what you want  ',0),(62,'help',' create a page to list users by role in this example you will create a page view listing users on your site through this stepbystep process you will become familiar with some basic steps in creating a view and familiarize yourself with the views user interface creating a new view go to add new view  give your new view the name userlist description a simple user listing tag users type user and click next  about the interface you have been brought to the views user interface as you start you are editing the default options for the view in the 1st column on the left you can see the dropdown menu offers block for example to select settings specific only to block views in the remaining columns you will be able to add or change options by clicking on links or icons these options will then appear below this main area most likely you will need to scroll to see the options appear as you make changes these options will appear in bold until you save your view creating a page display choosing a url and creating a menu link in the 1st column ensure that page is selected in the dropdown menu and click add display  next we ll define the path for this page a page must have a path and we define it early so that views doesn t warn us display page uses path but path is undefined locate the page settings in the 2nd column and click the none link next to the path setting in the options editing area that appears below set the path to userlist or something else if you prefer and click update  next to menu setting click the no menu link in the options which appear below select normal menu entry  and set the title to user list and click update  scroll up to basic settings  in that same 2nd column and click the no link next to use pager  below in the options select full pager and click update default display  selecting the fields to display in 3rd column locate the fields options click the   icon to add fields scroll down to defaults add fields  in the groups dropdown menu select user then check the following fields  user created date   user delete link   user edit link   user last access   user name and user picture  then click add  you will be taken through the fields you added one at a time click update default display to go to each next field leave the default options on all fields except delete link  change that field s label to operations scroll back up to fields and click the   icon to rearrange fields down below drag the name field by dragging its foursided arrow to the top drag the delete link operations  field to the bottom and the edit link field just above it then click update  seeing what we ve done so far at this point you have done enough to create a valid view if you scroll down you will see a preview of your view if it doesn t show already click the preview button but generally this display updates automatically whenever you finish working in one of the mini forms styling the view as a table combining related fields into columns under basic settings  in the 1st column click the unformatted link next to the style setting in the options below under page how should this view be styled  choose table and click update default display  you will be taken to a page style options form to edit the table settings locate our edit link field in this mini form and notice the column dropdown change this dropdown to show operations  in the separator column next to the operations field type note the spaces around the   symbol check all of the sortable checkboxes and set default sort to name  when finished click update default display  filtering the user list to exclude unwanted entries click the   icon next to filters  in the groups dropdown menu select user then check the user name filter and click add  select is not one of and enter anonymous in the usernames box click update default display  adding an argument to list users by role dynamically scroll up to arguments  and click its   icon check the user roles argument and click add  set the title to 1 don t type the quotes and under action to take if argument is not present select summary sorted ascending  leave the other settings as they are click update default display  and click update through the prompts that follow to accept their default values saving the view finally click the save button to save your work at the very top click view page  to go to your new view  ',0),(63,'help',' create a block of recent stories in this example you will create a list of nodes of the content type story to be shown in a block through this stepbystep process you will become familiar with some basic steps in creating a view and familiarize yourself with the views user interface creating a new view go to add new view  give your new view the name recentstories description recent stories tag story type node and click next  about the interface you have been brought to views user interface as you start you are editing the default options for the view in the 1st column on the left you can see the dropdown menu offers block for example to select settings specific only to block views in the remaining columns you will be able to add or change options by clicking on links or icons these options will then appear below this main area most likely you will need to scroll a bit to see the options appear selecting the fields to display in 3rd column locate the fields options click the   icon to add fields scroll down to defaults add fields  in the groups dropdown menu select node then check the following two fields  node post date   node title  then click add  you will be taken through the fields you added one at a time make the changes specified below for the post date field delete the post date label change the date format to custom  and the custom date format to f j y g i a do not type the single quotes for the meaning of these letter codes click on the php docs link under that box to arrive at the explanation click update  for the title field delete the title label select link this field to its node click update  scroll back up to fields and click the   icon to rearrange fields drag the foursided arrow next to node title so that it appears above node post date  click update to save the new field order filtering to story nodes only click the   icon next to filters  in the groups dropdown menu select node then check the node published and node type filters and click add  select the published checkbox click update select is one of and check story in the node type field click update  sorting to show most recent first scroll up to sort criteria and click the   icon in the groups dropdown menu below select node then check node post date  and click add  alternatively you may instead check node last comment time  or node updated commented date  or node updated date  select descending sort order  click update  refining the basic settings in 1st column under basic settings locate these options  items to display setting click 10  change the 10 to 4 click update style setting click unformatted  change to list  click update  adding a block display for custom options in the dropdown on the left ensure that block is selected and click add display  under block settings  click the none link next to the admin setting change block block admin description to recent stories  saving the view click save to save your work instructing drupal to show the block finally you should tell drupal to show this block configure your block by going to admin build block  locate the block in the list it is labeled recent stories  place this block in a region and click save  you may click configure to set a different title to determine which roles can view the block and on which pages it appears if you want your block on the front page only enter front  ',0),(64,'help',' create an rss feed of user posts in this example you will create a feed display to show nodes by individual users dynamically selected through the url you will become familiar with the views 2 interface as well as learn how to use an argument to pull in a user name and use it in a dynamically created path a feed is a data format that places your site s content into a file that can be read and displayed by news reader programs when visiting a site you may notice a small rss transmission icon  whereby clicking on it you can subscribe to the site s most recent content this makes it easier for your visitors to keep up to date with your website you can also use this format to aggregate information into other sites for more information please watch a video from common craft about rss in plain english  note drupal automatically creates a feed for your website but you may want to create feeds with specific information in this case a list per user creating a new view go to add new view  give it the name userfeed description a feed of user nodes tag users type node and click next about the interface you have been brought to the views user interface as you start you are editing the default options for the view in the 1st column on the left you can see the pulldown menu offers feed for example to select settings specific only to rss views in the remaining columns you will be able to add or change options by clicking on links or icons these options appear below this main area most likely you will need to scroll to see the options appear as you make changes these options will appear in bold until you save your view change default display under basic settings in the 2nd column click row style fields a menu loads below  defaults how should each row in this view be styled  check the node option and click update  this loads another options menu  defaults row style options click update  create the rss view in the 1st column select feed in the dropdown menu and click add display  under basic settings in the 2nd column click row style missing style plugin note options appear below the views interface you may need to scroll to see feed how should each row in this view be styled tick node  then update this loads the next options menu display type  select use default rss settings click update  set the path for accessing your feed in the 2nd column under feed settings  click path none in options below feed the menu path or url of this view enter in the path with an argument feeds rssxml click update set up your arguments to say which user s nodes to display to the right of arguments  click the sign to add and argument in the feed add arguments menu that loads below select user in the pulldown menu check the box user name  click add scroll down to options to find case in path  select lower case check the box transform spaces to dashes in url click update default display sort to show most recent at top of feed scroll up to sort criteria in the right most column and click the icon in the groups dropdown menu below select node then check node post date  and click add  select descending sort order  click update  set filters to hide unpublished entries click the icon next to filters  in the options below select node under groups dropdown menu choose the node published filter and click add  check the box published  click update default display test click save under live preview type in the name of a user in lowercase replacing spaces with dashes click preview  you should test and find your feeds at urls like http yoursitecom feeds username rssxml you can use this path for aggregating on another site you can also attach the rss feed to another display of view to make the feed link appear on that display  ',0),(65,'help',' create a block of author s recent blog posts in this example you will create a contextsensitive block that shows the titles of recent blog entries by an author when viewing one of their posts this will demonstrate using views arguments to dynamically filter a view s contents at display time before working through this example enable the blog module and populate some entries from a few different users creating the view the first step is creating a view for our recent blog entries block because the block will show the titles of blog entries this view is considered a node type go to add new view  enter the following properties and click next  view name recentblogentries view description list of recent blog entries for a given author view tag blog view type node generating a list of blog entries it will be much easier to see the view progress if we can see it doing something in this section we will create a basic view displaying blog entry titles in the third column locate the fields area generally speaking fields are the pieces of information that you want to display in the view in this case node title click the   icon to add a field scroll down to defaults add fields  below the settings table a large selection of fields will be available in the groups dropdown menu select node  this will limit the list to only the default fields exposed by node module scroll down the list select the node title field and click add  you will now be presented with settings for the node title field delete the label from the label field so that each individual node title is not prefixed with the word title additionally check the link this field to its node box so that visitors who see an interesting title can click directly on it to read the blog entry to which it belongs when finished click update  if you scroll down to the live preview section you should now see a list of several node titles however both blog entries and other node types will be in the list let s fix that in the fourth column locate the filters area filters limit the results displayed in the view and we can use this to our advantage here by showing node titles only from blog entries and not every type of node click the   icon to add a filter as before scroll down to the defaults add filters section select node from the groups select box to limit the list of options to only those exposed by node module scroll down and select the node type field and click add  in the settings page that appears leave operator as is one of and select blog entry under node type  click update when finished now by scrolling down to live preview  you ll see that the list only shows blog entries adding context with arguments while filters are very useful for limiting the results of a view when the condition is always consistent for example a view of blog entry nodes should always be filtered by the blog entry type something filters can t do is smart decisionmaking based on the page context in our case we want the view to display a different list of blog entries when looking at a post by user admin than we do when looking at a post by user member and filters won t be able to help luckily there s another way to filter a view s content  arguments  through arguments views are able to obtain additional context typically via dynamic urls with ids in them and can take this context into consideration when displaying the view let s walk through adding and configuring an argument to our view so that we can change its contents based on post author in the third column locate the arguments area click the   icon to add an argument because we are basing the view around content authors  this time under groups select user  check user uid and click add  the defaults configure argument user uid settings page has a lot going on but only a few things that need our attention the title field here unlike the title field under basic settings  can be based upon the context that the view is being displayed in change the title to recent entries by 1 1 will later be expanded to the user s name based on the user uid argument when the view is displayed under action to take if argument is not present  there are a variety of options ranging from displaying a 404 or a 403 page to simply displaying all values in the view in our case if an argument isn t specified which it won t be since this view will be displayed in a sidebar block not as a page with its own url we want to give it a default one to act on select provide default argument  assuming javascript is enabled in your browser you should now get another selection for default argument type  select user id from url  which will then provide a new option  also look for a node and use the node author  select it this will cause views to first see if it can figure out a user id from the current url for example user 1 if it can t it will instead check to see if the current page is a node page such as node 42 and if so take the user id from the node s author field instead validator options provide a useful way to control what kind of arguments your view will accept select user as the validator  by default changing this setting will check the incoming argument and ensure it s a valid user id if not the view will be hidden from the page once you have changed the argument s title default argument and validator options click update to save your changes you ll notice that now the live preview no longer shows anything did we just break the view fortunately no it s merely abiding by our wishes to hide itself if there is no valid user id given to it try entering a 1 in the arguments box and clicking preview  you should now see a list of only user 1 s blog entries creating the block so the live preview is now showing basically what we want there s just one problem we have no way to stick what we ve done so far into a sidebar block let s fix that by adding a new display  in the first column under defaults  there is a select box containing entries such as page   feed  and yes  block  select block and click add display  there s not much else to do here as far as views is concerned under block settings  click the none link next to admin and fill in a description for the block in the administrative interface such as recent blog entries by author and click update  save your work by clicking the save button at the bottom of the views interface you should receive a message that the view has been saved next navigate to the blocks interface and drag the recent blog entries by author block to the right sidebar region or similar and click save blocks  you ll notice this appeared to do nothing no block shows in the sidebar but remember we are looking at an adminitrative page we are not looking at a page that would provide a user id context navigate to the main blog listing and click on an entry there you should now see a sidebar block titled something like recent entries by admin with a list of blog entries beneath it finishing touches there are still a few remaining things to do before our view is complete for example we said that the block was to show recent blog entries but instead it s showing them in the order they were entered with oldest on top additionally even unpublished entries are showing in the list currently return to the recentblogentries view edit page  add an additional filter by clicking the   icon in the filters section in the fourth column change groups to node and select node published  click add  under the published selection choose yes and click update  to handle sorting locate the sort criteria area just above filters and click the   icon there under groups  again select node  from the list of options check node post date and click add  in the settings page change sort order to descending  this will place the newer posts on top of the older ones click update when finished finally  save the view for your new settings to take effect  ',0),(66,'help',' view types the view type describes how this view is stored views is capable of having views entirely in code that are not in the database this allows modules to easily ship with views built in and it allows you to create a module to store your views for easy deployment between development and production servers normal normal views are stored in your database and are completely local to your system default default views are stored only in code and are not anywhere in your database they may be enabled or disabled but you may not completely remove them from your system you can override the view which will create a local copy of your view if you do this future updates to the version in code will not affect your view overridden overridden views are stored both in code and in the database while overridden the version that is in code is completely dormant if you revert the view the version in the database will be deleted and the version that is in code will once again be used you may store your views in code with the following procedure create a module to store the views add the function modulenameviewsdefaultviews  to this module export the view you wish to store in your module in code cut and paste that into the abovenamed function make sure the last line of the view is   views view name view  make sure the last line of the function is return views  after you make any changes be sure to clear the views cache  you may do this from the tools menu  ',0),(67,'help',' displays displays tell views where the output should go by adding a display to a view you can have your view appear as a page or as a block or even as an attachment to a different display on the view each display can have its own settings but when it s created a display will take all of its basic settings from the default display which all views must have for most settings there is an override button that will override that single setting for the current display overridden settings will have a mark in the summary for that display all default display settings are shown in the other displays  italic  when you override a setting than it is shown normal please keep in mind that when you are editing a setting on a display that is not overridden then by default you are editing that for all displays for fields   arguments   sorts   filters and relationships  you can only override all of them or none of them to do this click on the header for the filters or the rearrange button once you override the display will then have its own copies of the fields filters etc and changes to the defaults will not be reflected on your display ',0),(68,'help',' default display the default display is primarily a display to store settings and isn t actually used anywhere within the views system it is possible for external programs to use the default display but if they do they will hopefully tell you which display they will be working with the default display is also a convenient display to use to embed into your site using php snippets this is useful for example in node content but this is something that should generally only be done by administrators in general you probably want to add either a page display or a block display   ',0),(69,'help',' page display page displays have a path and an optional menu component page displays will be the primary content for the page meaning they will be displayed in the main content area when you visit the url that corresponds to the path page displays take their arguments from the url you can embed arguments into the url using in previous versions of views this was arg for example node foo will accept urls such as node 1 foo please remember that using a placeholder makes the argument required if you wish to have an optional argument simply omit the from the path ie using page as the path requires an argument and visiting http wwwexamplecom page will not trigger the view ',0),(70,'help',' block display block displays will show up on your blocks administration page once a block display is created and saved it can be enabled and positioned in your theme by visiting administer site building blocks and selecting it from the list blocks do not accept arguments from any source the only way to get arguments to a block is to provide defaults to it possibly via the php code default setting edit the argument in question you may want to override this argument if you have multiple displays using it change the action to take if argument is not present to provide default argument this will bring up a new box called provide default argument options the most common default argument type used for blocks is node from url where it attempts to determine if the url refers to a node for example if visiting node 1 or node 1 edit user id from url is also very common if you change the default argument type to php code note you must have permission to use php code on your site you can enter php to define the argument needed simply return the argument  ',0),(71,'help',' attachment display attachment displays are attached to another display in the same view when the display is visited the attached display will also be rendered and may be placed before after or both before and after the original display attachment displays are often useful for displaying an argument summary view along with a page display that accepts arguments this can be used to provide a kind of glossary ',0),(72,'help',' feed display a feed display allows you to attach an rss feed to a view  ',0),(73,'help',' arguments arguments are input while they often come from the url  they don t always so please don t be shocked when they don t each display type may have its own source for arguments block displays have no source of arguments at all they cannot pull arguments from the url and often require use of the default argument php code in order to get arguments the argument default plugins can be used to get arguments into a block view see provide default below in general arguments are used to filter the view and in that sense they have a very close relationship to filters but that isn t necessarily true for every argument arguments can be used for any purpose really the extent of what the argument does is up to the developer of the argument but the arguments that come with views are almost entirely filters a typical use of an argument might be to reduce a view to a single node a single user or nodes with a given taxonomy term action to take if argument is not present ignore the argument is removed from the view as though it weren t there and all results will be displayed hide view page not found the view will remove itself entirely if the argument is not present for a block this means it simply won t appear for page views the view will return a 404 and present a page not found error display empty text the value of the empty text will be displayed summary the view will attempt to display a summary of arguments available based upon the view and provide links to the view with those arguments summaries have their own style handlers as well as options the default summary style simply displays a list of arguments with a count of entries found per argument this special mode is a very powerful part of views provide default if no argument is given a default argument can be selected the method of choosing the default argument is selectable and pluggable wildcards all arguments have a wildcard which is an argument that means to use all values in practice it is the same as ignore above where the argument is simply removed and the view is created without the argument the wildcard title is used in titles and breadcrumb trails default arguments default argument selection is available only if the action to take is provide default   when that is selected a new fieldset will appear letting you choose what the default argument will be views provides the following default selectors by default but other modules may add more fixed entry you may directly enter what the argument will be this is not a variable it will always be the same argument node id from url this will attempt to find a node id from the url and is primarily useful for the node id argument though other arguments that use node ids such as the cck node reference argument will find it useful too for example when visiting the path node 1 or node 1 edit it will know that the 1 in that path is a node id and use it user id from url like node id from url this will attempt to find a user id from the path it also includes an option to look for a node and use the node author as the user id user id from logged in user you can use this to easily default a menu item to the logged in user for example if you created the path blogs and gave it a user id argument with this default blogs would go to the user s own blogs and blogs 1 would go to user id 1 s blogs please bear in mind that the selection of default argument happens only if an argument is not provided if using a display that has no argument source such as a block this will always be used however if using a display that reads arguments from the url this will happen only if the url did not contain an argument argument validation arguments can also have validators which are pluggable systems used to ensure that arguments fit within certain parameters when a validator is chosen it may provide some settings for the validator including the action to take if an argument is presented but it fails to validate these actions are generally the same as the default actions above excluding the ability to provide another default if a view provides a menu option such as a tab if the argument does not validate the tab will not appear this sytem can have other validators plugged in by default views provides basic validation ensures that the argument is present a php null value from eg php default argument code will invalidate node ensure that the argument is a valid node id you may select which types of node the validator will accept taxonomy term ensure that the argument is a valid taxonomy term this includes options to limit to specific vocabularies and can transform the argument to the right type depending upon the actual argument set the argument type option to the actual type of data that the argument being used is expecting php code you may enter arbitrary php code similar to the php block visibility code to determine if the argument is valid or not  ',0),(74,'help',' fields fields are the individual pieces of data being displayed adding the fields node title   node type  and node post date to a node view for example includes the title content type and creation date in the displayed results fields may not appear on every display because not all style plugins actually use fields for example the node row plugin simply displays the node through drupal s normal mechanisms and fields are not involved for the most part the field settings should be self explanatory fields will appear in the order that they are arranged in and they will usually appear with the label they are given ',0),(75,'help',' sorts sort criteria determine what order the records are retrieved from the database and displayed in generally all you need to do is pick a field and choose ascending 1 2 3 4 or descending 4 3 2 1 and it will be done if you have multiple sort criteria the second and later items only come into play if the first item is the same different data types sort just a little bit differently from others number fields number fields sort like you would expect 1 comes before 2 which comes before 10 which comes before 100 which comes before 200 etc text fields text fields always sort alphabetically even if the text contains numbers this can have some odd effects if you have numbers stored in text because the values 1 3 7 10 12 20 100 120 will sort like this 1 10 100 12 120 200 3 7 this is because these fields sort purely by characters and not numeric value ie comparing 200 and 3 the 2 comes before the 3 therefore 200 is smaller than 3 date fields date fields often can have a granularity which is a way of making similar dates actually be the same date take two dates that are close to each other  may 1 2007 530 am and may 1 2007 945am  without granularity the two dates are compared and the first date comes before the second date however if the granularity is set to day it only looks at the parts of the date up to the day  may 1 2007 and may 1 2007  at that point they are the same and the sort would move on to the next sort criterion  ',0),(76,'help',' filters filters are used to reduce the data set that views provides that is to say without any filters applied views will return all of your content you don t want that so at least some filters must be used some very commonly used filters the node published filter is used to restrict a node view to only nodes that are are have the published box checked this can be very important to prevent users from viewing content they should not have access to the node promoted to front page filter can be used to show only nodes that have the promote to front page turned on the node type filter is useful for showing only certain types of nodes let s say you wanted users to see only nodes that were book nodes or a combination of book nodes and staffblog nodes this filter allows you to select exactly that the user current filter will show only nodes that the logged in user has authored the node post date filter can be used to show only nodes posted before after or between a range of dates the above list is only a tiny fraction of the filters available in views referenced here to give an idea of the kinds of tasks filters can accomplish  ',0),(77,'help',' relationships relationships allow you to expand the query to include objects other than the base query this is actually made more difficult to understand by the fact that views actually includes a few relationships by default and doesn t tell you they re there for historical reasons it would be inconvenient to remove these default relationships when relationships are present all fields including relationships will gain a new form item to let you select which relationship they will use they will default to using no relationship at all the main example of the relationship that is there by default is the node user relationship every node has an author and if a node is in the query the user who wrote that node is automatically made available note the author considers it an error that this relationship is automatic but by the time it was realized this was in error it was too late to change it a similar relationship that is not automatically made available is for node revisions each revision has its own author which is the user who made the revision by adding the node revision user relationship all of the user fields sorts filters and arguments available to a user will now be available for the revision author when a relationship is added to the view all applicable items will gain a relationship select box where you can choose which version of that particular item you wish to use this can be illustrated with an example a comment view contains the relationships comment node and comment user this means that all the fields for the node that a comment is attached to are available and all the user fields for that node author also become available the other relationship makes fields for the author of the comment available very often not the author of the node when you add the user name field you will be presented with a select box either the node relationship or the user relationship must be selected because there are two possible user names in the view to choose from another example of relationships involves the files table in drupal files are related to users but files are not necessarily related to nodes however the uploadmodule allows some files to be attached to nodes the only way for views to deal with this discrepancy is with relationships when creating a node view it s possible to add an uploaded files relationship to get file data for nodes that were attached with the upload module it is also possible to go the other way from a files view you may add a relationship via the upload table to view information about the node  ',0),(78,'help',' output styles view styles  the views  style system is how you customize the output produced by your view a view style is basically a smart theme template that processes the view data and then outputs it all styles in views can be overridden by placing copies of the templates in your theme directory and then modifying them see the theme information link available on all views to get hints for which templates a given view is using a breakdown of view output by default the style is unformatted  which means that there is very little style actually used the records are simply displayed one after another enclosed in a div tag so that you can use css to manipulate the view  some styles use a separate row style to determine how each row of the view looks this is useful for mixing and matching styles to more readily produce exactly the kind of output you need many styles can be grouped  for styles that can there will be a grouping field option pick one of the fields to group by this grouping field will be displayed as a header and all rows will be displayed beneath it with the theme developer module enabled the field grouping in views does not work disable the theme developer module before grouping by fields each style is its own entity  ',0),(79,'help',' view row styles a row style is an individual style to display only an individual record within a view for example a node type view would display one node per row a user type view would display one user per row some row styles use fields which means you select from the available fields to display others do not they are able to use the base type and create a display usually row styles that do not use fields produce less efficient slower views  so bear this in mind when contemplating the performance of your site ',0),(80,'help',' list output style the list view style will display every row of the view as part of an html list construct for example row 1 row 2 row 3 row 4 you may select whether or not the list is ordered which just means whether or not it uses numbers instead of the bullet row 1 row 2 row 3 row 4 the list style also uses a row style which means that it doesn t care what the actual output for each row of the view is if you need information about using css to style list views you may find this a list apart guide to styling lists useful ',0),(81,'help',' unformatted output style the unformatted output style simply places each row of the view one after another with no additional formatting  ',0),(82,'help',' table output style the table style will display the view results as a table each row of the table will correspond to a row from the view result when setting the table options each field in the view will be presented with some information next to each field  column by default each field is its own column however you can place multiple fields in the same column to do this pick which field you want to represent the column then pick another field and set the column value to that field you can place as many fields as you like in a single column but only the main field in a column can be clicksorted separator if you have multiple fields in the same column the separator will be placed between each one at the very least nbsp should be used as without the separator the fields will be placed very close to each other common separators are a bullet the symbol and a comma if there are no other fields in the column the separator will have no effect sortable if checked the header for the column will be clickable and the user may resort the table by clicking on this to sort by that field at this time views does not support clicksorting to sort by multiple columns at the same time default sort you may select a column which will be sorted by default when the table is first viewed this column will be highlighted to the user you may also select whether the default sort is ascending or descending  ',0),(83,'help',' grid output style the grid style will display each row of your view within a grid you may customize the number of columns though it defaults to 4 a grid looks like this row 1 row 2 row 3 row 4 row 5 row 6 row 7 row 8 row 9 row 10 row 11 row 12 row 13 row 14 row 15 row 16 the above uses the horizontal alignment where rows are added into the grid from left to right with a vertical alignment rows will be placed from top to bottom like this row 1 row 5 row 9 row 13 row 2 row 6 row 10 row 14 row 3 row 7 row 11 row 15 row 4 row 8 row 12 row 16 this style uses a row style to determine what each row will look like ',0),(84,'help',' rss output style the rss output style is only available for feed display types it will display the view as an rss feed which is a specialized xml output this output is not user visible but can be parsed by feed readers for aggregation you may supply a description for the rss feed most feed readers will display this description along with the contents of the feed you may also select to use the site s mission statement for the description ',0),(85,'help',' fields row style the fields row style displays each field defined in the view one after another each field defines its own output by default each field is put in a div unless it is selected to be inline  if it is inline it is put in a span two items in div s will be displayed one after another with the second one below the first two items in span s will be displayed on the same line one item in a span next to div s is the same as two items in div s this means that for the inline setting to do anything at least two consecutive items must be set inline you may define a separator which will be placed between each item this separator may be html you can use nbsp to print blank space ',0),(86,'help',' node row style the node row style will display each item of the view through drupal s standard nodeview  function views has very little control over this output except for the options you see instead the output is run through the standard node template mechanism typically nodetplphp or a variant thereof and any decisions about what is output may be done there views does add an extra suggestion to the list of possible node templates  nodeviewviewnametplphp  you may use this to theme a node specifically for the view this can be handy for creating very small teasers and the like you may opt to display the full node body or the node teaser and you may add the node links such as he comment links that appear after a node or not because of this behavior  the node row style does not utilize fields and the fields section will not be displayed please note that this row style performs a nodeload for every row and as such can produce a lot of extra queries sometimes this is necessary but it can have a negative impact on your site s performance  ',0),(87,'help',' node rss item row style this row style is only available to rss styles it produces xml necessary for an rss feed for the node record ',0),(88,'help',' comment rss item row style this row style is only available to rss styles it produces xml necessary for an rss feed for the comment ',0),(89,'help',' unformatted summary style the unformatted summary style is only available for summary styles which are when an argument has been set to provide a summary if it was not provided with a value this summary provides the possible candidates for the argument one after another with no special formatting if inline is selected the summary items will be enclosed within span tags otherwise the items will be in div tags you can also elect to display the number of matching records for the argument plus change the number of items per page for the summary this is often useful because summary views are often quite small but other views quite space intensive it is very common to have far more records available in the summary view than in the more normal view ',0),(90,'help',' list summary style the list summary style is only available for summary styles which are when an argument has been set to provide a summary if it was not provided with a value this summary provides a list of possible candidates for the argument in a standard html list like the normal list style you may set this list to be ordered or not you can also elect to display the number of matching records for the argument plus change the number of items per page for the summary this is often useful because summary views are often quite small but other views quite space intensive it is very common to have far more records available in the summary view than in the more normal view ',0),(91,'help',' menu options page display  page displays can hook into the drupal menu system and provide menu links that will appear in the navigation system as well as tabs that can be used to keep views next to each other for simple menu links  there is very little you need to do simply select normal menu entry and fill in the text for the title this will appear in the navigation menu by default you will need to visit the menu administration page to move this to another menu tabs are not quite so simple there are some complex rules for using tabs in drupal all tabs must have a parent which is the next level up in the path hierarchy for example if the view path is example taba then the parent must be example all tabs must have one and only one default tab this is usually the same content as the parent if a parent does not exist when creating the default tab views will allow you to also create a parent item it will automatically set up the url for you when it does this tab weight is used to control what order the tabs are displayed in lower numbers will display more to the left for tabs whose numbers are the same they will be displayed alphabetically drupal only supports 2 levels of tabs so be careful about trying to put tabs within tabs within tabs that won t work for example if you have two views that you want to be tabs you could set it up like this in the first view set the path to tabs tab1 set it to be the default tab set the title to tab 1 and the weight to 0 click update and you will be taken to a form that lets you define the parent since tabs doesn t already exist in the system select normal menu item and set the title to tabs on the second view set the path to tabs tab2 set it to be a menu tab and set the title to tab 2 with this done you will now have a navigation link named tabs and when you click on it you will go to the tabs with tab 1 being the default tab that appears you can then click between tab 1 and tab 2  ',0),(92,'help',' path options page display  if a display has a path that means that it can be retrieved directly by calling a url as a first class page on your drupal site any items after the path will be passed into the view as arguments for example if the path is foo bar and a user visits http wwwexamplecom foo bar baz beta  baz and beta will be given as arguments to the view these can be handled by adding items to the arguments section you may also use placeholders in your path to represent arguments that come in the middle for example the path node someview would expect the first argument to be the second part of the path for example  node 21 someview would have an argument of 21  note  views 1 used  arg for this kind of thing arg is no longer allowed as part of the path you must use instead if multiple displays within the same view have the same path the user will get the first display they have access to this means you can create successfuly less restricted displays in order to give administrators and privileged users different content at the same path ',0),(93,'help',' theme information you may use any of the following possible theme files to modify individual parts of your view in total there are four parts to theming a view the display theme is usually viewsviewtplphp and it largely controls the decorations around a view where the header footer pager more link feed icon etc will be placed the style will control how all of the results of the display are put together it may be as simple as just displaying all of the rows or it may be a complex table generator or something in between the row style controls each individual row not all styles utilize the row style notably the table but most others do finally  field themes allow you to override the look and even the data of each individual field if the style uses fields the actual template the system will use should be hilighted in bold  a breakdown of view output the link to the left of each type will give you information about the default template used for that type you may cut and paste this and place it in your theme with the appropriate template or you may copy the base file from the views theme directory or if provided by a module from the module s directory  it is important that you clear the theme registry cache every time you add a new template or the new template will not be picked up important note  you place your custom template files in your theme directory  not views theme  this is always true of theming with drupal in addition to this tool the very useful devel module contains a tool called the theme developer which does a good job of visually showing you which areas of your site use which themes be careful with it though as the theme developer causes the views edit page to break also this feature will only work properly with drupal 63 and later prior to drupal 63 this patch will be required  ',0),(94,'help',' using views templates views theme templates are straightforward to use with the drupal theming system if you are unfamiliar with the theming system at all you should probably at least read drupalorg theming documentation  that said these are the important things you need to know copy a base views template to one of the names provided from the theme information section of the view copy this template right into your theme directory clear the theme registry see the instructions for how to do this your new template should now operate assuming you picked a nicely named template that includes the view name that template should now be active for your view a good example is viewsviewlistfoobartplphp which would work for a view named foobar you can now modify this template all you like for any template that uses fields the fields will be in array in order to use this effectively you will need to understand enough php to fetch data from an array this is a place where the devel module can really help you because you can use its dsm function right in your template to see what variables it uses there is an alternative to dsm that works without devel module but it s a bit longer to use for example i placed the following code inside a loop in viewsviewtablephpphp php drupalsetmessage pre varexport row true pre and it produced this output array nid 97 title scisco ideo vicis feugiat qui name luwrepuslan my view had three fields node nid node title user name the contents of the row variable included these fields in precisely the order that i had arranged them to using the views rearrange link also worth noting though is that each field also has an identifier so it can easily be pulled out of the row should i want to display it differently using php print row title would print just the title for that row please remember that i m doing this inside the loop so this will get repeated for every row of the view the ids used to fetch items from the array id  row title  can be quickly and easily looked up on the theme information page once a field has been added to the view its id will not change but note that if there are two title fields in a view one will be title and the other will be title1 in order to prevent namespace collisions the important thing here is that views does provide ids views doesn t tell you what these ids are but it s easy to get them by dumping the row data and doing a simple visual inspection views does guarantee that these ids will not change unless you actually add a new field and remove the existing one in which case title above would become title1  the basic fields template the most common template people will need to rewrite is the simple viewsviewfieldstplphp which is the template used by the fields row style and all it does is display a simple list of fields however it is not that simple to the user because the template can t inherently know what the fields are it has to go through an array in a loop this loop isn t very handy when you really want to have fine control over the template by placing your fields precisely where and how you want relax though if you know what your fields are you can rewrite this if you end up writing your own html the only part that is really important is the content for each field we know from above that you can get the id for each field on the theme information page from the view in the header for the template we can see that the fields are all in the fields array and each field is an object that leads us to this php print fields someid content assuming you replace someid with an id found on the theme information page this code will print the content for that field you can also get the label and some other data about the field as well as the raw information complete details for what is available are documented directly in viewsviewfieldstplphp keep in mind that if you rewrite your templates using this you ll need to maintain this template whenever changes are made to the fields of the view while this isn t generally recommend sometimes it s necessary to get the kind of control you might ultimately need  ',0),(95,'help',' using css with views views uses a wide array of css classes on all of its content to ensure that you can easily and accurately select exactly the content you need in order to manipulate it with css typically every view is wrapped in a div with the name of the view as part of its class for all these examples we will assume the name of the view is myview  as well as the generic class view div class view viewmyview div in your css you can modify all views divview border 1px solid black or just your view divviewmyview background yellow by default the general view template also provides the following classes to easily style other areas of the view viewheader viewfilters viewcontent viewempty if an empty text is used when the view has no results viewfooter feedicon attachmentbefore if using an attachment display attachmentafter if using an attachment display so for example divviewmyview divviewheader make the header stand out fontsize 120 fontweight bold divviewmyview divviewfooter make the footer less important fontsize 80 fontstyle italic color ccc in the above example we whimsically made the header bold and in a bigger font and the footer smaller italicized and greyish views with fields if your view has fields each field is uniquely tagged with its id a field s id may be gleaned from the theme information page note that due to css rules any in the id will be converted to automatically so if you have a field whose id is editnode this is the field used to provide an edit link to a node it will be editnode additionally to make sure that the view ids don t conflict with other css classes in the system they will be pretended with viewsfield thus the final css class for the field with the id editnode will be viewsfieldeditnode  exactly how this appears is going to depend upon the style you re using for example the unformatted style uses divviewsfieldeditnode and divviewslabeleditnode to access that particular field but a table would use tdviewsfieldeditnode and thviewsfieldeditnode to access the table header or just viewsfieldeditnode to affect both viewmyview th color red make all headers red viewmyview viewsfieldtitle fontweight bold make the title field bold viewmyview tdviewsfieldbody fontsize 60 make the text in the body field small  ',0),(96,'help',' what are overrides  if an item is using defaults then it is using values from the default display  important note  if you modify this value you are modifying the default display and thus modifying for all displays that are using default values if that is not what you intend you must click the override button once overridden that display now has its own version of the value modifying it will not modify it for other displays for relationships   arguments   fields   sort criteria  and filters  each of these must be overridden as a group in other words you cannot override a single filter but instead must override all filters a message will appear on the item to let you know what its status is but you can only change the status by clicking on the header or the rearrange button for that item  ',0),(97,'help',' embedding a view into other parts of your site you can easily embed the results of a view into other parts of your site either with code as a module or in nodes or blocks as snippets the easiest way is to use the function viewsembedview   embed a view using a php snippet this function is meant to be called from php snippets should one wish to embed a view in a node or something it s meant to provide the simplest solution and doesn t really offer a lot of options but breaking the function apart is pretty easy and this provides a worthwhile guide to doing so param name the name of the view to embed param displayid the display id to embed if unsure use default as it will always be valid but things like page or block should work here param any additional parameters will be passed as arguments function viewsembedview name displayid default to figure out the id of a display hover your mouse over the tab to select that display everything after the viewstab is the id of that display this id is guaranteed never to change unless you delete the display and create a new one  ',0),(98,'help',' what s new in views 2 views 2 is the newest major release of views and it is specifically coded for drupal 6 views 2 retains all of the core functionality of views 1 together with a completely revamped user interface and a large set of new features which greatly expand upon the original featureset of views 1 this document is a sidebyside comparison of views 1 versus views 2 from a user s perspective detailing the ui changes some new ways to perform old tasks the cool new features of views 2 and how these features can be used to address some of the shortcomings of views 1 admin interface the first thing that pops out after you install views 2 is the radically different admin interface  views 2 admin interface compared to the old comfy views 1 interface  views 1 admin interface the new admin interface performs the same functions as the old listing all the views in the system providing links to add or import views and a link to views tools but has been compacted with each view displayed as a paragraph stylerow compared to the table of views 1 and set of filters on top to ease locating views among a large list contexthelp is available by clicking the small blue questionmark icon contexthelp in views 2 is provided by the advanced help module so make sure to install that together with installing views 2 the small blue help icons will be available in various parts of the views ui in particular look for them as part of the description of a display  when setting style options and in various editing sections such as path   menu and the like several new attributes of each view are visible in the filter header  tag  this is just another label for organizing and sorting views tags can be any text views that are provided by modules will often be tagged together to make it easy to find them display  in views 1 each view query was tied to its display in other words your fields sorts filters and arguments could only be displayed in the single page or block display provided in the view definition in views 2 view displays have been decoupled from view queries it is now possible to have multiple page block and feed displays from a single view more on view displays later type  views 2 view types are radically different from views 1 types views 1 types basically defined how the node list displays were styled  you had full nodes teaser list table view and so on in views 2 view display styles have been broken out into the separate style attribute view types now refer to the primary table on which information for the query will be retrieved which controls what arguments fields sort criteria and filters are available views 2 view types are discussed later adding a view so let s jump in and add a view for this example we re going to create a user view which will display a list of users adding a view the first step in adding a view is simply entering a name only alphanumeric characters no spaces a description tag and the view type to get the user view we selected the user radio button configuring the new view this might be the 2nd whoa moment as the interface here is also completely revamped from views 1x the best way to summarize is to say all the pieces from the views 1x interface are still therejust in different places fields arguments sort critera and filters are all still there there just in new ajaxyflavours let s start by adding some fields  adding fields clicking on the icon next to the word fields unfurls a section beneath the view information with all the available fields grouped by comment file node node revision taxonomy and user and probably a few others this is a general paradigm for the views 2 interface clicking on a widget or link unfurls a section beneath the view information with the relevant interface usually what is being edited will be hilited in yellow as well when adding items you can use the groups dropdown box to show only a subset of the fields available according to the above groups or select all to see all fields available which is what was selected when the section unfurled for our example we re selecting the user group and adding the user email   user name and user picture fields adding fields once we add our fields they show up in the fields section of the interface we will be walked through each field we added so keep clicking update  even if you don t make changes to the field and you will see the next one the fields we added can be rearranged by clicking the up down icon right next to the add icon we used earlier we can also remove a field using the same interface rearranging fields from here the fields can be dragged up and down by grabbing the little drag handle on the left and moving them where you like making a change to any part of the view by clicking update usually triggers a refresh of the view preview which is conveniently located right below the main interface views preview now that we have some fields set up we can turn our attention to basic settings for the view it s important to note that all the interface elements pertain to the current display selected for the view as mentioned before a view can have multiple displays the first time you create a view you ll be manipulating the default display you can add displays using the add display button whose basic settings are completely different from each other this lets you have as many displays of a view as you would like all sharing items such as sort criteria filters and arguments but different display settings like title style fields and pager settings also any display you add automatically inherits display settings from the default display initially so you can keep a core of common settings in your default display and add additional settings for every other display adding a page display let s stick with the default display and twiddle some settings we can set the title to user view 1 and the style to table as mentioned earlier view styles in views 2 correspond more to view types in views 1 remember list table teasers full nodes  selecting a views 1 view type in views 2 view styles control how a view display looks these styles are significantly different from the types in views 1 in particular types have been broken up there is now the style as well as the row style which focus on different parts of the output a breakdown of view output we change the style by clicking on the current style on the left hand side of the view information area selecting a views 2 display style we re given the style options of grid   list   table and unformatted  additional display styles can be added by modules which have views style plugins  choosing a style reveals a settings button which you can click to configure the style you ve chosen in the shot below we ve selected and are configuring the table style which we re using to produce a more compact output than we had earlier selecting and configuring the table style  todo finish this document  ',0),(99,'help',' updating your views from views 1 to views 2 todo this document needs to be fleshed out  ',0),(100,'help',' views api views allows modules to describe their tables relationships to each other as well as fields filters sort criteria and arguments via hookviewsdata   whenever views deems it necessary this hook is called the data aggregated together and cached hookviewsdataalter  may also be used to modify existing data changing other module s handlers or adding handlers to other module s tables views also allows modules to create new display types style types row styles argument default handlers and argument validators via hookviewshandlers  and hookviewsplugins   these hooks are kept in a file named modulenameviewsinc this file is automatically included upon need so there is no need to try and include this in hookinit or any other method of including inc files this file should store hookviewsdata hookviewsdataalter hookviewsplugins hookviewshandlers as well as any other hooks and subsidiary data that will only be used by your module when views is active all handlers and plugins provided by your module should be in separate inc files there are two similar files modulenameviewsdefaultinc and modulenameviewsconvertinc which contain default views and views 1 to views 2 convert helpers respectively hookviewsapi  in order for your files to be included your module must first implement hookviewsapi  in the main module file this module should return array of information the following items may be returned  api this must appear it should be the oldest api version that your module can work with if views is currently running an older version of the api it will ignore your module s views integration this is a good thing as it will prevent code crashes at the expense of your module s functionality disappearing you may find the current views api version by calling viewsapiversion  which is implemented at the top of viewsmodule this version numbering starts at 20 every time changes are made to the views handlers and plugins or other aspects of the views api the number will tick up by either 001 01 1 or 1 depending upon how major the changes are note that viewsapiversion  was introduced in views 20rc2 and may not exist prior to that version you may use functionexists to test to see if this function is there often these versions are basically compatible with each other and views won t care if your module implements 2000 2001 2002 etc your module can request that it won t work with any version older than a given version however views will determine itself if a newer version will work path if your views inc files are not in the same directory as the module file then return the full path here you should probably use something like drupalgetpath module yourmodulename includepath  ',0),(101,'help',' describing tables to views tables are described to views via hookviewsdata which returns an array of table information keyed by the name of the table for example if your module is describing three tables foo bar and baz your array will look like this data array foo array info here bar array info here baz array info here the key should be the actual database name of the table not including prefix but it can be an alias as long as the join information explained later contains the real name of the table each item in the array should be a field in the table with the exception of a special information section called table example data foo array table array info about the table described later bar array info about the field named bar ie foobar baz array info about the field named baz ie foobaz once you get down to an array that contains actual data that piece of the array will often be referred to as the definition the table section each table should have a table section in it which is used to set default information for the table such as the group as well as the very important joins and whether or not this is a base table first there are several items that are actually for fields but can be placed here so that all fields within the table inherit them group the name of the group this item will be with in the ui this is displayed as group title for example node node id taxonomy term description etc it is important to be consistent with groups because the ui sorts by group and allows filtering by group to find fields as well title the actual name of the field it should be concise and descriptive help a longer description to help describe what the field is or does it should try to be only a line or two so as not to clutter the ui in general having title and help at the table level doesn t make a lot of sense but usually every item in a table is in the same group thus it is very common to define the group data foo table group t foo  base table if your table is a base table meaning it can be the primary central table for a view to use you can declare it to be a base table this primarily provides ui information so that it can be selected for example advertise this table as a possible base table data node table base array field nid title t node help t nodes are a drupal site s primary content weight 10 the following tags are available in the field the primary key field for this table for views to treat any table as a base table it must have a primary field for node this is the nid for users this is the uid etc without a single primary key field ie not a composite key views will not be able to utilize the table as a base table if your table does not have a primary key field it is not too difficult to just add a serial field to it usually title the title of this table in the ui it should be singular and describe the object that this table contains from the perspective of the user help a short piece of text to describe what object this table contains database if this table is held in a different database from your drupal database specify it as a string in the exact same format as the settingsphp file this is a special purpose variable that will probably be only used in site specific code and it must be the same database type as your drupal database  also don t try to join it to any table that isn t in the same database that ll just create all kinds of silly errors for example in settingsphp for your site your drupal site database needs to be called default dburl default mysqli user pass host drupaldb dburl budget mysqli user pass host otherdb then when you are describing the external database in your base table you would write something like this data table table base array field primary key title t field name help t field description database budget weight 10  linking your table to existing base tables for views to use your table it has to either be a base table or know how to link to an existing base table or sometimes both views uses this information to create a path to the base table when the table is added to the query views will walk along this path adding all tables required into the query how termdata joins to node in the above example to use these with node as the base table both termdata and termnode need to be defined and they each need a join handler for node data termdata table join node array lefttable termnode leftfield tid field tid the above can be read as in order to join to the node table the termdata table must first link to the termnode table and they join on the tid field when adding this table to the query for a node view views will look at this and then look for the termnode table data termnode table join node array leftfield nid field nid above the fact that lefttable is left out lets us know that termnode links directly to the node table using the nid field on both sides of the join quite a few more fields are available in this definition handler the name of the handler object to use defaults to viewsjoin you may create custom join handlers that may or may not use any of the data below as they see fit table table to join this is optional and should only be used if the table being referenced is an alias field field to join on this is required lefttable the next step toward the final destination if this is the final destination it may be omitted leftfield the field to join to on the left side this is required type either left default or inner extra either a string that s directly added or an array of items each item is itself an array field field or formula operator similar to filters this is the operator such as etc defaults to or in value must be set if an array operator will be defaulted to in numeric if true the value will not be surrounded in quotes and d will be used for its placeholder extra type how all the extras will be combined either and or or defaults to and describing fields on tables aside from the special table tag each table can also have an unlimited number of field designations these correspond roughly to fields on the table though it is very common to use nonfields to display data that isn t directly in a field such as data arrived from formulae or special links related to the object the table is part of each field is described in the view data with an array keyed to the database name of the field this array may contain some information fields plus an entry in each of the five types of items views has per field argument field filter relationship sort for example data node nid array title t nid help t the node id of the node the help that appears on the ui information for displaying the nid field array handler viewshandlerfieldnode click sortable true information for accepting a nid as an argument argument array handler viewshandlerargumentnodenid name field title the field to display in the summary numeric true validate type nid information for accepting a nid as a filter filter array handler viewshandlerfilternumeric information for sorting on a nid sort array handler viewshandlersort the above example describes the nid field on the node table providing 4 of the 5 handlers note that while field is normally expected to be the database name of the field it doesn t have to be you can use an alias which is how you get multiple handlers per field or something completely made up for items that aren t tied to the database for example data node editnode array field array title t edit link help t provide a simple link to edit the node handler viewshandlerfieldnodelinkedit the above handler definition an edit link to a node but this isn t a field in and of itself for aliased fields here is another example data users uidcurrent array real field uid title t current help t filter the view to the currently logged in user filter array handler viewshandlerfilterusercurrent the above definition provides an alternate filter handler on the uid field for the current user the following items are allowed in the field definition group title help as above these fields are for the ui if placed here any of these fields will override a setting on the base table real field if this field is an alias the real field may be placed here and the handler will never know the difference field a handler definition for the field section which is a field that may be displayed in a view the definition is an array the contents of the array are completely up to the handler other than the handler definition if omitted handler will default to viewshandlerfield filter a handler definition for the filters section which will be used to apply where clauses to the view the definition is an array the contents of the array are completely up to the handler other than the handler definition if omitted handler will default to viewshandlerfilter sort a handler definition for the sort criteria section which will be used to add an order by clause to the view the definition is an array the contents of the array are completely up to the handler other than the handler definition if omitted handler will default to viewshandlersort relationship a handler definition for the field section which is a way to bring in new or alternative base tables in the view the definition is an array the contents of the array are completely up to the handler other than the handler definition if omitted handler will default to viewshandlerrelationship the basic relationship handler requires base and base field to be set base and base field represent the right half of the join that will use this field as the left side argument a handler definition for the field section which is method of accepting user input from the url or some other source the definition is an array the contents of the array are completely up to the handler other than the handler definition if omitted handler will default to viewshandlerargument for more information about what handlers need use what data visit the views api site and check out the available handlers  ',0),(102,'help',' using default views in your module views can be stored in the database which is typical of smaller sites and hobby sites however views may also be stored directly in the code as default views which simply means they re available by default modules often come with views that are specific to the module data but it s also possible and highly recommended that sites which have separate development and production sites export their views into default views in a sitespecific module this makes it very easy to transfer views from dev to production without making database changes creating a module first create a directory in sites all modules for your new module call it whatever you like but for this example we will call it mymodule  in this directory create a mymodulemodule file it can be empty for now but it should at least contain an opening php tag php id it should not contain a closing tag as the closing tag is not required and anything after the closing tag such as a space or a linefeed will be displayed directly to the browser and can potentially cause problems the module file will contain functions and drupal hooks hooks are specially named functions that drupal will call in order to get your module s response at certain times while generating pages the only function you will need for this exercise is the viewsapi hook that tells views that this module supports the views api and what version function mymoduleviewsapi return array api 20 for other uses you may well add additional functions second you need to create a mymoduleinfo file id name my module description my site specific module core 6x once you have these two files set up you should be able to activate your new module at the administer site building modules page exporting your views the easiest way to do this is to activate the viewsexport module and navigate to administer views tools bulk export place a check next to each view that you want in your module type the module name into the text field and click export this will create the entire hookviewsdefaultviews  function for you you can also export individual views if you do this keep in mind that this export does not include the line that adds the exported view into the larger views array views view name view to place this into your hookviewsdefaultviews  you will need to place that after the view and make sure the function returns views at the end placing your exported views into your module cut and paste the entire output of the bulk export tool into mymoduleviewsdefaultinc and be sure to put a php at the top of the file so that the webserver knows that it s php code then visit the views tools page and clear the views cache your views should now be listed as overridden on the view list page if you revert these views they will be removed from the database but will remain in code theming your views in your module you can theme these views in the module and not need to rely on the theme to do this at all and in fact the theme can continue to override these just like it ordinarily would even if your module provides a theme this is very useful for distributing a module where the view needs to look just so to do this you need to implement hooktheme  in your module function mymoduletheme existing return array viewsviewviewnamedisplayid array arguments array view null template viewsviewviewnamedisplayid original hook viewsview path drupalgetpath module mymodule there are a small number of gotchas in doing this that you must be aware of when referring to a template filename you always use dashes in the name ie  viewsviewviewnamedisplayidtplphp  however when referring to the hook or function names you use underscores instead of dashes ie  viewsview and viewsviewviewnamedisplayid the arguments change based upon which of the 3 types you re overriding there s the display the style and the row style the above code is assuming the display which is usually just viewsview  here are the possibilities display array view null style array view null options null rows null title null row style array view null options null row null be sure to use the right arguments line or the theme system will not properly translate the template line should never include the extension so drop the tplphp from it you need to make sure that the views preprocess functions get registered the original hook line in the definition does that but it can only do it if it comes after the views registration which actually happens very late in theme building 99 of the time your module will come before views you have two choices to deal with this set your module s weight to 11 or higher in the database views weight is 10 you can make this happen automatically when the module is first installed by creating a mymoduleinstall file and using this code function mymoduleinstall dbquery update system set weight 11 where name mymodule if you use this method the original hook should be set to the name of the original template being used ie if this is a variate of viewsviewlisttplphp this should be viewsviewlist you can also just force it to list the preprocessors without actually having to detect them this doesn t require modifying your module s weight which is not always possible you can insert this code into the array preprocess functions array templatepreprocess templatepreprocessviewsview mymodulepreprocessviewsviewviewnamedisplayid the first one is the global templatepreprocess function which all templates utilize it does some basic things such as setting up zebra and a few other items see apidrupalorg for specifics the second one is the plugin specific preprocess like original hook it should conform to the name used by the original template ie if the original template was viewsviewlisttplphp then that preprocess function would be named templatepreprocessviewsviewlist  the third one is your module s preprocess function if it needs one in general you probably will not need one and you should only attempt to use one if you are reasonably familiar with the concept of preprocess functions and drupal s theme system in general see drupal s theme documentation for more information if you leave the path blank the template file will be searched for in which is the drupal install base path  ',0),(103,'help',' how views handlers work in views a handler is an object that is part of the view and is part of the query building flow handlers are objects much of the time the base handlers will work but often you ll need to override the handler for something one typical handler override will be viewshandlerfilteroperatorin which allows you to have a filter select from a list of options you ll need to override this to provide your list handlers have two distint code flows the ui flow and the view building flow for the query flow handler construct create the initial handler at this time it is not yet attached to a view it is here that you can set basic defaults if needed but there will be no knowledge of the environment yet handler setdefinition set the data from hookviewsdata relevant to the handler handler init attach the handler to a view and usually provides the options from the display handler prequery run prior to the query stage to do early processing handler query do the bulk of the work this handler needs to do to add itself to the query fields being the only handlers concerned with output also have an extended piece of the flow handler prerender called prior to the actual rendering this allows handlers to query for extra data the entire resultset is available here and this is where items that have multiple values per record can do their extra query for all of the records available there are several examples of this at work in the code handler render this does the actual work of rendering the field most handlers are just extensions of existing classes with a few tweaks that are specific to the field in question for example filter by node type class viewshandlerfilternodetype extends viewshandlerfilterinoperator function getvalueoptions if isset this valueoptions this valuetitle t node type types nodegettypes foreach types as type info options type info name this valueoptions options  viewshandlerfilterinoperator provides a simple mechanism to set the list used and the rest of the handler is perfectly fine for this handlers are stored in their own files for these files to be loaded by views on demand they must first be registered since views core handlers are also loaded this way it s imperative that your module also implement this pattern in order to prevent code crashes when your handler s parent class is not yet available to register handlers you must implement hookviewshandlers   this hook returns an array with two keys the first key is info which contains the modulename which is only necessary if you re registering handlers on behalf of another module such as what views does and path  which is the search path to find the files this path is only necessary if your files will not be stored in the same directory as the module file the other key is handlers which contains a full array of handlers and the information for each handler the key to each handler array is the name of the handler class it can contain  parent the class that this handler extends this is important to make sure that the parent class is included before your handler class without this you may cause people s sites to crash in a difficult to recover state be sure you get this right  file the filename the handler is in by default this will be classnameinc however you can have multiple similar handlers together in one file however because there is only one parent please be sure that the parentage on these handlers matches otherwise you will run into whitescreens as not all parents will be loaded you can see examples of this function in any of the various moduleviewsinc files in the views modules directory the best place to learn more about handlers and how they work is to explore the views api site and use existing handlers as a guide and a model understanding how viewshandler and its child classes work is handy but you can do a lot just following these models you can also explore the views module directory particularly nodeviewsinc please note that while all handler names in views are prefixed with views you should use your own module s name to prefix your handler names in order to ensure namespace safety note that the basic pattern for handler naming goes like this module handler type tablename fieldname sometimes table and fieldname are not appropriate but something that resembles what the table field would be can be used ',0),(104,'help',' how views plugins work in views a plugin is a bit like a handler but plugins are not directly responsible for building the query instead they are objects that are used to display the view or make other modifications there are 6 types of plugins in views display display plugins are responsible for controlling where a view lives page and block are the most common displays as well as the ubiquitous default display which is likely what will be embedded style style plugins control how a view is displayed for the most part they are object wrappers around theme templates row style row styles handle each individual record from a node argument default argument default plugins allow pluggable ways of providing arguments for blocks views includes plugins to extract node and user ids from the url additional plugins could be used for a wide variety of tasks argument validator validator plugins can ensure arguments are valid and even do transformations on the arguments access access plugins are responsible for controlling access to the view plugins are registered by implementing hookviewsplugins  in your modulenameviewsinc file and returning an array of data the array will look something like this return array display array list of display plugins style array list of style plugins row array list of row style plugins argument default array list of argument default plugins argument validator array list of argument validator plugins access array list of access plugins each plugin will be registered with an identifier for the plugin plus a fairly lengthy list of items that can define how and where the plugin is used here is an example from views core node array title t node help t display the node with standard node view handler viewspluginrownodeview path drupalgetpath module views modules node not necessary for most modules theme viewsviewrownode base array node only works with node as base uses options true type normal of particular interest is the path directive which works a little differently from handler registration each plugin must define its own path rather than relying on a global info for the paths also there is an optional parent directive which is automatically filled in to be the base parent for the plugin type usually this is enough but if your plugin derives from something other than the base it must be filled in for example feed array title t feed help t display the view as a feed such as an rss feed handler viewsplugindisplayfeed parent page so it knows to load the page plugin inc file uses hook menu true use ajax false use pager false accept attachments false admin t feed help topic displayfeed note that unlike handler registration where parentage is referred to by object name with plugins it is referred to by the unique plugin identifier please be sure to prefix your plugin identifiers with your module name to ensure namespace safety after all two different modules could try to implement the grid2 plugin and that would cause one plugin to completely fail todo finish this document  ',0),(105,'help',' integrating the node example module for the new table defined by the node example module to be understood by the views module you need to create a nodeexampleviewsinc file that describes the table and its relationships to the rest of the database in order for views to know that this file is to be loaded you need to implement hookviewsapi this is done by adding the following function into your nodeexamplemodule file php implementation of hookviewsapi this tells drupal that there is views integration file named modulenameviewsinc function nodeexampleviewsapi note that you can include path in this array so that your viewsinc file can be stored in a different location return array api 20 below is the contents of a simple nodeexampleviewsinc file that allows you to create views that include the new color and quantity information php id apiexamplehtml v 12 20090915 154414 merlinofchaos exp this file is used to tell the views module about the new nodeexample table database definition code create table nodeexample vid int 10 unsigned not null default 0 nid int 10 unsigned not null default 0 color varchar 255 not null default quantity int 10 unsigned not null default 0 primary key vid nid key nodeexamplenid nid endcode function nodeexampleviewsdata basic table information nodeexample table new group within views called example the group will appear in the ui in the dropdown tha allows you to narrow down which fields and filters are available data array data nodeexample table group t example let views know that our example table joins to the node base table this means it will be available when listing nodes and automatically make its fields appear we also show up for node revisions data nodeexample table join array noderevisions array leftfield vid field vid node array leftfield vid field vid quantity data nodeexample quantity array title t quantity help t quantity of items field array handler viewshandlerfieldnumeric click sortable true filter array handler viewshandlerfilternumeric sort array handler viewshandlersort color data nodeexample color array title t color help t color of item field array handler viewshandlerfield click sortable true filter array handler viewshandlerfilterstring argument array handler viewshandlerargumentstring sort array handler viewshandlersort return data some notes on usage within views click on the add tab you have a number of type options here normally you would select either node if you only want to display information on current nodes or node revision if you want to display information on all revisions of the nodes with this configuration you always pull out of the database data for every single node whether or not it has color and quantity information to display information on just those nodes that have color and quantity information you can use a filter so that only nodes which don t have a null color or a null quantity are displayed type relationship extension when your tables have first class data you will often need to have own view types and view relationships defined with the current nodeexample table this isn t required although i try to justify it below on an efficiency basis see http groupsdrupalorg node 17236 comment58980 this discussion as to why it isn t justified pulling data out of the database for every node when you only want data for the new example node type is inefficient to reduce the initial data extraction to just that relating to the new example nodes requires that you make the nodeexample table the base table this can be done by adding the following code into the nodeexampleviewsinc file just before the return data php begin optional extra for type and relationships use nodeexample as a new base table by creating a new views type called node example this allows it to be selected as the view type when you initially add a new view data nodeexample table base array field vid title t node example help t node example type with color and quantity information weight 9 when using the new node example type you need to use relationships to access fields in other tables relationship to the node revision table data nodeexample vid array title t node revision help t the particular node revision the color and quantity is attached to relationship array label t node revision base noderevisions base field vid this allows us to not show this relationship if the base is already noderevisions so users won t create circular relationships skip base array node noderevisions relationship to the node table data nodeexample nid array title t node help t the particular node the color and quantity is attached to relationship array label t node base node base field nid this allows us to not show this relationship if the base is already node so users won t create circular relationships skip base array node noderevisions end optional extra for type and relationships the above code adds a new node example to the view types that can be selected within the add tab window of views selecting this sets the nodeexample table to be the base table if you select node example as view type when you initially go into the edit window of views you will find the only fields available are the color and quantity fields to get fields from other tables you need to add a relationship relationships may be found at the top in the same column as the fields  ',0),(106,'help',' about page manager the page manager module creates and manages pages in your drupal site pages are defined as items that have a path and provide output to the user it is a complete round trip from getting user input to providing user output there are two types of pages that the page manager currently supports custom pages custom pages are defined completely by the administrator their path access control and visible menu characteristics are completely arbitrary system pages system pages are defined by drupal and drupal modules they primarily override preexisting pages to provide different functionality they often do not allow such features as access control in favor of what already exists and they will usually fall back to default drupal behavior both types of pages figure out what to show the user by using variants  variants are output handlers and every page should have at least one most pages will simply have only one pages with multiple variants will choose one and only one variant to display content to the user and will use the selection rules to figure out which variant to display ',0),(107,'help',' getting started note this page is currently very preliminary please visit http drupalorg node 528034 to help provide this documentation page this is a quick summary visit administer site building pages to get to the primary page manager interface you can add custom pages for your basic landing pages front pages whatever you like for normal content display you can use the system pages to create finer control of how taxonomy vocabularies nodes and user profiles are displayed when you add your first custom page do not bother with the optional features you will not need these until you get to more advanced tasks the selection rules are the key to creating node displays for just one node type everything in this system is pluggable a little php knowledge and exploration of the plugins directories can take you a long way  ',0),(108,'help',' the page list please visit http drupalorg node 528036 to help provide this documentation page ',0),(109,'help',' creating a page please visit http drupalorg node 528038 to help provide this documentation page ',0),(110,'help',' tutorial make a page that looks different for members please visit http drupalorg node 528040 to help provide this documentation page ',0),(111,'help',' tutorial customize the look of a single node type please visit http drupalorg node 528044 to help provide this documentation page ',0),(112,'help',' tutorial customize the look of a single taxonomy vocabulary please visit http drupalorg node 528046 to help provide this documentation page ',0),(113,'help',' custom pages please visit http drupalorg node 528050 to help provide this documentation page ',0),(114,'help',' arguments please visit http drupalorg node 528058 to help provide this documentation page ',0),(115,'help',' access control please visit http drupalorg node 528072 to help provide this documentation page ',0),(116,'help',' menu items please visit http drupalorg node 528078 to help provide this documentation page ',0),(117,'help',' variants please visit http drupalorg node 528078 to help provide this documentation page ',0),(118,'help',' readme  id readmetxt v 1526 20100909 030434 sun exp summary jquery ui http uijquerycom is a set of cool widgets and effects that developers can use to add some pizazz to their modules this module is moreorless a utility module that should simply be required by other modules that depend on jquery ui being available it doesn t do anything on its own for a full description of the module visit the project page http drupalorg project jqueryui to submit bug reports and feature suggestions or to track changes http drupalorg project issues jqueryui requirements the jquery ui library installation copy the jqueryui module directory to your sites all modules directory so it is located in sites all modules jqueryui download the jquery ui 16 release from http codegooglecom p jqueryui downloads list q 16 put the downloaded archive into the module directory sites all modules jqueryui jqueryui16zip extract the archive this will create the following subdirectory sites all modules jqueryui jqueryui16 rename the subdirectory into jqueryui within the jqueryui module folder sites all modules jqueryui jqueryui so the actual jquery ui javascript files are located in sites all modules jqueryui jqueryui ui js enable the module at administer site building modules jquery ui 17 the jquery ui module uses jquery ui 16 because jquery ui 17 requires at least jquery 13 which is not shipped with drupal 6 if you absolutely need to move to jquery ui 17 you can get around this by doing the following download and install the corresponding jquery update module from http drupalorg project jqueryupdate download the latest jquery ui 17 release from http codegooglecom p jqueryui downloads list q 17 put the downloaded archive into the module directory sites all modules jqueryui jqueryui17zip extract the archive this will create the following subdirectory sites all modules jqueryui jqueryui17 rename the subdirectory into jqueryui within the jqueryui module folder sites all modules jqueryui jqueryui so the actual jquery ui javascript files are located in sites all modules jqueryui jqueryui ui js enable the module at administer site building modules api developers who wish to use jquery ui effects in their modules need only make the following changes in your module s info file add the following line dependencies jqueryui this will force users to have the jquery ui module installed before they can enable your module in your module call the following function jqueryuiadd files for example jqueryuiadd array uidraggable uidroppable uisortable jqueryuiadd uisortable for a single file see the contents of the jqueryuixx subdirectory for a list of available files that may be included and see http uijquerycom docs for details on how to use them the required uicore file is automatically included as is effectscore if you include any effects files contact current maintainers jeff robbins jjeff angela byron webchick addison berry add1sun daniel f kudwien sun http drupalorg user 54136  ',0),(119,'help',' readme  id readmetxt v 12 20080521 050445 webchick exp contents of this file introduction installation introduction authors jeff robbins jjeff angela byron webchick addison berry add1sun this module made by robots http wwwlullabotcom jquery update module upgrades drupal s stable version of jquery in order to support the most current jquery version available once a stable release of drupal comes out only minor bugfix changes may be added to it so drupal s version of jquery will often lag behind the most recent release offered by the jquery project the jquery community tends to only support the most recent version so this module ensures that your drupal installation can run the most uptodate jquery plugins installation 1 copy the jqueryupdate directory to your sites sitename modules directory 2 enable the module at administer site building modules 3 that s it thanks to the new theme system in drupal 6x you no longer need to copy files around hooray  ',0);
