Closed (cannot reproduce)
Project:
Content Construction Kit (CCK)
Version:
6.x-2.x-dev
Component:
content_copy.module
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
9 Feb 2009 at 20:52 UTC
Updated:
21 Sep 2012 at 15:02 UTC
Comments
Comment #1
kenorb commented_POST after submit:
form_state after processing function content_copy_export_form_submit($form, &$form_state):
It looks like it's still step 1?
Comment #2
kenorb commentedTemporary solution for me
to change this (in content_copy.module file):
to that one:
But the problem is that it's exporting all fields without asking (for me it's ok).
Remove the last condition.
For me it should be something like !empty($exportable_fields), but even this one doesn't work.
I think there is some problem, because $exportable_fields contain the array with fields even the user haven't select the field yet, weird.
Result of following code:
P.S. I couldn't reproduce on fresh Drupal.
Comment #3
damienmckennaI've started running into this issue too.. it worked fine for a while and now is doing the endless loop mentioned above.
In order to try to work out what's going on, I added the following after the following after the include_once() lines of content_copy_export_form():
First run through:
The list of content types are now listed.
After submitting the form it prints:
This prints a list of custom fields for this content type.
Submitting the above results in the following:
I'll see if I can dig up anything else.
Comment #4
damienmckennaDigging around some more, I've noticed that the second call to content_copy_export_form() happens after there's a call to drupal_rebuild_form().. why would it need to do that?
Comment #5
kenorb commentedI've found the problem.
It's because of not fully working cache.
All Drupal forms and states are kept in cache table, even cache is disabled, Drupal still wanted to load them from cache (even form was not correct).
Before I'd to disable cache_menu and cache_form caching manually, because packets were too big (and I couldn't change the limit) using instruction here:
#321154: can I disable cache_menu? how?
That cause the problems and Drupal was trying to rebuild it twice.
Description of problem here as well: http://drupal.org/node/93779#comment-1254794
So I've installed #361967: Increase MAX_JOIN_SIZE and MAX_ALLOWED_PACKET settings in system.install
and http://drupal.org/project/fastpath_fscache
for 6.x
And now it's working fine.
Thanks for your help.
Comment #6
kenorb commentedComment #7
damienmckennakenorb: the db changes did not make any difference for my setup, so I definitely would not mark this as being resolved.
Comment #8
kenorb commentedBasically it's Drupal core issue, because I've disabled cache_form caching (because of mysql errors) and Drupal tried to take this form via:
without checking if state of this form was kept in cache or not and that's why $step couldn't change to 3.
It's not related to CCK, but when disabling form cache, Drupal freaking out causing different very weird workflows for some modules.
Comment #9
damienmckennaAfter doing a reinstall and updating all modules to the latest revisions, this is still a problem.
Comment #10
kenorb commentedDamienMcKenna: so you saying that you have the same problem?
Comment #11
damienmckennaYes. D6.10, the problem persists with both the most recent stable release of CCK and the latest dev release. I'll see if I can do some more testing to see if maybe a module is breaking something..
Comment #12
kenorb commentedI thought it was caused by my cache (because in this time everything wasn't work for me), but maybe there is some other problem.
But when I've check that recently, it suppose to work.
Do you using some external cache? Did you tried to disable it?
Comment #13
damienmckennaOk.. I'm starting to wonder if a bug gets its way into the system and causes this. I rebuilt my site entirely from scratch using install profiles, added back in all the same fields using the helper functions from install_profile_api, and now I can export the content types again. Go figure.
Comment #14
damienmckennaOf course then I do another deployment and it stops working. Go figure.
Comment #15
kenorb commentedCan you check if you don't have any errors in watchdog like too big cache_form packets?
Did you try to disable the cache?
Because I'm sure that it's related to caching forms and basically Drupal can't get your form from cache_form table.
Comment #16
damienmckennaThere are no errors in dblog at all, the only messages are regarding actions and widgets that were added during the install process.
Comment #17
damienmckennaAfter a few clean re-installs from an install profile and some module updates, right now I have it half-working - it outputs the basic details and the groups but not the individual fields...
Comment #18
kenorb commentedComment #19
damienmckennaEveryone should be using Features anyway ;)