Respect: What is it?

Respect Meaning and Definition:

  1. (v. t.) To consider worthy of esteem; to regard with honor.
  2. (v.) Esteem; regard; consideration; honor.
  3. (v.) The act of noticing with attention; the giving particular consideration to; hence, care; caution.
  4. (v.) Relation; reference; regard.
  5. (v. t.) To take notice of; to regard with special attention; to regard as worthy of special consideration; hence, to care for; to heed.
  6. (v. t.) To have regard to; to have reference to; to relate to; as, the treaty particularly respects our commerce.
  7. (v.) An expression of respect of deference; regards; as, to send one’s respects to another.
  8. (v. t.) To look toward; to front upon or toward.
  9. (v.) Consideration; motive; interest.
  10. (v. t.) To regard; to consider; to deem.
  11. (v.) Particular; point regarded; point of view; as, in this respect; in any respect; in all respects.
  12. (v.) Reputation; repute.

Brought to you by thinkexist.com

Do you agree or disagree?

I personally love the quote from Mark Cement where he says:
“Leaders who win the respect of others are the ones who deliver more than they promise, not the ones who promise more than they can deliver.”

2011
02/28
CATEGORY
Uncategorized
Leave a comment

Positive Attitude: What it takes in the design world

A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort.  ~Herm Albright, quoted in Reader’s Digest, June 1995

Continue reading →

2011
01/31
CATEGORY
Web Class
Leave a comment

Communication: How does it relate to Web Design

Ok, lets break this down.  Communication, what is it and how does it effect our lives when it come to development.  People all around me tell me that the key to life is to have good communication.  Does this relate to Web Design?  I would have to say that it does in SO many ways.

A website depends on the communication of everything.  From client side to server side communications, the Internet connection and how the client can communicate with the internet, to communication with client and how they want their site to be displayed, the communication with your team and how you are going to accomplish the build of the site.  This is just the beginning of what is involved in our everyday life.

According to Wikipedia.com if defines communication as:

Communication is a process whereby information is enclosed in a package and is channeled and imparted by a sender to a receiver via some medium. The receiver then decodes the message and gives the sender a feedback. All forms of communication require a sender, a message, and an intended recipient, however the receiver need not be present or aware of the sender’s intent to communicate at the time of communication in order for the act of communication to occur. Communication requires that all parties have an area of communicative commonality. There are verbal means using language and there are nonverbal means, such as body language, sign language, paralanguage, haptic communication, chronemics, and eye contact, through media, i.e., pictures, graphics and sound, and writing.

As I read this, communication is a broad covering for how we navigate through life with everything that we come in contact with.  With the body language and excitement, or anger, when we are speaking with the client, to the images that we create for the site to communicate with the customers on the internet as we try and convey what we want them to see.  As we add the content that goes along with communicating with the customer but also the search engines to place our site to be seen by the world, I would have to consider that communication is the foundation to what makes our life and web design a reality.

2010
11/29
CATEGORY
Web Class
Leave a comment

TEAMwork, what does it take?

Have you every felt like you were the only one out there in the world with an idea, and had no idea how to make that idea come to life?  It reminds me of this guy here. One of the great things is that when you go to company, in hopes of them to give you a way of bringing your idea to life, they do not just give you to one person and leave it up to them to make your dreams come alive.  They have a team in place to take your idea and present you with all the options that they ALL think of.

I work with a team that is a nation wide development company.  When someone comes to us to do whatever they need done, they are put in contact with the team that is going to accomplish what they need. With me being one of the developers for this company, by the time that I receive the job to build, the client has already worked with and spoken with 7 different people of our team, to make sure that we are doing the best that we can for this client.  Then on top of that, depending on the job, I may be the only one designing for that client or we may bring in 4 or 5 different developers to help in areas that they are strong in to complete the project at hand.

You may be a strong person, in and of yourself, but you would not compare to a team that is working together at any given time.  The more that you surround yourself with people, that can give you ideas that you didn’t think of, to lend a hand when you are stuck or having problem, to step in and take some load off your plate at times, the stronger person that you will become in the long run.  Not to mention the clients that you will blow away with your combined ideas and service that you can provide them.

2010
10/31
CATEGORY
Web Class
Leave a comment

TRUSTWORTHINESS: is a moral value considered to be a virtue.

Trustworthiness is a moral value considered to be a virtue. A trustworthy person is someone in whom you can place your trust and rest assured that the trust will not be betrayed. A person can prove their trustworthiness by fulfilling an assigned responsibility – and as an extension of that, not to let down expectations. The responsibility can be either material, such as delivering a mail package on time, or it can be non-material such as keeping an important secret to themselves. A trustworthy person is someone that you can tell your worries and secrets to and know they won’t repeat them without your permission. In general, in order for trust to be earned, worth and integrity must be proven over time.

(provided by wikipedia.org)

When I read through the description of what “trustworthiness” means, I see a lot of what we have already been writing on throughout this class.  To get the root of this topic, it is trust that we are after.  Trust is something that takes time to receive and it can be very quick to loose.  Through time and through your reputation, you will start to see the change in people that come through your office.  When the questions change from “What can you do for me?” to “Would you do that for me?”

I have gone through many client situations, where they were looking for something specific and only wanted that.  I have always looked at trust, as being honest, up front, truthful, and responsible.  So with those clients that I have dealt with, I was honest to the point that I even told them when I would not be able to help them due to my lack of knowledge in the area that they were looking.  In the long run, I lost them for that one project, but I stayed close, offered my help where I could and now they are my clients for life because I was honest and trustworthy to them from the beginning.

You never know who will walk into your life, and when your reputation proceeds you as a honest, trustworthy, and up front person in real life, it will filter over into your working profession and give you an upper hand in the tasks and career positions that you take on in your future.  In this, is how you will find yourself at the head of the line…

2010
09/30
CATEGORY
Web Class
Leave a comment

CHOICES: How many Choices do you have when it come to Web Design

So lets see here, lets choose where we want to start.  Well as you can see there are choices everywhere you look.  With web design, it is the same as well.

When you are a business owner and you are wanting to have a presence on the web, the first thing you normally are looking for is a great, eye-catching, design.  Then you want functionality, possibly with a shopping cart or reservation system, forms, and other ways for your customers to communicate with you.  Of course in anything that you invest in, you want it to be reliable.  You want to make sure that when you customer goes to you site, they find your site, and that it displays and performs properly.  Does this sound about right??

Well here is where the choices come into play.  Unfortunately enough, finances play a big part when making decisions about your website.  Just like in the diagram to the left, it illustrates 4 choices right there, and that just covers how you are going to start building your site.  Again, even those choices can be narrowed down by the amount of money you can put towards your design.

With all the technology that is out there, from Content Management Systems like: Drupal, PageLime, Light (by Element Fusion), and Javelin (by Back40Design), to having a company design and maintain you site, or even studying and building your own site, they all have their place and their pros and cons.

Have you ever looked at a site that was hard on the eyes?  or what if their content was outdated from 3 years back?  What about when you went to their site and non of their navigation or forms worked?   You might look a little like her  —–>

When it comes to web design and development, the choices you make, effect everyone. They effect the business owner and the potential profit/loss they may receive, and they effect you and I as potential customers.  If we go to a site and from first look, it was designed poorly, and the navigation was hard to use, and it has broken links, and some of the images were not showing up;  I don’t know about you, but I would more than likely leave, resulting in that business owner loosing profits.  This is an example of what will happen when you make the wrong choice when designing you site.

So in ending, Choose wisely, study and investigate the different choices and options that you have.  Go look at other sites that are in the same market as you, then look at the people who designed their site.  Look at things that are going to be beneficial to you and your company, to display what you have to offer along with the personality and charisma that you want to come with your business. Have fun and I hope to be seeing your new designs!

