How to import users from a CSV file in acyMailing component

How to import users from a CSV file (comma-separated values):
Step 1:

The first line of your CSV file should indicate to AcyMailing the name of the fields to import. For example, if your file contains a list of users with the format “email,name,listids”, the first line of your file should be : email,name,listids (always in English). So if you have a file with only e-mail addresses the first line of your file will be : email
remember to always edit your file’s first line so that AcyMailing knows how to import the new users. The following phrases can be used to import to their relevant fields:

  • email- The email adress of the new user in the file
  • name- The name of the new user (AcyMailing can automatically generate a name using the email address)
  • listids- the id number of the list you want the new user to be subscribed to.
  • confirmed- the values should be 0 (for not confirmed) or 1 (for confirmed). If you don’t specify this column in your file, the default value is 0 (not confirmed).
  • html- the values should be 0 (receive Text) or 1 (receive HTML). If you don’t specify this column in your file, the default value is 1 (receive HTML).

Step 2:

After you have edited your CSV file you log into the back end of your site (www.yoursite/ click on “Components” and then “AcyMailing”

navigate to acymailing
Step 3:

Click on “Users”, its the first item under the toolbar

click on users
Step 4:

In the top right toolbar click on “Import” button

Step 5:

In this menu you can select if you would like to Import the users as confirmed etc, and also which list you would like the new users to be imported to. (note: you can do this instead now of doing it in step 1, But the CSV file “MUST” be edited on its first line)
Click on “browse” button


Browse to the location that the edited CSV file is saved and open it. Then click on “Import” button in top right

browse to
Step 6:

A notification will appear informing you of the new users that have been imported from the CSV file.



the basics of cloud computing and google apps

What is Cloud computing?

Cloud computing is the next stage in the Internet’s evolution, providing the means through which everything — from computing power to computing infrastructure, applications, business processes to personal collaboration — can be delivered to you as a service wherever and whenever you need.

The “cloud” in cloud computing can be defined as the set of hardware, networks, storage, services, and interfaces that combine to deliver aspects of computing as a service. Cloud services include the delivery of software, infrastructure, and storage over the Internet (either as separate components or a complete platform) based on user demand. (See Cloud Computing Models for the lowdown on the way clouds are used.)

Cloud computing has four essential characteristics: elasticity and the ability to scale up and down, self-service provisioning and automatic deprovisioning, application programming interfaces (APIs), billing and metering of service usage in a pay-as-you-go model. (Cloud Computing Characteristics discusses these elements in detail.) This flexibility is what is attracting individuals and businesses to move to the cloud.

the world of the cloud has many of participants:

  • The end user who doesn’t have to know anything about the underlying technology.
  • Business management who needs to take responsibility for the governance of data or services living in a cloud. Cloud service providers must provide a predictable and guaranteed service level and security to all their constituents. (Find out what providers have to consider in Cloud Computing Issues.)
  • The cloud service provider who is responsible for IT assets and maintenance.

Cloud computing can completely change the way companies use technology to service customers, partners, and suppliers. Some businesses, such as Google and Amazon, already have most of their IT resources in the cloud. They have found that it can eliminate many of the complex constraints from the traditional computing environment, including space, time, power, and cost.

cloud computing: A networking solution in which everything — from computing power to computing infrastructure, applications, business processes to personal collaboration — is delivered as a service wherever and whenever you need.

cloud service: The delivery of software, infrastructure, or storage that has been packaged so it can be automated and delivered to customers in a consistent and repeatable manner.

Google apps advantages

  • Your work is always backed up, While you work, all your critical data is automatically backed up on Google servers. So when accidents happen – if your computer crashes or gets stolen – you can be up and running again in seconds.
  • You own and control your data, When you put your data in Google Apps, you still own it, and it says just that in our contracts. Apps’ powerful, easy-to-use tools help administrators manage things like users, documents and services, and keep track of usage and data via dashboards.
  • Increased security and reliability, data centers are designed and built for our applications and don’t include unnecessary hardware or software. This reduces the number of potentially exploitable vulnerabilities.
  • Strong encryption and authentication, Google Apps offers an extra layer of security with two factor authentication, which greatly reduces the risk of hackers stealing usernames and passwords. We also automatically encrypt browser sessions with SSL for Apps users without the need for VPNs or other costly, cumbersome infrastructure. This helps protect your data as it travels between your browser and our data centers.
  • Stay connected from anywhere, With Google Apps, all your work is automatically saved in the cloud. You’ll have access to your email, calendar, documents, and sites and be able to work securely, no matter where you are in the world and what device you’re on. For your business, this means every employee and everyone you work with can be productive from anywhere, using any device with an Internet connection.

Installing LAMP on Ubuntu 12.04 Precise Pangolin

When working on web development, I prefer to work within the privacy of my own development environment located on my computer. I’d rather make the majority of my mistakes where no one else can see them rather than out in the wild of the Internet. In order to have that private development environment, I install a LAMP configuration. If you’re not familiar with LAMP, it stands for Linux, Apache, MySQL, php (and/or Perl). LAMP is one of the most common web hosting platforms on the Internet, so it’s a great environment to build and test your website. Follow these step by step instructions to install and configure LAMP on Ubuntu

Install LAMP on Ubuntu

The developers at Ubuntu have made it really easy to install and configure the packages for LAMP with a single terminal command. So open up a terminal window and let’s get started.

sudo apt-get install lamp-server^

Yes, you read that right. Don’t leave out the caret (^) at the end. The command won’t work without it. It’s magical!

sudo apt-get install lamp-server^

The apt package manager will now show the packages to be installed and ask for confirmation. Hit <Enter> to confirm and continue with the install.

Install LAMP packages

After some time downloading packages, you will be prompted to set a password for the root user for MySQL.

Set MySQL root password

Enter the password you want to use for MySQL. Do not leave it blank. You’ll be prompted a second time to confirm your password.

Confirm MySQL root password

After confirming your password, apt will continue installing the remaining packages.

Remaining LAMP package installation

Your LAMP installation is now complete. Wow, that was easy! Now there’s just a few more steps to get things configured to make it easy to work with your system.

Test Apache

Open a web browser window and enter the address http://localhost/. You should see a web page that says “It Works!
Apache works

Test php

Now that you’ve confirmed that the Apache web server works, you want to make sure that your php installation is working. To do that you need to create a file in /var/www called testing.php. You can use your favorite text editor as root, or you can use the following terminal command:

echo “” | sudo tee /var/www/testing.php

Go back to your web browser and enter the address http://localhost/testing.php/ and you should see a page displaying information about your php installation.

php information
Fix Apache fully qualified domain name

You may have noticed an error message from Apache about the server’s fully qualified domain name.

apache2: Could not reliably determine the server’s fully qualified domain name, using for ServerName

This is not a big deal, but if it bothers you, you can fix it with the following commands.

echo “ServerName localhost” | sudo tee /etc/apache2/conf.d/fqdn

Now reload the Apache web server.

sudo service apache2 reload

You should no longer see the error message.

Configure MySQL

Since this tutorial is for setting up a local web development environment, the MySQL needs to be bound to the localhost IP address. By default this should be on your system. Just in case, you can verify it with these commands.

cat /etc/hosts | grep localhost

You should see something like: localhost
::1 ip6-localhost ip6-loopback

You now want to verify that you have the correct bind address in MySQL’s my.cnf file.

cat /etc/mysql/my.cnf | grep bind-address

You should see:
bind-address =

If the bind address doesn’t match the one set for localhost on your system, you’ll need to edit /etc/mysql/my.cnf as root to correct it.

Install phpMyAdmin

You don’t need to install


, but unless you’re a wizard with SQL, you’ll want it to do administrative tasks on your MySQL databases.

You can install phpMyAdmin with this terminal command:

sudo apt-get install libapache2-mod-auth-mysql phpmyadmin

You’ll be prompted to confirm that you want to install the packages. Hit <Enter> to continue.

Install phpMyAdmin packages

You’ll next be prompted to select a web server to configure with phpMyAdmin. This is important! Use the arrow keys on your keyboard to highlight apache2 and then used the space bar to select it. Then hit <Enter> to continue. Make sure to click the picture below to see it in full size to see what I’m describing.

Configure phpMyAdmin for Apache

The next screen will ask if you want to configure


with a database called


Select “Yes” and hit <Enter>.

phpMyAdmin configure dbconfig-common

You’ll next be prompted to enter the MySQL root password you created earlier so that the new database can be created. So enter your MySQL root password and hit <Enter>.

Enter MySQL root password

The next prompt is to create a MySQL application password for phpMyAdmin. You can hit <Enter> if you want a random password to be created. I usually use the same password that I used for the MySQL root password. It’s probably not the greatest idea in terms of security, but since this is for a closed development environment, it’s probably low risk.

phpMyAdmin MySQL application password

Finally, you’ll be prompted to confirm your MySQL application password. Type the same password as the previous step and hit <Enter>.

Confirm MySQL application password

Installing and configuring phpMyAdmin is now complete.

Testing phpMyAdmin

The last step is to make sure that phpMyAdmin is working. Open a web browser and enter the address http://localhost/phpmyadmin/. You should see a page that looks like this.

phpMyAdmin login screen

You should now be able to log in with the username root and the root password that you created earlier.

phpMyAdmin logged in

Congratulations, you are now done installing and configuring LAMP and phpMyAdmin on Ubuntu 12.04. You can now start building the local version of your website. If you are only working on one site, you can place your files in /var/www. Note that /var/www is owned by the user and group root, so you will either need to copy files over as root, or change the ownership and/or permissions of that directory so you can write your files there. As an alternative, you can do some additional Apache configuration so that you can keep your files somewhere under your home directory. You can even set up multiple sites that way.

Courtesy of tuxtweaks


The Original Web developer


Internet problems


User Group Access levels explained in simple terms

Joomla controls access to certain areas and features of a site through use of a basic ACL, or Access Control Level mechanism called Groups. Certain groups have certain access level features and they are directly related to the creation, editing and publishing of content (through the Frontend and Backend interfaces) as well as to access to the Administrative (Backend) interface.

Each group has different levels of access control and once a user is made a member of that group, they inherit those rights. Note that the ‘Public Front-end’ and ‘Public Back-end’ groups are merely placeholders at this point in time. They are not valid group selections at this time, but in the future, they will define the default access levels for anonymous users in the Front-end and Back-end systems.

The Joomla ACL has been completely reworked in Joomla 1.6 (released in Jan 2011) further information on the new ACL mechanis can be read here [1] and in many other places on-line.

There are four (4) Front-end groups available:

Registered – This group allows the user to login to the Frontend interface. Registered users can’t contribute content, but this may allow them access to other areas, like a forum or download section if your site has one.

Author – This group allows a user to post content, usually via a link in the User Menu. They can submit new content, select options to show the item on the front page and select dates for publishing but they cannot directly publish any content. When content is submitted by an Author level user, they receive the message, “Thanks for your submission. Your submission will now be reviewed before being posted to the site.” They can edit only their own articles but only when that article has been published and is visible.

Editor – This group allows a user to post and edit any (not just their own) content item from the Frontend. They can also edit content that has not been published. If your site uses the default installation’s menu option “News”, which is a Table List – Content Section type, Editors will see unpublished articles in the list that they can select for editing, where as an Author or Public (unregistered) user will not even see the unpublished items in the list. Still, Editor users cannot, publish or change the publishing status of any articles, even their own.

Publisher – This group allows a user to post, edit and publish any (not just their own) content item from the Front-end. Publishers can review all articles, edit and change publishing options but the can also determine when an article is ready for publication, making it visible to Registered, Author and the Unregistered Public (depending on what visibility was chosen in the article, of course!)

There are three (3) Administration section groups that allow access to Joomla:

Manager – This group allows access to content creation and other system information from the Backend. Think of Manager users as Publishers, with Backend access. They can log in through the Administrator interface, but their rights and access are generally restricted to content management. They can create or edit any content, access to some Backend only features like adding, deleting and editing Sections and Categories, editing the Front Page and Menus, but they don’t have any access to the “Mechanics” of Joomla, like user management or the ability to install components or modules. Note that if a Manager logs in through the Frontend interface, they’re treated just like a Publisher, with the same rights and access.

Administrator – This group allows access to most administration functions. An Administrator user has all the privileges on the back end of a Manager, but they also have access to set options on, and install/delete components, modules and bots, User Manager access and can view the site statistics. What they cannot do however is change, edit or install Site Templates or make any changes to the sites Global configuration options. On login through the Frontend, they are treated as Publishers, just like the Manger users. Interesting to note; when an Administrator accesses the User Manager list, they will see all users at their access level or below; in other words they can modify any user EXCEPT a Super Administrator – in fact, they will not even see Super Administrator accounts in the list! Also, they cannot create additional Super Administrator level accounts, only a Super Admin can do that.

Super Administrator – This group allows access to all administration functions. Only another Super Administrator can create or edit a Super Administrator user account. Full access to ALL AREAS is given to Super Administrators, and once created they cannot be as easily deleted. It might not be obvious, but you have to change the user’s group to something other than Super Administrator first. Then you can delete them.

Because of this, give a bit of thought to who you need to grant this highest level of access to. Super Admins can block the user from logging in or change the password on another SA account. Like the other Backend user accounts, SA’s are treated as Publishers when they login through the Frontend interface.


As mentioned previously, the Joomla ACL has been completely re-written for Joomla! 1.6 to provide new features and greater control.

Many third-party extensions exist to extend the Joomla ACL, but due diligence should be exercised with ANY ACL extension – not only in how it affects currently available extensions for Joomla, but also how it may or may not cooperate with future releases of Joomla.

Courtesy of Joomla Documentation


How to set up your email on BlackBerry

  • Make sure you’ve enabled IMAP in your Gmail account.
  • On your BlackBerry®, navigate to your home screen.
  • Select the icon that lets you set up email (this can be called Setup, Setup Wizard, Email Setup, BlackBerry® Set-up, E-mail settings, or Personal Email Set-up).
  • Follow the setup instructions provided on your device to create a new email account.
  • Be sure to enter the following:

    Mail Server:
    Username: [your full Gmail address (]
    Password: [your Google Apps password]
    IMAP Port: 993

  • Allow the system to add your account, but do not enter your Google Apps password into the utility boxes (this causes the system to default to POP3 instead of IMAP).
  • Select Next.
  • Select Next again (bypassing the Additional Information Required section).
  • Select your account type, and then select Next. You may encounter a “We were unable to configure…” error. If so, select I will provide the settings to continue.
  • Select the option that mentions IMAP/POP.
  • Select I will provide the settings…, and then select Next.
  • Select Set up existing email account…
  • Enter your Gmail account information here, with as your mail server.
  • Select Next.
  • Select Save.

Support, anybody?


Correct HTML coding?


Funny Pics

Rethink your websites name?