Hi,

Thanks for your work on contributing this backport. I'm just wondering if you know whether this might conflict/work with Pressflow?

Thanks,

Thomas

Comments

pribeh’s picture

So I've tried the following, having put project/apc and project/cache_backport into the modules directory of a pressflow site:

$conf['cache_inc'] = 'sites/all/modules/cache_backport/cache.inc';

$conf['cache_backends'][] = 'sites/all/modules/cache/apc/drupal_apc_cache.inc';

$conf['cache_class_cache_menu'] = 'DrupalAPCCache';

And I get WSOD. I'm trying to see if I can do some bug testing but my skills are limited in this regard. Perhaps I'm just barking up the wrong tree here and the cache tech in pressflow is incompatible with drupal 7 cache. Let me know what you think.

Thanks

pounard’s picture

I'm really interested about this issue, could you please give me what your PHP error log tell you when you get the WSOD ? I'll try installing a pressflow as soon as I have time to do it, meanwhile I'll need your log to ensure this is not environment specific!

Thanks for reporting anyway, please give me all the details you can so I can fix it.

rjbrown99’s picture

I haven't tested for more than 10 minutes, but I have a bit of feedback.

- This module can be enabled on Pressflow without blowing things up. Just enable it normally.

- It also did not blow up when enabling the base include via settings.php:

$conf['cache_inc'] = 'sites/all/modules/cache_backport/cache.inc';

- After the above, run 'drush cache-clear all' and that's where it goes boom. In my case, it's dumping arrays to the screen. The arrays include module_list, drupal_get_filename, sess_write, and sess_write. They also include the SQL query in the array. Refreshing keeps showing more SQL queries, where the sess_write is changing from UPDATE to INSERT INTO. Weirdo.

I don't have a lot of time to test, so that's all for now. But I would say at least for the moment it probably isn't going to work without a few bug fixes. All of the above is before I even got to APC.

pounard’s picture

Thanks for reporting, I'll test it.

pounard’s picture

For your information, latest release fixed a real bug (my fault!). Could you please test it again and tell me if this still happen?

For fixing the bug you'll need to manually empty every database cache table using an SQL client once you upgraded the files.

pounard’s picture

Status: Active » Fixed

Still no answer, guessing that it works, probably. Re-open it if you still have problems.

rjbrown99’s picture

I don't have time to test it at the moment so at least for me I can't state either way if it's working or not.

pounard’s picture

Thanks for answering. Don't hesitate to re-open if one day you test it again.

EDIT: Don't forget that PressFlow mess badly with core, so doing a module such as low-level as this one could clearly conflict with it. If anyone find an easy-to-fix issue, I'd be pleased to do it, but if someone finds out a bad by design issue related to PressFlow core alterations, I probably won't fix it.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.