Suddenly received the following JSON error when creating a new entry.
Internal callback died with: Usage: JSON::XS::new(klass) at lib/MT/CMS/Entry.pm line 234.
Would appreciate some help on this, as haven't a clue why it's suddenly started now.
Version: MT 4.23
Reported on Movable Type 4.2
I would recommend you to consult Mike's advice from:
http://forums.movabletype.org/2010/06/mt-moved-to-new-server-json-error.html
If that won't work, consider taking a backup of your current mysql database and then upgrade to v4.37.
Also, if you need somebody to do the upgrade for you, I'm available for consultancy.
Kind Regards,
Mihai Bocsaru
----------------------------------
Daily Movable Type Consultant
Web Development
Movable Type Consulting
Six Apart Partner
http://www.pro-it-service.com/
----------------------------------
Movable Type Demo
http://www.movabletypedemo.org/
----------------------------------
Open Melody Demo
http://www.openmelodydemo.org/
hi thx
tried moving a fresh extlib directory but didn't work. not really looking to do an upgrade as this version is generally stable. why would this break just now?
What do you mean "moving"?
You should remove the current "extlib" folder or rename it to something like "TO_BE_DELETED".
And then to upload the "extlib" folder in ASCII mode, form the MT v4.23-en package.
Yes done that. That's what I meant.
Honestly, what is the stability of v4.37, as have had issues with MT upgrades before.
v4.37 works very well and lots of issues since v4.23 have been fixed, plus a few other features implemented.
Are you also using custom fields? There are some issues with CF data when upgrading from v4.23.
think we're ok for custom fields. backing up now for upgrade.
Alright!
Ok. Currently stuck on the "Upgrading database" starting upgrade browser screen. Hope this is nothing serious and just due to the database size. Which is 350 mb.
BTW, when copying over to mt-static, can you just copy the whole old mt-static directory over (which I did), or must you ensure that you copy the files within the directory inside the new v437 mt-static directory. i.e. are there files from the new version's mt-static that are necessary?
Ok just realised it's MT_HOME/mt-static/support. Re. last post, would it make any difference if I had copied over the all of the old mt-static directory by deleting or renaming new mt-static directory first?
ok wiped the mt-static and added a copy of the new version and copied over mt-static/support. Install worked but still issues.
1. When hovering over Dashboard/System Overview, now get a Javascript void and can't navigate to my existing sites from there. Have to go to Manage Blogs then hit the site, then open blog. Is this a known bug with v4.37?
2. Javascript void also on plugin settings in Chrome and Firefox.
3. MORE ERRORS. Not body text showing when editing entries. Just blank.
What if you send me access to your MT admin via email and I take a look for you?
I gather that you've uploaded all the MT files, excepting /mt-static/ in ASCII mode and without overwriting the previous installation files.
Thanks,
Mihai
Ok sending an email. search for "codelynx"
Got it, please I would need access, as I've mentioned to you on your other post.