Associating a new context (for a section front) with a theme

But didn't see a solution reached, so I thought I would ask again.
I've looked through the OP docs and checked context but not found anything that seems to work..

I suppose I could create a subtheme and then link that through my view. But then, I suppose, I'd be in the same situation, attempting to link the view/theme to the context,

It's great that you have webinars and all. It's nice that this is introduced at DrupalCon.

But seriously, OP users have issues every day that are never addressed
Section Front Pages, for example. This has come up over and over and over and over again. And we are getting no response from the OP maintainers.
Even when someone suggested an OP BUG prevented a solution.

http://groups.drupal.org/node/91579
http://groups.drupal.org/node/88719
http://groups.drupal.org/node/69153
http://groups.drupal.org/node/65823
http://groups.drupal.org/node/65668
http://groups.drupal.org/node/65828
http://groups.drupal.org/node/65808
http://groups.drupal.org/node/66698
http://groups.drupal.org/node/65998
http://groups.drupal.org/node/65798
http://groups.drupal.org/node/65993
http://groups.drupal.org/node/65813

Through all these, there was only one response from an OP maintainer.
"The problem is with regions. My ultimate goal is to turn the frontpage context in a section context, replacing the sitewide context."

Does this mean that contexts can not be used to create section landing pages?

@midek,

OpenPublish is an open-source project. We are trying to provide the foundation for building online news sites in Drupal that allows people to start at a higher level than with the vanilla Drupal core. It is not an out-of-the-box solution that can solve every specific need.

At the same time, we do try to help people adopt it by participating in group discussions. And we consistently release new versions of Openpublish that often address community concerns. However, it's impossible for us to answer every specific implementation question. The resources needed for that just are not available. Neither do we necessarily know a ready-to-use answer to every question off of our heads. But that's where the power of the open-source community lies and why we created this group - so we are not the only ones trying to answer the questions. If somebody else, who uses OP, has run into similar question and has found a solution to the problem, this is where they can share it with the community (and hope for the same from the community next time around).

This is how Drupal works. This is how OpenPublish works, too.

As for your specific question: I am not sure I fully understand your requirements, but from what I hear, it looks like you expect more from Context that it can really provide. The logic of serving ads should be in separate code. You may need some kind of ad-management code or you will have to write a custom Context condition, if you need custom logic. That's not necessarily a thing Context can handle out of the box.

Thank you

Well said irakli. I have been getting updates from this group for last couple of weeks and have seen people complaining about the issues in OP. I contemplated writing something, but stuck on the sidelines. just like everything else Drupal, it's community driven. Here is a post i came across the other day that might help to explain to those complaining about OP. It was originally written for module development, but it applies to distros too..

"Perhaps it's the language gap, but your posts are coming across pretty harsh. Or, maybe you're just figuring out how parts of the Drupal space actually works and you're frustrated by it. That's understandable - it's tough realizing that Drupal isn't actually run by a team of tireless developers with infinite patience and no bills to pay - and I don't mind bearing the brunt of your frustration if I can help you and other folks in your shoes come to terms with a more accurate perspective.

From a user's point of view, in the ideal world every developer would have the time and desire to regularly pummel their issue queues into submission (like some people). In the developer's world, things look a little different. Most of us have enough going on that we have to prioritize what gets done, and that depends on a huge number of factors, including but not limited to:

* Can the module / community work be integrated into client work? (i.e. killing two birds with one stone)
* What kind of time is there beyond client work (i.e. bill-paying work) is there to work on other projects?
* Out of the numerous projects that you have on your plate, which ones are the most important strategically in getting you closer to your longer-term goals?
* How many people will be affected by your work?
* Who are the people will be affected by your work?
* How educational or exciting is the work going to be?

I may be speaking just for myself, but I'm not positively influenced by how upset a single community user gets about poor support. That sort of reaction means that the user probably has some other pressures in their life impacting their overall happiness and they aren't going to get an awful lot happier through you responding to their demands. So posts like yours above beget the opposite reaction to what you were probably hoping for. I'm actually less enthusiastic about tackling the issues you mentioned, not out of spite, but just because I can't help but get a little bummed out.

Each module on Drupal.org has a backstory, and some of those stories involve a developer who actually is tireless and is doing this work only because of a pure desire to make Drupal better and push their own skills, and it's this focus that allows them to put a strong focus on supporting the module, regardless of who asks or what they're getting paid.

There are other situations where a developer creates a module because they are asked to do so for a client - as with this particular module. What I was actually asked for was a particular feature, and upon my suggestion the client generously agreed to sponsor the extra time that would be required to make the feature modular and share it on Drupal.org - i.e. they understood the value of sharing. I wouldn't have built this module without the financial support because I don't have enough use cases to justify the time required. So my motives are around making the client happy while sharing as much of the work as I can with others.

Now here's the next part of the equation, which is where you come in. You found a good use case for the module - which is great, but doesn't mean that it changes how or when I can work on it. Because the code is open source and free to use, however, you now have the ability to actually go in and fix those problems you've found, or find someone who has the skill set to do so. You're free! You're not beholden to my currently limited ability to offer support, you can actually take action and get something done. And I'd say that in contrast to what you suggested Drupal was all about, that this is a lot closer. It's people doing what they can, when they can, as they need to, and sharing it all.

Good luck!

As Irakli suggested, try using taxonomy to "categorize" your "landing pages" then use the taxonomy selection available in context to display your ads accordingly

Midek,

I think what you need/want is outlined here: http://drupalcode.org/viewvc/drupal/contributions/modules/context/contex...
It explains what a theme needs to do the trick for you.

This way, you can write your own OP subtheme to make it work I think

-Ronald