Drupal 6 to Drupal 7 image_attach to imagefield migration

The old table structure

image_attach → image → files

becomes

field_data_field_image → file_managed

Assuming that the database name is test, imagefield is named field_image. file access type is public and the files folder is located in DRUPAL_ROOT,

fill the field_data_field_image table:

INSERT INTO file_managed (fid, uid, filename, uri, filemime, filesize, status, timestamp)
SELECT DISTINCT f.fid fid, f.uid uid, REPLACE(f.filepath, 'files/images/', '') filename, REPLACE(f.filepath, 'files/images/', 'public://') uri,
f.filemime filemime, f.filesize filesize, f.status status, f.timestamp timestamp
FROM image_attach ia, image i, files f WHERE ia.iid=i.nid AND i.fid=f.fid AND f.filename='_original' AND;

then, fill the file_managed table:

INSERT INTO field_data_field_image (entity_type, bundle, deleted, entity_id, revision_id, language, delta, field_image_fid, field_image_alt, field_image_title, field_image_width, field_image_height)
SELECT DISTINCT 'node' node, 'event' bundle, 0 deleted, ia.nid entity_id, n.vid revision_id, 'und' language, 0 delta, f.fid field_image_fid, '' field_image_alt, '' field_image_title, NULL field_image_width, NULL field_image_height
FROM image_attach ia, image i, files f, node n WHERE n.nid = ia.nid AND ia.iid=i.nid AND i.fid=f.fid AND f.filename='_original';

As the default location of uploaded images changed, we should move files

FairSearch.org tries to persuade EU decision-makers to crack down on Google

There's been a fair amount of talk about FairSearch.org in US, and how ill-though their campaigning is.

One of my clients is now rolling out ads for FairSearchEurope.eu. Just as its US counterpart, FairSearchEurope.eu is very shy of itself. It's website is registered to a law firm, its founding is unclear, it banners are the most obvious examples of FUD tactics I have seen in the past years. Come on, dudes! There are so many reasons to attack Google, don't whine about the only thing that works, their search engine.

Не вращайте айтишников

Есть у моего клиента сайт на Wordpress. Проект, которому пророчили большое будущее. Будущее не пришло, денег проект не приносит, посещаемость мизерная, поддерживается по остаточному принципу. Cегодня с утра заглянул я по привычке в LinkedIn, а там как раз рекламировалась статья Bare Minimum SEO: 3 Things You Must Do. А первым пунктом в статье шло… «check your indexing status in Google Webmaster Tools». Ну я и пошёл проверить.

Какого же было моё удивление, когда оказалось, что на проекте не проиндексировано ни одной страницы, а в /robots.txt сайта написано User-agent: *\nDisallow: /\n. Wordpress создаёт /robots.txt программным способом, поэтому проблему было сложно заметить. Теперь сижу и гадаю, было ли это подлянкой одного из бывших айтишников, либо просто разгильдяйством. Как обычно, правда наверно где-то посередине.

Software industry has tools and processes to help transparency in law and policymaking

Software that we now use constantly in our daily life wouldn't be possible if people creating these systems did not follow the practice of recording even the smallest change to the software in version control systems. Now, political activists all around the world convert legal texts to version control systems in an attempt to open up the lawmaking processes.

Pages