So my Last.fm records plugin that is built-in or implemented with this amazing theme broke after I upgraded it, so I checked and it seems the whole plugin is now using jQuery. I have had to do some modifications to make it work, I hope this helps.

FIrst, you need to add this in your wp-content/themes/absynthe/header.php right after <![endif]-->.

<script type='text/javascript' src='/wp-includes/js/jquery/jquery.js'></script>

After that, you need to edit wp-content/themes/absynthe/footer.php and replace this:

if (function_exists('lastfmrecords_display')) {
lastfmrecords_display();
}
?>

By this:

<div id="lastfmrecords"></div>

Once you’ve made those changes, go to Settings > Last.fm Records, make sure that the CSS is disabled else it won’t look pretty and make sure the placeholder is set to “lastfmrecords”.

Enjoy

I will let the developer of this theme know so he can fix this too.

This little script disables mod_security on specific domains that you pick, mod_security2 does not allow disabling it from .htaccess and it’s pretty annoying to do the same work all over and over again, why not make it one line only.

Introducing, disable_modsec — Enjoy lazy cPanel server admins.

#!/usr/bin/perl

# Enable vHost includes
system ('/scripts/ensure_vhost_includes --user='.$username);
} else {
print("Usage: disable_modsec [domain]\n");
}

This blog looks much better thanks to the awesome Absynthe theme by Chris Wallace who makes awesome wordpress themes (there’s some free SEO for you

Also, he had implemented Last.FM & Twitter integration that’s very prettttttty. Thanks!

Here’s the magical code:

cat /etc/userdomains | awk -F ':' '{ print $1 }' | sed 's/.*\.\(.*\.\)/\1/' | sort -u

First of all, telnet to your switch, these instructions are for Cisco switches, that’s all I ever worked with anyways, heh. All those instructions use IOS.

First of all you need to pick the port that you’ll be working on, make sure you have physical access to the server you’re going to be working with, I’m not responsible for some settings going poof and you having to drive down to your data center to fix the issue.

So, the interface that I will be working with is FastEthernet1/8 — Enter configuration mode and go to the port

conf t
int FastEthernet1/8

Enable trunking and 801q capsulation

switchport mode trunk
switchport trunk encapsulation dot1Q
switchport trunk native vlan 1000

Make sure the native VLAN is the same VLAN that the network was running on previously, read more information why here:

To establish 802.1q trunking both sides must be in the same native VLAN this is because the encapsulation is not setup yet and the 2 switches must talk over an un-encapsulated link (native VLAN) to setup the encapsulation in the first place. Why this works is because neither side is encapsulating packets with its VLAN tag since they are both talking over their native VLAN, basicly neither side knows that the other side is in a different VLAN to begin with and they are just sending unencapsulated packets back and forth. So if you set a port on the core switch as native vlan 5 for example and connected a dumb switch to it vlan 5 traffic would go un encapsulated to the dumb switch and it can understand it but it will put it in its VLAN 1 ports there is no actual trunking going on. No 802.1q or ISL!
juniperr @ DevShed

/usr/local/cpanel/uninstall

And the content:
#!/bin/sh
# Uninstall script for Cpanel
rm -f "/usr/local/cpanel/uninstall"
#### END OF UNINSTALL
echo "Cpanel has been uninstalled."

Nice to know that developers still have a sense of humor. cPanel’s developers are always known to be down to earth guys and I can assure you that’s true! (not if that little bit of code in a production program didn’t prove it! )

Alert: not_in_list_of_allowed_ip [xx.xx.xx.xx]

The IP of the client is located at the “xx.xx.xx.xx” part, this is easily fixed by clearing the block list on the server with this command (on the main node), you must replace the user.vm part by the username of the client at HyperVM (most of the time, something.vm).

/script/clearallowedblockedip --class=client --name=user.vm

It should return something like the following:

AllowedIp Sucessfully cleared for client:user.vm

Afterwards, the client/you should be able to login with no problem at all.

/usr/local/cpanel/bin/update-horde --force

Also, this might be useful to run hourly, I leave this on our servers “just in case”.

(mysqlcheck --auto-repair eximstats ; mysqlcheck --auto-repair horde) >/dev/null 2>/dev/null

First of all, we need to get all the accounts and create a backup of their accounts, this is done using a couple of bash lines and parsing the file /etc/trueuserowners. That file contains every account on the server and the accounts that own it. This following will go over that file, take out the resellers accounts and back them up one by one. The best way to make sure no mistake happens is to ensure that /home or /home2 or any other /home directories because the /scripts/pkgacct creates them there. We also use cpuwatch not to create excessive load on the server when creating the backup. It will stop the process once load averages go higher than 10.

for i in `cat /etc/trueuserowners | grep resellerusername | awk -F ':' '{ print $1; }'`;
do /usr/local/cpane/bin/cpuwatch 10 /scripts/pkgacct $i;
done;

Usually this takes a while so this is what you can do if it’s halfway done to save time

/usr/bin/rsync --delete -avvxHt --progress -e ssh /home/cpmove-* 1.2.3.4:~

This will start moving the files from the old server to the new one, we use rsync so that we can just run it again after the full backup is done so we don’t have to restart the whole process again. Once it’s done and all data has been moved, another loop, I did this one quickly however I think it could be cleaner, if someone has a better way to do with (regexp?), please let me know.

for i in `ls | grep cpmove- | awk -F '.' '{ print $1 }' | awk -F '-' '{ print $2 }'`;
do /scripts/restorepkg $i;
done;

After finishing that, you should be all done!

The only small modification is that now, it deletes all sess_* files that have not been accessed for 5 days therefore are probably just sitting there and never going to be used again, the rest remain deleted because it’s failed uploads/etc that will never be used again.


#!/bin/bash

# Clean up failed ImageMagick conversions.
ls | grep 'magick*' | xargs rm -fv


Thanks!