2010
08/30
CATEGORY
Web Class
Leave a comment

Drupal 7, Whats to Come!

What is Drupal?
Drupal is an open-source platform and content management system for building dynamic web sites offering a broad range of features and services including user administration, publishing workflow, discussion capabilities, news aggregation, metadata functionalities using controlled vocabularies and XML publishing for content sharing purposes. Equipped with a powerful blend of features and configurability, Drupal can support a diverse range of web projects ranging from personal weblogs to large community-driven sites.

When I first started working with websites, I started with a company that offered a CMS system that would only work on their site.  I have grown up in a family business where we will do anything that we can in house, so if we did not know how to do it, we would learn.  We loved the idea of a CMS where we would be able to edit and make changes whenever we wanted to.  We also didn’t have to pay someone else to do the work for us.  Well over time it becomes expensive for the hosting to justify the monthly hosting.  That is when I cam across Drupal.  Now I know that Drupal is not new, and widely popular.  However, not very many people really know what Drupal is and how it all works.

Here is a video about Drupal:

Now that you have watched the video, notice all the different people that have lent a hand in developing Drupal.

Here is a brief idea of what Drupal offers:

General features

Collaborative Book – Our unique collaborative book feature lets you setup a “book” and then authorize other individuals to contribute content.

Friendly URLs – Drupal uses Apache’s mod_rewrite to enable customizable URLs that are both user and search engine friendly.

Modules – The Drupal community has contributed many modules which provide functionality that extend Drupal core.

Online help – Like many Open Source projects, we can’t say that our online help is perfect but have built a robust online help system built into the core help text. Available to you on your own site.

Open source – The source code of Drupal is freely available under the terms of the GNU General Public License 2 (GPL). Unlike proprietary blogging or content management systems, Drupal’s feature set is fully available to extend or customize as needed.

Personalization – A robust personalization environment is at the core of Drupal. Both the content and the presentation can be individualized based on user-defined preferences.

Role based permission system – Drupal administrators don’t have to tediously setup permissions for each user. Instead, they assign permissions to roles and then group like users into a role group.

Searching – All content in Drupal is fully indexed and searchable at all times if you take advantage of the built in search module.

User management

User authentication – Users can register and authenticate locally or using an external authentication source like Jabber, Blogger, LiveJournal or another Drupal website. For use on an intranet, Drupal can integrate with an LDAP server.

Content management

Polls – Drupal comes with a poll module which enables admins and/or users to create polls and show them on various pages.

Templating – Drupal’s theme system separates content from presentation allowing you to control the look and feel of your Drupal site. Templates are created from standard HTML and PHP coding meaning that you don’t have to learn a proprietary templating language.

Threaded comments – Drupal provides a powerful threaded comment model for enabling discussion on published content. Comments are hierarchical as in a newsgroup or forum.

Version control – Drupal’s version control system tracks the details of content updates including who changed it, what was changed, the date and time of changes made to your content and more. Version control features provide an option to keep a comment log and enables you to roll-back content to an earlier version.

Blogging

Blogger API support – The Blogger API allows your Drupal site to be updated by many different tools. This includes non-web browser based tools that provide a richer editing environment.

Content syndication – Drupal exports your site’s content in RDF/RSS format for others to gather. This lets anyone with a News Aggregator browse your Drupal sites feeds.

News aggregator – Drupal has a powerful built-in News Aggregator for reading and blogging news from other sites. The News Aggregator caches articles to your MySQL database and its caching time is user configurable.

Permalinks – All content created in Drupal has a permanent link or “perma link” associated with it so people can link to it freely without fear of broken links.

Platform

Apache or IIS, Unix / Linux / BSD / Solaris / Windows / Mac OS X support – Drupal was designed from the start to be multi-platform. Not only can you use it with either Apache or Microsoft IIS but we also have Drupal running on Linux, BSD, Solaris, Windows, and Mac OS X platforms.

Database independence – While many of our users run Drupal with MySQL, we knew that MySQL wasn’t the solution for everyone. Drupal is built on top of a database abstraction layer that enables you to use Drupal with MySQL and PostgreSQL. Other SQL databases can be supported by writing a supporting database backend containing fourteen functions and creating a matching SQL database scheme.

Multi-language – Drupal is designed to meet the requirements of an international audience and provides a full framework to create a multi-lingual website, blog, content management system or community application. All text can be translated using a graphical user interface, by importing existing translations, or by integrating with other translation tools such as the GNU gettext.

Administration and analysis

Analysis, Tracking and Statistics – Drupal can print browser-based reports with information about referrals, content popularity and how visitors navigate your site.

Logging and Reporting – All important activities and system events are captured in an event log to be reviewed by an administrator at a later time.

Web based administration – Drupal can be administered entirely using a web browser, making it possible to access it from around the world and requires no additional software to be installed on your computer.

Community features

Discussion forums – Full discussion forum features are built into Drupal to create lively, dynamic community sites.

Performance and scalability

Caching – The caching mechanism eliminates database queries increasing performance and reducing the server’s load. Caching be tuned in real time and many high-traffic sites have performed very well under load.

Here is what is coming with the new Drupal 7.

As with all software and development programs, new and updated programs will always be in the works.  Below is a list posted on the Drupal.org website about all the additional modules, securities, and bug fixes that will be coming with the New Drupal 7.

I just wanted to share some of the information that I have been finding out about this CMS that is new to me.

You will see that this list is just a summery of the additions that are being done with Drupal.  I will mention that this list is a long list!  Feel free to read what you like.  The information is provided by Drupal.org.

