Hi,

I'm facing a strage problem after migrating from D6 to D7:

- If I activate some modules (example: CKEditor, ) and configure it for HTML text it doesn't work.
- If I clear the cache, it works...
- ... but it stops working after a few minutes, reverting back to the previous state.

The same happens for the Statuses module, Heartbeat, etc. Heartbeat, for example, will create entries in the DB for the new nodes after cleaning the cache. However, a few minutes later, and it'll revert back (no logs at all). The same for Google Analytics, without sending information after the first minutes

This is happening even with the Admin user.

I'm completely lost. Any idea of what might be wrong?

Thank you,
Juan

Comments

juan.bangkok’s picture

juan.bangkok CreditAttribution: juan.bangkok commented
Issue summary: View changes

Added some extra info

juan.bangkok’s picture

juan.bangkok CreditAttribution: juan.bangkok commented

As extra information, the "Cache blocks" checkbox is disabled, stating that "Block caching is inactive because you have enabled modules defining content access restrictions."

juan.bangkok’s picture

juan.bangkok CreditAttribution: juan.bangkok commented

Further info: I've been manually deleting the cache tables one by one in the database.

Deleting the table cache_bootstrap does the trick: all the new modules mentioned above work again... for a few minutes (I guess until the cache works again)

juan.bangkok’s picture

juan.bangkok CreditAttribution: juan.bangkok commented

Hmm, if is there a SOS, this is it. I'm really lost here.

Let's put it this way: I'm not a Drupal developer -this is just for a non-profit site and I don't need too many fancy things- but of course I'm willing to learn how the bootstrap cache code works and to review it to find out what's going on

Could you provide some files / methods to start with? That'd be just amazing.

Best regards,
Juan

juan.bangkok’s picture

juan.bangkok CreditAttribution: juan.bangkok commented
Issue summary: View changes

Added more information

jp.stacey’s picture

jp.stacey CreditAttribution: jp.stacey commented
Issue summary: View changes

This bug is probably unsolveable as it currently stands, as it's so hard to reproduce and hard to know if anyone has reproduced it. Here are some things that could be improved:

  • Use the Issue Summary template to make the problem clearer. Don't worry if you can't fill out everything.
  • Provide clear steps to repeat, including the full list of modules to be installed before D6, and the modules that are re-installed in D7 for the issue to occur.
  • Maybe attempt an automated upgrade with drush site-upgrade and see if it has any more success, or if it provides you with some feedback you can use.
  • Confirm that e.g. you've done all schema updates following the upgrade; you've no errors on the site's report summary page; ensure you've e.g. migrated all your CCK content to field API; finally, install schema and ensure that your database is up to date with no extra or missing tables.
  • Provide clearer information of exactly what is going wrong e.g. "it doesn't work" - what does that mean? CKEditor doesn't appear, leaving a blank text area? No text area appears at all? The site whitescreens, or shows a fatal PHP error? The computer catches fire? Similarly "it'll revert back" - do you mean Heartbeat disables itself? or that it just stops making entries in the database? Or that the data base table(s) "revert back" i.e. all the entries disappear? What entries, and in what table?

Because of its age I think this issue should be closed if no further information is available. It's quite likely after 15 months that the OP has moved on, or their project requirements have changed.

matysek145’s picture

matysek145 CreditAttribution: matysek145 commented

I had similar problem while taking a part in developing some project. In my case the version of jquery in the jquery update module was reverting to the version of jquery coming with drupal, some time after clearing the cache.

It turned out that there were two unsynchronised instances of drupal, connected to the same database. In one, jquery update module's files existed, in the other they did not. But the module was 'installed' in the database. When someone connected through domain (let's call it example1.com) linked to instance WITH the files, everything worked perfect, but once there was a connection through the domain (example2.com) linked to directory WITHOUT jquery_module files, drupal couldn't find the files despite of the configuration in database, so it set jquery for 1.4 version...

I hope it may be useful for someone :)

Version: 7.14 » 7.x-dev

Core issues are now filed against the dev versions where changes will be made. Document the specific release you are using in your issue comment. More information about choosing a version.