Thread

Well, the location of the problem is fairly evident from the template debugger:

(0.193627) -> Class Called: Allowphp
(60.310421) -> Method Called: allowphp

You jump from .19 seconds to 60 seconds there.  Is there a plugin or similar in your template code that calls something named similar to allow php?

Ah!  Now this rings a bell.

Way back when, I wanted to be able to embed a little php snippet for a mini music player in some blog entries… specifically those in the music category.

Not sure why this started going haywire suddenly.  Or maybe it’s just something to do with my (somewhat) new host [sigh].  Anyway, I’m going to try removing this from my template:

[quote{exp:allowphp}
{phpthingy}
{/exp:allowphp}

And I’ll let you know what happens… 😊

Indeed, that did the trick!

And to further clarify… I created an extra field in the publish section of EE called “phpthingy.”  This is where, for relevant music entries, I included a snippet of php code to embed a music player.

But now with services like lala and grooveshark and so on, this becomes less necessary, and, in fact, less desirable (I’d rather use third parties’ bandwidth than my own, especially since via my hosting plan, I pay per megabyte served).  For the moment, it means that now many of my music entries in my blog will be broken [sigh]... but once I get off my duff and update them with music clips from other sites, things will be hunky dory.

Thanks again to all of you for so helpfully and quickly troubleshooting this situation! 😊

Adam, for your music player - this will take some backwards modifying. But what I’d recommend is putting just the URL to your file and putting the PHP code/player in your template, calling that custom field where the URL is required.

I’m glad we were able to help you figure out where the issue was, if anything else comes up please don’t hesitate to post again.