6 * Fully rewritten database layer utilizing PHP 5’s PDO abstraction layer.
7 * Drupal now requires MySQL >= 5.0.15 or PostgreSQL >= 8.3.
8 * Added query builders for INSERT, UPDATE, DELETE, MERGE, and SELECT queries.
9 * Support for master/slave replication, transactions, multi-insert queries,
10 delayed inserts, and other features.
11 * Added support for the SQLite database engine.
12 * Default to InnoDB engine, rather than MyISAM, on MySQL when available.
13 This offers increased scalability and data integrity.
14 – Security:
15 * Protected cron.php — cron will only run if the proper key is provided.
16 * Implemented a pluggable password system and much stronger password hashes
17 that are compatible with the Portable PHP password hashing framework.
18 * Rate limited login attempts to prevent brute-force password guessing, and
19 improved the flood control API to allow variable time windows and
20 identifiers for limiting user access to resources.
21 * Transformed the “Update status” module into the “Update manager” which
22 can securely install or update modules and themes via a web interface.
23 – Usability:
24 * Added contextual links (a.k.a. local tasks) to page elements, such as
25 blocks, nodes, or comments, which allows to perform the most common tasks
26 with a single click only.
27 * Improved installer requirements check.
28 * Improved support for integration of WYSIWYG editors.
29 * Implemented drag-and-drop positioning for input format listings.
30 * Implemented drag-and-drop positioning for language listing.
31 * Implemented drag-and-drop positioning for poll options.
32 * Provided descriptions and human-readable names for user permissions.
33 * Removed comment controls for users.
34 * Removed display order settings for comment module. Comment display
35 order can now be customised using the Views module.
36 * Removed the ‘related terms’ feature from taxonomy module since this can
37 now be achieved with Field API.
38 * Added additional features to the default install profile, and implemented
39 a “slimmed down” install profile designed for developers.
40 * Added a built-in, automated cron run feature, which is triggered by site
41 visitors.
42 * Added an administrator role which is assigned all permisions for
43 installed modules automatically.
44 * Image toolkits are now provided by modules (rather than requiring a
45 manual file copy to the includes directory).
46 * Added an edit tab to taxonomy term pages.
47 * Redesigned password strength validator.
48 * Redesigned the add content type screen.
49 * Highlight duplicate URL aliases.
50 * Renamed “input formats” to “text formats”.
51 * Moved text format permissions to the main permissions page.
52 * Added configurable ability for users to cancel their own accounts.
53 * Added “vertical tabs”, a reusable interface component that features
54 automatic summaries and increases usability.
55 * Replaced fieldsets on node edit and add pages with vertical tabs.
56 – Performance:
57 * Improved performance on uncached page views by loading multiple core
58 objects in a single database query.
59 * Improved performance for logged-in users by reducing queries for path
60 alias lookups.
61 * Improved support for HTTP proxies (including reverse proxies), allowing
62 anonymous pageviews to be served entirely from the proxy.
63 – Documentation:
64 * Hook API documentation now included in Drupal core.
65 – News aggregator:
66 * Added OPML import functionality for RSS feeds.
67 * Optionally, RSS feeds may be configured to not automatically generate feed blocks.
68 – Search:
69 * Added support for language-aware searches.
70 – Aggregator:
71 * Introduced architecture that allows pluggable parsers and processors for
72 syndicating RSS and Atom feeds.
73 * Added options to suspend updating specific feeds and never discard feeds
74 items.
75 – Testing:
76 * Added test framework and tests.
77 – Improved time zone support:
78 * Drupal now uses PHP’s time zone database when rendering dates in local
79 time. Site-wide and user-configured time zone offsets have been converted
80 to time zone names, e.g. Africa/Abidjan.
81 * In some cases the upgrade and install scripts do not choose the preferred
82 site default time zone. The automatically-selected time zone can be
83 corrected at admin/config/regional/settings.
84 * If your site is being upgraded from Drupal 6 and you do not have the
85 contributed date or event modules installed, user time zone settings will
86 fallback to the system time zone and will have to be reconfigured by each user.
87 * User-configured time zones now serve as the default time zone for PHP
88 date/time functions.
89 – Filter system:
90 * Revamped the filter API and text format storage.
91 * Added support for default text formats to be assigned on a per-role basis.
92 * Refactored the HTML corrector to take advantage of PHP 5 features.
93 – User system:
94 * Added clean API functions for creating, loading, updating, and deleting
95 user roles and permissions.
96 * Refactored the “access rules” component of user module: The user module
97 now provides a simple interface for blocking single IP addresses. The
98 previous functionality in the user module for restricting certain e-mail
99 addresses and usernames is now available as a contributed module. Further,
100 IP address range blocking is no longer supported and should be implemented
101 at the operating system level.
102 * Removed per-user themes: Contributed modules with similar functionality
103 are available.
104 – OpenID:
105 * Added support for Gmail and Google Apps for Domain identifiers. Users can
106 now login with their user@domain.com identifier when domain.com is powered
107 by Google.
108 * Made the OpenID module more pluggable.
109 – Added code registry:
110 * Using the registry, modules declare their includable files via their .info file,
111 allowing Drupal to lazy-load classes and interfaces as needed.
112 – Theme system:
113 * Removed the Bluemarine, Chameleon and Pushbutton themes. These themes live
114 on as contributed themes (http://drupal.org/project/bluemarine,
115 http://drupal.org/project/chameleon and http://drupal.org/project/pushbutton).
116 * Added Stark theme to make analyzing Drupal’s default HTML and CSS easier.
117 * Added Seven theme as the default administration interface theme.
118 * Variable preprocessing of theme hooks prior to template rendering now goes
119 through two phases: a ‘preprocess’ phase and a new ‘process’ phase. See
120 http://api.drupal.org/api/function/theme/7 for details.
121 * Theme hooks implemented as functions (rather than as templates) can now
122 also have preprocess (and process) functions. See
123 http://api.drupal.org/api/function/theme/7 for details.
124 – File handling:
125 * Files are now first class Drupal objects with file_load(), file_save(),
126 and file_validate() functions and corresponding hooks.
127 * The file_move(), file_copy() and file_delete() functions now operate on
128 file objects and invoke file hooks so that modules are notified and can
129 respond to changes.
130 * For the occasions when only basic file manipulation are needed–such as
131 uploading a site logo–that don’t require the overhead of databases and
132 hooks, the current unmanaged copy, move and delete operations have been
133 preserved but renamed to file_unmanaged_*().
134 * Rewrote file handling to use PHP stream wrappers to enable support for
135 both public and private files and to support pluggable storage mechanisms
136 and access to remote resources (e.g. S3 storage or Flickr photos).
137 * The mime_extension_mapping variable has been removed. Modules that need to
138 alter the default MIME type extension mappings should implement
139 hook_file_mimetype_mapping_alter().
140 * Added the hook_file_url_alter() hook, which makes it possible to serve
141 files from a CDN.
142 * Added a field specifically for uploading files, previously provided by
143 the contributed module FileField.
144 – Image handling:
145 * Improved image handling, including better support for add-on image
146 libraries.
147 * Added API and interface for creating advanced image thumbnails.
148 * Inclusion of additional effects such as rotate and desaturate.
149 * Added a field specifically for uploading images, previously provided by
150 the contributed module ImageField.
151 – Added aliased multi-site support:
152 * Added support for mapping domain names to sites directories.
153 – Added RDF support:
154 * Modules can declare RDF namespaces which are serialized in the <html> tag
155 for RDFa support.
156 * Modules can specify how their data structure maps to RDF.
157 * Added support for RDFa export of nodes, comments, terms, users, etc. and
158 their fields.
159 – Search engine optimization and web linking:
160 * Added a rel=”canonical” link on node and comment pages to prevent
161 duplicate content indexing by search engines.
162 * Added a default rel=”shortlink” link on node and comment pages that
163 advertises a short link as an alternative URL to third-party services.
164 * Meta information is now alterable by all modules before rendering.
165 – Field API:
166 * Custom data fields may be attached to nodes, users, comments and taxonomy
167 terms.
168 * Node bodies and teasers are now Field API fields instead of
169 being a hard-coded property of node objects.
170 * In addition, any other object type may register with Field API
171 and allow custom data fields to be attached to itself.
172 * Provides most of the features of the former Content Construction
173 Kit (CCK) module.
174 * Taxonomy terms are now Field API fields that can be added to any fieldable
175 object.
176 – Installer:
177 * Refactored the installer into an API that allows Drupal to be installed
178 via a command line script.
179 – Page organization
180 * Made the help text area a full featured region with blocks.
181 * Site mission is replaced with the highlighted content block region and
182 separate RSS feed description settings.
183 * The footer message setting was removed in favor of custom blocks.
184 * Made the main page content a block which can be moved and ordered
185 with other blocks in the same region.
186 * Blocks can now return structured arrays for later rendering just
187 like page callbacks.
188 – Translation system
189 * The translation system now supports message context (msgctxt).
190 * Added support for translatable fields to Field API.
191 – JavaScript changes
192 * Upgraded the core JavaScript library to jQuery version 1.4.2.
193 * Upgraded the jQuery Forms library to 2.36.
194 * Added jQuery UI 1.8, which allows improvements to Drupal’s user
195 experience.
196 – Better module version support
197 * Modules now can specify which version of another module they depend on.
198 – Removed modules from core
199 * The following modules have been removed from core, because contributed
200 modules with similar functionality are available:
201 * Blog API module
202 * Ping module
203 * Throttle module
204 – Improved node access control system.
205 * All modules may now influence the access to a node at runtime, not just
206 the module that defined a node.
207 * Users may now be allowed to bypass node access restrictions without giving
208 them complete access to the site.
209 * Access control affects both published and unpublished nodes.
210 * Numerous other improvements to the node access system.
211 – Actions system
212 * Simplified definitions of actions and triggers.
213 * Removed dependency on the combination of hooks and operations. Triggers
214 now directly map to module hooks.
215 – Task handling
216 * Added a queue API to process many or long-running tasks.
217 * Added queue API support to cron API.
218 * Added a locking framework to coordinate long-running operations across
219 requests.
220
221 Drupal 6.0, 2008-02-13
222 ———————-
223 – New, faster and better menu system.
224 – New watchdog as a hook functionality.
225 * New hook_watchdog that can be implemented by any module to route log
226 messages to various destinations.
227 * Expands the severity levels from 3 (Error, Warning, Notice) to the 8
228 levels defined in RFC 3164.
229 * The watchdog module is now called dblog, and is optional, but enabled by
230 default in the default install profile.
231 * Extended the database log module so log messages can be filtered.
232 * Added syslog module: useful for monitoring large Drupal installations.
233 – Added optional e-mail notifications when users are approved, blocked, or
234 deleted.
235 – Drupal works with error reporting set to E_ALL.
236 – Added scripts/drupal.sh to execute Drupal code from the command line. Useful
237 to use Drupal as a framework to build command-line tools.
238 – Made signature support optional and made it possible to theme signatures.
239 – Made it possible to filter the URL aliases on the URL alias administration
240 screen.
241 – Language system improvements:
242 * Support for right to left languages.
243 * Language detection based on parts of the URL.
244 * Browser based language detection.
245 * Made it possible to specify a node’s language.
246 * Support for translating posts on the site to different languages.
247 * Language dependent path aliases.
248 * Automatically import translations when adding a new language.
249 * JavaScript interface translation.
250 * Automatically import a module’s translation upon enabling that module.
251 – Moved “PHP input filter” to a standalone module so it can be deleted for
252 security reasons.
253 – Usability:
254 * Improved handling of teasers in posts.
255 * Added sticky table headers.
256 * Check for clean URL support automatically with JavaScript.
257 * Removed default/settings.php. Instead the installer will create it from
258 default.settings.php.
259 * Made it possible to configure your own date formats.
260 * Remember anonymous comment posters.
261 * Only allow modules and themes to be enabled that have explicitly been
262 ported to the correct core API version.
263 * Can now specify the minimum PHP version required for a module within the
264 .info file.
265 * Drupal core no longer requires CREATE TEMPORARY TABLES or LOCK TABLES
266 database rights.
267 * Dynamically check password strength and confirmation.
268 * Refactored poll administration.
269 * Implemented drag-and-drop positioning for blocks, menu items, taxonomy
270 vocabularies and terms, forums, profile fields, and input format filters.
271 – Theme system:
272 * Added .info files to themes and made it easier to specify regions and
273 features.
274 * Added theme registry: modules can directly provide .tpl.php files for
275 their themes without having to create theme_ functions.
276 * Used the Garland theme for the installation and maintenance pages.
277 * Added theme preprocess functions for themes that are templates.
278 * Added support for themeable functions in JavaScript.
279 – Refactored update.php to a generic batch API to be able to run time-consuming
280 operations in multiple subsequent HTTP requests.
281 – Installer:
282 * Themed the installer with the Garland theme.
283 * Added form to provide initial site information during installation.
284 * Added ability to provide extra installation steps programmatically.
285 * Made it possible to import interface translations at install time.
286 – Added the HTML corrector filter:
287 * Fixes faulty and chopped off HTML in postings.
288 * Tags are now automatically closed at the end of the teaser.
289 – Performance:
290 * Made it easier to conditionally load .include files and split up many core
291 modules.
292 * Added a JavaScript aggregator.
293 * Added block-level caching, improving performance for both authenticated
294 and anonymous users.
295 * Made Drupal work correctly when running behind a reverse proxy like
296 Squid or Pound.
297 – File handling improvements:
298 * Entries in the files table are now keyed to a user instead of a node.
299 * Added reusable validation functions to check for uploaded file sizes,
300 extensions, and image resolution.
301 * Added ability to create and remove temporary files during a cron job.
302 – Forum improvements:
303 * Any node type may now be posted in a forum.
304 – Taxonomy improvements:
305 * Descriptions for terms are now shown on taxonomy/term pages as well
306 as RSS feeds.
307 * Added versioning support to categories by associating them with node
308 revisions.
309 – Added support for OpenID.
310 – Added support for triggering configurable actions.
311 – Added the Update status module to automatically check for available updates
312 and warn sites if they are missing security updates or newer versions.
313 Sites deploying from CVS should use http://drupal.org/project/cvs_deploy.
314 Advanced settings provided by http://drupal.org/project/update_advanced.
315 – Upgraded the core JavaScript library to jQuery version 1.2.3.
316 – Added a new Schema API, which provides built-in support for core and
317 contributed modules to work with databases other than MySQL.
318 – Removed drupal.module. The functionality lives on as the Site network
319 contributed module (http://drupal.org/project/site_network).
320 – Removed old system updates. Updates from Drupal versions prior to 5.x will
321 require upgrading to 5.x before upgrading to 6.x.
322
323 Drupal 5.7, 2008-01-28
324 ———————-
325 – fixed the input format configuration page.
326 – fixed a variety of small bugs.
327
328 Drupal 5.6, 2008-01-10
329 ———————-
330 – fixed a variety of small bugs.
331 – fixed a security issue (Cross site request forgery), see SA-2008-005
332 – fixed a security issue (Cross site scripting, UTF8), see SA-2008-006
333 – fixed a security issue (Cross site scripting, register_globals), see SA-2008-007
334
335 Drupal 5.5, 2007-12-06
336 ———————-
337 – fixed missing missing brackets in a query in the user module.
338 – fixed taxonomy feed bug introduced by SA-2007-031
339
340 Drupal 5.4, 2007-12-05
341 ———————-
342 – fixed a variety of small bugs.
343 – fixed a security issue (SQL injection), see SA-2007-031
344
345 Drupal 5.3, 2007-10-17
346 ———————-
347 – fixed a variety of small bugs.
348 – fixed a security issue (HTTP response splitting), see SA-2007-024
349 – fixed a security issue (Arbitrary code execution via installer), see SA-2007-025
350 – fixed a security issue (Cross site scripting via uploads), see SA-2007-026
351 – fixed a security issue (User deletion cross site request forgery), see SA-2007-029
352 – fixed a security issue (API handling of unpublished comment), see SA-2007-030
353
354 Drupal 5.2, 2007-07-26
355 ———————-
356 – changed hook_link() $teaser argument to match documentation.
357 – fixed a variety of small bugs.
358 – fixed a security issue (cross-site request forgery), see SA-2007-017
359 – fixed a security issue (cross-site scripting), see SA-2007-018
360
361 Drupal 5.1, 2007-01-29
362 ———————-
363 – fixed security issue (code execution), see SA-2007-005
364 – fixed a variety of small bugs.
365
366 Drupal 5.0, 2007-01-15
367 ———————-
368 – Completely retooled the administration page
369 * /Admin now contains an administration page which may be themed
370 * Reorganised administration menu items by task and by module
371 * Added a status report page with detailed PHP/MySQL/Drupal information
372 – Added web-based installer which can:
373 * Check installation and run-time requirements
374 * Automatically generate the database configuration file
375 * Install pre-made ‘install profiles’ or distributions
376 * Import the database structure with automatic table prefixing
377 * Be localized
378 – Added new default Garland theme
379 – Added color module to change some themes’ color schemes
380 – Included the jQuery JavaScript library 1.0.4 and converted all core JavaScript to use it
381 – Introduced the ability to alter mail sent from system
382 – Module system:
383 * Added .info files for module meta-data
384 * Added support for module dependencies
385 * Improved module installation screen
386 * Moved core modules to their own directories
387 * Added support for module uninstalling
388 – Added support for different cache backends
389 – Added support for a generic “sites/all” directory.
390 – Usability:
391 * Added support for auto-complete forms (AJAX) to user profiles.
392 * Made it possible to instantly assign roles to newly created user accounts.
393 * Improved configurability of the contact forms.
394 * Reorganized the settings pages.
395 * Made it easy to investigate popular search terms.
396 * Added a ‘select all’ checkbox and a range select feature to administration tables.
397 * Simplified the ‘break’ tag to split teasers from body.
398 * Use proper capitalization for titles, menu items and operations.
399 – Integrated urlfilter.module into filter.module
400 – Block system:
401 * Extended the block visibility settings with a role specific setting.
402 * Made it possible to customize all block titles.
403 – Poll module:
404 * Optionally allow people to inspect all votes.
405 * Optionally allow people to cancel their vote.
406 – Distributed authentication:
407 * Added default server option.
408 – Added default robots.txt to control crawlers.
409 – Database API:
410 * Added db_table_exists().
411 – Blogapi module:
412 * ‘Blogapi new’ and ‘blogapi edit’ nodeapi operations.
413 – User module:
414 * Added hook_profile_alter().
415 * E-mail verification is made optional.
416 * Added mass editing and filtering on admin/user/user.
417 – PHP Template engine:
418 * Add the ability to look for a series of suggested templates.
419 * Look for page templates based upon the path.
420 * Look for block templates based upon the region, module, and delta.
421 – Content system:
422 * Made it easier for node access modules to work well with each other.
423 * Added configurable content types.
424 * Changed node rendering to work with structured arrays.
425 – Performance:
426 * Improved session handling: reduces database overhead.
427 * Improved access checking: reduces database overhead.
428 * Made it possible to do memcached based session management.
429 * Omit sidebars when serving a ‘404 – Page not found’: saves CPU cycles and bandwidth.
430 * Added an ‘aggressive’ caching policy.
431 * Added a CSS aggregator and compressor (up to 40% faster page loads).
432 – Removed the archive module.
433 – Upgrade system:
434 * Created space for update branches.
435 – Forms API:
436 * Made it possible to programmatically submit forms.
437 * Improved api for multistep forms.
438 – Theme system:
439 * Split up and removed drupal.css.
440 * Added nested lists generation.
441 * Added a self-clearing block class.
442
443 Drupal 4.7.11, 2008-01-10
444 ————————-
445 – fixed a security issue (Cross site request forgery), see SA-2008-005
446 – fixed a security issue (Cross site scripting, UTF8), see SA-2008-006
447 – fixed a security issue (Cross site scripting, register_globals), see SA-2008-007
448
449 Drupal 4.7.10, 2007-12-06
450 ————————-
451 – fixed taxonomy feed bug introduced by SA-2007-031
452
453 Drupal 4.7.9, 2007-12-05
454 ————————
455 – fixed a security issue (SQL injection), see SA-2007-031
456
457 Drupal 4.7.8, 2007-10-17
458 ———————-
459 – fixed a security issue (HTTP response splitting), see SA-2007-024
460 – fixed a security issue (Cross site scripting via uploads), see SA-2007-026
461 – fixed a security issue (API handling of unpublished comment), see SA-2007-030
462
463 Drupal 4.7.7, 2007-07-26
464 ————————
465 – fixed security issue (XSS), see SA-2007-018
466
467 Drupal 4.7.6, 2007-01-29
468 ————————
469 – fixed security issue (code execution), see SA-2007-005
470
471 Drupal 4.7.5, 2007-01-05
472 ————————
473 – Fixed security issue (XSS), see SA-2007-001
474 – Fixed security issue (DoS), see SA-2007-002
475
476 Drupal 4.7.4, 2006-10-18
477 ————————
478 – Fixed security issue (XSS), see SA-2006-024
479 – Fixed security issue (CSRF), see SA-2006-025
480 – Fixed security issue (Form action attribute injection), see SA-2006-026
481
482 Drupal 4.7.3, 2006-08-02
483 ————————
484 – Fixed security issue (XSS), see SA-2006-011
485
486 Drupal 4.7.2, 2006-06-01
487 ————————
488 – Fixed critical upload issue, see SA-2006-007
489 – Fixed taxonomy XSS issue, see SA-2006-008
490 – Fixed a variety of small bugs.
491
492 Drupal 4.7.1, 2006-05-24
493 ————————
494 – Fixed critical SQL issue, see SA-2006-005
495 – Fixed a serious upgrade related bug.
496 – Fixed a variety of small bugs.
497
498 Drupal 4.7.0, 2006-05-01
499 ————————
500 – Added free tagging support.
501 – Added a site-wide contact form.
502 – Theme system:
503 * Added the PHPTemplate theme engine and removed the Xtemplate engine.
504 * Converted the bluemarine theme from XTemplate to PHPTemplate.
505 * Converted the pushbutton theme from XTemplate to PHPTemplate.
506 – Usability:
507 * Reworked the ‘request new password’ functionality.
508 * Reworked the node and comment edit forms.
509 * Made it easy to add nodes to the navigation menu.
510 * Added site ‘offline for maintenance’ feature.
511 * Added support for auto-complete forms (AJAX).
512 * Added support for collapsible page sections (JS).
513 * Added support for resizable text fields (JS).
514 * Improved file upload functionality (AJAX).
515 * Reorganized some settings pages.
516 * Added friendly database error screens.
517 * Improved styling of update.php.
518 – Refactored the forms API.
519 * Made it possible to alter, extend or theme forms.
520 – Comment system:
521 * Added support for “mass comment operations” to ease repetitive tasks.
522 * Comment moderation has been removed.
523 – Node system:
524 * Reworked the revision functionality.
525 * Removed the bookmarklet code. Third-party modules can now handle
526 This.
527 – Upgrade system:
528 * Allows contributed modules to plug into the upgrade system.
529 – Profiles:
530 * Added a block to display author information along with posts.
531 * Added support for private profile fields.
532 – Statistics module:
533 * Added the ability to track page generation times.
534 * Made it possible to block certain IPs/hostnames.
535 – Block system:
536 * Added support for theme-specific block regions.
537 – Syndication:
538 * Made the aggregator module parse Atom feeds.
539 * Made the aggregator generate RSS feeds.
540 * Added RSS feed settings.
541 – XML-RPC:
542 * Replaced the XML-RPC library by a better one.
543 – Performance:
544 * Added ‘loose caching’ option for high-traffic sites.
545 * Improved performance of path aliasing.
546 * Added the ability to track page generation times.
547 – Internationalization:
548 * Improved Unicode string handling API.
549 * Added support for PHP’s multibyte string module.
550 – Added support for PHP5’s ‘mysqli’ extension.
551 – Search module:
552 * Made indexer smarter and more robust.
553 * Added advanced search operators (e.g. phrase, node type, …).
554 * Added customizable result ranking.
555 – PostgreSQL support:
556 * Removed dependency on PL/pgSQL procedural language.
557 – Menu system:
558 * Added support for external URLs.
559 – Queue module:
560 * Removed from core.
561 – HTTP handling:
562 * Added support for a tolerant Base URL.
563 * Output URIs relative to the root, without a base tag.
564
565 Drupal 4.6.11, 2007-01-05
566 ————————-
567 – Fixed security issue (XSS), see SA-2007-001
568 – Fixed security issue (DoS), see SA-2007-002
569
570 Drupal 4.6.10, 2006-10-18
571 ————————
572 – Fixed security issue (XSS), see SA-2006-024
573 – Fixed security issue (CSRF), see SA-2006-025
574 – Fixed security issue (Form action attribute injection), see SA-2006-026
575
576 Drupal 4.6.9, 2006-08-02
577 ————————
578 – Fixed security issue (XSS), see SA-2006-011
579
580 Drupal 4.6.8, 2006-06-01
581 ————————
582 – Fixed critical upload issue, see SA-2006-007
583 – Fixed taxonomy XSS issue, see SA-2006-008
584
585 Drupal 4.6.7, 2006-05-24
586 ————————
587 – Fixed critical SQL issue, see SA-2006-005
588
589 Drupal 4.6.6, 2006-03-13
590 ————————
591 – Fixed bugs, including 4 security vulnerabilities.
592
593 Drupal 4.6.5, 2005-12-12
594 ————————
595 – Fixed bugs: no critical bugs were identified.
596
597 Drupal 4.6.4, 2005-11-30
598 ————————
599 – Fixed bugs, including 3 security vulnerabilities.
600
601 Drupal 4.6.3, 2005-08-15
602 ————————
603 – Fixed bugs, including a critical “arbitrary PHP code execution” bug.
604
605 Drupal 4.6.2, 2005-06-29
606 ————————
607 – Fixed bugs, including two critical “arbitrary PHP code execution” bugs.
608
609 Drupal 4.6.1, 2005-06-01
610 ————————
611 – Fixed bugs, including a critical input validation bug.
612
613 Drupal 4.6.0, 2005-04-15
614 ————————
615 – PHP5 compliance
616 – Search:
617 * Added UTF-8 support to make it work with all languages.
618 * Improved search indexing algorithm.
619 * Improved search output.
620 * Impose a throttle on indexing of large sites.
621 * Added search block.
622 – Syndication:
623 * Made the ping module ping pingomatic.com which, in turn, will ping all the major ping services.
624 * Made Drupal generate RSS 2.0 feeds.
625 * Made RSS feeds extensible.
626 * Added categories to RSS feeds.
627 * Added enclosures to RSS feeds.
628 – Flood control mechanism:
629 * Added a mechanism to throttle certain operations.
630 – Usability:
631 * Refactored the block configuration pages.
632 * Refactored the statistics pages.
633 * Refactored the watchdog pages.
634 * Refactored the throttle module configuration.
635 * Refactored the access rules page.
636 * Refactored the content administration page.
637 * Introduced forum configuration pages.
638 * Added a ‘add child page’ link to book pages.
639 – Contact module:
640 * Added a simple contact module that allows users to contact each other using e-mail.
641 – Multi-site configuration:
642 * Made it possible to run multiple sites from a single code base.
643 – Added an image API: enables better image handling.
644 – Block system:
645 * Extended the block visibility settings.
646 – Theme system:
647 * Added new theme functions.
648 – Database backend:
649 * The PEAR database backend is no longer supported.
650 – Performance:
651 * Improved performance of the forum topics block.
652 * Improved performance of the tracker module.
653 * Improved performance of the node pages.
654 – Documentation:
655 * Improved and extended PHPDoc/Doxygen comments.
656
657 Drupal 4.5.8, 2006-03-13
658 ————————
659 – Fixed bugs, including 3 security vulnerabilities.
660
661 Drupal 4.5.7, 2005-12-12
662 ————————
663 – Fixed bugs: no critical bugs were identified.
664
665 Drupal 4.5.6, 2005-11-30
666 ————————
667 – Fixed bugs, including 3 security vulnerabilities.
668
669 Drupal 4.5.5, 2005-08-15
670 ————————
671 – Fixed bugs, including a critical “arbitrary PHP code execution” bug.
672
673 Drupal 4.5.4, 2005-06-29
674 ————————
675 – Fixed bugs, including two critical “arbitrary PHP code execution” bugs.
676
677 Drupal 4.5.3, 2005-06-01
678 ————————
679 – Fixed bugs, including a critical input validation bug.
680
681 Drupal 4.5.2, 2005-01-15
682 ————————
683 – Fixed bugs: a cross-site scripting (XSS) vulnerability has been fixed.
684
685 Drupal 4.5.1, 2004-12-01
686 ————————
687 – Fixed bugs: no critical bugs were identified.
688
689 Drupal 4.5.0, 2004-10-18
690 ————————
691 – Navigation:
692 * Made it possible to add, delete, rename and move menu items.
693 * Introduced tabs and subtabs for local tasks.
694 * Reorganized the navigation menus.
695 – User management:
696 * Added support for multiple roles per user.
697 * Made it possible to add custom profile fields.
698 * Made it possible to browse user profiles by field.
699 – Node system:
700 * Added support for node-level permissions.
701 – Comment module:
702 * Made it possible to leave contact information without having to register.
703 – Upload module:
704 * Added support for uploading documents (includes images).
705 – Forum module:
706 * Added support for sticky forum topics.
707 * Made it possible to track forum topics.
708 – Syndication:
709 * Added support for RSS ping-notifications of http://technorati.com/.
710 * Refactored the categorization of syndicated news items.
711 * Added an URL alias for ‘rss.xml’.
712 * Improved date parsing.
713 – Database backend:
714 * Added support for multiple database connections.
715 * The PostgreSQL backend does no longer require PEAR.
716 – Theme system:
717 * Changed all GIFs to PNGs.
718 * Reorganised the handling of themes, template engines, templates and styles.
719 * Unified and extended the available theme settings.
720 * Added theme screenshots.
721 – Blocks:
722 * Added ‘recent comments’ block.
723 * Added ‘categories’ block.
724 – Blogger API:
725 * Added support for auto-discovery of blogger API via RSD.
726 – Performance:
727 * Added support for sending gzip compressed pages.
728 * Improved performance of the forum module.
729 – Accessibility:
730 * Improved the accessibility of the archive module’s calendar.
731 * Improved form handling and error reporting.
732 * Added HTTP redirects to prevent submitting twice when refreshing right after a form submission.
733 – Refactored 403 (forbidden) handling and added support for custom 403 pages.
734 – Documentation:
735 * Added PHPDoc/Doxygen comments.
736 – Filter system:
737 * Added support for using multiple input formats on the site
738 * Expanded the embedded PHP-code feature so it can be used everywhere
739 * Added support for role-dependant filtering, through input formats
740 – UI translation:
741 * Managing translations is now completely done through the administration interface
742 * Added support for importing/exporting gettext .po files
743
744 Drupal 4.4.3, 2005-06-01
745 ————————
746 – Fixed bugs, including a critical input validation bug.
747
748 Drupal 4.4.2, 2004-07-04
749 ————————
750 – Fixed bugs: no critical bugs were identified.
751
752 Drupal 4.4.1, 2004-05-01
753 ————————
754 – Fixed bugs: no critical bugs were identified.
755
756 Drupal 4.4.0, 2004-04-01
757 ————————
758 – Added support for the MetaWeblog API and MovableType extensions.
759 – Added a file API: enables better document management.
760 – Improved the watchdog and search module to log search keys.
761 – News aggregator:
762 * Added support for conditional GET.
763 * Added OPML feed subscription list.
764 * Added support for <image>, <pubDate>, <dc:date>, <dcterms:created>, <dcterms:issued> and <dcterms:modified>.
765 – Comment module:
766 * Made it possible to disable the “comment viewing controls”.
767 – Performance:
768 * Improved module loading when serving cached pages.
769 * Made it possible to automatically disable modules when under heavy load.
770 * Made it possible to automatically disable blocks when under heavy load.
771 * Improved performance and memory footprint of the locale module.
772 – Theme system:
773 * Made all theme functions start with ‘theme_’.
774 * Made all theme functions return their output.
775 * Migrated away from using the BaseTheme class.
776 * Added many new theme functions and refactored existing theme functions.
777 * Added avatar support to ‘Xtemplate’.
778 * Replaced theme ‘UnConeD’ by ‘Chameleon’.
779 * Replaced theme ‘Marvin’ by ‘Pushbutton’.
780 – Usability:
781 * Added breadcrumb navigation to all pages.
782 * Made it possible to add context-sensitive help to all pages.
783 * Replaced drop-down menus by radio buttons where appropriate.
784 * Removed the ‘magic_quotes_gpc = 0’ requirement.
785 * Added a ‘book navigation’ block.
786 – Accessibility:
787 * Made themes degrade gracefully in absence of CSS.
788 * Grouped form elements using ‘<fieldset>’ and ‘<legend>’ tags.
789 * Added ‘<label>’ tags to form elements.
790 – Refactored 404 (file not found) handling and added support for custom 404 pages.
791 – Improved the filter system to prevent conflicts between filters:
792 * Made it possible to change the order in which filters are applied.
793 – Documentation:
794 * Added PHPDoc/Doxygen comments.
795
796 Drupal 4.3.2, 2004-01-01
797 ————————
798 – Fixed bugs: no critical bugs were identified.
799
800 Drupal 4.3.1, 2003-12-01
801 ————————
802 – Fixed bugs: no critical bugs were identified.
803
804 Drupal 4.3.0, 2003-11-01
805 ————————
806 – Added support for configurable URLs.
807 – Added support for sortable table columns.
808 – Database backend:
809 * Added support for selective database table prefixing.
810 – Performance:
811 * Optimized many SQL queries for speed by converting left joins to inner joins.
812 – Comment module:
813 * Rewrote the comment housekeeping code to be much more efficient and scalable.
814 * Changed the comment module to use the standard pager.
815 – User module:
816 * Added support for multiple sessions per user.
817 * Added support for anonymous user sessions.
818 – Forum module:
819 * Improved the forum views and the themability thereof.
820 – Book module:
821 * Improved integration of non-book nodes in the book outline.
822 – Usability:
823 * Added support for “mass node operations” to ease repetitive tasks.
824 * Added support for breadcrumb navigation to several modules’ user pages.
825 * Integrated the administration pages with the normal user pages.
826
827 Drupal 4.2.0, 2003-08-01
828 ————————
829 – Added support for clean URLs.
830 – Added textarea hook and support for onload attributes: enables integration of WYSIWYG editors.
831 – Rewrote the RSS/RDF parser:
832 * It will now use PHP’s built-in XML parser to parse news feeds.
833 – Rewrote the administration pages:
834 * Improved the navigational elements and added breadcrumb navigation.
835 * Improved the look and feel.
836 * Added context-sensitive help.
837 – Database backend:
838 * Fixed numerous SQL queries to make Drupal ANSI compliant.
839 * Added MSSQL database scheme.
840 – Search module:
841 * Changed the search module to use implicit AND’ing instead of implicit OR’ing.
842 – Node system:
843 * Replaced the “post content” permission by more fine-grained permissions.
844 * Improved content submission:
845 + Improved teasers: teasers are now optional, teaser length can be configured, teaser and body are edited in a single textarea, users will no longer be bothered with teasers when the post is too short for one.
846 + Added the ability to preview both the short and the full version of your posts.
847 * Extended the node API which allows for better integration.
848 * Added default node settings to control the behavior for promotion, moderation and other options.
849 – Themes:
850 * Replaced theme “Goofy” by “Xtemplate”, a template driven theme.
851 – Removed the ‘register_globals = on’ requirement.
852 – Added better installation instructions.
853
854 Drupal 4.1.0, 2003-02-01
855 ————————
856 – Collaboratively revised and expanded the Drupal documentation.
857 – Rewrote comment.module:
858 * Reintroduced comment rating/moderation.
859 * Added support for comment paging.
860 * Performance improvements: improved comment caching, faster SQL queries, etc.
861 – Rewrote block.module:
862 * Performance improvements: blocks are no longer rendered when not displayed.
863 – Rewrote forum.module:
864 * Added a lot of features one can find in stand-alone forum software including but not limited to support for topic paging, added support for icons, rewrote the statistics module, etc.
865 – Rewrote statistics.module:
866 * Collects access counts for each node, referrer logs, number of users/guests.
867 * Export blocks displaying top viewed nodes over last 24 hour period, top viewed nodes over all time, last nodes viewed, how many users/guest online.
868 – Added throttle.module:
869 * Auto-throttle congestion control mechanism: Drupal can adapt itself based on the server load.
870 – Added profile.module:
871 * Enables to extend the user and registration page.
872 – Added pager support to the main page.
873 – Replaced weblogs.module by ping.module:
874 * Added support for normal and RSS notifications of http://blo.gs/.
875 * Added support for RSS ping-notifications of http://weblogs.com/.
876 – Removed the rating module
877 – Themes:
878 * Removed a significant portion of hard-coded mark-up.
879
880 Drupal 4.0.0, 2002-06-15
881 ————————
882 – Added tracker.module:
883 * Replaces the previous “your [site]” links (recent comments and nodes).
884 – Added weblogs.module:
885 * This will ping weblogs.com when new content is promoted.
886 – Added taxonomy module which replaces the meta module.
887 * Supports relations, hierarchies and synonyms.
888 – Added a caching system:
889 * Speeds up pages for anonymous users and reduces system load.
890 – Added support for external SMTP libraries.
891 – Added an archive extension to the calendar.
892 – Added support for the Blogger API.
893 – Themes:
894 * Cleaned up the theme system.
895 * Moved themes that are not maintained to contributions CVS repository.
896 – Database backend:
897 * Changed to PEAR database abstraction layer.
898 * Using ANSI SQL queries to be more portable.
899 – Rewrote the user system:
900 * Added support for Drupal authentication through XML-RPC and through a Jabber server.
901 * Added support for modules to add more user data.
902 * Users may delete their own account.
903 * Added who’s new and who’s online blocks.
904 – Changed block system:
905 * Various hard coded blocks are now dynamic.
906 * Blocks can now be enabled and/or be set by the user.
907 * Blocks can be set to only show up on some pages.
908 * Merged box module with block module.
909 – Node system:
910 * Blogs can be updated.
911 * Teasers (abstracts) on all node types.
912 * Improved error checking.
913 * Content versioning support.
914 * Usability improvements.
915 – Improved book module to support text, HTML and PHP pages.
916 – Improved comment module to mark new comments.
917 – Added a general outliner which will let any node type be linked to a book.
918 – Added an update script that lets you upgrade from previous releases or on a day to day basis when using the development tree.
919 – Search module:
920 * Improved the search system by making it context sensitive.
921 * Added indexing.
922 – Various updates:
923 * Changed output to valid XHTML.
924 * Improved multiple sites using the same Drupal database support.
925 * Added support for session IDs in URLs instead of cookies.
926 * Made the type of content on the front page configurable.
927 * Made each cloud site have its own settings.
928 * Modules and themes can now be enabled/disabled using the administration pages.
929 * Added URL abstraction for links.
930 * Usability changes (renamed links, better UI, etc).
931 – Collaboratively revised and expanded the Drupal documentation.
932
933 Drupal 3.0.1, 2001-10-15
934 ————————
935 – Various updates:
936 * Added missing translations
937 * Updated the themes: tidied up some HTML code and added new Drupal logos.
938
939 Drupal 3.0.0, 2001-09-15
940 ————————
941 – Major overhaul of the entire underlying design:
942 * Everything is based on nodes: nodes are a conceptual “black box” to couple and manage different types of content and that promotes reusing existing code, thus reducing the complexity and size of Drupal as well as improving long-term stability.
943 – Rewrote submission/moderation queue and renamed it to queue.module.
944 – Removed FAQ and documentation module and merged them into a “book module”.
945 – Removed ban module and integrated it into account.module as “access control”:
946 * Access control is based on much more powerful regular expressions (regex) now rather than on MySQL pattern matching.
947 – Rewrote watchdog and submission throttle:
948 * Improved watchdog messages and added watchdog filter.
949 – Rewrote headline code and renamed it to import.module and export.module:
950 * Added various improvements, including a better parser, bundles and better control over individual feeds.
951 – Rewrote section code and renamed it to meta.module:
952 * Supports unlimited amount of nested topics. Topics can be nested to create a multi-level hierarchy.
953 – Rewrote configuration file resolving:
954 * Drupal tries to locate a configuration file that matches your domain name or uses conf.php if the former failed. Note also that the configuration files got renamed from .conf to .php for security’s sake on mal-configured Drupal sites.
955 – Added caching support which makes Drupal extremely scalable.
956 – Added access.module:
957 * Allows you to set up ‘roles’ (groups) and to bind a set of permissions to each group.
958 – Added blog.module.
959 – Added poll.module.
960 – Added system.module:
961 * Moved most of the configuration options from hostname.conf to the new administration section.
962 * Added support for custom “filters”.
963 – Added statistics.module
964 – Added moderate.module:
965 * Allows to assign users editorial/moderator rights to certain nodes or topics.
966 – Added page.module:
967 * Allows creation of static (and dynamic) pages through the administration interface.
968 – Added help.module:
969 * Groups all available module documentation on a single page.
970 – Added forum.module:
971 * Added an integrated forum.
972 – Added cvs.module and cvs-to-sql.pl:
973 * Allows to display and mail CVS log messages as daily digests.
974 – Added book.module:
975 * Allows collaborative handbook writing: primary used for Drupal documentation.
976 – Removed cron.module and integrated it into conf.module.
977 – Removed module.module as it was no longer needed.
978 – Various updates:
979 * Added “auto-post new submissions” feature versus “moderate new submissions”.
980 * Introduced links/Drupal tags: [[link]]
981 * Added preview functionality when submitting new content (such as a story) from the administration pages.
982 * Made the administration section only show those links a user has access to.
983 * Made all modules use specific form_* functions to guarantee a rock-solid forms and more consistent layout.
984 * Improved scheduler:
985 + Content can be scheduled to be ‘posted’, ‘queued’ and ‘hidden’.
986 * Improved account module:
987 + Added “access control” to allow/deny certain usernames/e-mail addresses/hostnames.
988 * Improved locale module:
989 + Added new overview to easy the translation process.
990 * Improved comment module:
991 + Made it possible to permanently delete comments.
992 * Improved rating module
993 * Improved story module:
994 + Added preview functionality for administrators.
995 + Made it possible to permanently delete stories.
996 * Improved themes:
997 + W3C validation on a best effort basis.
998 + Removed $theme->control() from themes.
999 + Added theme “goofy”.
1000 – Collaboratively revised and expanded the Drupal documentation.
1001
1002 Drupal 2.0.0, 2001-03-15
1003 ————————
1004 – Rewrote the comment/discussion code:
1005 * Comment navigation should be less confusing now.
1006 * Additional/alternative display and order methods have been added.
1007 * Modules can be extended with a “comment system”: modules can embed the existing comment system without having to write their own, duplicate comment system.
1008 – Added sections and section manager:
1009 * Story sections can be maintained from the administration pages.
1010 * Story sections make the open submission more adaptive in that you can set individual post, dump and expiration thresholds for each section according to the story type and urgency level: stories in certain sections do not “expire” and might stay interesting and active as time passes by, whereas news-related stories are only considered “hot” over a short period of time.
1011 – Multiple vhosts + multiple directories:
1012 * You can set up multiple Drupal sites on top of the same physical source tree either by using vhosts or sub-directories.
1013 – Added “user ratings” similar to SlashCode’s Karma or Scoop’s Mojo:
1014 * All rating logic is packed into a module to ease experimenting with different rating heuristics/algorithms.
1015 – Added “search infrastructure”:
1016 * Improved search page and integrated search functionality in the administration pages.
1017 – Added translation / localization / internationalization support:
1018 * Because many people would love to see their website showing a lot less of English, and far more of their own language, Drupal provides a framework to set up a multi-lingual website or to overwrite the default English text in English.
1019 – Added fine-grained user permission (or group) system:
1020 * Users can be granted access to specific administration sections. Example: a FAQ maintainer can be given access to maintain the FAQ and translators can be given access to the translation pages.
1021 – Added FAQ module
1022 – Changed the “open submission queue” into a (optional) module.
1023 – Various updates:
1024 * Improved account module:
1025 + User accounts can be deleted.
1026 + Added fine-grained permission support.
1027 * Improved block module
1028 * Improved diary module:
1029 + Diary entries can be deleted
1030 * Improved headline module:
1031 + Improved parser to support more “generic” RDF/RSS/XML backend.
1032 * Improved module module
1033 * Improved watchdog module
1034 * Improved database abstraction layer
1035 * Improved themes:
1036 + W3C validation on a best effort basis
1037 + Added theme “example” (alias “Stone Age”)
1038 * Added new scripts to directory “scripts”
1039 * Added directory “misc”
1040 * Added CREDITS file
2010
05/13
CATEGORY
Web Class
Leave a comment

Honesty & Integrity in Webdesign

The definition of Integrity is 1. Steadfast adherence to a strict moral or ethical code.  (according to http://www.thefreedictionary.com.)  When it comes to being a web designer this is a code that we have to live by, both for ourselves and for our clients.  When we are consulting with a client we need to be honest and upfront about what we can do and what the client can expect from us on that particular project.  Things such as: Deadlines/Completion date, functionality, S.E.O., maintenance for the site, ETC…   When we live by strict codes, our tract record will show our integrity and that we stand behind what we say we are going to do.

I recently started doing some redesigns for some Bed and Breakfasts in Oklahoma that were designed by a freelancer that had grown to big for what he could offer.  When he first started, he offered to design and maintain the site for the lifetime that he was the webmaster of the site.  He started about 8 years ago and now has over 60 sites that he is trying to maintain for “free” while still trying to develop new sites so he can pay the bills.  While his integrity is good, and had very good intentions at the time when he was starting up, he now is not able to keep up with what he said he was going to do.  A part that goes along with honesty is being honest with yourself and your clients and offer a optional solution for maintaining their site as the times have changed.

2010
04/30
CATEGORY
Web Class
Leave a comment

Anger Management in the Web Designing World

“Anger Management…..hmmmm…..  What is that?  I would have never thought about anger being something that you deal with in web design.”

Ok, now to the real world.  I could start rambling off many things that could and would have the potential to make you or I angry in our day to day schedule as a web designer.  From the client who only wants one thing and nothing else will do, to problems with that one character not right in the code that take you the whole afternoon trying to find.

I have learned through many other areas in life that management is not only controlling the event, (anger) at the time it occurs, but also planning for the inevitable occasion that you know is going to happen.  If you know that there is a possibility that when you are coding a web page, and all of a sudden the program crashes and you loose everything that you have worked on for that day, a part of managing that situation is to take the extra steps to save your page many times while you are working on it.  You take into account what is going to make you angry, and set up the “Air Defense” plan to go into action when you reach that critical moment.

2010
03/31
CATEGORY
Web Class
Leave a comment

New School Website!!!!

Come take a look at what
CaptureTheScene.Tv has to offer! New School website
Check it OUT!!! http://inetstudent1.francistuttle.com/mh0867620/index.html

2010
03/21
CATEGORY
Web Class
Leave a comment

Recent entry

Archive

Category