Class 'MarketplaceRemoteItem' not found

Permalink
Following an upgrade to 5.5 I'm getting the following error when clicking the 'Update Add-ons' button in the Add Functionality window:

PHP Fatal error: Class 'MarketplaceRemoteItem' not found in /www/test.surefyre.com/updates/concrete5.5.1/concrete/single_pages/dashboard/extend/update.php on line 43

Anyone know what's causing this ?

(Is it because the site expects to be connected to the Marketplace but isn't due to it being a copy on a test domain so the Community link is broken?)

surefyre
 
surefyre replied on at Permalink Reply
surefyre
OK, that would seem to be it, connected the test site to the Community ans it's happy.

Perhaps this should be flagged as a bug, it ought to at least say 'unable to connect to community' or something, rather than fail.
jbx replied on at Permalink Reply
jbx
Yeah, just hit the same issue - not exactly graceful :)
programmieraffe replied on at Permalink Reply
programmieraffe
I can confirm this. Has anybody filed a bug?
http://www.concrete5.org/developers/bugs/5-5-1/...
surefyre replied on at Permalink Reply
surefyre
Not filed a bug myself, wasn't sure where to do it!
andrew replied on at Permalink Reply
andrew
I don't think this is just as simple as it not working when not connected to the community. I've tried to reproduce this and cannot. I've set up a new trial from concrete5.org/about/trial/ and navigated to update with a site that's not connected and I don't get this PHP error.
programmieraffe replied on at Permalink Reply
programmieraffe
On my instance the problem was that the site was moved to another domain, so it had to be reconnected.
jbx replied on at Permalink Reply
jbx
Yep - that's right...

If you have a site on dev.jbxonline.net and connect it to the market place
and install an addon - then move it to live.jbxonline.net and try and
update that addon... The token is no longer valid and instead of handling
it gracefully, it throws up an error.

Jon



On 26 March 2012 20:17, concrete5 Community <discussions@concretecms.com>wrote:
andrew replied on at Permalink Reply
andrew
Can someone testing the 5.5.2RC1 that's in the github master branch and see if that fixes this particular issue?