I love the Drupal CMS. One of my favorite features of Drupal is the ability to do a multisite install. This site and my other blog, i <3 stella, are hosted on the same box, using the same Drupal install. Several sites can share one codebase. Updates are easily rolled out to every site simultaneously. Overall, it's a wonderful idea. But I have some problems with the implementation...
We'll look at one solution to these problems.
I assume here that you are using Linux hosting, that you have shell access, and that you have at least a passing acquaintance with symlinks. If you're looking for a webhost that meets these requirements, check out 1and1 shared hosting. I've been happy with them, and all of their packages above $9.99/mo will do what you need.
Microsoft/IIS guys, you can't do a symlink. You're looking for something called a junction... good luck with that.
I love the Drupal CMS. One of my favorite features of Drupal is the ability to do a multisite install. This site and my other blog, i <3 stella, are hosted on the same box, using the same Drupal install. Several sites can share one codebase. Updates are easily rolled out to every site simultaneously. Overall, it's a wonderful idea. But I have some problems with the implementation...
We'll look at one solution to these problems.
I assume here that you are using Linux hosting, that you have shell access, and that you have at least a passing acquaintance with symlinks. If you're looking for a webhost that meets these requirements, check out 1and1 shared hosting. I've been happy with them, and all of their packages above $9.99/mo will do what you need.
Microsoft/IIS guys, you can't do a symlink. You're looking for something called a junction... good luck with that.
Here's a code snippet that you can use to set the disabled attribute of a CCK field.
First, you need to create a small module containing the following code:
Explanation:
Setting the #disabled attribute of the element in form_alter doesn't work because the FAPI process handler of the CCK field won't transfer the #disabled attribute to its children elements. So we need to find a different method...
We can do this using our own #after_build handler, but here we cannot simple set the $element['#disabled'] attribute of the element. The reason is this attribute is transformed into $element['#attributes']['disabled'] by _form_builder_handle_input_element executes(), which is the format FAPI theme functions know about. However, _form_builder_handle_input_element executes() is executed before #after_build handlers are invoked, so our own handler needs to set the value as the theme functions expect. See form_builder().
Finally, we need to use a recursive function so that we can set the disabled attribute of all the FAPI elements that depend on the CCK field we're interested in. Think for example about a checkboxes element, etc.
We can think of more ideas to enhance the form.
For example, we can save the user clicking the "Update location field" button by... clicking it for him. We do this by attaching an onchange event handler to the 'country' and 'state' fields. This onchange handler would automatically click the button for the user. Furthermore, the user don't even have to see this button, so we can hide it (hide it via Javascript so in case no Javascript support is there the user can still access the button).
That was one idea.
But we have another idea, a marvelous one with chocolate on top:
We don't like the way all the page gets refreshed when this button is clicked. Why don't we channel the response from the server into a hidden frame (IFRAME), load this textual response from here into a Javascript variable and finally replace only the "Location" fieldset the user sees on screen with this response? This would have a pleasant visual effect: the user would feel he never
It is still possible to execute shell code without shell access. To execute shell code in Drupal, simply create a PHP page with the following and execute it from your root Drupal directory:
print `ln -s /root_path/public_html/ /root_path/public_html/newsite`; ?>
We've recently begun putting together the infrastructure for a number of upcoming projects which will organize people around the world toward some pretty powerful, ambitious goals. While the details of those sites are still in the works, working with Drupal to create multi-language sites has been a great experience involving a great deal of learning. This is the first of a two part series covering how Drupal works with multiple languages and the best practices/tricks of the trade for making the most of the Drupal Local, i18n and L10n systems.
上圖顯示了一個經過修改的 user page 的 tabs
tabs 其實來自一個 hook(), menu_local_tasks()
用 theme developer 指一下便可以看到
但這次介紹的並不是要修改這個 hook 的 theme template
而是使用 views, 新增一個tab 到這個地方
在上圖的例子,
一個 url 為 [root]/user 的 頁面,
要在 views 建立一個的 tab,
if your career as a developer has included a stay in the j2ee world, then when you arrived at drupal one of your initial questions was "where's the log file?". eventually, someone told you about the watchdog table. you decided to try that for about five minutes, and then were reduced to using a combination of
and print_r to scrawl debug data across your web browser.
when you tired of that, you learned a little php, did a little web research and discovered the PEAR log package and debug_backtrace(). the former is comfortably reminiscent of good old log4j and the latter finally gave you the stacktrace you'd been yearning for. still, separately, neither gave you quite what you were looking for : a log file in which every entry includes the filename and line number from which the log message originated. put them together though, and you've got log4drupal
log4drupal is a simple api that writes messages to a log file. each message is tagged with a particular log priority level (debug, info, warn, error or em
One of the powerful features in Drupal is the node_access system. This is an API within Drupal which allows modules to do fine grained access access contol to individual nodes.
If you are using Drupal core, this system does nothing. You need to either enable one of the many node access modules, or write your own module to do that.
Writing a simple specialized node access module is what this article covers.
The resume_access module is part of the Drupal jobsearch module, which 2bits wrote. In a nutshell, the jobsearch modules allows you to define one or more content types to be job postings (openings, contracts, ...etc), and one or more to be resumes (CVs for those across the pond). Then for the job postings, there is an "apply" link that prompts job candidates to apply to the job.
One request is to make resumes private so job applicants cannot see other job applicants' resumes.
The module we are discussing today is called resume_access, and it does this by using the node_access system.
First we define a permission called "view resumes". Under Roles, you select one or more roles that has the right to see resumes, for example employers, recruiters, ...etc.
Drupal Code Search helps you find Drupal code easier!
Search Examples
make a template called “node-type.tpl.php”. for cck circa aug 2006, this is ‘node-content_cust_content_name.tpl.php’. then put this in to find out what info is available:
gleaned from creating a template handbook.
This is a collection of useful links on debugging, tracing, and profiling Drupal.
Got a good article about debugging Drupal or hints and tips on that? Post it as a comment below
However, there are sometimes side effects to enabling the devel module on 4.6 and 4.7, that may manifest itself in certain situations. For example, showing errors on the screen directly.
If you want the timer functionality without the full devel, here is a tiny module that displays the timer at the bottom of every page.
To configure it, you have to add the following to the bottom of your settings.php file.
http://www.comeongame.com/ english game site, online games, flash games
其实我不知道用drupal是否适合设计这样的站，但是用drupal已经习惯了，就设计个，不会php, 虽然难了点，但还是被他强大的灵活性所吸引，欲罢不能...
这次我用了6.x设计我的game搜集站，主要是因为image field可以有link to node，并且图片和swf文件的上传都采用 用户ID/年月...这个方式，避免了大量文件都传到一个文件夹下的情况.... 以后站大了，这样做文件管理也好些... 这次是5.7版的comeongame(www.greenidea.net)的升级。。。
第一：主题设计
关于主题设计主要是采用了复写，在这里感谢drupaluser.cn提供给我的帮助，使我终于脱离了panels模块, 可以随意设计自己的排版!
page-front.tpl.php 复写首页
page-taxonomy.tpl.php 复写列表页
page-flashnode.tpl.php 和 node-flashnode.tpl.php 复写flash内页
复写page-flashnode.tpl.php注意....直接复写并不会成功，参照http://drupaluser.cn/html/mytheme/2009-01-01/332.html
这里主要是采用drupal的复写机制... 首先在.info文件里面建立自己的region, like this:
regions[left] = Left sidebar
regions[right] = Right sidebar
regions[content] = Content
regions[header] = Header
regions[footer] = Footer
然后你可以用css+div写自己的模板，将regins放在你想放的地方... regions不能放在node上... 如果想法似乎要搞template.php,我也尝试过，成功了！
关于flash游戏页面的设计，$content变量被我具体化成很多变量，主要是我想按照自己的div排版安排位置...这里我主要用content templete去找变量...然后同样道理用div+css结合变量去设计layout....这样可以方便随意设计出自己的排版.....为了有很好的seo, mate keywords和desciption部分我也加入了部分变量输出.....
第二：模块的使用
因为我的站是flash小游戏搜集站，所以主要依靠flash node的功能.....输出用view2+cck, 然后还有投票的功能我用了vote up and down....你也需要cck的image field去输出游戏的截图, 用pathauto去定义了下node的url,形式是...../分类名/文章标题，分类用 Taxonomy
主要有6大类，分别在首页输出block,关于view2的主题制作也是复写....用css+div控制下就可以了
大概就是这么个流程.... 希望高手指点....
有很多朋友拿到了我的主题，启用以后却发现和我的主题有很多差别，这是因为我的主题是定制的，
不像drupal官方提供的那样拿过来就能直接用，区块的位置和我的后台设置的不一样的话，样式都会乱
所以我在这里只是提供一个制作方法；
在第一部分当中，我已经介绍过了，Drupal使用者中文社区[ http://drupaluser.cn ]的tpl文件主要是以下几个
首页我们使用page-front.tpl.php文件覆写
列表页面我们使用page-taxonomy.tpl.php文件覆写
内容显示我们使用page-story.tpl.php和 node-story.tpl.php来覆写
其他的静态页面我们使用page-page.tpl.php和node-page.tpl.php来覆写
其中page-story.tpl.php 和page-page.tpl.php不是默认就会起作用，比较常见的有两种方法可以让他起作用，
一种是drupal的风格，在template.php中覆写函数实现，这种方法老葛的zhupou上面有介绍，在此不再赘述了
另一种是比较容易理解的风格，可以在page.tpl.php上面写一个判断，让他根据内容类型自己选择模板文件，
如以下写法：
最近在盤算在兩個freelance 之間擠出些時間做一個全新的theme
碰巧又沒有什麼特別的題目或教學
所以發表些我定制這個theme 時的一些小技巧
(這些小技巧不一定會出現在未完成的這個theme 內)
比如說我要在 "Read more" "Add new comment" 之前加個可愛的icon
但因為"Read more" 和 "Add new comment" 畏使用不同的icon (當然吧)
所以要看看從css 上它們的class 或 id 值有否特定
才可以用css 定制不同的icon
如不, 可能要hack 核心或使用js 來忙了
Check out Zucker's post entitled " Sorry I didn't respond sooner" at http://drupal.org/node/23991. Let me know if this answers your question.
This section of the site contains Drupal tutorials. When browsing the Drupal-specific areas of this site, look for the Drupal tutorials menu that appears on the left sidebar. The list of tutorials is also listed below.
![a more secure drupal [multisite] install | justin hileman dot info](/pages/images/toolbar-mark.gif)
