Closed (fixed)
Project:
Node export
Version:
7.x-3.x-dev
Component:
Node export
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 Jul 2012 at 12:57 UTC
Updated:
11 Dec 2012 at 17:43 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
danielb commentedCan you please post a sample node export that causes this problem? It would be best to try and figure out if it's a specific node or set of nodes causing this?
Comment #2
pijus commentedThank you.
I've attached the content type screenshot and node exported file.
Looking for your kind help.
Comment #3
danielb commentedCan you find out what PHP versions you have on the two sites?
This export looks a bit different to the exports I expect.
Are you using the same version of Node Export on both sites?
Have you tried exporting without drush?
Comment #4
danielb commentedThe code in drupal_var_export() explicitly prevents the __set_state() magic method, yet I'm seeing it in your code.
Is there any way your nodes might not be stdClass ?
Comment #5
pijus commentedI'm using the PHP 5.3.5 version and the both the sites in the same local environment. Also I'm using same node_export module.
Yes, I've tried without drush also. I've tried to import a single node from admin UI. I'm getting the same error in all the cases.
I'm not sure how the nodes will be without stdClass.
If you have any test export then please provide me.
Comment #6
danielb commentedEnsure you are using the latest version of Node export. If this problem continues, try exporting to a format other than 'Drupal'. It seems to be producing unusable exports in your case, but I cannot reproduce it.
Comment #7
danielb commentedI hope the idea of using a format other than 'Drupal' is suitable for you.
I can't reproduce this problem, I have no idea how the __set_state stuff got into your export when the code explicitly prevents that from happening.
UNLESS you are using an old version of something (the module, or drupal) which might explain it.
Comment #8
pijus commentedWhat do you mean by other format than Drupal? If you have any example file and module (that worked for you) then please provide me.
I've used the latest version of the node export module. I will try with the other one.
Also it will be grateful if you plz suggest the configuration (PHP and the Drupal) to make it work.
Comment #9
pijus commentedWhat do you mean by other format than Drupal? If you have any example file and module (that worked for you) then please provide me.
I've used the latest version of the node export module. I will try with the other one.
Also it will be grateful if you plz suggest the configuration (PHP and the Drupal) to make it work.
Comment #10
danielb commentedhuh?
This module comes with various formats for exports, e.g. Drupal, XML, DSV, and Json
If you don't know of this, then I'm not sure I want to accept bug reports from you.
Comment #11
pijus commentedThanks Daniel. The JSOn, XML and DSV is working. I've tried with one node and it's working.
Comment #12
christenson commentedI had this same issue on a local environment, using the latest version of Node Export and Features. I changed the export format to JSON and it worked as expected.
Comment #13
revnoah commentedI can also confirm that changing the default format to JSON works, and that this problem still exists. It would be simplest to just change the module's default format to JSON if var_export is unreliable.