Blogs

Microsoft Windows Firewall has been conflicting with McAfee security, and preventing me from properly sharing folders and accessing network drives in our LAN. The firewall was automatically turned on by a Windows XP update a few weeks ago, and it has cause us unnecessary pain. Finally put it in it's place and the configuration between the multiple Firewalls (hardware and software) works properly

The title of this document may sound contradictory and unclear, but the detailed statement is: Looking for a way to maintain versions of Drupal core and modules in SVN-Subversion over time, and still be able to have clean files on the development and production server without risking old files that may prevent the application from functioning properly.

I just realised (from reading online) that IE (sadly both 6 and 7) do not support either CSS pseudo-classes not JQuery last-child method (http://www.evotech.net/blog/2007/05/ie7-css-selectors-how-they-fail/) in strict XHTML mode. Strangely though IE7 supports first-child as long as there is a space before :first-child i.e:

li :first-child

For the purpose of effectively describing the intended features, RSS syndication will be understood to stand for the availability of XML feeds (Atom, RSS etc) of documents from the site we are building categorised using the various available criteria, and available for external users (RSS consumption applications) to aggregate and display on other presentation media

The scope objective of this particular implementation requires that content be limited to a certain section of the registered audience made up of paying members.

Methodology

1. Use the main feature of Drupal Organic Groups to create a setup where content can be published and assigned into groups and/or public access. These silos of information will include all the features of Drupal (KB, books, news items, traditional forum etc) and will be created to mimic the main product-lines of company. Group owners/admins will control admission to the groups.

How to create items

1. Create new documents of the content type (KB)
2. If the documents will have children, use the 'outline' tab of the document to place it within an existing hierarchy, or to enable it to have child-documents
3. Commenting: Any knowledgebase entry can have comments entered at the bottom, but at least a generic account is required to post comments (with approval) or a higher account is required to post without approval
4. Captcha is not used in KB commenting situations because KB commenting is only allowed for account holders (bo

Drupal provides basic blogging features out of the box. These base feature can be augmented and enhanced by the other CMS features and most of the modules available for Drupal. Blog entries are treated as generic content types with the key difference that they are each attributed to a given user account. Just like other content types, CCK and VIEWS can be used to extend the data fields available for each blog post.

It is amazing that FTP is still widely used and even promoted (by inaction and implication) by most commercial web hosts. Using FTP to send files to your web server, and even having the FTP service running on your web server is equivalent to making banking transactions without SSL enabled - the door is almost wide open and you could be setting yourself up for disaster.

SSH

SSH has been around for a long time and there are now many commercial and freeware tools that enable you to get at least the same functionality as you have always had from your FTP server but without the risk.

It appears that loading the JStools tabs CSS @import derictive before the default line for CSS styles in a Drupal theme prevents the default styles from being applies in IE browsers (yes, including IE7 and IE8).

<style type="text/css" media="all">@import "/modules/jstools/tabs/tabs.css"</style>

I have been looking for a maintainable way to limit the taxonomy lists produced by the Drupal taxonomy module by the autor. In a project that seems to categorise nodes by the author to create a paradigm were the user experience is dictated by the profile page that a viewer last visited, restricting taxonomy lists by author supports this UX paradigm.

Requirements
My main requirements was to create a maintainable setup that would not require intervention as new taxonomy terms are created in a given vocabulary.