Support

UNiTE, Remote CLI, eXtract Wizard

#3512 XML-RPC Error

Posted in ‘UNiTE and Remote CLI’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

PHP version
n/a
Tool
UNiTE
Tool version
n/a

Latest post by nicholas on Tuesday, 07 July 2009 00:59 CDT

user6269
I've just installed JoomlaPack 2.2.1 free on my site and took a successful backup (initiated from the backend). This worked very well and without problems.

I'm now trying to get Joomlapack remote working, but with no success whatsoever.

Firstly, I have enabled Webservices from the global configuration and installed the plug-in plg-jpremote-2009.3 on my site. It is enabled from extension/plugin manager.

When I set up the connection from JPremote main screen I get a message indicating that JPremote can not log in to the server.

Following some articles on the forum, I used the expert to set up my connection. I now get XML-RPC layer error: invalid payload received xml-rpc server.

When I look at the log for the backup I see errors relating to undefined constant JPSPECIALEDITION. (I have attached the JPREMOTE Log file below).

I'm not sure whether it is relevant or not, but I also get the following messages in the backend of my Joomla site when I go into Component/Joomlapack:

Notice: Trying to get property of non-object in /var/www/vhosts/nissan4x4vic.com.au/httpdocs/administrator/components/com_joomlapack/models/update.php on line 240

Notice: Undefined variable: reldate in /var/www/vhosts/nissan4x4vic.com.au/httpdocs/administrator/components/com_joomlapack/models/update.php on line 249

Notice: Trying to get property of non-object in /var/www/vhosts/nissan4x4vic.com.au/httpdocs/administrator/components/com_joomlapack/models/update.php on line 252

Notice: Trying to get property of non-object in /var/www/vhosts/nissan4x4vic.com.au/httpdocs/administrator/components/com_joomlapack/models/update.php on line 253

Notice: Trying to get property of non-object in /var/www/vhosts/nissan4x4vic.com.au/httpdocs/administrator/components/com_joomlapack/models/update.php on line 255


I am using Joomla 1.5.11, PHP 5.2.9

Thanks,

Pete[attachment=0:2lq3lvxl]

dlb
Pete,

The "non object" errors are benign, just annoying. :) D

Dale


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user6269
Hi Dale,

Thanks for the reply. I upgraded to JP Special. Unfortunately, I have exactly the same error. Log from JPremote attached below.

Thanks,
Pete

dlb
I should just quit looking at these Remote errors, I don't even remember the last one I actually solved. I should just sent them to Nicholas. :(

The error is one I haven't seen before, I'll flag it for Nicholas. :)

Dale


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
The two errors are related, but do not make sense to me. Please look for the file administrator/components/com_joomlapack/version.php. It must exist (it's part of our distribution) and its contents must be (for the 2.2.1 Special Edition):
[code]

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user6269
Hi Nicholas,

Thanks for your reply.

I think I know what's going on now....

My administrator directory is protected with an .htaccess such that a special password is required to be able to get to the back end.

Would it be correct to assume that this is the problem? If so, do you have any suggestions for me as I don't really want to remove the security I've put on the administrator directory.

Thanks for your quick responses. It is much appreciated.

Regards,
Pete

user6269
Hi Nicholas,

I removed the .htaccess and .htpasswd from my administrator directly. It didn't help. After checking I found some posts that indicate that JPREMOTE doesn't need access to the back end. (I've put them back in place now).

No errors occurred when I installed either Joomlapack or the plugin.

I checked for the version.php file. It is exactly as you coded in your post above.

Pete

nicholas
Akeeba Staff
Manager
I think this is a permissions problem. For whatever reason, it seems that the version.php file is not being loaded. Can you please try to change the permissions of the entire administrator/components/com_joomlapack directory (recursively, including all contained subdirectories and files) to 0755? I think this should solve the issue.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user6269
Hi Nicholas,

I went through the entire administrator/components/com_joomlapack directory. I found that all subdirectories are set to 755 and all files are set to 644.

I haven't changed any of the files as yet (do you think this is still worth doing?).

What I did do was create a local installation using XAMPP on my local machine (Note the .htaccess and .htpasswd were in place in the administrator directory). I can connect with JPREMOTE with this successfully.

One other thing I did was to run wireshark against the initial error (from the wizard) and check what was returned when JPREMOTE says to check the username and password. It is actually the same message as appears in the log when I use the Expert mode to input username and password. ie: complaining about the constant JPSPECIALEDITION. So both errors are actually one and the same.

Do you still recommend to convert all files to 755? The other thing I might try is restore my .htaccess and .htpasswd on my local installation and see if I can recreate the error

Pete

user6269
Hi Nicholas,

In my wireshark traces, I found this response to the GET /xmlrpc/index.php:

"XML Error: Invalid document end at Line 1, column 1"

I believe that there is a problem with the version of PHP and LIBXML I have on my host.
This is reported in
http://bugs.php.net/bug.php?id=45996
http://social.microsoft.com/Forums/en-U ... ec06b142b/

Effectively, the bug appears in versions of PHP

nicholas
Akeeba Staff
Manager
Wow! This was actually a far cry from being catchable! I am stilled concerned that you are getting the notices. It really means that the version.php file is not loaded, so I think that in any case you must CHMOD all the files to 0755. FileZilla can do it automatically (hint: use the recursive option in the change permissions dialog).

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user6384
I was having the same problem ..
I fixed it ..
I will tel you what steps I took.

Using on 2 Joomla 1.5.12 sites.

On new site #1, I had loaded a new copy of com_joomlapack-2.2.1-free.zip and the remote plug-in.. Every thing worked just fine.

On old site #2, I upgraded with the same copy of com_joomlapack-2.2.1-free.zip and added the remote plug-in ... GOT THE "XML-RPC Error".

After reading some post here, I decided to try un-installing Joomplack and then re-installing com_joomlapack-2.2.1-free.zip.

Without any other changes or actions the remote program worked wonderfully.

Could be some problem in upgrading of the package.

nicholas
Akeeba Staff
Manager
Upgrade from the previous minor stable version (e.g. 2.0 to 2.1, 2.1 to 2.2 or to 2.2.1, etc) should work without a problem. Upgrades between major versions (e.g. 1.2.x to 2.x) are not possible, they cause havoc. We've only changed the major version once so far, when the changes in the component's architecture were guaranteed to break upgrades.

If you upgraded between minor releases, the most probable cause for failure is the package size. Since the Plus (formerly, Special Edition) version is very big, it is probable that Joomla! doesn't have enough time to install it and times out in the process. In this case, using the alternative installation, as described in our documentation, or installing the Core (formerly, Free Edition) is the only workaround.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!