As an early adopter, I tried to disable all blocks and to make my page completly with panels everywhere.

This works quite well. Only the URL filtering is quite difficult.

Why not using the same rules / posibilities as in blocks? I think the URL filter of blocks is well known and easy to handle.

And not everyone is able to write complex regex expressions.

CommentFileSizeAuthor
#3 path_visibility.patch2.32 KBcatch
#2 rule1.gif1.38 KBayalon
#2 rule2.gif9.64 KBayalon
#2 path.inc_.txt2.94 KBayalon

Comments

ayalon’s picture

ayalon commented

I think I found the function in the core:

path.inc:

drupal_match_path()

ayalon’s picture

ayalon commented
Title: Add better url filtering possibilities » Add better url filtering possibilities: new access control path.inc (patch included)
Category: feature » task
StatusFileSize
new path.inc_.txt2.94 KB
new rule2.gif9.64 KB
new rule1.gif1.38 KB

Because I wanted to completly go away from the drupal block system, I searched for an easy way to handle the panel visibility based on the path as I am used in the block settings.

inspired by merlinofchaos string access filter, I wrote a new access plugin for ctools, that is able to filter by path in the same way as the block system do.

Attached you will find a screenshot and the path.inc which has to be copied to ctools/plugins/access.

catch’s picture

catch
he/him
Primary language English
commented
Title: Add better url filtering possibilities: new access control path.inc (patch included) » Path visibility access plugin
Project: Panels Everywhere » Chaos Tool Suite (ctools)
Status: Active » Needs review
StatusFileSize
new path_visibility.patch2.32 KB

Just saw this as I was about to post a similar patch for a path visibility access plugin, doh. Here it is anyway. Moving to correct project.

ayalon’s picture

ayalon commented

:-) Almost identical code..

The master may choose and hopefully add one of this to the next release...

catch’s picture

catch
he/him
Primary language English
commented

Just a note I looked at the string match access plugin and context in panels_everywhere but wanted something that has the same basic UI as block module (for administrators who are used to that), and also for any arbitrary panel. There didn't see an obvious way to bend the string context / access to do that, hence the new plugin.

merlinofchaos’s picture

merlinofchaos commented

Hmm. I am unsure about this. I'd kind of like this to work on string contexts, rather than forcing to $_GET['q']. Of course, that means we need to make the URL context generally available, not just on panels everywhere, I suppose.

catch’s picture

catch
he/him
Primary language English
commented

I looked at the string contexts, but couldn't see a way to get that to work with both system paths and path aliases.

merlinofchaos’s picture

merlinofchaos commented
Status: Needs review » Fixed

Upgraded somewhat and committed. Thanks!

Status: Fixed » Closed (fixed)

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