My personal notes on all things technical and factual....

This site has no ads. To help with hosting, crypto donations are accepted:
Bitcoin: 1JErV8ga9UY7wE8Bbf1KYsA5bkdh8n1Bxc
Zcash: zcLYqtXYFEWHFtEfM6wg5eCV8frxWtZYkT8WyxvevzNC6SBgmqPS3tkg6nBarmzRzWYAurgs4ThkpkD5QgiSwxqoB7xrCxs

Wed, 27 Jul 2016

/SW/graphics: Fixing Simple Photo Issues at the Command Line

(Without having to startup a huge program like gimp or photoshop.)

These utilities are also drawn from the ImageMagick[1] graphics suite. Imagemagick is available for all of Linux, Windows, and the Mac environment[2]. Some examples:

Identify: find out photo characteristics with identify:
identify image1.jpg
Rotation: Do you sometimes turn your camera 90 degrees to get that "tall" shot? Rotate the photo back clockwise with the convert command:
convert -rotate 90 image1.jpg image2.jpg
Resize: How about a whole directory full of photos that you want to reduce in size, without having to edit every photo to do it? Again use convert to do the job, this time in a little Unix shell script. First create the directory "convert-folder" in the same directory as the one containing your "big" photo directory. Then cd into the "big" photo directory and run this scrip:
for i in *.jpg ; do convert $i -resize 800x800 ../convert-folder/$i ; done

This may take a while if you have a lot of photos. In this example, photos will be resized such that they have a maximum width or heighth of 800 pixels, with no change in aspect ratio.
mogrify: resize while preserving aspect ratio. 600x500 are therefore maximum dimensions of the result. Use of the quality option with a value less then 100 reduces the size of the resulting file a little:
mogrify -resize 600x500 -quality 70 Gabe.jpg

