[SOLVED] Mambo + G2/Remote = err "no protocol implement
speleo
Joined: 2005-06-14
Posts: 13 |
Posted: Thu, 2005-06-30 11:41 |
Hi, Got a problem with Gallery Remote when Gallery2 is embedded in Mambo 4.5.3.2. When running the full screen Java applet I get the following error. Quote:
Gallery Remote can find on protocol implementation at the URL http://www.mysite.co.uk/. Check with a web browser that http://www.mysite.co.uk/ is a valid Gallery URL. If I access the Gallery via a direct URL (ie not via mambo) it works fine, so I'm assuming there is nothing wrong with the Gallery2 install or the Remote applet. Background info Quote:
Gallery version = 2.0-beta-3 core 0.9.17 Mambo Gallery2 integration via com_gallery2-v2.0.5 config as below: Quote:
Full Path to Gallery G2: /home/hunters/public_html/gallery2/ I've also noticed that when I access the gallery embedded in Mambo that the url gains an extra slash after the domain. For example http://www.batproducts.co.uk/index.php?option=com_frontpage&Itemid=1 Clearly I've looked around for a solution to this but so far have been stumped. Any ideas? PS. Gallery 2 is the mutts nuts. Thanks to all those who have got it here. |
|
Posts: 32509
upgrade your G2 to the current nightly snapshot (http://galleryupdates.jpmullan.com).
and make sure in config.php mode.embed.only is set to false.
Posts: 13
Hmm...OK will take some time as I've no shell access. Do I simply unzip the snapshot locally and FTP it over the top of the existing install or is there an upgrade routine?
Thanks for the quick response!!!
Posts: 13
Quick complete noob question.
Is there a simple PHP code snippet that I can run on the server so that I can upload a tarball or zip file and uncompress it on the host? This would be far far faster than the painful process of using FTP to push across a large filebase.
Posts: 32509
see:
http://codex.gallery2.org/index.php/Gallery2:faq#How_to_upgrade_Gallery2.3F
Posts: 13
Valiant,
Cheers my man! It's the age old support thing of patching youself to the latest code base before hassling the support channels (if you've still got the problem).
All sorted now. Many thanks!