cPanel Podcasts

cPanel officially launched its podcast series Sunday, August 1, 2010, www.cpanel.net/podcast. The cPanel team added this new multimedia addition to provide listeners with practical instruction for improving their websites.

Every two weeks, Technical Writer Lindsey White will interview cPanel experts and investigate a variety of subjects to help listeners learn more about cPanel products.

The cPanel podcast team will release a new episode on a bi-weekly basis as well as offer information about the next episode via the podcast site. There is a pre-released schedule for the first three podcasts in the series, which includes:

Podcast Overview

  • Episode 1- “How to Install WordPress in cPanel”
    • Will go through the basic steps to help answer this commonly asked question
    • This podcast became available August 1, 2010.
  • Episode 2- “Secure Sockets Layer (SSL) Certificates Demystified”
    • Will explain how SSL certificates can be used to make a website more secure
    • This podcast will be available August 15, 2010
  • Episode 3- “Installing Custom Web Applications
    • Will provide listeners with insight into the process of installing web applications in cPanel
    • This podcast will be available September 1, 2010

Podcast episodes will be available via direct download from the cPanel Podcast site. Listeners will also have the option to subscribe via RSS feed or through iTunes.

Listeners may visit http://www.cpanel.net/podcast for more information about the cPanel podcast series.

cPanel 11.25.1 Database Mapping!

Got a technical advisory this morning, though I would share with the rest of the world!

With version 11.25.1, cPanel introduces the Database Mapping feature. This feature lays the groundwork for providing more flexibility in naming databases and database users.

In the past, cPanel has always appended an account’s username to any database name or database username created by the account (for example, a database might be named “user_dbname”). This changes with the addition of the Database Mapping feature.

In cPanel 11.25.1, Database Mapping provides the following benefits:

1. Accounts transferred from non-cPanel servers, such as those running Plesk or Ensim, will no longer have the cPanel account name added as a prefix to the names of databases and database users. This means applications like blogs and forums should work with minimal (or no) changes after transfer.

2. Server owners can disable use of the database name prefix server-wide. If a server owner chooses this option, databases and database users will no longer be created with the cPanel account as a prefix (for example, a database could be named “dbase” instead of “user_dbase”). This option is not reversible.

Both the above features will make a server incompatible with older versions of cPanel. If either 1) a non-cPanel account is transferred to an 11.25.1 server, or 2) the server owner opts to disable prefixing, then that server will not be able to later downgrade to 11.25.0.

Likewise, transferring an account from a cPanel system that does not use the database prefix to one that does (e.g., cPanel 11.25.1 with prefixing disabled, to cPanel 11.25.0) will result in support issues. Databases and database users whose names lack the prefix will not be manageable in the cPanel interface.

What are your thought’s comments on this?  I personally don’t see this working too well with shared hosts, just due to the sheer numbers of customers.

cPanel’s mailperms not working

I hope I’m not the only one that’s seeing this issue.

/scripts/mailperms is no longer working as of cPanel 11.25:


root@houston [/home/user/mail/learncpanel.com]# stat abuse | grep "dr"
Access: (0743/drwxr---wx) Uid: (32014/user) Gid: (32017/user)
root@houston [/home/user/mail/learncpanel.com]# /scripts/mailperm user
root@houston [/home/user/mail/learncpanel.com]# stat abuse | grep "dr"
Access: (0743/drwxr---wx) Uid: (32014/user) Gid: (32017/user)

I’ve put in a cPanel ticket about this on April 26th, with the reply:

This bug is active in the linux development department for a fix. Once it is fixed, it will be sent to BETA, then EDGE, then CURRENT, then RELEASE, and then STABLE. It can take some time for these to be pushed out.

Hopefully this will be fixed soon, as this is a pretty major script that’s used.