Showing posts sorted by relevance for query drupal. Sort by date Show all posts
Showing posts sorted by relevance for query drupal. Sort by date Show all posts

Monday, November 17, 2008

Drupal In Theory and Practice

I continue to poke around the Web, hoping I'll come upon the Drupal resource that will make it all clear. (That does happen to me sometimes.) I'm actually making a little sense of it, between experimenting with an installation on localhost and reading more manuals.

Drupal.org and many other Web sites have excellent documentation on how to accomplish specific tasks, but the place where I'm hung up is approaching my planned content, breaking it up into content types, and determining how to organize and display it. The documentation skips over this theoretical aspect, assuring us that we can do anything we can imagine, and "don't be intimidated bye the steep learning curve." (I'm really getting annoyed with that "steep learning curve" metaphor--it's so ubiquitous that most of the posters on the drupal.org forums feel obligated to slip it into their questions and answers.)

Here are some resources that have given me some inkling of how to classify and organize my content and begin to plan a web presence of the Pocahontas County local history project.

Friday, January 02, 2009

Getting a Handle on Drupal Modules

I'm still flapping around with Drupal. (I'm currently experimenting on my Spice Ridge site, because there are things you just can't test on localhost.) The Drupal book I bought was necessary but not sufficient for me to get started. It let me know what to work with first--Drupal modules. Intuitively, I thought the first thing would be to create content, then work out how to display it. As it turns out, you need to get a grip on the Drupal modules before you bother with content or appearance (themes). While Drupal.org has loads of documentation, some of it is helpful, some of it is inscrutable. Here is some module advice I've found helpful, comforting, and/or inspiring.

Saturday, November 15, 2008

Lost In the Archives--Using Drupal

I've been test-driving content management systems, both general-purpose Web site packages and archive/collections management tools. I've decided I really like Archon, The Simple Archival Information System. It works on Mac, *nix, and Windows, its easy to install, and it can work as an archive manager, a digital collections manager, and an online exhibit manager. The other tools I've reviewed and tried out don't suit my purposes, or else, like Omeka, look promising, but are not quite ready for prime-time.

The "regular" content management systems for Web development are more problematic for me. I've narrowed my choice to a couple of systems I've installed and test-driven locally. Wordpress is easy to get started with, but it seems to turn everything I try to do into a blog with a few static pages on the side. I know it can do much more, but I'm not sure it's a good use of my time to bend it to my will. Drupal will do everything I can imagine, but I'm getting lost in the nine million alternative modules, themes, and add-ons. I need to read about what other people have done on projects similar to mine. With that in mind, I've assembled these links:

Using Drupal

Saturday, November 29, 2008

Buying a Drupal Book

I try to avoid buying computer books, partly because I'm cheap, partly because I have limited shelf space, and partly because free online resources are often better. However, I've been having trouble getting started with Drupal--I know how to make it work, but I don't really "get" what I need to know to start working on a real Web site. (By the way, my latest set of helpful Drupal links is listed below.)

There's useful information here, but not what I'd been hoping to find. That's why I ordered Building Powerful and Robust Websites with Drupal 6: Build your own professional blog, forum, portal or community website with Drupal 6 by David Mercer. It came in the mail yesterday, and I started working my way through it this morning. Even though it was quite pricey, I'm pleased to have it. The author walks you through developing and implementing a sample Web site. The drupal.org site tells you how to do hundreds of different things, but David Mercer tells you why you want to do a few of the more basic things, and what things you need to learn about first. It was this orientation that I've been missing.

Sunday, January 18, 2009

My Quest to Enable Clean URLs

I've spent the weekend with a series of computer problems I didn't expect. (I never expect computer problems; I don't know why not.) Saturday seemed like the right time to install Drupal in my root directory on Spiceridge.com. It was working well on localhost, and in a subdirectory on Spiceridge.com, so I thought it was ready for prime time. (Silly, heedless me!) Turns out it wasn't, and something untoward happened to my old Web page backups. Eventually, I got Spiceridge.com back to its accustomed state of neglect. (That problem involved a lot of futile chmod activity.)

Meanwhile, the Drupal problem was that I couldn't enable "Clean URLs" when I installed Drupal in the root directory. "Clean URLs" rewrites dynamically generated URLs so they don't have the little "?q=" thing that tells us the page was generated from a php script, and tells search engines it's not a "real" web page, so don't index it. If you want people to find you using search engines, you really want "Clean URLs."

OK, the Clean URLs manual page from drupal.org tells us there are two reasons Drupal installation might fail to enable "Clean URLs:" the Apache server doesn't have mod_rewrite enabled, and/or the .htaccess file in the root directory is missing or wrongly constructed. Now, because Clean URLs worked in the subdirectory, I knew that my provider's server had the rewrite_module enabled, but I checked anyway:

[rclayton@w6 ~]$ apachectl -M
httpd: Could not reliably determine the server's fully qualified domain name, using w6.meer.net for ServerName
Loaded Modules:
 core_module (static)
 mpm_prefork_module (static)

...lotsa modules...

 imagemap_module (shared)
 actions_module (shared)
 speling_module (shared)
 userdir_module (shared)
 alias_module (shared)
 rewrite_module (shared)
Syntax OK
[rclayton@w6 ~]$

There it is, at the end. OK, I read through the .htaccess file from start to finish, and I tried commenting and uncommenting a couple of potential lines that might make a difference. They didn't. I spent some time Googling for other people's observations on this phenomenon; those who solved it used one of these two solutions.

Sigh. At last, I came across a bug report: Clean URLs test fails with JS enabled; Passes with JS disabled and clicking 'Test Clean URLs' link. This is not for Drupal 6, which I'm running, but one commenter observes:

For what it's worth, all my clean url problems were solved by deleting an errant "Admin" folder in my root directory (a remnant of some old installation of something or other, but no longer needed).

Bingo! My service provider uses yourwebsite.com/admin to send us to our stats, phpmyadmin, and other utilities. Since Drupal uses yourwebsite.com/admin for many things including "Clean URL's," it's not ever going to work. The bug report closes with:

The clean urls test uses an url like "http://yoursite/admin/clean-url-test" so if you have an "admin" folder in your drupal install, that path will not be handled by Drupal. Going to mark this as 'by design.'

So, it's up to me to find a solution. There are many possibilities, and I'm still reading all about them. I could put my Drupal installation at spiceridge.com/drupal/ and alias or redirect spiceridge.com to the drupal directory....Well, it's a lot to read about. Here are some resources that seemed helpful.

Saturday, February 27, 2010

Getting Ready to Break My Websites

I've been a bad Drupal website administrator. I have ignored update after update on my own site Spice Ridge and Pocahontas County History. They are minor, fiddly updates, but I've put them off again and again. However, now something is broken on one of these sites. It doesn't have to do with Drupal, but I'm going to have to go into repair mode anyway, so I guess I might as well update Drupal now. Why not break everything all at once?

First, I need local installations to test stuff before I start breaking Websites out in public. My original local installations were vaporized when my last Linux box fried its cpu and hard drive in April of 2009, and because I messed up my Debian Lenny and switched to Kubuntu, I need to set up Apache2, PHP5, MySql, and PHPMyAdmin from scratch in order to rassle with Drupal. It turns out my collection of links on setting up a Debian server from my initial Drupal adventure is still up-to-date. This process goes surprisingly quickly this time.

The next step is to download the Drupal installations (and the broken Archon CMS as well). I'll just ftp the files to my localhost directories, but I also need to recreate the MySQL databases locally, and I don't remember how to do that.

  • How to backup your Mysql database with phpMyAdmin. This worked like a charm, but phpMyAdmin balked at importing the .sql file into my local database--it said my file was too large. Well, I was once an old hand at command-line sql interactions, but I couldn't remember syntax....
  • How to restore MySQL database from sql dump file? gave me the directions I needed:
    rebecca@hecate:/var/www/spiceridge$ mysql -u root -p spiceridge < spicerid_dp.sql
    Enter password:
    rebecca@hecate:/var/www/spiceridge$
    
    This creates all the tables I needed, as well as populating them. Pretty slick.

In the process of doing all this, I discover that my hosting service's new setup has a nifty, easy-to-use backup utility that handles files, scripts and databases in a single step, eliminating the time-consuming process I just completed for my Spice Ridge website. Oh well, it'll really help when I start on the local history site.

Here's some stuff I found about Drupal updates and back-ups. I haven't tried any of this yet, but I'm saving it here so I don't misplace it.

  • Upgrading from previous versions
  • HowTo: Updating Drupal 6.x to newer minor version
  • Drupal Backup and Migrate Module

    Backup and Migrate simplifies the task of backing up and restoring your Drupal database or copying your database from one Drupal site to another. It supports gzip, bzip and zip compression as well as automatic scheduled backups.

    With Backup and Migrate you can dump some or all of your database tables to a file download or save to a file on the server, and to restore from an uploaded or previously saved database dump. You can chose which tables and what data to backup and cache data is excluded by default.

Tuesday, January 06, 2009

Moving from Blogger to Drupal

I'm actually pretty happy with Blogger, but because I'm learning about Drupal for a work project, I've been experimenting with my blog content in Drupal. Who knows--if I really like it, I might "convert." Here are links on how to import bloggish materials into Drupal.

Wednesday, January 07, 2009

Drupal Views and Taxonomy

I'm learning about Drupal modules, and what sorts of things you can do with a Drupal website. Everything I read tells me the "Views" modules are sine qua non, but that's where they stop. I'm trying to find out why the views modules are so useful, and what I might be able to do with them.

Same goes for Drupal's "Taxonomy." Drupal tutorials say it's wonderful, then they explain what taxonomy means, and then they stop. Now, as an insect taxonomist, I've got a good grip on what taxonomy means, and why it's wonderful, and I understand the various types of taxonomy they discuss. But how can you actually use the taxonomy capabilities? What can you make for readers/viewers? Here are a few things I've been reading on these topics.

Saturday, March 06, 2010

Drupal Updates, the Afterword

I've updated At Home on Spice Ridge and Pocahontas County History on the Web, and I've been asking myself, "What was all the fuss about, Boots?" It was much more trouble to set up test sites on localhost than it was to run the update processes on the live web sites. Of course, I see the point of having a test site, and I'm going to keep localhost up-to-date and backed up, so that next time I have a hardware disaster, I won't be starting from scratch.

I never got the Drupal image gallery modules and the enable clean urls functioning on localhost, but they never stopped working on the live sites, so there's not much pressure to fix the issue locally.

It seems that it's best to update modules one at a time, so that if there's a problem, you'll know which module caused it. Because I had both module updates and core updates, I updated the modules first, one at a time, and then did the core last.

Here's a list of the resources I used in the update process, with short descriptions.

  • How to Upgrade Drupal from the O'Reilly Web site. This was much more helpful than the equivalent Drupal.org explanations, mostly because it was better written and edited. This is the link to go back to.
  • HowTo: Updating Drupal 6.x to newer minor version. From the title, you'd think this Drupal.org guide would be exactly what you want when you're ready to update, but that's not the deal. It's a discussion of different tools that expedite the updating process, but you need to fuss with these long before you need to update. Frankly, I'm wondering whether these are worth the trouble...given how painless updating was. Of course, painless updates may be a fluke....
  • Introduction to Upgrading. This seems to be Drupal.org's canonical upgrade instruction. It seemed pretty complete, but I didn't hit any snags, so I don't know whether it will help when one really needs help.
  • update modules best practice--This is a nice discussion on a Drupal forum. I found it helpful in figuring out the sequence of my updates--that is, what to update first, second, third...

Sunday, February 28, 2010

Relocating Drupal Installations

As I said yesterday, before I disrupt my Web presences with Drupal updates, I'm going to break them locally. So today's project is to create a replica of the spiceridge.com installation of Drupal on localhost here on my Linux box, set up as an Apache2 server. I'm hoping that if I write it all out once, I can do this over and over without too much trouble. (Please don't laugh. Sometimes it does work that way.)

  1. Go to the /var/www/ directory, and make a directory to contain the Drupal installation you're cloning. the URL will be http://localhost/yourDrupaldirectory/
  2. Grab a copy of the website. The cPanel tools can create a compressed back-up copy of the website, and let the user download it through the browser. When doing this, be sure you just compress and back up the Drupal portion of the website--there's all sorts of extraneous stuff you don't need, like the email accounts. Then you can expand it using tar on the command line. Here's the syntax for tar:

    tar -xvwzf myfile.tar.gz to uncompress (untar) the myfile.tar.gz file in the current directory where "x" is for "extract;" "v" is for "verbosely list files processed;" "w" is for "ask for confirmation for every action;" "f" is for "use archive file or device ARCHIVE;" and "z" is for "filter the archive through gzip." To skip the annoying request for confirmation, use tar -xvzf myfile.tar.gz

  3. Alternatively, you can download the files and directories you want via ftp and use phpMyAdmin to export the contents of your database to a .sql file, which you can download. See How to backup your Mysql database with phpMyAdmin for exactly which buttons and boxes to click to get the .sql file for the whole database.

  4. Once the files are uncompressed and arranged the way they're supposed to be, It's time to recreate the database. It's probably a good practice to create a new user with password and new database for that user, rather than use the root user for the new database, so:

    1. Log into phpMyAdmin as root user.
    2. Click on "Privileges" and then "Add a new User"
    3. Set "Database for User" option to "Create database with same name and grant all privileges" and check all "Global Privileges."
    4. Hit "Go" and do what phpMyAdmin tells you to do. Remember to write down your user and database name, and the password you selected. Your database won't have any tables, but don't worry. We'll fix that next.
  5. PhpMyAdmin has an "Import" option, but it can only import very small databases. My Spiceridge database doesn't have much in it at all, but it's about three times too large for phpMyAdmin to import. Not a problem, though, because it's really easy to do this through the command-line program mysql. Here's the command: mysql -u username -p databasename < databasedump_dp.sql and it will prompt you for the password after you hit enter. This creates all the tables and populates them in one step.

  6. Now you've got the files on localhost and, and the database in your local MySQL database, you just need to update your settings.php file, which is in /var/www/your_Drupal_directory/sites/default/. You'll have to give yourself write permissions via the command-line program chmod a+w settings.php Then go into a text editor, and look for this:

    * Database URL format: * $db_url = 'mysql://username:password@localhost/databasename'; * $db_url = 'mysqli://username:password@localhost/databasename'; * $db_url = 'pgsql://username:password@localhost/databasename'; */ $db_url = 'mysql://yoursecret stuff';

    Modify it to include your local user name, database name, and password in the format they demonstrate for you. It's probably best to remove the write permissions when you're sure everything is working.

  7. Point your browser to http://localhost/yourDrupaldirectory/ and you should see your Drupal website.
  8. After fussing about with the Drupal site's documentation, the search engines showed me this short and sweet set of directions: Moving A Drupal Site From One Host To Another - How To. This worked for me.