Note that the key difference between mogrify and convert are that morgify over-writes the original file, and convert writes to a different file.
format: file format can also be changed:
convert input.jpg output.png
Annotate: an image with some text:
# convert -font helvetica -fill white -pointsize 36 \
-draw 'text 10,50 "This is the annotation text"' \
floriade.jpg comment.jpg
Thumbnailing: all the JPEGs in the current directory (note that this is a Unix shell script):
for img in *.jpg ; do convert -sample 25%x25% $img thumb-$img ; done
Sub-Directories: shrinking a bunch of jpg files spread out through a number of sub-directories:
nice ionice -c3 find . -type f -name "*.jpg" -exec mogrify -resize 200x200 -quality 70 {} \;
(Note that "nice" and "ionice" lower the priority of the operations' claim on CPU and disk resources, respectively. Especially useful for a production server.)
PDFs:
convert file.jpg file.pdf
pdftoppm -r 300 -jpeg file.pdf file
(Note: convert converts to PDF just fine, but in the other direction (sometimes? always?) quality is problematic. pdftoppm works perfectly in that direction.)

I have not yet found an Imagemagick manual that has the gift of making difficult tasks seem easy. Here[3][4][5] are some suggestions for manuals.

[1] http://www.imagemagick.org/script/index.php
[2] http://www.imagemagick.org/script/binary-releases.php
[3] http://www.imagemagick.org/script/command-line-tools.php
[4] http://linux.about.com/library/cmd/blcmdl1_ImageMagick.htm
[5] http://www.imagemagick.org/Usage/

posted at: 03:59 | path: /SW/graphics | permanent link to this entry

Sun, 07 Feb 2016

/SW/business/WordPress: Drupal 6 to WordPress 4 Migration

With many thanks to this[1] post for doing most of the work. Note that I have a simpler situation with only one user and no URL aliases.

Prepare your freshly install WordPress 4.4 database by truncating default posts / pages / comments after installation.

TRUNCATE TABLE wordpress.wp_comments;
TRUNCATE TABLE wordpress.wp_links;
TRUNCATE TABLE wordpress.wp_postmeta;
TRUNCATE TABLE wordpress.wp_posts;
TRUNCATE TABLE wordpress.wp_term_relationships;
TRUNCATE TABLE wordpress.wp_term_taxonomy;
TRUNCATE TABLE wordpress.wp_terms;

Migrate tags:

Copy over Drupal posts to your WordPress database.

Update post to tag / category relationship:

Update tags / category post count:

The following code is supposed to help fix taxonomy:

Insert comments to posts:

Update post comments count:

You can avoid this step if you omit copying the teaser / post_excerpt post field. Or, after the fact:

UPDATE wp_posts SET post_excerpt = NULL WHERE post_excerpt is not null;

My tag category links did not display out of the box, and this fixed that:

In backend --> Settings --> Permalinks set a custom value ("topics" for instance) for category base.

And finally, the comments that I imported are not displaying properly yet. At this point I do not care enough to try to fix it, so caveat emptor.

[1] http://www.jamediasolutions.com/blog/migrating-drupal-to-wordpress.html

posted at: 03:49 | path: /SW/business/WordPress | permanent link to this entry

Mon, 02 Dec 2013

/SW/Micro$soft: Windows Sucks

So I last made daily use of a Microsoft operating system on my desktop around about '00. It was that pig Win98, which drove me right into the arms of Linux, and I have never looked back since. (And no, Macs do not even tempt me. OSX might have some really shiny apps, but as an OS it is inferior to Linux, IMO.)

Fast forward to '13, and most or all of the damn banks in China insist on the use of Internet Explorer for their online banking. (Biting my tongue....) For various reasons, I am having to do this more and more, so thought it might be nice (and more secure) to be doing so on a legal, UP-TO-DATE, Win-something-or-other.

I managed to get a real cheap (legal, licensed, unopened packaging) copy of Win7 off of Taobao. Installed it in a virtual machine under Linux, typed in the serial number and had it accepted. And Windows Update did not work. Dies with some kind of (standard for Microsoft) completely useless and unintelligible error message. Probably has something to do with my accidentally clicking through the license code screen, and then adding the code after the fact.

And then I poured the rest of my afternoon down the drain, doing the Windows dance: tried a dozen different things, including an attempt to upgrade the same install from the same DVD image that failed (at the very end!) miserably. Finally I had to scrub the whole thing and start from scratch, being careful to give Microsoft it's little code at exactly the appointed time, and no other.

Ten years later, Windows still sucks.

posted at: 06:16 | path: /SW/Micro$soft | permanent link to this entry

Thu, 18 Jul 2013

/SW/business/Drupal: Drupal: How to Delete Users Without Content

I run a community Drupal 6 site that allows anyone to register, and my MySQL dumps were starting to get pretty big. I just reduced the number of users from 105,121 to 98 by deleting all users who had contributed no content or comments. There seems to be no easy way to do this, so here is my way. It is a little complicated:

mysql> select users.mail, node.title from users, node where users.uid=node.uid;

will list all users with content, ie. a Drupal "node".

mysql> select * from users where users.mail not in (select users.mail from users, node where users.uid=node.uid)

will list all users WITHOUT content.

mysql> select users.mail, comments.subject from users, comments where users.uid=comments.uid;

will list all users who have made a comment, and....

mysql> select * from users where users.mail not in (select users.mail from users, comments where users.uid=comments.uid);

will list all users who have never made a comment. Now this

mysql> select * from users where (users.mail not in (select users.mail from users, comments where users.uid=comments.uid)) and (users.mail not in (select users.mail from users, node where users.uid=node.uid));

will display all users who have neither content nor comments, which would lead one to expect that this

mysql> delete from users where (users.mail not in (select users.mail from users, comments where users.uid=comments.uid)) and (users.mail not in (select users.mail from users, node where users.uid=node.uid));

would work. But no,

ERROR 1093 (HY000): You can't specify target table 'users' for update in FROM clause

Stupid, but true. Damn MySQL. So now we have to play rocket scientist to get it done, and create a temporary table of users we want to delete:

mysql> CREATE TEMPORARY TABLE t select mail from users where (users.mail not in (select users.mail from users, comments where users.uid=comments.uid)) and (users.mail not in (select users.mail from users, node where users.uid=node.uid));

And now finally delete the damn SPAMers (which would be the vast majority of this garbage):

mysql> delete users from users join t on t.mail = users.mail;

posted at: 02:31 | path: /SW/business/Drupal | permanent link to this entry

Thu, 11 Jul 2013

/SW/fileSharing/btsync: BitTorrent Sync

Your own personal "dropbox". The puppet configuration below is for my personal convenience in deploying to multiple machines. BitTorrent Sync[1] is really easy to install and use without Puppet. On each machine you want to sync, just put the btsync in some convenient subdirectory, start it from within that directory, point your browser to http://localhost:8888/, and there tell it which directory to sync and what the shared "secret" is for that directory, and it should then just work for machines on the same network. Without further ado, here is my Puppet module:

class btsync ($syncdir) {

    # BitTorrent Sync: setup of multiple nodes
    #
    # Note that because btsync is not yet packaged for Debian/Ubuntu, I am using
    # the sync directory to distribute new versions of btsync to the nodes. However,
    # this means the initial installation must be "primed" for a new installation:
    # place the btsync executable required on the new node in the sync directory, named
    # as "btsync_", ie. btsync_amd64 / btsync_i386 / btsync_x86_64 for most Linux people.
    #
    # Note that this configures all nodes with the same basic settings, but 
    # WITHOUT shares. You must login to the webUI at http://VPN-IP:8888/
    # and manually specify shares for each machine with this configuration.
    # This line
    #       "listen" : "<%= ipaddress_zentuxnet %>:8888"
    # in btsync.conf.erb is where I am setting the webUI listen restriction.
    # Replace with "0.0.0.0:8888" to allow connections from anywhere.
    #
    # btsync --generate-secret

    $btuser = 'btuser'
    $installdir = '/usr/local/btsync'

    user { $btuser:
        ensure => present,
    }

    file { "$installdir":
        ensure => directory,
        mode   => 740,
        owner  => $btuser,
        group  => $btuser,
        recurse => true,
        before => Exec['copybt'],
    }
    file { "$syncdir":
        ensure => directory,
        mode   => 640,
        owner  => $btuser,
        group  => $btuser,
        recurse => true,
    }

    # verify the latest version of btsync is installed (contained in the sync dir)
    exec { copybt:
        command => "cp $syncdir/btsync_$architecture $installdir/btsync",
        path   => "/usr/bin:/usr/sbin:/bin",
        unless => "diff $syncdir/btsync_$architecture $installdir/btsync >/dev/null",
        require => File["$syncdir"],
        notify => File["$installdir/btsync"],
    }
    file { "$installdir/btsync":
        ensure => file,
        mode   => 740,
        owner  => $btuser,
        group  => $btuser,
    }
    
    # configuration file for basic settings. Note that template is inserting
    # machine-specific values for:
    # * hostname
    # * webUI listen IP address (set to my VPN IP)
    file { "$installdir/sync.conf":
        ensure => file,
        mode   => 640,
        owner  => $btuser,
        group  => $btuser,
        require => File["$syncdir"],
        notify  => Service["supervisor"],
        content => template("btsync/sync.conf.erb"),
    }
    
    # supervisord because no init.d script. And keeps the thing running if it falls down.
    # Restart fails without the custom "restart" and the sleep period.
    package { 'supervisor': }
    service { 'supervisor':
        ensure     => running,
        restart    => "/etc/init.d/supervisor stop && sleep 3 && /etc/init.d/supervisor start",
        subscribe  => File['/etc/supervisor/conf.d/btsync.conf'],
        require => Package["supervisor"],
    }
    file { "/etc/supervisor/conf.d/btsync.conf":
        ensure => file,
        mode   => 640,
        owner  => root ,
        group  => root,
        require => Package["supervisor"],
        content => template("btsync/btsync.conf.erb")
    }
    
}

Two file templates are referenced, and can be downloaded from here:

[1] http://labs.bittorrent.com/experiments/sync.html

posted at: 03:18 | path: /SW/fileSharing/btsync | permanent link to this entry

Sun, 07 Apr 2013

/SW/business/SugarCRM: SugarCRM's "Silent Upgrade"

Lately SugarCRM's up-until-recently rock-solid upgrade process has become flaky, and I have had to turn to the "silent upgrade" tool to get the job done. I have not yet stumbled across official documentation, but this[1] does the trick for me.

The first step is to get the upgrade zip, for example SugarCE-Upgrade-6.5.x-to-6.5.12.zip, onto the server. Then just run something like this:

php -f /home/sugartest/public_html/modules/UpgradeWizard/silentUpgrade.php /home/clayton/SugarCE-Upgrade-6.5.x-to-6.5.12.zip /tmp/sugarUpgrade.log /home/sugartest/public_html/ admin

where most of the parameters should be fairly self-evident: the last is the account name you login to SugarCRM with, the second last is the path to the SugarCRM installation you are upgrading.

Then you probably have to correct the permissions, as you probably ran the above as root:

chown -R www-data:sugarcrm public_html/

And finally login to SugarCRM and click through the menus to do the following:

Admin --> Repair --> Rebuild Relationships

[1] http://www.hostknox.com/tutorials/sugarcrm/silent-upgrade

posted at: 04:01 | path: /SW/business/SugarCRM | permanent link to this entry

Fri, 30 Mar 2012

/SW/chat: An Unofficial but Working QQ Plugin for Pidgin

The official Pidgin QQ support disappeared[1] quite some time ago after it stopped working. However, there is a Chinese project[2] on Google Code that is currently delivering a working Ubuntu deb package. On my Debian testing machine, to /etc/apt/sources.list, per [3] I added

deb http://ppa.launchpad.net/lainme/libqq/ubuntu precise main

then

apt-key adv --keyserver keyserver.ubuntu.com --recv-keys 7C24E5AB949045F5

to avoid key complaints in the install, and then:

apt-get update
apt-get install libqq-pidgin

followed by a Pidgin restart, and QQ appears as an account option. All I needed to authenticate were my QQ userid and password, it just worked, and so far no sign of those annoying captchas!

Lord, am I glad to get rid of those official, closed-source QQ clients! Running that stuff, even WebQQ, on my personal machine gave me a SEVERE case of the creeps. Mind you, it must be noted that packages pulled from PPA are unofficial, but they are 100% Open Source with the code available for all to see, and I am seeing at least five people declared as working on the project. A worthy project for someone with free time....

[1] http://developer.pidgin.im/ticket/13193
[2] https://code.google.com/p/libqq-pidgin/
[3] https://code.google.com/p/libqq-pidgin/wiki/UbuntuUsers

posted at: 21:54 | path: /SW/chat | permanent link to this entry

Tue, 25 Oct 2011

/SW/business/Drupal: Drupal Migrate Module Basics

The Drupal migrate module[1] is an impressive tool for migrating databases from other web applications (or anywhere, really) into the Drupal database. It even has fairly impressive documentation[2], but not unlike a lot of other big chunks of documentation, it can be hard to extract from the documentation where to start in creating a simple functional example of the migrate module at work. Hopefully this example will help to fill that gap a little.

First install and enable the migrate family of modules in a sandbox Drupal site:

drush dl migrate migrate_example migrate_extras migrate_ui
drush en migrate migrate_example migrate_extras migrate_ui

If you then point your browser at:

drupal/?q=admin/content/migrate

you will see the migrate module's UI, which shows a couple of example migrations ("beer" and "wine") already coded and setup for you by the migrate_example sub-module. You can play with importing and rolling back data with the UI, or with drush:

drush help --filter="migrate"

To create your own migration, you need to create a custom module containing the migrate code. Using a MySQL database from another application, and based upon the beer.inc example from migrate_example, I was able to get a working migrate setup with three fairly small files in a new sub-module called "migrate_test" in sites/all/modules/migrate/migrate_test/ :

sites/all/modules/migrate/migrate_test/migrate_test.module:

sites/all/modules/migrate/migrate_test/migrate_test.info:

sites/all/modules/migrate/migrate_test/langex.inc:

Note that this is a "cross-database migration"[3]. The source data and the destination data are located on the same MySQL server, but in different databases.

[1] https://drupal.org/project/migrate
[2] https://drupal.org/node/415260
[3] https://drupal.org/node/1014558

posted at: 05:13 | path: /SW/business/Drupal | permanent link to this entry

Sun, 18 Jul 2010

/SW/business/Drupal: Youku & Tudou Videos in Drupal

For websites targeting users in mainland China, one of the issues is that many common services like Youtube and Google Video are blocked / censored from within China. For this specific case of video, there are a number of similar local Chinese video services that can be used instead.

Most ex-China video services seem to make it easy to embed their videos in other sites by prominently displaying a button which will generate the javascript code necessary for embedding a video in another site. For whatever reason, the Chinese sites do not seem to be so helpful.

First of all, in Drupal, turn on the PHP module. Then select "Create Content" and some content type to get to the content creation page. Select "PHP code" in the "Input Format" sub-section. And finally, for a youku[1] video, paste the following code into the content area:

This is the video generated by the above:

Youku video links are of the form http://v.youku.com/v_show/id_XMTkwNDgzMjE2.html

Note the part between the "id_" and the ".html", ie. XMTkwNDgzMjE2. This is the part of the link that must be swapped into the above code for XNDg5MTMwMDQ in order to make it work for a different video.

Similarly, for tudou[2] videos, use this code:

which produces this video:

Use a Flash Player to play Video from TUDOU - http://sites.google.com/site/annuairevin/flash-reader

Tudou video links are of the form http://www.tudou.com/programs/view/eD1xQ0WTlI8/

Swap "eD1xQ0WTlI8" in the latter link for "rsOg3YPXjDg" in the code above to make the code work for a different video.

[1] http://www.youku.com/
[2] http://www.tudou.com/

posted at: 03:02 | path: /SW/business/Drupal | permanent link to this entry

Sun, 30 May 2010

/SW/business/Redmine: Installing Redmine on Debian Linux

I have found Redmine to be extremely sensitive to the Ruby environment, often requiring that librairies be of exactly a certain version (not older, not newer). Configuration documentation is not sufficiently detailed. And error and diagnostic information is extremely difficult to obtain in a typical hosting account.

So if you are trying to install Redmine in a hosting account that supports Ruby on Rails, you would be well-advised to get the application running first in a controlled environment where you have root. In my case, that was my Debian Linux desktop. After flailing around for hours in the hosting account, everything simply fell into place when I went back to basics and installed the Redmine application locally.

These[1][2] were the main references for getting this working on Debian.

apt-get install ruby rake rubygems libmysql-ruby
gem install rails -v=2.3.5 (takes quite a while!)
gem install rake -v=0.8.3
gem install hoe -v=1.3.0

Checkout a fresh copy of the latest Redmine stable, currently:

svn co svn://rubyforge.org/var/svn/redmine/branches/0.9-stable redmine-0.9

Start the native Ruby web server and see what happens:

cd [...]/redmine-0.9
ruby script/server production

At this point I got a complaint about a missing database.yml. In my case, I was actually migrating Redmine from one hosting account where it suddenly broke, to another hosting account. So I installed the MySQL database from the old account to a database called mentage_redmine, then created a config/database.yml as follows:

production:
  adapter: mysql
  database: mentage_redmine
  host: localhost
  username: mentage_redmine
  password: ***********
  encoding: utf8
 
development:
  adapter: mysql
  database: mentage_redmine
  host: localhost
  username: mentage_redmine
  password: ***********
  encoding: utf8

Restart the server: this time an "Internal Server Error" that gave very specific instructions about adding a line pertaining to cookies to the config/environment.rb file. After adding this line, it basically worked.

In my particular case, again because I was migrating an existing application, in the new site I replaced the public/images, javascripts, stylesheets, and themes directories with those from the old site's public directory. After that, everything looked right as well.

[1] http://www.redmine.org/wiki/1/RedmineInstall
[2] http://www.redmine.org/wiki/1/HowTo_Install_Redmine_in_a_home_directory_on_Debian

posted at: 07:30 | path: /SW/business/Redmine | permanent link to this entry

Sat, 29 May 2010

/SW/business/Redmine: Installing Redmine in a Hostgator Hosting Account

To their credit, Hostgator[1] actually provides some documentation[2] about getting Ruby applications working in their hosting account. I, however, found them to be inadequate, and debugging information availability was little to none, so for me the magic key was getting Redmine working first on my desktop, then migrating to the Hostgator hosting account.

One of the first things one notices when looking at the rather sparse Redmine installation manual[3] is the need for specific versions of a number of Ruby librairies. This is what I found:

My Debian Desktop Hostgator Account

rails (2.3.5) rails (2.3.8)

rack (1.0.1) rack (1.1.0)

rake (0.8.3) rake (0.8.7)

hoe (1.3.0) hoe (2.6.0)

In the Hostgator account, I got the above librairy versions using "gem list --local". I then installed in the account the correct versions as follows:

gem install rails -v=2.3.5
gem install hoe -v=1.3.0

Now transfer Redmine from desktop to Hostgator, placing it in /home/mentage/redmine-0.9.

In /home/mentage/public_html, create the following symlink: redmine -> /home/mentage/redmine-0.9/public/

Hostgator is using Apache to server up Ruby applications. Create a public/.htaccess[2] file with the following contents:

AddHandler fcgid-script .fcgi 
     AddHandler cgi-script .cgi 
     Options +FollowSymLinks +ExecCGI 
  
     RewriteEngine On 
     RewriteCond %{REQUEST_URI} ^/notrails.* 
     RewriteRule .* - [L] 
  
     RewriteRule ^$ index.html [QSA] 
     RewriteRule ^([^.]+)$ $1.html [QSA]     
     RewriteCond %{REQUEST_FILENAME} !-f 
     RewriteRule ^(.*)$ dispatch.fcgi [QSA,L]

After that, it worked for me by pointing a browser at the redmine directory.

[1] http://www.hostgator.com/
[2] http://forums.hostgator.com/ruby-rails-support-t13038p8.html
[3] http://www.redmine.org/wiki/1/RedmineInstall

posted at: 09:08 | path: /SW/business/Redmine | permanent link to this entry

Sun, 10 Jan 2010

/SW/business/Drupal: My Favorite Drupal Modules

(As of Drupal version 6.x....)

Drupal is a very mature piece of software, with a vast number of modules to choose from, often with multiple modules vying to provide the same piece of functionality. After some trial and error, here are my candidates for "best of", modules someone new to Drupal should look into early:

First some easily overlooked core modules:

PHP filter: useful even if you do not know what PHP is (the language that Drupal happens to be coded in). There are a number of modules out there promising to "make it easy" to incorporate things like Youtube videos and Google Adsense ads into your site. You do not need those modules, because all you need to do to make this happen is to copy a bit of Javascript from the source site into the editing page for the node or block where you want the ad or video to appear. Generally speaking, Drupal will ignore user-entered Javascript, unless you turn on "PHP code" in the "Input format" section.
Taxonomy: If you need to organize content into categories, this is where you go.
Trigger: On the admin page there is an item called "actions" where you can define things you want your site to do automatically. And then under "trigger", you can specify the criteria for when that action will be taken. For example, this is the mechanism by which my sites send me an e-mail when a new comment has been posted and I need to take care of the moderation queue.

Third-Party modules:

Content Construction Kit (CCK)[1]: one of the modules that truly sets Drupal apart from the competition. The basic function of CCK is to allow the user, via the Drupal GUI, to create custom databases within Drupal. Which is to say, you can add custom fields to any content, and control read/write access on a per-field basis.
Views[2]: Views and CCK usually travel in a pair, since Views allows the user (via Drupal GUI) to construct and display custom queries of almost any data in the Drupal database. As a very simple example, Drupal does not come equipped with a comment RSS feed, and one can easily create such a feed with Views.
Image[3] / Image FUpload[4]: the image module seems to be the standard way to add photo upload and management to a Drupal site. The image module supports bulk uploads via FTP. If you wish to do bulk upload multiple photos using the Drupal site, add the "Image FUpload" module.
Lightbox2[5]: drop this module in for elegant AJAX "lightbox" displays of photos and galleries. ("Lightbox" refers to a standard effect where, if you click on a photo in a gallery, the whole page fades to a dark gray background while a white box pops up in the middle to display the photo. Delete the box and the background page brightens and again becomes the foreground.)
Boost[7]: As a web application Drupal can sometimes be a bit of a resource hog, particularly if there are a lot of modules installed. If the host server is a bit light on memory, the result can be sluggishness. Boost is very simple in concept: pages referenced by anonymous users are stored in an Apache cache, such that when cached pages are served up Drupal is taken completely out of the picture: no PHP or MySQL overhead, your website performs like a static site. Until the cache expires, of course, and pages have to be regenerated once per caching period.

Here is someone else's list of favorites[6].

[1] http://drupal.org/project/cck
[2] http://drupal.org/project/views
[3] http://drupal.org/project/image
[4] http://drupal.org/project/image_fupload
[5] http://drupal.org/project/lightbox2
[6] http://www.nicklewis.org/40-essential-drupal-6-modules
[7] http://drupal.org/project/boost

posted at: 22:40 | path: /SW/business/Drupal | permanent link to this entry

Thu, 17 Dec 2009

/SW/business/Drupal: Comparisons of Drupal and Joomla

Back some time ago when I was trying to figure out which Content Management System to use for a couple of website development clients, I do not remember seeing any definitive reviews. In the end, I think I made the correct choice (Drupal) for the situation despite the limited amount of information, but I see now that there might be some situations (event calendaring? desire for a simpler admin interface?) where Joomla might be the right choice.

Here are some references I would like to preserve for posterity:

http://www.alledia.com/blog/general-cms-issues/joomla-and-drupal-version-2/
http://www.topnotchthemes.com/blog/090224/drupal-vs-joomla-frank-comparison-ibm-consultant
http://www.communicopia.com/blog/joomla-versus-drupal
http://www.goodwebpractices.com/other/wordpress-vs-joomla-vs-drupal.html

posted at: 08:16 | path: /SW/business/Drupal | permanent link to this entry

Sun, 06 Dec 2009

/SW/business/Drupal: Drupal User Manual: How to Edit Content

This post aims to provide the basic knowledge required to begin editing Drupal content.

First and most basically, you require an account on the Drupal website you wish to edit. After login, if you click on any menu item to navigate to that page, if you have the privileges to edit that page, you will see an edit (编辑) button or link (this depends on the theme being used) at the top of the page. Click on edit / 编辑, then edit and save the page.

After you have logged in, if you have been given some admin privileges on the site, you will see an Admin (管理) link in your personal menu under "My account" (我的帐户). Another way to see and edit the pages on the site is to click on "My account" / 我的帐户, and then click on "Content management/Content" (内容管理/内容). You will then be presented with a list of all the content items on the site, which you may then choose to edit individually, or perform various bulk operations on (deleted large quantities of spam posts, for instance).

To create new content, click on "Create content" (创建内容) and select a content type. For ordinary website page content, you probably want to choose "Page" content. After you click on "Page" and write your content, do not forget to expand the "Menu settings" (菜单设置) and enter a "Menu link title" (菜单链接名称) and select the menu position from the "Parent item" (上级菜单项) dropdown list. (You probably want to select "Primary Links" or one of the items under "Primary Links".)

Finally, you will probably want to re-arrange the order of the "Primary Links" in the navigation menu at the top of the site. To do this, click on "Admin" --> "Site building/Menus" --> "Primary links" (管理 --> 站点构建/菜单 --> "Primary links"). To change the order or position of menu items, just grab the "+" with your mouse pointer and drag'n'drop. For dropdown menus it is also good practice to click the "Expanded" (展开) checkbox to enable submenus. And finally, click "Save Configuration".

posted at: 23:17 | path: /SW/business/Drupal | permanent link to this entry

Wed, 14 Oct 2009

/SW/business/SugarCRM: SugarCRM Built-in Data Tranfer Tool is Highly Developed

SugarCRM is fundamentally a big, complicated address book, and any migration to SugarCRM can often reasonably include a wish to import a bunch of contact data from another application. In my case, I have a MySQL database.

To get this database into SugarCRM is basically a two-step process:

First compare Sugar's existing Account/Contact fields and the fields in the database to see what matchs and what does not. Then in the Admin section of the user interface, use the "Studio" application to create new custom fields where necessary, by clicking on "Fields" under "Contacts" and/or "Accounts". And then do not forget to add those new fields to a form in the corresponding "Layouts" subsections. Click "Save & Deploy" and you are done.
Then export the MySQL database table into a .csv file (phpmyadmin works well for this) click on the "Accounts" tab in Sugar, then "Import" to process the .csv file. In the resulting display, just match up Sugar fields with the fields in the .csv file, then click "Import Now". Several iterations of this may be required to repair bad fields in the database, mainly messed-up e-mail addresses. Once the accounts are imported, just repeat the same process by clicking on Sugar's "Contacts" tab and "Import" to strip out the contact information in the same database. Note that selecting the same "Account ID" when importing an account and its matching contacts allows the contacts to continue to be associated within Sugar, under the same Account.

This all works quite well as of SugarCRM version 5.5. 5.2 does not work so well: e-mail addresses do not import as they *all* trigger a syntax error, Account/Contact association is lost, etc. If you are doing a substantial data import I recommend you go right for the not-yet-stable version 5.5. It is a release candidate so it will be the new stable very soon.

posted at: 01:31 | path: /SW/business/SugarCRM | permanent link to this entry

Home

Contact

Links

Categories:

Archives:

Subscribe XML RSS Feed

This site has no ads. To help with hosting, crypto donations are accepted:
Bitcoin: 1JErV8ga9UY7wE8Bbf1KYsA5bkdh8n1Bxc
Zcash: zcLYqtXYFEWHFtEfM6wg5eCV8frxWtZYkT8WyxvevzNC6SBgmqPS3tkg6nBarmzRzWYAurgs4ThkpkD5QgiSwxqoB7xrCxs

Wed, 27 Jul 2016

Sun, 07 Feb 2016

Mon, 02 Dec 2013

Thu, 18 Jul 2013

Thu, 11 Jul 2013

Sun, 07 Apr 2013

Fri, 30 Mar 2012

Tue, 25 Oct 2011

Sun, 18 Jul 2010

Sun, 30 May 2010

Sat, 29 May 2010

Sun, 10 Jan 2010

Thu, 17 Dec 2009

Sun, 06 Dec 2009

Wed, 14 Oct 2009

My Debian Desktop	Hostgator Account
rails (2.3.5)	rails (2.3.8)
rack (1.0.1)	rack (1.1.0)
rake (0.8.3)	rake (0.8.7)
hoe (1.3.0)	hoe (2.6.0)

Home

Contact

Links

Categories:

Archives:

Subscribe XML RSS Feed

This site has no ads. To help with hosting, crypto donations are accepted: Bitcoin: 1JErV8ga9UY7wE8Bbf1KYsA5bkdh8n1Bxc Zcash: zcLYqtXYFEWHFtEfM6wg5eCV8frxWtZYkT8WyxvevzNC6SBgmqPS3tkg6nBarmzRzWYAurgs4ThkpkD5QgiSwxqoB7xrCxs

Wed, 27 Jul 2016

Sun, 07 Feb 2016

Mon, 02 Dec 2013

Thu, 18 Jul 2013

Thu, 11 Jul 2013

Sun, 07 Apr 2013

Fri, 30 Mar 2012

Tue, 25 Oct 2011

Sun, 18 Jul 2010

Sun, 30 May 2010

Sat, 29 May 2010

Sun, 10 Jan 2010

Thu, 17 Dec 2009

Sun, 06 Dec 2009

Wed, 14 Oct 2009

This site has no ads. To help with hosting, crypto donations are accepted:
Bitcoin: 1JErV8ga9UY7wE8Bbf1KYsA5bkdh8n1Bxc
Zcash: zcLYqtXYFEWHFtEfM6wg5eCV8frxWtZYkT8WyxvevzNC6SBgmqPS3tkg6nBarmzRzWYAurgs4ThkpkD5QgiSwxqoB7xrCxs