Fix to the XBMC “could not enumerate file” error

Usu­al­ly, this hap­pens with files being loaded into the library don’t have the required reg­u­lar expres­sion pat­tern that XBMC is look­ing for, when it loads files into the library. That reg­u­lar expres­sion is usu­al­ly in the form of anything_s01e02 for exam­ple (sea­son num­ber, and episode num­ber). When this occurs, you may still view the episodes but you have to go through the “Files” way of view­ing it; not through your TV’s library (like the oth­er TV episodes them­selves).

After going through XBMC wik­i’s page regard­ing “Nam­ing video files/TV shows,” here’s the Nzb­Drone set­tings that I use now to rename my Ani­me episode files:


For easy copy­pas­ta:

  • Stan­dard Episode For­mat
    Ex. Series_Title_2010.s01e01_Episode_Title_(1)
  • Dai­ly Episode For­mat
    Ex. Series_Title_2010.2013–10-30_Episode_Title_(1)
  • Ani­me Episode For­mat
    Ex. Series_Title_2010.s01e01_Episode_Title_(1)
  • Ani­me Episode For­mat
    Ex. Series_Title_2010.s01e01_Episode_Title_(1)
  • Mul­ti-Episode Style = “Extend­ed”
    Ex. Series_Title_2010.s01e01-02_Episode_Title

Increase File Upload Size Limit

I am work­ing on a project that requires high-lev­el users to be able to upload more than the default Word­Press file-upload lim­it. I’ve done this in the past but I have set it to a mul­ti-domain set­ting. Mean­ing that it encom­pass­es all of my domains being host­ed in a par­tic­u­lar Dreamhost user account.

I want­ed to only increase the file size (again) to some­thing much larg­er than I’ve had before but only for a par­tic­u­lar sub­do­main; as I was using it for stag­ing. Here’s the process that I took to make that hap­pen.1

Con­tin­ue read­ing →

  1. These steps are a para­phrase from Dreamhost’s Wiki arti­cle. []

How Not to Use Default Gateway on VPN (PPTP) in Mac OSX

Well, after search­ing for hours and hours, I have final­ly found a solu­tion to a small but trou­ble­some prob­lem. The prob­lem (if you call it that) occurs when I tried con­nect­ing to my work’s VPN. Rather than not using my work’s gate­way when con­nect­ed, OSX does this by default. Hence, you can see and hit your inter­nal IPs but not resolve the rest of the inter­net.

In Win­dows XP, this may be dis­abled via the fol­low­ing:

  1. Open Net­work Con­nec­tions
  2. Under Vir­tu­al Pri­vate Net­work, open the Prop­er­ties of your con­nec­tion
  3. Click and open Prop­er­ties for “Inter­net Pro­to­cal (TCP/IP)”
  4. Click on Advanced
  5. Dis­able “Use default gate­way on remote net­work”
  6. Hit OK, OK, and then you’re done

Although it’s easy in Win­dows XP, I could­n’t fig­ure it out for OSX. I searched and search to final­ly get this arti­cle from macosx­hints, Avoid Cre­at­ing PPTP Default Routes. The hints at the very bot­tom of the com­ments helped some­what, but did­n’t get me to view my inter­nal IPs—which was the reverse of the orig­i­nal prob­lem. Luck­i­ly, with a lit­tle bit more search, I land­ed on this arti­cle page by Chris­t­ian Stock­er on Chang­ing default routes on OSX on VPN. Though it was the same as the pre­vi­ous page from macosx­hints, I saw this short and sweet reply which hap­pen to have fixed every­thing:

lon­nie @ 22.08.2006 19:22 CEST
Inter­net Con­nect 1.4.2 has

Con­nect Menu -> Options…

|X| Send all traf­fic over VPN con­nec­tion

Uncheck­ing should do the same.

I hope this arti­cle could be of help, and save those who are look­ing for the same solu­tion san­i­ty and time.