XML Capabilities in the core.

[stopsatgreen]

I've changed that line, but it still doesn't work for me

Can I just check I'm doing this right:

1. Download .xml file from Forge
2. In Extensions > Modules, browse to the .xml file on my PC
3. Check 'Automatically Install...'
4. Submit

Then it should show up in the Modules list, right?

[calguy1000]

I re-installed 0.12b1 from svn entirely today.

then used the listmodules.php to install the banners module via xml (Banners-2.0.7.xml) and had no difficulty.  Well, except the auto-install thing didn't do as it was supposed to. but Banners did show up in the list.

[stopsatgreen]

Downloaded the latest version from the Trunk, installed, cleared cache, tried a different XML file, tried everything I can think of... no luck. Maybe I just have to wait for the full release

[calguy1000]

Just tried it again, like twice, worked fine.

However.  I'm not running a default install of php.  I've increased my memory limit (though it shouldn't make much difference, as the xml files are small).

I did take out the "automatic install" checkbox though.

[stopsatgreen]

Just installed the new Beta, same problem

It doesn't use PHP5, does it? My host only supports PHP4.

If not, I'm TOTALLY stuck

[calguy1000]

No, it doesn't use PHP5.  I'm on an FC1 machine with PHP 4

I tested the thing again in 0.12beta2 to see if there was a problem with error messages not being displayed, and they displayed fine.

So I'm thinking it's either a php memory or a permissions issue somewhere.  Does your web server output any error messages in the logs that may give us a hint?

[stopsatgreen]

I took a look in the error log and there's no mention. Would there be a PHP/MySQL-specific error log somewhere? How could I find it?

Failing that, could it be a problem with permissions?

[badhoy]

The upload xml doesn't work for me either using .12b2 on a clean install.

PHP = 4.4.0, Apache 2.0 handler
Mysql = 4.0.25
Apache = 2.0.54
mod_perl/1.99_09
Perl/v5.8.0
mod_ssl/2.0.54
OpenSSL/0.9.7d DAV/2

[calguy1000]

hmm, everybody, check your web server acces, and error logs.  I don't see the same problem here.

I've tested changing all the permissions to read-only on my server, and improting an xml module file, and got an appropriate error message.  So I'm not sure what's happening.  I would however like some more information from error logs, etc.

thanks.

[badhoy]

hmm, everybody, check your web server acces, and error logs.  I don't see the same problem here.

I've tested changing all the permissions to read-only on my server, and improting an xml module file, and got an appropriate error message.  So I'm not sure what's happening.  I would however like some more information from error logs, etc.

thanks.

I'm on a shared hosting platform so can't see any logs but access logs.  Just to make sure, I am going to do another clean install on a different server and test again.  I did chmod 777 my modules directory and the module uploaded still doesn't show up.

[badhoy]

I just an entirely clean install and tried to upload the 'uploads' module and it didn't work.  No error messages or any indication that it did or did not work.

[badhoy]

Now that 0.12 is out and I've installed it, I am back to this issue.  The XML upload for modules still does not work for me.  I got access to the my web server log files and see no errors.

I did find out that fopen is restricted to only load files locally on the server.  Could this be causing a problem?

[calguy1000]

This could be it, but doubtful. We do an upload of the file first (we don't fopen the file in a remote location). 

[calguy1000]

I did notice today, that there were some problems with the XML stuff.

It does not appear to be directly related to the CMS code though, more related to the uploads already on the forge (most of them mine). 

I advise everybody, when downloading XML modules, to open them in a text editor or take a look at the top 2 lines with "head"  You should see the following:

Code: Select all

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE module [

If you don't then that means that there is a problem with the file that has been uploaded, either with the file itself, or something to do with the forge, I haven't sorted out exactly what's happening yet.  Either way don't use it, and resort to the old .tar.gz or .zip method of doing things.