Thursday, March 27, 2014

Taxes on the farmer feeds us all

Farmers and farmworkers are the way food is provided to us in the US.

The children of migrant farmworkers have a tough row to hoe.  The migrant education programs help to improve their lot.  At SUNY New Paltz, NY the program linked below is helping migrant farmworker families.  Follow the link below to learn more.

http://mid-hudson.org/

Mid-Hudson Migrant Education Tutorial & Support Services

Tuesday, February 28, 2012

Drupal 6 to 7 - clear errors by dropping Upload DB table

another guy figured this out -- I am just afraid to lose the solution -- so I copying it here --

I kept getting the error below when trying to run the update.php
grrrr!

Update #7061

Failed: PDOException: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry

the following worked -- from
http://user25.com/drupal/upgrade6-7-DB-schema-update-error-failed-7061-solution

Drupal 6 to 7 Upload/File module Database Schema update error - Solution

The following updates returned messages
system module
Update #7061
Failed: DatabaseSchemaObjectExistsException: Table system_update_7061 already exists. in DatabaseSchema->createTable() (line 629 of /---/includes/database/schema.inc).
Changes in Drupal 7
I notice that the Drupal core upload module has been removed from the latest version of Drupal (7). There is therefor a script in the system.install (also run during Database Schema updates /update.php) that is intended to take the data in the 'upload' database table and load it into the database table for the new file CCK field (that is the new way of handling file uploads in Drupal - in addition to using third-party solutions such as IMCE and the CKEditor WYSWYG commercial version of the editor).

DB Schema Update error
During the final stages of upgrading from Drupal 6 to Drupal 7 on this website - idonny.com there were 11 updates that could not clear from the update log resulting in the error message at the beginning of this entry. As usual, I checked on the Internet and Drupal-org in particular for what others have experienced and reported on this issue. One document (http://drupal.org/node/966210) came close to describing and identifying the problem. The document on Drupal.org refers to the existence of non-unique database entries (or just different by case) and the possibility that the row in question (file names/path) is of a type that is case-aware/sensitive. Being that I do not have too many uploads (apart from portfolio images that I am anyway rebuilding as part of a refresh of the portfolio section, and login public keys), I resolved to trunctate the database table "upload" so as to eliminate all upload entries and thus by-pass/solve the problem of the rows with identical values. That did however not solve the problem (To be safe, I created a new tables with the same schema and copied the data to it to avoid progressively damaging the database structure).


Solution
The approach that worked for me was to DROP the upload table.
I looked in the includes/database/schema.inc file on the line mentioned #629 and found that there was just an abstract function definition for throwing the error that we see on the screen.
* @throws DatabaseSchemaObjectExistsException
* If the specified table already exists.
*/
public function createTable($name, $table) {
if ($this->tableExists($name)) {
throw new DatabaseSchemaObjectExistsException(t('Table %name already exists.', array('%name' => $name)));
}
$statements = $this->createTableSql($name, $table);
foreach ($statements as $statement) {
$this->connection->query($statement);
}
}
So I decided to find if there are other DB tables and code instances that are explicitly referring to the required schema that is either unmodifiable of conflicting. I see that the file at /---/modules/system/system.install has a code sequence that is referencing the DB schema update #7061 and is also consistent with the fact that if the DB table exists, thent he error should be thrown
/**
* Migrate upload.module data to the newly created file field.
*/
function system_update_7061(&$sandbox) {
if (!db_table_exists('upload')) {
return;
}
So I dropped the DB table [DROP upload;] in mysql and was able to successfully update the core DB schema

Tuesday, January 10, 2012

problems "cloning" a Drupal site

Had a site that I wanted to have 3 iterations of -- to use as multiple sandboxes --

I had them in subdomains -- and copied the database -- but the copied sites didn't look like the original --

I could not find any reason for the discrepancy and in truth I don't even now know what was causing the problem -- but I did find a way to get the three sites back into step...

Found a solution to my problems --

I logged in as admin to the Drupal sites --

then I ran

update.php -- nothing was shown to have updated --

after update I ran

cron.php

and voila

or is it eureka??

either way -- the sites look like they should ---

why -- I don't know ---

so there it is --- now -- when I compare the 3 sites --- varying in name something like the sites below --

ALL IS WELL

http://rslts.example.com

http://rslts3.example.com

http://rslts152.example.com

Monday, January 9, 2012

Getting those neat drop down menus to work in Drupal 6 Acquia Marina theme


I had some trouble figuring this out -- nothing new about that -- but I got it to work -- which is always a good feeling..


Friday, April 29, 2011

Don't Get Fracked

There's "natural gas" locked in Devonian shale formations deep below the states of New York, Pennsylvania, Maryland, Virginia, and West Virginia. Marcellus Shale and Utica Shale have commercially viable amounts of gas but extraction has to be done using a new extraction method called "fracking" or hydraulic fracturing. Clean water is taken and combined with sand and a number of chemicals known and unknown to fracture the shale and keep the cracks open to allow the gas to migrate to the well bore and come to the surface.

Keep in mind that other things come back to the surface besides the sought after and valuable natural gas. Brine laden with a number of undesirable metals such as barium and perhaps radioactive chemicals are brought up. Currently there is no safe place to dispose of this water that comes back. For this procedure there is not a problem because a 2005 act excluded hydraulic fracturing from having to meet the standards set by

The Clean Water Act - passed by Congress while Nixon was in office
The Clean Air Act - passed by Congress while Nixon was in office
The Clean Drinking Water Act

These laws were major advances in protecting the environment we all share.

Why tolerate natural gas extraction if the process had to be excluded from these important acts?

Read more at

Phone number searching tips

I tried putting in phone numbers as

800-555-1212

and as

800.555.1212

but when I went to search for them they would not show up...

I tried

800x555x1212

and

800m555m1212

both worked

my preference if for the

800m555m1212

If you are using a "smart phone" with just a phone keypad m is easier than x because if you press 1 time on 6 you get m

to get x you have to press 9 twice.

Wednesday, May 5, 2010

Drupal 5.x Search vs 6.x Search

Sometimes it seems like I am just searching for the perfect search.

I have a site that has close to 7,000 nodes of resource contacts. All the contacts have a phone number. I can jot down a phone number and have it exactly right. In Drupal 5.x I could search on the phone number and just go right to that resource.

I upgraded to Drupal 6.16 from Drupal 5.22 and the search died.

That was bad news for me and the usefulness of my site.

I would put a phone number in the search box and get almost every node in the site in the output.

So I searched all over drupal.org and the web via google.com and tried to learn what had changed to kill my search from Drupal 5.x to 6.x.

I never did find any documentation on the change that did me in, but in the Drupal handbook at the link below

http://drupal.org/handbook/modules/search/

I found the following

"If you're looking for an exact phrase, enclose it in quotation marks."

Now there's an idea - put your search keyword in quotes. That wasn't necessary in 5.x searches -- but apparently it is necessary in Drupal 6.x searches.

I was doing things like adding the Custom Google Search Engine module and the Search Lacene API search - but it was all unnecessary.

The power of quotation marks was all that I needed.