EntryContents 1.2

I finally looked at my web stats today, so I finally saw that Emmanual Frécon posted about EntryContents, including the question of whether it would work with Textile. I had written it to look directly at the entry body text, so no. It would look at the entry text before Textile processing and find no <as or anything.

But of course that's wrong, so after looking up the MT API stuff about the text formatting filters, I fixed it in 1.2. Now it will work with any and all text formatting plugins you throw at it. So if you thought EntryContents was neat but found it didn't work with Textile, it does now (as I tested on my Radio discussion group FAQ, where I've been posting with Textile--so really, really it should work).

(For other plugin developers, it's really easy: just do MT->apply_text_filters($entry->text, $entry->text_filters) instead of $entry->text.)

Emmanuel 4:43 PM 4 May 2003

Great, thanks very much for reading and taking into account my comment. As soon as I get some free time, I will probably install and start running EntryContents

tarun 11:36 PM 28 Jul 2003

One thing I've noticed since installing is that I get errors mailed from my cron rebuilt zeitgeist from this plugin. Every hour I get an email stating:

Use of implicit split to @_ is deprecated at /path-to-mt/plugins/EntryContents1.2.pl line 52. Use of implicit split to @_ is deprecated at /path-to-mt/plugins/EntryContents1.2.pl line 61.

Mark 12:14 AM 29 Jul 2003

That's weird; MT itself does that a lot. Huh. Maybe your cronned rebuild is putting perl in -w mode when MT doesn't normally do that?

AMK4 7:01 PM 29 Sep 2003

I've also commented on the implicit split error mentioned above way back when, when I first installed EntryContents. I just now got to reading Mark's reply. All of MT's main scripts put perl into -w mode, and nothing generates any errors, except EntryContents. I don't know why, but the problem's isolated to this plugin, nothing else. It'd be nice if it's taken care off, somehow, somewhere...