name mode size
admin_menu 040000
advanced_help 040000
bday 040000
bkngcncl 040000
bkngcncl_bck 040000
bookingmanagement 040000
bulkmail 040000
bw_analytics 040000
bwadvancesearch 040000
bwbilling 040000
bwcharts 040000
bwcommon 040000
bwgroupmail 040000
bwmailtracker 040000
bwnewsletter 040000
canceldetails 040000
charts_graphs 040000
content_access 040000
css 040000
css_bck0n14thnov13 040000
ctools 040000
dashboard 040000
diner 040000
dinerdetails 040000
dinermobile 040000
directbooking 040000
entity 040000
fancy_login 040000
fancytest 040000
feedback 040000
fonts 040000
fusiontest 040000
groupmail 040000
groups 040000
images-source 040000
images 040000
imce 040000
js 040000
libraries 040000
mailinterface 040000
menu_per_role 040000
mobilesetup 040000
nodeaccess 040000
page_theme 040000
paypal-master 040000
plan 040000
restaurantholiday 040000
restaurantmenu 040000
restaurantmenu2 040000
restaurantprofile 040000
rules 040000
sass-extensions 040000
sass 040000
setupfiles 040000
shifttimings 040000
signup 040000
signup1 040000
simplesignup 040000
specialmealtype 040000
tableplan 040000
taxonomy_access 040000
tcpdf 040000
templates 040000
test 040000
times 040000
timeslot 040000
userpage2 040000
views 040000
views_charts 040000
views_slideshow 040000
yourdb 040000
README.txt 100644 6 kb
README.txt~ 100644 0 kb
bwcharts.tar 100644 17,430 kb
bwcommon.tar 100644 10 kb
bwcrs.info 100644 6 kb
bwgroupmail.tar 100644 320 kb
bwnewsletter.tar 100644 50 kb
config.rb 100644 2 kb
favicon.ico 100644 15 kb
logo.png 100644 1 kb
paypal-master.tar 100644 800 kb
screenshot.png 100644 9 kb
style-desktop.css 100644 55 kb
template.bck_20131209 100644 5 kb
template.php 100644 5 kb
template.php~ 100644 5 kb
templates_bckon16nov2013.tar 100644 200 kb
theme-settings.php 100644 1 kb
README.txt
<<<<<<< HEAD Place downloaded and custom modules that extend your site functionality beyond Drupal core in this directory to ensure clean separation from core modules and to facilitate safe, self-contained code updates. Contributed modules from the Drupal community may be downloaded at http://drupal.org/project/modules. It is safe to organize modules into subdirectories, such as "contrib" for contributed modules, and "custom" for custom modules. Note that if you move a module to a subdirectory after it has been enabled, you may need to clear the Drupal cache so that it can be found. In multisite configuration, modules found in this directory are available to all sites. Alternatively, the sites/your_site_name/modules directory pattern may be used to restrict modules to a specific site instance. Refer to the "Developing for Drupal" section of the README.txt in the Drupal root directory for further information on extending Drupal with custom modules. ======= BUILD A THEME WITH ZEN ---------------------- The base Zen theme is designed to be easily extended by its sub-themes. You shouldn't modify any of the CSS or PHP files in the zen/ folder; but instead you should create a sub-theme of zen which is located in a folder outside of the root zen/ folder. The examples below assume zen and your sub-theme will be installed in sites/all/themes/, but any valid theme directory is acceptable (read the sites/default/default.settings.php for more info.) Why? To learn why you shouldn't modify any of the files in the zen/ folder, see https://drupal.org/node/245802 *** IMPORTANT NOTE *** * * In Drupal 7, the theme system caches which template files and which theme * functions should be called. This means that if you add a new theme, * preprocess or process function to your template.php file or add a new template * (.tpl.php) file to your sub-theme, you will need to rebuild the "theme * registry." See https://drupal.org/node/173880#theme-registry * * Drupal 7 also stores a cache of the data in .info files. If you modify any * lines in your sub-theme's .info file, you MUST refresh Drupal 7's cache by * simply visiting the Appearance page at admin/appearance. * 1. Setup the location for your new sub-theme. Copy the STARTERKIT folder out of the zen/ folder and rename it to be your new sub-theme. IMPORTANT: The name of your sub-theme must start with an alphabetic character and can only contain lowercase letters, numbers and underscores. For example, copy the sites/all/themes/zen/STARTERKIT folder and rename it as sites/all/themes/foo. Why? Each theme should reside in its own folder. To make it easier to upgrade Zen, sub-themes should reside in a folder separate from the base theme. 2. Setup the basic information for your sub-theme. In your new sub-theme folder, rename the STARTERKIT.info.txt file to include the name of your new sub-theme and remove the ".txt" extension. Then edit the .info file by editing the name and description field. For example, rename the foo/STARTERKIT.info file to foo/foo.info. Edit the foo.info file and change "name = Zen Sub-theme Starter Kit" to "name = Foo" and "description = Read..." to "description = A Zen sub-theme". Why? The .info file describes the basic things about your theme: its name, description, features, template regions, CSS files, and JavaScript files. See the Drupal 7 Theme Guide for more info: https://drupal.org/node/171205 Then, visit your site's Appearance page at admin/appearance to refresh Drupal 7's cache of .info file data. 3. Choose your preferred page layout method or grid system. By default your new sub-theme is using a responsive layout. If you want a fixed layout for your theme, delete the unneeded "responsive" and "responsive-rtl" css/sass files and edit your sub-theme's styles.css or styles.scss file and replace the reference to "responsive" with "fixed". For example, edit foo/sass/styles.scss and change this line: @import "layouts/responsive"; to: @import "layouts/fixed"; Alternatively, if you are more familiar with a different CSS layout method, such as GridSetApp or 960.gs, etc., you can replace the "layouts/responsive" line in your styles.scss file with a line pointing at your choice of layout CSS file. Then, visit your site's Appearance page at admin/appearance to refresh Drupal 7's theme cache. 4. Edit your sub-theme to use the proper function names. Edit the template.php and theme-settings.php files in your sub-theme's folder; replace ALL occurrences of "STARTERKIT" with the name of your sub-theme. For example, edit foo/template.php and foo/theme-settings.php and replace every occurrence of "STARTERKIT" with "foo". It is recommended to use a text editing application with search and "replace all" functionality. 5. Set your website's default theme. Log in as an administrator on your Drupal site, go to the Appearance page at admin/appearance and click the "Enable and set default" link next to your new sub-theme. Optional steps: 6. Modify the markup in Zen core's template files. If you decide you want to modify any of the .tpl.php template files in the zen folder, copy them to your sub-theme's folder before making any changes. And then rebuild the theme registry. For example, copy zen/templates/page.tpl.php to foo/templates/page.tpl.php. 7. Modify the markup in Drupal's search form. Copy the search-block-form.tpl.php template file from the modules/search/ folder and place it in your sub-theme's template folder. And then rebuild the theme registry. You can find a full list of Drupal templates that you can override in the templates/README.txt file or https://drupal.org/node/190815 Why? In Drupal 7 theming, if you want to modify a template included by a module, you should copy the template file from the module's directory to your sub-theme's template directory and then rebuild the theme registry. See the Drupal 7 Theme Guide for more info: https://drupal.org/node/173880 8. Further extend your sub-theme. Discover further ways to extend your sub-theme by reading Zen's documentation online at: https://drupal.org/documentation/theme/zen and Drupal 7's Theme Guide online at: https://drupal.org/theme-guide >>>>>>> aee3f7a9d4f57dd68563af1ab4859a375227803a