Monday, September 22, 2008

Shopping For Content Management Systems

More Linux geekery: What tools to use in planning, developing, and maintaining my own Web site and the one I'm developing for a county historical preservation project? Should I have static Web pages? PHP and MySQL? Could I get by with Perl (which I already know how to use)?

I'm not very knowledgeable in Web 2.0 database driven stuff, but I'm going to need a photo gallery, thumbnails, and a database for the county Web site. That's why I've been reading up on "Content Management Systems." Here's a list of links showing what I've learned about so far.

  • Drupal requires Apache, PHP, MySQL. Drupal is a free software package that allows an individual or a community of users to easily publish, manage and organize a wide variety of content on a website. Tens of thousands of people and organizations are using Drupal to power scores of different web sites.
  • Joomla! is an award-winning content management system (CMS), which enables you to build Web sites and powerful online applications. Many aspects, including its ease-of-use and extensibility, have made Joomla! the most popular Web site software available. Best of all, Joomla is an open source solution that is freely available to everyone. It requires mySQL and PHP, which most ISP's provide.
  • Comparing Open Source CMSes: Joomla, Drupal and Plone. Another review of relative merits.
  • Drupal vs Joomla! comparison on Drupal's General Discussion Forum. The consensus seems to be that Joomla! is easier to use out of the box, but Drupal is better in taxonomy, search engine optimization, and customizability.
  • phpWebSite provides a complete web site content management system. Web-based administration allows for easy maintenance of interactive, community-driven web sites. phpWebSite's growing number of modules allow for easy site customization without the need for unwanted or unused features. Client output from phpWebSite is valid XHTML 1.0 and meets the W3C's Web Accessibility Initiative requirements. Founded and hosted by the Web Technology Group at Appalachian State University, phpWebSite is developed by the phpWebSite Development Team, a network of developers from around the world. phpWebSite is free, open source software and is licensed under the GNU GPL and GNU LGPL.
  • blosxom :: the zen of blogging: Blosxom (pronounced "blossom") is a lightweight yet feature-packed weblog application designed from the ground up with simplicity, usability, and interoperability in mind....Despite its tiny footprint, Blosxom doesn't skimp on features, sporting the lion's share of features one would find in any other Weblog application or full-blown content management and publishing system. Blosxom's plug-in architecture allows the core of Blosxom to remain small and sleek while providing room for extension and integration into different environments and uses....Blosxom is simple, straightforward, minimalist Perl affording even the dabbler an opportunity for experimentation and customization.
  • WordPress. It's not just a blogging tool, WordPress is a state-of-the-art publishing platform with a focus on aesthetics, web standards, and usability. WordPress is both free and priceless...
  • Plone" Plone is a ready-to-run content management system that is built on the powerful and free Zope application server. Plone is easy to set up, extremely flexible, and provides you with a system for managing web content that is ideal for project groups, communities, web sites, extranets and intranets. Zope doesn't seem to be supported that widely by ISP's.
  • PHPMYADMIN is a tool written in PHP intended to handle the administration of MySQL over the Web. Currently it can create and drop databases, create/drop/alter tables, delete/edit/add fields, execute any SQL statement, manage keys on fields.
  • CMS Mini (very very small CMS): A small PHP application for manage content for small web sites. Not intended for a cooperative group of editors and rewiers: simply one editor can insert new contents, immediatly pubblished on web: "one task, one click"The editor can edit through a browser interface; sounds really nice, but it seems there are security vulnerabilities.

