I have no personal experience, but previous threads have attributed this to incorrectly structured code in one of the twitter integration addons. If you search back through the forums over the last few weeks, you should find the thread with various work-arrounds. Or look through the support for whatever twitter addons you have installed, I expect the addon's support will be full of posts about this.

Hi John,

Many thanks for your response - thats really helpful.

The trouble is, I can't even log into the website now because of this error....so I am not really sure how to proceed.

Would logging into the FTP site and deleting the Twitter (we do use a Twitter feed block) block which seems to be causing the problem do the trick? At least so I can get back onto the site to diagnose and fix?

Cheers

J

Try copying json.php from

/concrete/core/
to
/concrete/models/

Then delete everything in
/files/cache/

Hiya,

OK tried that - no success and getting the same error messages.

I really don't want to have to wipe the website and start again if I can avoid it!

Any help would be appreciated :)

Cheers

J

Make sure all your packages are updated for 5.6. It could be a block other than tweet thats causing your issues.

Tweetcrete has been updated for version 5.6 to fix it's bad code.

I would try downloading the most recent archive of Tweetecrete from the C5 marketplace:

http://www.concrete5.org/marketplace/addons/tweetcrete/...

and unzip it to your local computer. Then upload the resulting 'jereme_tweetcrete' folder to your 'root/packages' folder so it ends up as 'root/packages/jereme_tweetcrete'

If this allows you back in, I would go to 'Dashboard->Extend Concrete5' and click the 'Edit' button next to Tweetcrete. Then Under 'Block Types', click on 'Tweetcrete', then 'Refresh'.

Good luck.

OK tried that - issue still persisting - attached screenshot!

Aha! We are backup! Huzah!

However, I now seem to have some random advert at the bottom of our page - any thoughts!?

Check your theme files?

@Phallanx, I'm confused. I don't do automatic updates so I never have anything in my 'root/updates' folder. Are you saying the updated Tweetcrete folder needs to go under 'root/updates' or are you saying your solution of copying the json.php file should have been done in their 'root/updates' folder. The 'packages' folder always stays in 'root/packages' correct? Or am I out to lunch.

No. The OP has upgraded so his core files are in updates

I'm still confused. I suggested he upload the latest Tweetcrete package and he said "Ok tried that - issue still persisting". I read that to mean he tried installing the new Tweetcrete package and it didn't make any difference. If he now has the updated Tweetcrete installed then copying the json.php from 'concrete/helpers' to 'concrete/models' (in the updates folder) isn't necessary because the new Tweetcrete code does not try to call it from the wrong place which was the original problem.

@oc861: Help me understand the situation. Did you successfully manually update your Tweetcrete package to the latest version?

While I'm really glad it's working, this problem is affecting a lot of people who upgrade to 5.6 and I think the best solution is to recommend that users upgrade to a compatible version of a package rather than dig into the core files. IMHO, I think in this case something else must have happened between the time he installed the new version of Tweetcrete and the time it started working again such as clearing the cache or turning off full page caching so that the new Tweetcrete package gets used.

@mhawke
Well. He tried that and it didn't work.

Once he gets into the Admin, if he's not manually installed the addon correctly, it will allow him to auto update the addon and do it properly. The only artifact after that point is a "spare", unused json file (if it really has been fixed) which will become obsolete after the next Concrete5 upgrade along with all the files contained in the update directory for that version.

The "best solution" is to get the admin panel working so that you can auto-update. No. forget that. The "best solution" is that the core is changed so misbehaving addons cannot break your website and are ignored (perhaps with a cross through them in the addons list).

I whole-heartedly agree that mis-behaving packages should not destroy your site so that you have to come on these forums for days on end to get it working again. C5 is being marketed as an easy CMS but it's not so easy if things break. 'Failing gracefully' is not one of it's features.

Thanks for the explanation.

I too was thinking that better protection for the core against misbehaving packages (and themes), or at least a way to simply disable (rather than uninstall) a package, without a working site or dashboard, would have saved a lot of users grief for the 5.6 upgrade. So +1 for some core changes to facilitate this.