Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

#2269575 - PathHasAlias condition implementation. #31

Closed
wants to merge 1 commit into from

Conversation

paranojik
Copy link
Contributor

Another take at implementing the PathHasAlias condition. Previously opened as #7.


namespace Drupal\rules\Plugin\Condition;


Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please remove the extra line break.

@paranojik
Copy link
Contributor Author

This is now almost completely copied from PathAliasExists condition. Still don't know why tests are failing...

@fubhy
Copy link
Collaborator

fubhy commented Jun 5, 2014

I can a look if you don't mind.

@paranojik
Copy link
Contributor Author

Sure. Go ahead.

2014-06-05 10:08 GMT+02:00 fubhy notifications@github.com:

I can a look if you don't mind.


Reply to this email directly or view it on GitHub
#31 (comment).

@fubhy
Copy link
Collaborator

fubhy commented Jun 5, 2014

Continued in #35

The reason for the failures here: There is something called AliasWhitelist in Drupal core that ensures that you cannot create/lookup path aliases for paths that don't actually exist. Hence you need to use a path like 'user' (which exists once you enable the system module which inheretly enables the user module).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants