search

heavenbr / wordpress-custom-content-type-manager

Automatically exported from code.google.com/p/wordpress-custom-content-type-manager
0 stars 0 forks source link

JSON Export not working properly #369

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem? (Be specific enough so that someone
else can make the plugin fail for themselves. Remember: if the issue can't
be fixed if it can't be reproduced!)
1. Make any CMS configuration (create post types...)
2. Add custom fields
3. Try to JSON export and import on the same machine or another one

What is the expected output? What do you see instead?

The JSON file is not recognized as valid. I can't deploy my settings.

Does the problem continue if you disable all other plugins? (Conflicts
between plugins are easily the #1 cause of errors, so it's important to
isolate the issue):

Yes

Please copy and paste the system information that appears in a yellow
textarea when you click on "Report a Bug" on any CCTM admin screen (this
includes the version of the
plugin, the version of PHP, the version of MySQL, a list of other active
plugins etc.):

*SYSTEM INFO* 
------------------------ 
Plugin Version: 0.9.5.11-pl
WordPress Version: 3.3.1
PHP Version: 5.3.2-1ubuntu4.9
MySQL Version: 5.1.41-3ubuntu12.9
Server OS: Linux
------------------------ 
ACTIVE PLUGINS: 
 * Breadcrumb NavXT v.4.0.2 [http://mtekk.us/code/breadcrumb-navxt/]
 * BuddyPress v.1.5.4 [http://buddypress.org]
 * Custom Login lite v.1.0.1 [http://austinpassy.com/wordpress-plugins/custom-login]
 * TinyMCE Advanced v.3.4.5.1 [http://www.laptoptips.ca/projects/tinymce-advanced/]
------------------------ 
CURRENT THEME: Bambini v.1.0 http://www.72300studio.fr/

Hello there,
First of all, many thanks for this great piece of free software...

Explanation of my problem :

I use this plugin to create a CMS architecture on a website locally hosted, and 
then I export my params using the Export tool to deploy my config on the 
production server. Nonetheless, I got on my last project a wrong JSON export : 
the file exported is not recognized as a valid JSON file when trying to import 
it on my production platform.

After a few minutes crawling in the file, I just realized that the last closing 
bracket what systematically missing, making this file totally unusable.  It is 
totally reproductible because I run in this problem each time I export now. 

I provide you a valid JSON param file (a not valid one on which I added the 
missing bracket) so that you could mount it and perhaps get a lead about this 
problem.

Let me know and thanks again,

Nicolas

Original issue reported on code.google.com by nicolas....@gmail.com on 6 Apr 2012 at 2:00

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks for the report. Looking into this.

Original comment by ever...@fireproofsocks.com on 6 Apr 2012 at 2:18

GoogleCodeExporter commented 8 years ago 
Is the bracket missing if you copy and paste the JSON from the text area and 
save it manually?  See screenshot:

https://img.skitch.com/20120424-ce39xsfysptk9rtsrtwscp9npd.jpg

Original comment by ever...@fireproofsocks.com on 24 Apr 2012 at 5:44

GoogleCodeExporter commented 8 years ago 
I could not reproduce this on the dev branch, but I believe it may have had 
something to do with the UTF8 characters.  After correcting the corrupted file, 
I was able to import it, export it, and import it again with no problems, so 
take a look at the dev branch... this will go live as 0.9.5.12 shortly.

Committed revision 536819.

Original comment by ever...@fireproofsocks.com on 26 Apr 2012 at 3:50

GoogleCodeExporter commented 8 years ago 
Thank you.

Do you mean that the Server charset in httpdconf wouldn't be in UTF8?

Thx!

Le 26 avr. 2012 à 17:51, wordpress-custom-content-type-manager@googlecode.com 
a écrit :

Original comment by nicolas....@gmail.com on 30 Apr 2012 at 4:22

GoogleCodeExporter commented 8 years ago 
That's a good question... most often it is UTF8.  When you experienced this 
problem, what was your encoding in your wp-config.php?  Was it UTF8?  Or UTF16?

Original comment by ever...@fireproofsocks.com on 30 Apr 2012 at 4:41

GoogleCodeExporter commented 8 years ago 
Hi there,
For sure it was UTF-8.

Cheers

Original comment by nicolas....@gmail.com on 30 Apr 2012 at 4:55

GoogleCodeExporter commented 8 years ago 
Ok, that's what I tested.  If you're able to test out the current dev version 
that'd be helpful, otherwise keep an eye for 0.9.5.12 -- it appears to be fixed.

Original comment by ever...@fireproofsocks.com on 30 Apr 2012 at 4:57

GoogleCodeExporter commented 8 years ago 
Many thanks for that ! I will try as soon as I can.

Cheers

Original comment by nicolas....@gmail.com on 30 Apr 2012 at 5:03

GoogleCodeExporter commented 8 years ago 
Sorry for the late answer : yes It does the same thing when I copy from the 
textbox, meaning the last bracket is missing.

Thx!

Le 24 avr. 2012 à 19:44, wordpress-custom-content-type-manager@googlecode.com 
a écrit :

Original comment by nicolas....@gmail.com on 1 May 2012 at 4:02

GoogleCodeExporter commented 8 years ago 
Is that with the dev version?  Or with the 0.9.5.11 version?

Original comment by ever...@fireproofsocks.com on 1 May 2012 at 4:09

GoogleCodeExporter commented 8 years ago 
Sorry for that : I don't know what happened, I posted this very last answer few 
days ago. I thought you got it... 

So th version related to this answer is the 0.9.5.11-pl version.

Cheers

Original comment by nicolas....@gmail.com on 1 May 2012 at 7:10