D7 version of Patterns

We are in the process of deciding about the future direction of patterns module. Until that is resolved we are not planning to work on D7 version. Unfortunately, that means D7 version will not happen very soon.

I'm curious what you're considering in terms of the future of the module. I've long been very enthusiastic about it, but I've never entirely been able to get it into my team's workflow.

Unfortunately there hasn't been much progress in determining the future of patterns since my last post.

I would appreciate if you could share what were the main reasons/obstacles for not being able to integrate patterns into your team's workflow.

Thanks,
Vaish

Hi,

I have made an attempt of porting Patterns to DR7. Only basic functionalities such as taxonomies, users, and users additional fields work more or less correctly, but I believe there is a good basis for further integrating other features.

Most importantly, I have restructured the code and commented it quite extensively (at least the core). I added a non-batch mode (useful for debugging), and updated all the methods .6 to its .7 counterpart.

I am part of a group of researches interested in developing new free tools for scientific online networks (see www.qlectives.eu) and we believe that the functionalities offered by Patterns are indispensable to accomplish our aims and for the future of Drupal. We are willing to take up DR7 Patterns development in liaison with the current developers and we are open to discuss with them in which direction to go in the future.

I don't know if posting here is the most orthodox way, but I wanted to signalized our interest in developing Patterns in DR7, and of course I make the last version of the code available here.

Looking forward to your comments.

Hi, @shakty - glad to see there are other people committed to the future of Patterns! I'll take a look at your port to 7 when I get a chance. Is there a public git repo of your code? I'd hate to get into passing a tarball back and forth if we can avoid it! :)

Hi, @vaish. In general, it's been the places where we've had to stop using Patterns for a configuration because of a hole in Patterns support: an existing bug that prevented a configuration (#939772: Creating multiple view displays of the same type) or a form that requires something other than a string/number as a parameter. Once we'd hit a snag that required us to do any manual configuration, the work we'd done in setting up the pattern to that point was pretty much unusable - the attraction of patterns is in writing it, running it, revising it, running it, forgetting it, not to mention keeping all the configuration in SCM instead of the database.

Hi michaek,

we don't have a public repo for now...we do have a private one, I can give you access to it of course, if you give me an email I can send you the credentials.

ps: just noted a problem with the installation of the pattern version I posted here, so better to use the repo version.

Just sent you a message through your d.o contact form.

really interested!!!

It's great to see progress on this, thanks for sharing!

I'm attaching the newest version from the repository shakty mentioned (we need to work out a common version control system, though).
It fixes an installation bug, a few porting issues, a lot of code standards related things, along with a few localization issues.

Mostly works:

• user creating

Not working:

• taxonomy – some functions changed from drupal6.x to drupal7.x
• node, updating– missing nid related warning
• editing certaing patterns through the form – form problem?

Untested

• importing
• server import, export

Also, anything not listed here is untested.

Things to be done:

• Test things out using a wide variety of patterns. It would be nice to have SimpleTests as well.
• Fix the remaining porting related issues using Coder Review
• Port the most important missing content types
• If still needed, rewrite _patterns_taxonomy_get_tree() based on the 7.x http://api.drupal.org/api/drupal/modules--taxonomy--taxonomy.module/func...
• Similarly, for drupal_process_form(), drupal_validate_form(), taxonomy_form(), _taxonomy_term_select(), menu_tree_all_data(), menu_parent_options()

Rewrite dynamic db_query calls using the Drupal 7.x database abstraction layer (http://drupal.org/developing/api/database, http://drupal.org/node/310075)

Thanks csko!

Now that we've got a 7 dev release, we can open specific tickets against it!