Hi @all,

I am really stuck with a strange problem: We have two servers (one for the live site - handling the crons, one for the development environment) which connect to the SAME database. Yesterday I installed the pollfield-module on the development-server (which means that the module files are not present on the live-server, but the system-table has a record with the module installed), because the live users should not have this new field appearing already. everything worked fine and I worked with the new node form field for my content type and started theming the ouput.

But now, when I opened up the same site again, my field is gone from the node form and the "manage fields" tab, even though all database tables, references etc. are still present. So what happened? is there something like a cron that cleans up something or is it because the module is not present on the live server where the crons are run?

The same strange behaviour occured with the calender module using the date field...

I hope it is not because the module files are not present on the live server, because we cannot put them there while developing, because users would see the field while development. also: restricting access with cck field perm module will not work, as this module causes multiple errors...

I'd appreciate your help and comments on this & thanx in advance

hctom

Comments

hctom’s picture

hctom
Primary language German
commented

forgot to mention:

- pollfield version: 5.x-5.x-dev
- date: 5.x-1.5

cheers

hctom

JamesSharpe’s picture

JamesSharpe commented

I have the same issue with the date module cck field disappearing.

maximago’s picture

maximago commented

Me too!

hctom’s picture

hctom
Primary language German
commented

Has anybody of the maintainers mentioned this post? I'd really like to get an answer as I would like to use the CCK module... So can you please post any answer, so that users can see that you care about your module?

Thanx & cheers

hctom

yched’s picture

yched commented

Does this happen for *all* of your content types ? or only the ones using the incriminated poll and date fields ?

hctom’s picture

hctom
Primary language German
commented

This only happens with the content types using these CCK field-types. I got another content type using textfields from cck and they are working fine.

Cheers

hctom

yched’s picture

yched commented

Karen, if you're reading this - do you have any idea ?

yched’s picture

yched commented
Status: Active » Closed (works as designed)

Ah, very sorry, I read you initial post closer, and this _is_ most probably caused by your staging / production site setup.
I know this staging area is a bit tricky with drupal sites, but your configuration (2 different installs hitting the same db) is definitely not the right answer, and it's not something drupal can support. It is bound to cause this kind of synchronization issues.

You have to use a different db for your testing site. At best, use a multisite setup and share _some_ db tables, but the system table, for instance *cannot* be shared... I think you can find more info on multisite in the handbooks.

karens’s picture

karens commented

It's true you can't do this juggling of multiple databases, so that should be an answer to the first poster. A couple other people said 'Me, too' without providing enough info to tell much. Are they saying they too are using multiple databases? If so, you just can't do that.

This is definitely not happening in most instances, the date module, at least, is used by hundreds or thousands of sites and if this was happening other places I'd be inundated with reports like this. This is the first report like this, so I suspect something else is the problem.

CCK perms is mentioned and could be an issue since it is designed to hide fields and might be hiding things you didn't intend. If everyone reporting this is using that module, that would be the place to investigate and it would need to be reported on that issue queue. If that's not it, the people reporting this issue will have to narrow things down. Copy everything to a test installation that is not trying to share a database with anything else. Uninstall all other modules but CCK core and Date (that means no other CCK modules except those that come packaged with the Content module), clear the cache to be sure nothing is lingering there, and see if there are still problems. Without lots more info there's no way to provide any more help than that.