Monday, March 01, 2010

More Fun With My Local Drupal Laboratory

I was very happy yesterday when I edited my settings.php file and a normal-looking copy of my Spice Ridge home page appeared at http://localhost/spiceridge. I posted my step-by-step directions here, and marveled that I had completed my cloning project before the wee small hours of the morning, and without weeping or cussing. Then, I sat down to tweak, modify, and update the local installation, and discovered to my dismay that the only thing that worked as intended was the front page, the page generated by index.php

The course of true upgrades never did run smooth....So I turned to Community Plumbing for Drupal advice:

  • Copy your live site to a test site (GUI). OK, that's what I'm trying to do...but these things aren't working.
  • How to copy a Drupal site from server to local? Here's a forum question from someone who's having the same problems I am, and who has tried a bunch of the same things I have. One helpful person points to this:
  • How do I unset the clean URLs? There were three things to try, and I tried them all. when I tried logging in by adding ?q=user to the end of the localhost URL, I got a 404 error as usual; while the msql commands to clear the cache files in the database had syntax errors that I couldn't work out. However, when I added $conf['clean_url'] = 0; to the end of the settings.php file I was back in business.
  • But only for a minute. This lets me log in, but I still can't find my image files, and I get "Fatal error: Allowed memory size of 16777216 bytes exhausted (tried to allocate 40961 bytes) in /var/www/spiceridge/projects/includes/theme.inc on line 1010" when I try to navigate to the admin page. The Drupal.org advice was quite confusing and probably not applicable to my situation: Increase PHP memory limit.
  • It seemed to me that the thing I should do (since the installation on my hosting provider's server runs like a top) is to fiddle with my newly-installed PHP stuff.
  • Ubuntu Documentation--Drupal has this to say:

    You should increase the default PHP memory limit value (the amount of memory dedicated to running scripts), since the default 8 Mb is not sufficient. Use 96 Mb (or even 160M) if you intend to use graphics (although for simple uses 32 Mb may be sufficient).

    In newer versions of Drupal6, you can simply edit the settings.php file and add the line:

    ini_set('memory_limit', '96M');

    In older versions of Drupal5, or if using PHP for many different uses, it is best to increase the amount of PHP memory using this method:

    Edit the /etc/php5/apache2/php.ini file and increase the memory_limit value to 96M (or another value of your choice).

    Of course, you have to do all this as root, and then you restart apache2: /etc/init.d/apache2 restart (also as root).

  • All right! now I can log in and access my Administration page, and start playing with the core and module updates. However, I notice that all my pictures are missing. What's an image gallery with no photos? Well, I know where they're supposed to be:

    rebecca@hecate:/var/www/spiceridge/projects/sites$ ls default/files/images
    ls: cannot access default/files/images: Permission denied

    Permission problems? This is really weird...I can't navigate into the default/files directory, even after I chmod the files as root. So I delete them, and ftp the originals from http://spiceridge.com, where the permissions are normal. OK, these are fine; let's see if the browser can get to them now....

  • OK, I'm seeing some images, but I'm also getting lots of copies of this error: warning: unlink(sites/default/files/images/1908Xmas001.preview.jpg) [function.unlink]: Permission denied in /var/www/spiceridge/projects/includes/file.inc on line 435. OK, I read in the comments in includes/file.inc that directory permissions might be the problem....I chmod a+w for the involved directories, and this brings in some, but not all of my images. About half of the thumbnails are gone.

Well, I never liked that image gallery anyway....This permissions issue is the inelegant and rather haphazard way Drupal handles an aspect of security. That's the down-side of having an automated installation, I guess. They say all this will be much improved in Drupal 7.x, but of course, that will be its own "learning experience."

I'm going to say, "Good enough for government work," and start messing around with the updates now.

Thursday, March 03, 2011

Drupal Updates Long Deferred

I've been putting off updating my Drupal Web page for most of the winter, but I thought I'd better get it taken care of before spring or I wouldn't do it at all.

The first thing I had to do was get my desktop computer set up as LAMP, Linux Apache Mysql PHP, so I could have a test site.

  • I had apache2 and php5 already installed on my Linux desktop (Debian Wheezy). All I needed to do was add php gd support to Apache thus:
    # apt-get install php5-gd
    # /etc/init.d/apache2 restart
  • For the "M" in LAMP, all I had to do (as root) in Debian was:
     # aptitude install mysql-server mysql-client
     # aptitude install phpmyadmin
    and then tell apache2 to find phpmyadmin: "Include /etc/phpmyadmin/apache.conf"

In the process of relocating a Drupal site to a local machine for testing, one has to clone the database. PHPmyAdmin has a push-button function for exporting a database; however, my database has grown too large for the push-button "import" to work. There are lots of bad hacks with high Google ratings, but they're much harder than using command line MYSQL with the commands given at Import/Export Large MYSQL Databases. "Source" is a dandy sql command I'd totally forgotten--it tells mysql to read a file and do the commands given there.

After all this, adding the updates to the Drupal installation took a few minutes. I haven't finished with the Spice Ridge site yet--I'd like to do it after a good night's sleep, in case something goes wrong; however, it's been my experience that the live site is easier to manage than the localhost one.

Every time I update Drupal, things go a little differently; however this time, I found most of the things I needed to do in my own Drupal posts here on my blog. I may bore my readers, but these Linux and Open Source posts are the things I revisit most often.

Monday, March 07, 2011

Rethinking My Web Presence

Now that I've updated my Drupal website, I need to think of something useful to do with it. I've used it for sharing information with my students, and as a trial ground to learn to use content management systems, but I don't currently have a need for either of those purposes. I've also thought about using it as an adjunct to selling my fiber arts projects, but I've made no move in that direction.

I made that site to learn how to use Drupal, but I'm also thinking about switching to Wordpress. Ironically, I started this Blogger blog to get my website indexed, but these days, this blog covers most of my web presence needs. Maybe I should drop the spiceridge.com site all together?

Here are some tips I've collected for using Drupal for a personal site. (See, I'm using this blog to keep track of links I don't want to lose.)

Tuesday, October 07, 2008

Wordpress, MAMP, Drupal, LAMP--Linux Is Easier Than Mac

I was very taken with the idea of MAMP: One-click solution for setting up your personal webserver. MAMP is installed in the typical Mac fashion: very easily. MAMP will not compromise any existing Apache installation already running with your OS X. You can install Apache, PHP and MySQL without starting a script or having to change any configuration files! Furthermore, if MAMP is no longer needed, it is sufficient to delete the MAMP folder and everything returns to its original status (i.e. MAMP does not modify any of the "normal" OS X).

I really liked the idea that I could install a CMS, play around with it, and just dump the whole database and loalhost content if I messed it up. I thought it would be easiest to start out with Wordpress, rather than Drupal or one of the digital library CMS's, because so many people use Wordpress successfully. It must be easy, right?

Well, it didn't work that way. I installed MAMP successfully, I thought, but I couldn't get Wordpress to communicate with the MySQL database. Eventually, I gave up and turned to my Debian desktop, where I installed the usual LAMP setup. Drupal worked almost right "out of the box." The only problem I had was that I had an old version of Apache 1.3 installed, from my efforts to configure a network file system (NFS) back in March. Once I removed that and reinstalled Apache 2, it was a cinch to install Drupal on localhost.

This gave me an idea--I thought I had turned off all the network services in the Mac "System Preferences: Sharing" window, but when I poked around a bit more, I found "Apple Share" turned on. Once that was turned off, Wordpress installed easily on MAMP's localhost:8888 just as advertised. Here are a couple of resources that helped me with the Wordpress/MAMP install.

So, it probably would have been easier to start with Drupal in the regular /var/www directory for localhost on the Mac. Here are the directions I found helpful for that process.

Guides to a "Full-blown" LAMP setup for Mac OSX Leopard

  • Installing WordPress On Your Apple MacAn interesting but often overlooked feature of an Apple Mac is that it comes bundled with a fully functional copy of the Apache web server and PHP - the language of WordPress. Add a MySQL database server to the mix and you have a fully functional, but personal, web server where, like me, you can test your website and write and debug code without ever exposing it to public view.
  • Leopard: How to Install Wordpress also details adding MySQL, turning on PHP5, installing your CMS of choice (Wordpress again), and running localhost.

Sunday, September 28, 2008

Still More Digital Library Resources

I continue to shop around, kicking the tires on content management systems for Web sites and software for digital collections libraries. I'm planning to download Drupal (digital content management for Web sites) and experiment with it. As for Digital Collection management, I'm leaning strongly toward Archon, and have downloaded and started to play with it as a tool in managing the historical society's cataloging project.

However, all this shopping is a recursive project. As I've tried to understand the tools I've selected, I keep finding more tools that also deserve a look. The essay Drupal as a digital library content management system pointed me to these interesting applications:

  • Greenstone Digital Library Software Greenstone is a suite of software for building and distributing digital library collections. It provides a new way of organizing information and publishing it on the Internet or on CD-ROM....The aim of the Greenstone software is to empower users, particularly in universities, libraries, and other public service institutions, to build their own digital libraries. It requires Apache; it also has some nice features only available on the Windows version....
  • STREETPRINT.ORG, A growing community of public web archives powered by the Streetprint Engine. This package actually looks very nice, but there's no recent sign of life on the Web site, where the newest post on the forums is dated 2007.
  • ContentDM from OCLC (Online Computer Library Center) is a nonprofit, membership, computer library service and research organization dedicated to the public purposes of furthering access to the world's information and reducing information costs. You have to email to request a quote, and it seems Windows-centric. They say the server runs on UNIX platforms, but it doesn't sound like they've tested on Linux since kernel 2.4 came out.
  • digitizationblog focuses on digitization and related activities (such as electronic publishing) in libraries, archives, and museums, and is intended to be a source of news relevant to people who manage and implement digitization projects. Even though there are several excellent sources of digitization news such as the DigiCULT Newsletter and RLG DigiNews (and this blog certainly isn't intended to replace them), there is a lack of space on the web where implementors can share ideas and useful pointers. digitizationblog is intended to fill part of this gap.
  • Welcome to the WebAPP, Web Automated Perl Portal!: WebAPP is the most fully-featured, versatile, free and open-source, flat-file Perl portal script available today! Acronym for Web Automated Perl Portal, WebAPP is easily installed on virtually any UNIX-based server. WebAPP requires no SQL backend, no PHP, only a hosting environment offering support for Perl. This seems very attractive to me because I wouldn't have to learn much new stuff, and I could get Web sites up quickly, for me and for the library project. Also, it wouldn't be vulnerable to these spam SQL-insertion attacks that have been going around lately.

Sunday, February 08, 2009

Pocahontas History Goes Live

It's got an URL now, and there's something relevant on its index page: Pocahontas County History has gone live on the Web. After all the time I've put into Drupal and the study of archive management arcana, I had hoped to have something more to show for my time. Still, I've got an actual mission statement and some relevant Pocahontas County links, so I guess it beats a "Coming Soon!" page.

If you see typographical errors, factual errors, or can think of a better title for the website, let me know.

The next thing I'll roll out is the Archon database, with its slender but well-organized catalog of Pocahontas County Historical Society archives. (Barring unforeseen disasters, which are common.) After that, Drupal, and then some cool old pictures and local history.

I hesitate to forecast how quickly this will happen because unexpected (but not unwelcome) things have been happening here on the ridge. This project's time line had the content management systems already in place by now.

Thursday, January 05, 2012

Debian Wheezy to Sid--Are You Sure It Won't Blow Up?

Yesterday's post reporting a successful switch to KDE was a bit premature, at least on my desktop machine. The laptop is still OK (I hope).

After a few days, all the "Desktop Effects" quit abruptly, perhaps after an update. (I was running Debian testing, which has daily updates.) I tweaked and adjusted, and eventually some of them started working again, perhaps because I switched compositing type from OpenGL to XRender. This change is located:

System Settings > Desktop Effects > Advanced

KDE has changed so much since I last used it that I have much frustration in locating these sorts of things.

More updates, including a kernel update, ensued, and I had a flashback to my Mysterious Errors and kernel panics of a year ago. Restarting the computer produced either a grub rescue > prompt, a "can't find the file" message after selecting the kernel on the grub menu, or a kernel panic. In every case, I was able to boot from a Debian net install disk using "rescue mode," re-install grub thus:

# grub-install followed by #update-grub

I could then remove the CD and reboot successfully once. Every time I restarted the computer, I had to go through this song and dance. As I said last January,

After I...powered up, the little darlin' booted right up....I really hate it when I don't know what was wrong, or why it's running now. Did something reset while it was powered down? Did jiggling the cables do the trick? Was it dust? And what's with all the update-grub/reboot iterations? Why do I always have to do that over and over again? And why does none of this ever happen with my Linux laptop?

Last year, the problem mysteriously resolved after a few tries, but this time, I started getting more and different error messages that I couldn't figure out. Googling showed me that I wasn't alone in my troubles, but I couldn't find a solution that worked for me. I made two fresh back-ups of my home directories, and resolved to choose "Install" rather than "Rescue Mode" at the next reboot.

The re-install ran without any problems, and, while I'll have to reconfigure my localhost installations of Wordpress and Drupal (they needed work anyway), this fresh install is now scoured clean of all the Gnome, XFCE, icewm, sawfish, awesome, metacity, etc. libraries and programs, which I'm not using but which require updates anyway.

Last time I installed testing, I tried without success to upgrade to sid, that is, Debian unstable. This time, it worked for me, and I am now typing on cutting edge Debian. The Debian GNU/Linux FAQ--Choosing a Debian distribution recommends sid over testing:


There is no perfect answer but only a "wise guess" could be made while deciding between unstable and testing. My personal order of preference is Stable, Unstable and Testing. The issue is like this:

  • Stable is rock solid. It does not break.
  • Testing breaks less often than Unstable. But when it breaks, it takes a long time for things to get rectified. Sometimes this could be days and it could be months at times.
  • Unstable changes a lot, and it can break at any point. However, fixes get
    rectified in many occasions in a couple of days and it always has the latest
    releases of software packaged for Debian.

Raphael Hertzog also reassures me that "Unstable is a quickly moving target and it's not for everybody. But you can use it and your computer won't explode" in his blog post 5 reasons why Debian Unstable does not deserve its name

Now, it's back to fiddling with my brave new Debian. I wonder how long before I break it?

Wednesday, May 06, 2009

Mental Fragments, Mental Fractals....

The last few days, I've been converting an OCR'ed text of William Price's Historical Sketches of Pocahontas County into sensible and legible text, then loading it into Drupal a bit at a time at Pocahontas County History. I'm working my way through the 400-plus pages of genealogical information first, because that is the portion most desired by genealogists and least accessible to Internet search engines. It's also the least enjoyable reading for those of us not seeking to understand a particular family's ancestral relationships. Lists of marriages, sons and daughters, sons-in-law and daughters-in-law, interspersed with the unfortunate fatal accidents and illnesses which ended their various lives...it's not as much fun as you might imagine.

At the same time I've been doing some supplemental reading for the chemistry course I'm teaching. (Fragmented? I try to tell myself it's my free-ranging intellect, but I keep picturing free-ranging chickens....)

In any case, I read this very exciting article: Can fractals make sense of the quantum world? illustrated with the pretty cauliflower picture above. I believe it's there to illustrate a fractal pattern rather than quantum mechanics, but according to Dr. Tim Palmer, fractal mathematics may eventually resolve the puzzles that quantum theory poses.

Quantum theory just seems too weird to believe. Particles can be in more than one place at a time. They don't exist until you measure them. Spookier still, they can even stay in touch when they are separated by great distances.

Einstein thought this was all a bit much, believing it to be evidence of major problems with the theory, as many critics still suspect today. Quantum enthusiasts point to the theory's extraordinary success in explaining the behaviour of atoms, electrons and other quantum systems. They insist we have to accept the theory as it is, however strange it may seem.

But what if there were a way to reconcile these two opposing views, by showing how quantum theory might emerge from a deeper level of non-weird physics?

If you listen to physicist Tim Palmer, it begins to sound plausible. What has been missing, he argues, are some key ideas from an area of science that most quantum physicists have ignored: the science of fractals, those intricate patterns found in everything from fractured surfaces to oceanic flows....

Take the mathematics of fractals into account, says Palmer, and the long-standing puzzles of quantum theory may be much easier to understand. They might even dissolve away....

It is an argument that is drawing attention from physicists around the world. "His approach is very interesting and refreshingly different," says physicist Robert Spekkens of the Perimeter Institute for Theoretical Physics in Waterloo, Canada. "He's not just trying to reinterpret the usual quantum formalism, but actually to derive it from something deeper."

That Palmer is making this argument may seem a little odd, given that he is a climate scientist working at the European Centre for Medium-Range Weather Forecasting in Reading, UK. It makes more sense when you learn that Palmer studied general relativity at the University of Oxford, working under the same PhD adviser as Stephen Hawking....

"It has taken 20 years of thinking," says Palmer, "but I do think that most of the paradoxes of quantum theory may well have a simple and comprehensible resolution."

Tuesday, May 12, 2009

Sycamores and Pioneers

I'm still pecking away at Historical Sketches of Pocahontas County, making a search-able, sort-able version on Pocahontas County History for the genealogy researchers. I have about 70 more "sketches" edited and waiting to go into Drupal. Some of them have brief stories included, others are just lists of descendants.

Last week, Sherry Chandler shared some fascinating excerpts from her reading on Kentucky history, including Samuel Shepard's diary entries, in which he notices a family encamped inside a hollow sycamore tree. As it happens, our most famous local history story involves Marlinton's founders, Marlin and Sewell, and how one of them came to spend the winter living in a sycamore.

Jacob Marlin and Stephen Sewall, p. 105, Historical Sketches of Pocahontas County by William T. Price (1901)

The first persons of English or Scotch-Irish antecedents to spend a winter in what is now Pocahontas County, were Marlin and Sewall. This was the winter of 1750-51. Their camp was in the delta formed by Marlin Run and a slough or drain near the east bank of Knapp's Creek.

In the course of time--having agreed to disagree--they separated and were found living apart, by Colonel Andrew Lewis, Marlin in the cabin and Sewall in a hollow tree. Upon expressing his surprise at this way of living apart, distant from the habitation of other human beings, Sewall told him they differed in sentiments and since the separation there was more tranquility, or a better understanding, for now they were upon speaking terms, and upon each morning "it was good morning, Mr Marlin, and 'Good morning, Mr Sewall!'"

Under the new arrangement, Sewall crossed the slough, and instead of building another cabin, went into a hollow sycamore tree on the west margin of the slough, quite near where the board walk now crosses, and about in line with a walnut tree now standing on the east bank of the drain and the court house.

The lower part of this tree bore a striking resemblance to a leaning Indian tepee. The cavity could shelter five or six persons, and the writer has been often in it for shade or for shelter from rain or heat. At the top of the cone, some eight or ten feet from the ground, the tree was not more than twenty inches in diameter, and at that height was chopped off about the year 1839, to avoid shading the crops. Thus the stump was left, a great convenience for shade or shelter, until it disappeared during the War, being probably used for a camp fire.

These persons differed, Sewall told Colonel Lewis, about their "relagian." There is a traditional hint that "immersion" was the theme of contention. But it is more than probable that one was a conformist and the other a non-conformist to the thirty-nine articles of the English rubric. This is known to have been a very live question of those times, both before and after.

This new arrangement did not last long, and Sewall in search of less molestation about his religion, withdrew about eight miles to a cave at the head of Sewell Run, near Marvin. Thence he went forty miles farther on to Sewell Creek, west Greenbrier, and was found and slain by Indians. How impressively this illustrates the evils of religious controversy, so called.

"Against her foes religion well defends, 
Her sacred truths, but often fears her friends. 
If learned, their pride: if weak their zeal she dreads 
And their heart's weakness who have soundest heads;
But most she fears the controversial pen, 
The holy strife of disputatious men, 
Who the blest Gospel's peaceful page explore, 
Only to fight against its precepts more." 

It is moreover interesting in this connection to recall the fact that on the banks of Marlin's Run is the burial place of a little child that was dashed to death by an Indian warrior in 1765, when overtaken by a party of Bath and Rockbridge men, seeking to rescue Mrs Mayse, her son Joseph, an unmarried woman with an infant in her arms, a Mr McClenaehan, and some other captives. This burial place is a few rods diagonally from the east angle of Uriah Bird's barn on the margin of the rivulet. The infant corpse was buried at the foot of the tree where it had been found a few minutes after its death. The burial took place just a few hours later, before the pursuers set out on their return. The grave was dug with hunting knives, hatchets, and naked fingers. The little body laid in its place very tenderly, and the grave partly filled with earth. The covering of the grave was completed with rather heavy stones, to prevent foxes or other animals from getting at the remains.

Thus died and was buried the first white child known to history west of the Allegheny Mountains.

Joseph Mayse, 13 years old, was rescued at that same time, somewhere between the Island and the mouth of Indian Draft. In 1774 he fought in the battle of Point Pleasant, where he was wounded, and after suffering from the injury for forty-six years, his leg was amputated. He recovered, and lived a number of years thereafter, a busy man of affairs. He died "serene and calm," April, 1840, in the 89th year of his age.

In the Richmond Dispatch, April 14, 1901, it is stated that the last survivor of the Point Pleasant veterans was Ellis Hughes, who passed away at Utica, O., in 1840, over ninety years of age. In early manhood he may have lived in the Lower Levels of our county. Now if it was known what month Hughes died in, it could be decided who was the last one of the veterans to bivouac in those "silent tents" that Glory "guards with solemn round."