Is there a version for Drupal 7 available?

Copied from comment below
Here are a couple issues that need to be worked on for a Drupal 7 version of Expire:

* Convert to use DBTNG #1333894: Convert queries to use DBTNG syntax
* Changes to VotingAPI require refactoring of VotingAPI integration #1393258: votingAPI integration in d7 version requires minor changes
* Flush CCK references - CCK in Drupal 7 does not include the old CCK nodereference and userreference modules. There is a contrib module that is attempting to port the old CCK reference idea: References. This module page also links to the likely future of references in the form of Entity Reference. For support in Expire of the reference flush feature some will need to be done to refactor to fit the changes in Drupal 7 referencing.
* Change of Path Redirect module to Redirect module. The old contrib module path_redirect has been moved to a new Drupal 7 only module called redirect. The current integration in Expire will have to be converted to use Redirect module. That being said from looking at the current path_redirect integration code I'm not sure it's even needed anymore.
* Comment and Menu modules are optional in drupal 7 I believe. Code that operates on comments or menus should be wrapped in conditionals so that undefined functions are not run.

Files: 
CommentFileSizeAuthor
#13 i1151684_13.patch3.74 KBattiks
#9 i1151684.patch3.82 KBattiks
#8 i1151684.patch1.79 KBattiks

Comments

Sub

Subscribe

subscribe

Shameless sub

Status:Active» Needs work

In a rare brave mood I just opened the 7.x branch and will start a rough initial port to D7. For starters I will try to get just a minimal drush up to test the initial D7 port of Purge.

Integration of the 7.x code of Boost that comes after will be most of the job. I'll admit not having looked at boost 7.x source since the initial ports I might be in for a few surprises or two. Cheers, patches and testing pledges are welcome ;-)

sounds good

Ok, a little status update on my porting efforts so far:
Node, comment and user hooks are working (when taxonomy is turned off, more on that later)
Both varnish and purge receive the expire urls through the hooks.
Flushing nodes, paths and urls now works through drush.
I find the taxonomy part quite challenging and haven't found a working solution yet. The D6 code already contains workarounds for CCK. D7 Taxonomy is a completely different beast then D6 since it's based on the field_api. I'm not the only one at least but no single approach stands out for this use case. See [#909968] and #959984: taxonomy_node_get_terms doesn't work with drupal 7 It comes down to a d7 version of the current expire_taxonomy_node_get_tids that works across ALL term reference fields and just just the default tags field some people have been able to dig up from the fields_api.

While porting this while creating many minor variations of the same code for all entity types I thought about moving completely to the entity level. This would be a complete rewrite and I propose we save that for an 2.x branch if we can get the rest of the code working. One might argue the current approach has some theoretical performance benefits... not sure how that would turn out in the wild.

When I started out I was just expecting a copy/past job from boost 7.x but doing the actual porting myself has been fun and has learned me a lot about Drupal 7. I'm sure some of my code could use improvement. Any help is appreciated.

Version:6.x-1.x-dev» 7.x-1.x-dev
StatusFileSize
new1.79 KB

i ran into a 2 problems while using drush xp
1/ i didn't had menu enabled, so i got an undefined error

2/ there are some db_fetch_arrays inside, patch included, but quick and dirty

StatusFileSize
new3.82 KB

new patch with some more clean up

Title:Drupal 7 portDrupal 7

Here are a couple issues that need to be worked on for a Drupal 7 version of Expire:

* Convert to use DBTNG #1333894: Convert queries to use DBTNG syntax
* Changes to VotingAPI require refactoring of VotingAPI integration #1393258: votingAPI integration in d7 version requires minor changes
* Flush CCK references - CCK in Drupal 7 does not include the old CCK nodereference and userreference modules. There is a contrib module that is attempting to port the old CCK reference idea: References. This module page also links to the likely future of references in the form of Entity Reference. For support in Expire of the reference flush feature some will need to be done to refactor to fit the changes in Drupal 7 referencing.
* Change of Path Redirect module to Redirect module. The old contrib module path_redirect has been moved to a new Drupal 7 only module called redirect. The current integration in Expire will have to be converted to use Redirect module. That being said from looking at the current path_redirect integration code I'm not sure it's even needed anymore.
* Comment and Menu modules are optional in drupal 7 I believe. Code that operates on comments or menus should be wrapped in conditionals so that undefined functions are not run.

Title:Drupal 7Drupal 7 port
Issue tags:+drupal7

Title:Drupal 7Drupal 7 port

This is an important module. In the interest of getting it stable in 7 here's a proposal;
1. We split the issues. This particular issue is only devoted to integration with core modules.
2. We start a second issue to attack the problem of integration with contrib (which should be a whole different discussion).

Better to comment out lines of code that whitescreen drupal installs, get the bloody thing working again, than to wait imo. I can write a patch for number 1 above.

StatusFileSize
new3.74 KB

I rerolled my patch from #9

Title:Drupal 7 portDrupal 7 version of Cache Expiration?

Title changed for clarity

Version:7.x-1.x-dev» 7.x-1.0-alpha1
Status:Needs work» Fixed

Closing as fixed per 7.x-1.0-alpha1 release, please file new issues separately.

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

Issue summary:View changes

Updated issue body with summary of outstanding drupal 7 issues.