Mt Reblog Plugin

**Julius** · September 1, 2005

I have a working install of Movable Type on my account, runs very well. However, I've recentyl installed the reBlog plugin, and now I'm getting some grief. The blog itself works fine, but when I try to import from an RSS feed, I get the following error:

>Going to import entries from http://www.[mydomain].com/mt/[feed]/out/rss.php?v=2

Content-Type: text/html Got an error:

Can't locate object method "new" via package "XML::Parser" (perhaps you forgot to load "XML::Parser"?) at /home/[acct]/public_html/mt/extlib/XML/XPath/XMLParser.pm line 54.

Spoke with the tech support folks, and they said "I have reinstalled the perl module XML::Parser to the server and it is accessible to your account too" and then forwarded me here to ask for additional help if I still have the same error . . . which I am.

So . . . help?

**TCH-Bruce** · September 1, 2005

Welcome to the forums Julius

Sorry nobody has responded yet. But hang in there, we have many MT users in this forum and they may have a solution for you.

I went to their forums and I assume this is your thread. You don't have command line access but if the techs say it's installed I would assume that it is. You can go into your cPanel and see which Perl modules are installed. Under General Server Settings select the "Click to View" link next to Installed Perl modules.

**TCH-Bruce** · September 1, 2005

Also, I did some searching in the forum and found a reply in this thread by TCH-Rick that says.

As I mentioned in the Help Desk ticket, a big advantage to installing the module into your site is that it will be avalilable should anything change. Most Perl modules can be installed locally either to the directory that the script is in or to a directory specified as an includes directory.

We run into a number of issues when a server is moved, for example, when scripts stop working. In most cases it is because a module was added that is not a part of the default install and so it is missing when the server is moved. Installing modules locally will mean they are moved when the account is moved.

So you could try installing teh module in your plugins directory yourself.

**Julius** · September 1, 2005

Also, I did some searching in the forum and found a reply in this thread by TCH-Rick that says.
So you could try installing teh module in your plugins directory yourself.

<{POST_SNAPBACK}>

Thanks, Bruce. TCH-Dave is on IM with me, though, and he said that XML::Parser cant be installed locally just by uploading it to the server. And yes, that is my thread.

Edited September 1, 2005 by Julius

**Julius** · September 1, 2005

FIXED! Turns out I put a file called parser.pm in a folder that was confusing the plugin . . . because the contents of the file weren't an XML parser.

**TweezerMan** · September 2, 2005

Thanks, Bruce. TCH-Dave is on IM with me, though, and he said that XML::Parser cant be installed locally just by uploading it to the server. And yes, that is my thread.

<{POST_SNAPBACK}>

Many perl modules can be installed locally by uploading a copy to your account where a script can find it, but XML::Parser isn't one of them. XML::Parser requires compilation on the server, which in turn requires shell + root access. The Help Desk has to install XML::Parser for you, if it's not already installed on the server.

FIXED! Turns out I put a file called parser.pm in a folder that was confusing the plugin . . . because the contents of the file weren't an XML parser.

<{POST_SNAPBACK}>

In trying to fix another error, Julius copied a .pm file from an MT plugin and named it 'Parser.pm', and saved it to the plugin's lib/XML directory. When Julius tried to import an RSS feed with the reBlog plugin, perl started looking for XML::Parser, found the copied file, and thought it had the real XML::Parser module. Removing the copied file allowed perl to find the real XML::Parser module on the server, and the error was resolved. :wacko: